Re: Current Kernel does not boot

[Ede Wolf <listac%nebelschwaden.de@localhost>]

I had the same problem with stable. The panic was gone when using -O2, in 
complete:

 COPTS+=-O2 -mcpu=21164a -pipe

does work for me, with the -O2 being important. -Os does work, too, -O0 (or 
none -O Option at all) did not  work and produced a trap, though it paniced 
at a different stage. 
Was a topic in here a couple of weeks ago, too. Did not recheck, but maybe 
Problem Report 34446 is of interest. 


Am Dienstag, 28. Oktober 2008 schrieb Aaron J. Grier:
> On Sat, Oct 25, 2008 at 07:57:52PM +0200, Jan Lentfer wrote:
> > NetBSD 4.99.73 (PWS_MLX) #0: Sat Oct 25 16:34:04 UTC 2008
> >        
> > lentferj%bsd-alpha.lan.net@localhost:/usr/obj/sys/arch/alpha/compile/PWS_MLX
> > Digital Personal WorkStation 500au, 500MHz, s/n
> > 8192 byte page size, 1 processor.
> > total memory = 448 MB
> > (1896 KB reserved for PROM, 446 MB used by NetBSD)
> > avail memory = 432 MB
> > mainbus0 (root)
> > cpu0 at mainbus0: ID 0 (primary), 21164A-0
> > cpu0: Architecture extensions: 1<BWX>
>
> [...]
>
> > Kernelized RAIDframe activated
> >
> > CPU 0: fatal kernel trap:
> >
> > CPU 0    trap entry = 0x2 (memory management fault)
> > CPU 0    a0         = 0x4a
> > CPU 0    a1         = 0x1
> > CPU 0    a2         = 0x0
> > CPU 0    pc         = 0xfffffc00005b5810
> > CPU 0    ra         = 0xfffffc00003e9740
> > CPU 0    pv         = 0xfffffc00005b5810
> > CPU 0    curlwp     = 0xfffffc001beb9c00
> > CPU 0        pid = 0, comm = system
> >
> > panic: trap
> > Stopped in pid 0.2 (system) at  netbsd:cpu_Debugger+0x4:        ret
> > zero,(ra
> > )
> > db>
>
> this smells familiar, and I seem to recall running into it on my 1000A
> with kernels built with COPTS="-mcpu=21164a" .  does a GENERIC kernel
> built with default COPTS boot?