Jason Thorpe <thorpej@nas.nasa.gov> writes:

> How does the kernel crash?

Digital Personal WorkStation 500au, 500MHz
8192 byte page size, 1 processor.
real mem = 134217728 (1933312 reserved for PROM, 132284416 used by NetBSD)
avail mem = 111566848
using 1614 buffers containing 13221888 bytes of memory
mainbus0 (root)
cpu0 at mainbus0: ID 0 (primary), 21164A (reserved minor type)
cpu0: VAX FP support, IEEE FP support, Primary Eligible
cia0 at mainbus0: DECchip 2117x Core Logic Chipset (Pyxis), pass 1
cia0: extended capabilities: 1<BWEN>
cia0: using BWX for PCI config access
cia0: WARNING: Pyxis pass 1 DMA bug; no bets...
pci0 at cia0 bus 0
pci0: i/o enabled, memory enabled
de0 at pci0 dev 3 function 0
de0: interrupting at dec 550 irq 8
de0: DEC 21143 [10-100Mb/s] pass 3.0
de0: address 00:00:f8:75:6d:9a
de0: enabling 10baseT port
pciide0 at pci0 dev 4 function 0: CMD Technology PCI0646 (rev. 0x01)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel wired to compatibility mode
wdc2 at pciide0 channel 0
atapibus0 at wdc2
cd0 at atapibus0 drive 0: <CRD-8241B, 1997/09/18, 2.01> type 5 cdrom removable
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel ignored (not responding; disabled or no drives?)
sio0 at pci0 dev 7 function 0: Intel 82378ZB System I/O (SIO) (rev. 0x43)
ppb0 at pci0 dev 20 function 0: Digital Equipment DECchip 21052 PCI-PCI Bridge (rev. 0x02)
pci1 at ppb0 bus 1
pci1: i/o enabled, memory enabled
isp0 at pci1 dev 8 function 0
Qlogic ISP Driver, NetBSD (pci) Platform Version 0.97 Core Version 1.2
isp0: setting input clock to 60
isp0: Board Revision 1040B, loaded F/W Revision 7.55
isp0: Last F/W revision was 5.54
isp0: interrupting at dec 550 irq 20
scsibus0 at isp0: 16 targets
sd0 at scsibus0 targ 0 lun 0: <DEC, RZ1CC-BA (C) DEC, 880F> SCSI2 0/direct fixed
sd0: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
sd1 at scsibus0 targ 1 lun 0: <DEC, DSP3105S, T384> SCSI2 0/direct fixed
sd1: 1001MB, 2570 cyl, 14 head, 57 sec, 512 bytes/sect x 2050860 sectors
sd2 at scsibus0 targ 4 lun 0: <SEAGATE, ST118273W, 5698> SCSI2 0/direct fixed
sd2: 17366MB, 7501 cyl, 20 head, 237 sec, 512 bytes/sect x 35566480 sectors

unexpected machine check:

    mces    = 0x1
    vector  = 0x660
    param   = 0xfffffc0000006068
    pc      = 0xfffffc0000588fbc
    ra      = 0xfffffc0000588fa0
    curproc = 0xfffffc0000672e10
        pid = 0, comm = 

panic: machine check
Stopped in  at  Debugger+0x4:   ret     zero,(ra)
db> c
halted.


halted CPU 0

halt code = 5
HALT instruction executed
PC = fffffc0000300140
MCHECK_ERR - 217 - I/O Timeout occurred

IOA timeout has occured

*** Unexpected interrupt through vector 00000066

IPRs:
EXC_ADDR:0000000000126360   EXC_SUM:0000000000000000  EXC_MASK:0000000000126360
     ISR:0000000180400000      ICSR:0000004166020000   IC_PERR:0000000000000000
 DC_PERR:0000000000000000        VA:0000000000127370   MM_STAT:0000000000014910
 SC_ADDR:FFFFFF00000136AF   SC_STAT:0000000000000000  BCTAG_AD:FFFFFF80002D6FFF
 EI_ADDR:FFFFFF000008883F  FILL_SYN:0000000000000058   EI_STAT:FFFFFFF4C5FFFFFF
 LD_LOCK:FFFFFF00000DC63F

MIATA Error CSRs (CPU 0):
 PYXIS_ERR:FFFFFFFF88000800     STAT:00000000000000F0 ERR_MASK:0000000000000B93
   ECC_SYN:0000000000000000     MEAR:0000000000886D80     MESR:0000000058000000
  ERR_DATA:0000000000000000
  PCI_ERR0:000000000306040E PCI_ERR1:000000000000000E PCI_ERR2:00000000000003D4

I/O CSRs:

MEMORY CSRs
BBAR0:    00000000    BCR0:    00000027    BTR0:    00000022
BBAR1:    00000000    BCR1:    00000000    BTR1:    00000000
BBAR2:    00000000    BCR2:    00000000    BTR2:    00000000
BBAR3:    00000000    BCR3:    00000000    BTR3:    00000000
BBAR4:    00000000    BCR4:    00000000    BTR4:    00000000
BBAR5:    00000000    BCR5:    00000000    BTR5:    00000000
BBAR6:    00000000    BCR6:    00000000    BTR6:    00000000
BBAR7:    00000000    BCR7:    00000000    BTR7:    00000000
MCR:    3FFF1600
*** Console Stopped because of Machine Check  ***
*** Press HALT Button to return to console !! ***

> Sounds like the Firmware is Confused...

Most likely.

/Johan