daily CVS update output

2015-10-11 Thread NetBSD source update 

Updating src tree:
P src/external/bsd/pkg_install/dist/create/pkg_create.1
P src/external/mit/lua/dist/src/lobject.c
P src/external/mit/lua/dist/src/lstrlib.c
P src/external/mit/lua/dist/src/luac.c
P src/external/mit/lua/dist/src/luaconf.h
P src/libexec/lfs_cleanerd/Makefile
P src/libexec/lfs_cleanerd/coalesce.c
P src/sbin/fsck_lfs/lfs.c
P src/sbin/newfs_lfs/make_lfs.c
P src/share/misc/acronyms
P src/share/misc/acronyms.comp
P src/sys/arch/alpha/alpha/cpu.c
P src/sys/arch/sparc/stand/ofwboot/Locore.c
P src/sys/arch/sparc/stand/ofwboot/Makefile
P src/sys/compat/linux/common/linux_mod.c
P src/sys/compat/netbsd32/netbsd32_mod.c
P src/sys/dev/dkwedge/dk.c
P src/sys/external/bsd/drm2/dist/drm/i915/i915_dma.c
P src/sys/kern/init_sysent.c
P src/sys/kern/syscalls.c
P src/sys/kern/syscalls.master
P src/sys/kern/syscalls_autoload.c
P src/sys/kern/systrace_args.c
P src/sys/rump/include/rump/rump_syscalls.h
P src/sys/rump/librump/rumpkern/rump_syscalls.c
P src/sys/sys/exec.h
P src/sys/sys/syscall.h
P src/sys/sys/syscallargs.h
P src/sys/ufs/lfs/lfs_accessors.h
P src/sys/ufs/lfs/lfs_alloc.c
P src/sys/ufs/lfs/lfs_balloc.c
P src/sys/ufs/lfs/lfs_segment.c
P src/sys/ufs/lfs/lfs_syscalls.c
P src/sys/ufs/lfs/lfs_vfsops.c
P src/usr.bin/make/meta.c
P src/usr.bin/xinstall/Makefile
P src/usr.sbin/dumplfs/dumplfs.c

Updating xsrc tree:
P xsrc/external/mit/ctwm/dist/README


Killing core files:

Running the SUP scanner:
SUP Scan for current starting at Sun Oct 11 05:24:56 2015
SUP Scan for current completed at Sun Oct 11 07:44:41 2015
SUP Scan for mirror starting at Sun Oct 11 07:44:41 2015
SUP Scan for mirror completed at Sun Oct 11 08:29:08 2015




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  53697524 Oct 11 08:59 ls-lRA.gz

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Christos Zoulas 
In article <20151011151458.GA6780@odin>, Mayuresh   wrote:
>+current list
>
>On Sun, Oct 11, 2015 at 04:00:49PM +0530, Mayuresh wrote:
>> On an i386 desktop I was running 6.x and just upgraded 7.0 sets (excluding
>> etc). After this I am not able to boot.
>> 
>> I am not aware how to gather the error trace, though quoting lines that I
>> think are relevant:
>> 
>> ACPI Exception: AE_NOT_FOUND
>> 
>> pagp0 at pchb0: i965-family chipset
>> 
>> pcim_mem_find: expected mem type 0004, found 
>> 
>> agp0: can't find MMIO registers
>> 
>> uvm_fault(,2) -> 0xe
>> 
>> Stopped in pid 0.1 (system) at netbsd:_atomic_swap_32+0x8
>> 
>> 
>> Please help. I am not able to boot my system.
>> Let me know if any more details are needed.
>> 
>> 
>> If I disable ACPI I get:
>> 
>> uvm_fault(..,0,1) -> 0xe
>> Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44: movl..

Disable agp?

christos

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Mayuresh 
+current list

On Sun, Oct 11, 2015 at 04:00:49PM +0530, Mayuresh wrote:
> On an i386 desktop I was running 6.x and just upgraded 7.0 sets (excluding
> etc). After this I am not able to boot.
> 
> I am not aware how to gather the error trace, though quoting lines that I
> think are relevant:
> 
> ACPI Exception: AE_NOT_FOUND
> 
> pagp0 at pchb0: i965-family chipset
> 
> pcim_mem_find: expected mem type 0004, found 
> 
> agp0: can't find MMIO registers
> 
> uvm_fault(,2) -> 0xe
> 
> Stopped in pid 0.1 (system) at netbsd:_atomic_swap_32+0x8
> 
> 
> Please help. I am not able to boot my system.
> Let me know if any more details are needed.
> 
> 
> If I disable ACPI I get:
> 
> uvm_fault(..,0,1) -> 0xe
> Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44: movl..
> 
> Mayuresh.

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Mayuresh 
On Sun, Oct 11, 2015 at 03:41:57PM +, Christos Zoulas wrote:
> >> agp0: can't find MMIO registers
> 
> Disable agp?

Could try that, but before that does this observation give any other clue:

If I start with acpi disabled, I do not get agp error. Get the following
instead:


RTC BIOS diagnostic error 0x80

uvm_fault(...,0,1) -> 0xe

Mayuresh.

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Christos Zoulas 
On Oct 11, 10:27pm, mayur...@acm.org (Mayuresh) wrote:
-- Subject: Re: NetBSD 7.0 i386 panic during boot

| On Sun, Oct 11, 2015 at 12:31:51PM -0400, Christos Zoulas wrote:
| > | RTC BIOS diagnostic error 0x80
| > 
| > That means that something is wrong with the battery, it is not fatal.
| 
| This is a desktop. You mean CMOS battery or something? 6.1 was working
| fine so far on this.

Yes. Does not matter, some are spurious.

| I am trying to type out more text. (Sorry, not yet learned how to gather
| the trace.)
|
| RTC BIOS diagnostic error 0x80
| mainbus0 (root)
| mainbus0: Intel MP Specification (Version 1.4) (
| uvm_fault(...,0,1)->0xe
| fatal page fault in supervisor mode
| trap type 6 code 0 ...
| curlwp...
| kernel: supervisor trap page fault, code=0
| Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44 movl ...
| 
| > | uvm_fault(...,0,1) -> 0xe
| > 
| > This looks like a NULL pointer dereference. Do you have a backtrace?
| 
| Unfortunately the keyboard stops working when db prompt appears. So cannot
| gather complete trace.

Compile a kernel with
options DDB_ONPANIC 2
(man 4 options)

cbristos

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Christos Zoulas 
On Oct 11, 10:58pm, mayur...@acm.org (Mayuresh) wrote:
-- Subject: Re: NetBSD 7.0 i386 panic during boot

| On Sun, Oct 11, 2015 at 07:15:39PM +0200, Leonardo Taccari wrote:
| > Hello Mayuresh,
| > 
| > Mayuresh writes:
| > > [...] 
| > > Unfortunately the keyboard stops working when db prompt appears. So cannot
| > > gather complete trace.
| > I think that:
| > 
| >  # sysctl -w ddb.commandonenter="trace"
| > 
| > will do the trick.
| 
| Ok. But I am not able to boot. Probably I should boot with installation
| media and edit /etc/sysctl.conf?

No, it does not matter. You are not making it that far yet. If you can't
get to userland to execute init, how do you expect the sysctl will make
a difference.

| BTW, just for clarity - with 7.0 installation media I face the same
| problem. I have 5.0 installation media that works.

Ok, yes.

christos

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Christos Zoulas 
On Oct 11,  9:33pm, mayur...@acm.org (Mayuresh) wrote:
-- Subject: Re: NetBSD 7.0 i386 panic during boot

| On Sun, Oct 11, 2015 at 03:41:57PM +, Christos Zoulas wrote:
| > >> agp0: can't find MMIO registers
| > 
| > Disable agp?
| 
| Could try that, but before that does this observation give any other clue:
| 
| If I start with acpi disabled, I do not get agp error. Get the following
| instead:
| 
| 
| RTC BIOS diagnostic error 0x80

That means that something is wrong with the battery, it is not fatal.

| uvm_fault(...,0,1) -> 0xe

This looks like a NULL pointer dereference. Do you have a backtrace?

christos

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Mayuresh 
On Sun, Oct 11, 2015 at 12:31:51PM -0400, Christos Zoulas wrote:
> | RTC BIOS diagnostic error 0x80
> 
> That means that something is wrong with the battery, it is not fatal.

This is a desktop. You mean CMOS battery or something? 6.1 was working
fine so far on this.

I am trying to type out more text. (Sorry, not yet learned how to gather
the trace.)

RTC BIOS diagnostic error 0x80
mainbus0 (root)
mainbus0: Intel MP Specification (Version 1.4) (
uvm_fault(...,0,1)->0xe
fatal page fault in supervisor mode
trap type 6 code 0 ...
curlwp...
kernel: supervisor trap page fault, code=0
Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44 movl ...

> | uvm_fault(...,0,1) -> 0xe
> 
> This looks like a NULL pointer dereference. Do you have a backtrace?

Unfortunately the keyboard stops working when db prompt appears. So cannot
gather complete trace.

Mayuresh

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

2015-10-11 Thread Robert Elz 
Date:Mon, 12 Oct 2015 10:31:32 +0530
From:Mayuresh 
Message-ID:  <20151012050132.GA11271@odin>

  | Even nicer if such device could be a smartphone, which can make it
  | convenient to collect data, just from ease point of view.

Yes, that would work also, but would need someone able to make
the phone's USB port implement the correct protocol and identify
itself appropriately.Here we find mostly NetBSD developers,
not those for Android or IOS...

For what it is worth, if anyone were to do this, ideal would be to make
it a parallel console, always available (assuming the relevant code is
compiled, or linked, into the kernel) whenever a suitable console type
device is connected to a USB port - ie: not as a boot time option, or
similar as is done with traditional serial consoles.

It is also worth being clear, that this is something that might (or might
not) be possible to provide at some unknown future time, and even if possible,
might never happen - it is of no relevance to current problems.

kre

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

2015-10-11 Thread Felix Deichmann 
2015-10-12 7:01 GMT+02:00 Mayuresh :
>> ps: it would be interesting to know if there was any rational way to
>> develop a NetBSD to NetBSD USB protocol that could maybe be used to
>> replace serial consoles ... requiring just a cable to link 2 NetBSD
>> systems to each other - I know nothing about USB, but if there's enough
>> access to the raw bits, it should be possible to make the running
>> NetBSD identify itself as some kind of new USB device, and have the
>> booting kernel look for that, and if found, use it as a console device.
>> Might that be possible?
>
> Even nicer if such device could be a smartphone, which can make it
> convenient to collect data, just from ease point of view.

Sounds complicated. Why not just use a ucom(4) device as console then?
Gives RS232 again with the right adapter. :)

Another alternative I already thought about was creating a "real"
RS232 interface (in place of a TPM module) for the quasi-standardized
TPM pin header on modern PC mainboards. It has all relevant LPC lines
which would also be needed to interface to a super I/O or RS232@LPC
controller (there are some on the market).
Don't know if this requires BIOS support or it'll just work though...

Like that:
http://www.eltan.com/products/manufacturing-tools/327-lpc-post-serial.html

Regards,
Felix

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

2015-10-11 Thread Robert Elz 
Date:Mon, 12 Oct 2015 07:15:43 +0200
From:Felix Deichmann 
Message-ID:

Re: NetBSD 7.0 i386 panic during boot

2015-10-11 Thread Mayuresh 
On Sun, Oct 11, 2015 at 02:10:48PM -0400, Christos Zoulas wrote:
> No, it does not matter. You are not making it that far yet. If you can't
> get to userland to execute init, how do you expect the sysctl will make
> a difference.

Alright. So, I'll compile a kernel that will help me gather trace. At the
same time shall I try disabling any modules? (agp is one but that is not
in picture when I disable acpi.)

What will help me gather the trace in a file? I think there is a notion of
dump device, but that's all I know about it. Is there any good document?

Mayuresh