Re: bin/41033: current init panic alpha

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR bin/41033; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/41033: current init panic alpha
Date: Sun, 29 Mar 2009 18:23:37 +0000

 On Tue, Mar 17, 2009 at 07:45:01PM +0000, petervanbohning%gmail.com@localhost 
wrote:
  > I followed instructions on
  > http://www.netbsd.org/docs/current/index.html.  Installed kernel,
  > rebooted.  Fine.  Installed userland, rebooted, and I got panic,
  > init, exit 12, I think, segmentation fault.  It opened a debugger
  > db> to "cpudebugger 0x4 ret 0,(ra)
  > 
  > I think that was it, I might have written it down anywhere.  There
  > was also a core dump, which I could send to someone, I'm not really
  > sure what's in it but I know it wrote it to /var the next time it
  > started booting.  But I guess that just means the stack gets
  > screwed up by something somewhere.
 
 The exact panic message would be helpful, plus if init printed any
 messages before dying, please report those. However, if init really
 exited with code 12 (and not e.g. 13, or with *signal* 11) it means it
 couldn't open the console, so there won't be any.
 
 Before you start any testing, copy the working init to /sbin/oinit or
 /sbin/init.bak; then you can use it by booting with the -a flag.
 
  > There were also, during compile, a couple of warnings treated as
  > errors, missing prototype for bcmp() and also blkdevclose had an
  > issue where a Makefile defined blkdevclose(f)=0, so I added #undef
  > blkdevclose in order to get the distribution to build.  I have
  > trouble believing that's related though, I think that's separate.
 
 Probably not, but please file separate bug reports on them if they
 haven't already been fixed.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost