Re: NetBSD 7.0 i386 panic during boot

On Sat, Oct 17, 2015 at 01:33:32PM +0300, Andreas Gustafsson wrote: > The discussion that ensued branched out in lots of different > directions, but as far as I can see, none of them actually > offered a diagnosis of the original problem reported. > > To me, this looks very much like the same

Re: NetBSD 7.0 i386 panic during boot

In the very first message of this thread, 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:

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

On Mon, Oct 12, 2015 at 09:32:13PM +0700, Robert Elz wrote: > > Joerg Sonnenberger said: > | You don't need "just" a cable, but one with quite a bit logic in between. > | USB is not designed for host-to-host communication, > > Thanks - that's the kind of info I was

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 9:02pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: | > Add some printfs to vmem_alloc? This is happening way too early. | | I tried enabling following option to see whet

Re: NetBSD 7.0 i386 panic during boot

On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. Is there a way to read source level info (line number etc) in the trace? May be, if that doesn't give a clue, I'll get into printfs? Mayuresh.

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 8:18pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | That apart. Now I get the trace, mentioning the function names: Add some printfs to vmem_alloc? This is happening way too early. christos

Re: NetBSD 7.0 i386 panic during boot

On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. I tried enabling following option to see whether trace shows source level info. But it didn't. makeoptions DEBUG="-g" Is there any way to get source level

Re: NetBSD 7.0 i386 panic during boot

On Tue, Oct 13, 2015 at 08:20:23AM -0400, Christos Zoulas wrote: > So you have a usb keyboard and it does not work for you? > Comment out the following lines: > > #pckbc* at acpi?# PC keyboard controller > #pckbc0 at isa? # pc keyboard controller

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 8:52pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: | > Add some printfs to vmem_alloc? This is happening way too early. | | Is there a way to read source level info (l

Re: NetBSD 7.0 i386 panic during boot

On Tue, Oct 13, 2015 at 05:24:31PM +0530, Mayuresh wrote: > On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: > > | > This looks like a NULL pointer dereference. Do you have a backtrace? > > | > > | Unfortunately the keyboard stops working when db prompt appears. So cannot > > |

Re: NetBSD 7.0 i386 panic during boot

On Wed, Oct 14, 2015 at 07:51:53AM -0400, Christos Zoulas wrote: > | $sysctl ddb.onpanic > | ddb.onpanic = 2 > | > | So looks like my procedure was alright. Is there anything else needed to > | make kernel print trace on entering ddb, when keyboard can't be used? > > Did the instructions I

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

On 12 October 2015 at 10:32, Robert Elz wrote: > Long long ago I did an implementation of config code (more or less a console) > for a device that had nothing but ethernet. For that (and to avoid the > issue that would arise here, of needing specialised client code) I used

Re: NetBSD 7.0 i386 panic during boot

On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: > | > 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

Re: NetBSD 7.0 i386 panic during boot

On Oct 13, 5:24pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: | > | > This looks like a NULL pointer dereference. Do you have a backtrace? | > | | > | Unfortunately the ke

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

2015-10-12 7:50 GMT+02:00 Robert Elz : > No, that makes no sense. The whole point is that no-one has RS232 > on anything modern - forcing it to exist, just because it is what used > to be used helps nothing. This generalising statement is at least wrong in an industrial

Re: NetBSD 7.0 i386 panic during boot

On Mon, 12 Oct 2015, Andreas Gustafsson wrote: Robert Elz wrote: If it is (as I believe is the case) failing to boot correctly, there is no operating system running to write files, no filesystems visible to write them, or crash dumps, to, nothing available but what appears on the console. The

Re: NetBSD 7.0 i386 panic during boot

Robert Elz wrote: > If it is (as I believe is the case) failing to boot correctly, there > is no operating system running to write files, no filesystems visible > to write them, or crash dumps, to, nothing available but what appears on > the console. > > The traditional way to handle this was to

Re: NetBSD 7.0 i386 panic during boot

Paul Goyette wrote: > Of course you'd still need to manually transcribe the console display, > or take a pic for screen capture. Of course. I think we should encourage the latter option; it's less work for the user, less error prone, and likely to contain more information. -- Andreas

Re: NetBSD 7.0 i386 panic during boot

jo...@britannica.bec.de (Joerg Sonnenberger) writes: >On Mon, Oct 12, 2015 at 11:21:41AM +0700, Robert Elz wrote: >> 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 >You don't

Re: NetBSD 7.0 i386 panic during boot

On Mon, Oct 12, 2015 at 11:21:41AM +0700, Robert Elz wrote: > 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]

First, I know I was a little overboard on the "RS232 is dead" theme, there are still uses for it, and it remains useful for its purpose. However, the time when *everything* had rs232 available has passed now, and it was that which made it attractive as an alternative console (boosted by many

Re: NetBSD 7.0 i386 panic during boot

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

+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

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

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

Re: NetBSD 7.0 i386 panic during boot

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 w

Re: NetBSD 7.0 i386 panic during boot

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 o

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. I am trying to type out more

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

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

Date:Mon, 12 Oct 2015 07:15:43 +0200 From:Felix Deichmann Message-ID:

Re: NetBSD 7.0 i386 panic during boot

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.