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

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

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: > >

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

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

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

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

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

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

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

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.