I had another panic today (7457 G4, netbsd-2, no ALTIVEC option in the 
kernel config):

trap: pid 914.1 (setiathome): kernel MCHK trap @ 0x33f880 
(SRR1=0x40009030)
panic: trap
Begin traceback...
0x0075adb0: at trap+0xec
0x0075ae30: kernel MCHK trap by pfil_run_hooks+0: srr1=0x40009030
             r1=0x75aef0 cr=0x4020f032 xer=0 ctr=0x32816c
0x0075aef0: at bpf_mtap+0xdc
0x0075af20: at ex_intr+0x314
0x0075af60: at ext_intr_openpic+0x17c
0x0075afa0: at trapstart+0x868
saved LR(0xfffffffb) is invalid.End traceback...
syncing disks... wdc0:0:1: lost interrupt
         type: ata tc_bcount: 2048 tc_skip: 0
wdc0:0:1: lost interrupt
         type: ata tc_bcount: 16384 tc_skip: 0
wdc0:0:1: lost interrupt
         type: ata tc_bcount: 16384 tc_skip: 0
wdc0:0:1: lost interrupt


What's interesting is that I've never seen lost interrupts on the 
motherboard IDE controller - ever. They're common on PCI IDE cards, but 
this is new. Is this because the state of the interrupt handlers is all 
screwy when in the debugger?

Any ideas about the panic in general?

Thanks,
John Klos