bin/41033: current init panic alpha

[petervanbohning%gmail.com@localhost]

>Number:         41033
>Category:       bin
>Synopsis:       current init panic alpha
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 17 19:45:00 +0000 2009
>Originator:     Peter
>Release:        current
>Organization:
>Environment:
NetBSD 5.99.8 (GENERIC-$Revision: 1.328 $) alpha
>Description:
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.

I'm actually not sure what the procedure is for reporting bugs on current.  
Maybe no one cares unless I take the time to fix it and submit a patch.

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.
>How-To-Repeat:

>Fix:
To fix it, I booted off of a CD and then replaced the -current init with an 
init from 4.0.1 sets.  System runs fine as far as I can tell now.