On Sat, Apr 03, 2004 at 09:28:33AM +0900, Christopher SEKIYA wrote:
> On Fri, Apr 02, 2004 at 10:32:35PM +0200, Manuel Bouyer wrote:
> 
> > spurious interrupt, ipending c000
> 
> That's MIPS_INT_MASK_5 and MIPS_INT_MASK_4, which are timer and buserror
> interrupts respectively.
> 
> Hmmm, it looks like the buserror handler isn't actually being hooked into
> the interrupt routine.  Try the patch below and let me know what happens.
> 
> (it would be interesting to find out _why_ you're receiving a bus error in
> the first place :)

Well, I also got:
db> reboot(0xc)
halting...


Exception: <vector=Normal>
Status register: 0x30004803<CU1,CU0,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
Cause register: 0xc300<CE=0,IP8,IP7,SW2,SW1,EXC=INT>
Exception PC: 0x9fc3e260, Exception RA: 0x9fc02580
Interrupt exception
CPU Parity Error Interrupt
Local I/O interrupt register 2: 0x20 <DUART>
CPU parity error register: 0x304<B2,MEM_PAR>
CPU parity error: address: 0x8a8a210 <SIMM S2> 
  Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
  arg: a8740000 3 2 1fbd988f
  tmp: a8740000 5 3 2 0 8836d6c0 8864bb28 24
  sve: a8740000 3 400000 8000000 16 3f80 0 4000000
  t8 a8740000 t9 0 at 0 v0 0 v1 0 k1 30410000
  gp a8740000 fp 0 sp 0 ra 0

PANIC: Unexpected exception

[Press reset or ENTER to restart.]

and unfortunably it's stuck here. I can't power-cycle it remotely, I'll see
is there is someone at work who can do it

Looks like a problem with a SIMM, isn't it ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--