Subject: Re: kernel panic in 1.6_BETA4
To: Jason R Thorpe <thorpej@wasabisystems.com>
From: Sean Davis <dive-nb@endersgame.net>
List: port-alpha
Date: 07/15/2002 21:20:24
On Mon, Jul 15, 2002 at 05:59:12PM -0700, Jason R Thorpe wrote:
> On Mon, Jul 15, 2002 at 08:55:25PM -0400, Sean Davis wrote:
> 
>  > Is there something I should try in the config file that might work around
>  > that?
> 
> Not that I'm aware of -- this is a software bug, plain and simple :-)

Do you think it would work OK if I tried -current instead of netbsd-1-6? I
haven't been watching commits in non-i386 arch's very closely, but that's
going to change now. :)

> 
>  > (also... how do I drop back to firmware when connected via serial console?
>  > I'm using cu -l tty00 on a NetBSD/i386 box to talk to the alpha, and I can't
>  > figure out how to get back to firmware so that I can tell it to boot a good
>  > kernel. It's just loading /netbsd which is the bad one over and over again.)
> 
> When the machine goes back to SRM as it begins to reboot, you should be
> able to ^C repeatedly to stop the booting process.

I can't even get it to try that anymore, while tinkering around in DDB, I
managed to throw it into a memory management fault loop that I can't break
out of:
CPU 0: fatal kernel trap:

CPU 0    trap entry = 0x2 (memory management fault)
CPU 0    a0         = 0x73
CPU 0    a1         = 0x1
CPU 0    a2         = 0x0
CPU 0    pc         = 0xfffffc00004e1270
CPU 0    ra         = 0xfffffc000037a5ac
CPU 0    pv         = 0xfffffc00004e1260
CPU 0    curproc    = 0xfffffc00005e7090
CPU 0        pid = 0, comm = swapper

        Caught exception in ddb.
panic: longjmp botch from 0xfffffc000037ae4c
Stopped in pid 0 (swapper) at   rn+0x53:
CPU 0: fatal kernel trap:

CPU 0    trap entry = 0x2 (memory management fault)
CPU 0    a0         = 0x73
CPU 0    a1         = 0x1
CPU 0    a2         = 0x0
CPU 0    pc         = 0xfffffc00004e1270
CPU 0    ra         = 0xfffffc000037a5ac
CPU 0    pv         = 0xfffffc00004e1260
CPU 0    curproc    = 0xfffffc00005e7090
CPU 0        pid = 0, comm = swapper

        Caught exception in ddb.
panic: longjmp botch from 0xfffffc000037ae4c

I'll go back to GENERIC once I get the machine power-cycled, and maybe try
-current on it instead.

-- 
/~\ The ASCII                         Sean Davis
\ / Ribbon Campaign                    aka dive
 X  Against HTML
/ \ Email!                   http://endersgame.net/~dive/