At 09:35 AM 4/1/2004, Chris Tribo wrote:
>GENERIC 1.6ZL on an 8500 with G3 CPU upgrade. (L2 cache not enabled)
>
>root file system type: ffs
>Thu Apr 1 07:23:22 EST 2004
>trap type 13020 at 41853088
>panic: trap
>Stopped in pid 11.1 (rcorder) at netbsd:cpu_Debugger+0x10: lwz r0, r1,
>0x14
>
>db> bt
>0xd45d7e30: at panic+19c
>0xd45d7ec0: at trap+100
>0xd45d7f40: user trap 0x3020 by 0x41853088: srr1=0xd032 r1=0xffffe2d0
>cr=0x24002044 xer=0 ctr=0x418e0b24
>
>I ran this same kernel last night without a problem, something strange is
>afoot. I just rebooted and it went through fine. Is mesh still
>unstable? I could move the drive to esp but I don't really want to.

That's strange.  It seems you got an AST trap but instead of being at
0x3000 it's at 0x3020 and caused the trap code to go "WTF?".  Can you do
a db> show event ?

Since that kernel loads at 0x100000, there is no code at 0x3000 NetBSD
will try to execute.  And if there was, I doubt it would know the magic
to call back into the trap code.

Did I say it was strange?

-- 
Matt Thomas                     email: matt@3am-software.com
3am Software Foundry              www: http://3am-software.com/bio/matt/
Cupertino, CA              disclaimer: I avow all knowledge of this message.