[SOLVED] mpt2sas failure

fkaws · Post by **fkaws** » 2013/10/24 07:08:37

I've got an semi-urgent error message from my machine and I don't know how to interpret its meaning. I'm too useless at hardware issues.
But here goes,

mpt2sas0: _base_wait_for_doorbell_int: failed due to timeout count (10000),
tatus(c0000000)!
mpt2sas0: doorbell handshake int failed (line=3052)
mpt2sas0: _base_get_ioc_facts: handshake failed (r=-14)
mpt2sas0: sending diag reset !!
Switching to clocksource tsc
mpt2sas 0000:01:00.0: PCI INT A disabled
mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8104/_scsi_probe()
scsi: Fusion MPT SAS Host
mpt2sas 0000:42:00.0: PCI INT A -> GSI 50 (level, low) -> IRQ 50
mpt2sas 0000:42:00.0: setting latency timer to 64

I have a raid card in the machine so I thought it was that who was generating the error message, but its not. I have tried without the raid card and got the same error message when it is loading the driver. The computer specs can be found here http://www.supermicro.com/products/system/4u/8047/sys-8047r-7jrft.cfm .

The machine is working fine because I run the hole thing on a raidcard (LSI2108) and all systems checks out well. But I doesn't feel good to put this unit in production if I got error messages at this level. So if anyone knows what this doorbell-thing is I would be glad to here from you.

/Fredrik

fkaws · Post by **fkaws** » 2013/10/24 08:42:38

Got some more information. I did a dmesg on another fine working machine and grepped the mpt2sas. So here is the differnces:

WORKING comp

[root@db311 /]# dmesg | grep mpt2sas0
mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (99029620 kB)
mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 144
mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 145
mpt2sas0-msix2: PCI-MSI-X enabled: IRQ 146
mpt2sas0-msix3: PCI-MSI-X enabled: IRQ 147
mpt2sas0-msix4: PCI-MSI-X enabled: IRQ 148
mpt2sas0-msix5: PCI-MSI-X enabled: IRQ 149
mpt2sas0-msix6: PCI-MSI-X enabled: IRQ 150
mpt2sas0-msix7: PCI-MSI-X enabled: IRQ 151
mpt2sas0-msix8: PCI-MSI-X enabled: IRQ 152
mpt2sas0-msix9: PCI-MSI-X enabled: IRQ 153
mpt2sas0-msix10: PCI-MSI-X enabled: IRQ 154
mpt2sas0-msix11: PCI-MSI-X enabled: IRQ 155
mpt2sas0-msix12: PCI-MSI-X enabled: IRQ 156
mpt2sas0-msix13: PCI-MSI-X enabled: IRQ 157
mpt2sas0-msix14: PCI-MSI-X enabled: IRQ 158
mpt2sas0-msix15: PCI-MSI-X enabled: IRQ 159
mpt2sas0: iomem(0x00000000bb640000), mapped(0xffffc9001cf00000), size(65536)
mpt2sas0: ioport(0x0000000000006000), size(256)
mpt2sas0: sending message unit reset !!
mpt2sas0: message unit reset: SUCCESS
mpt2sas0: Allocated physical memory: size(17336 kB)
mpt2sas0: Current Controller Queue Depth(9977), Max Controller Queue Depth(10240)
mpt2sas0: Scatter Gather Elements per IO(128)
mpt2sas0: LSISAS2308: FWVersion(13.00.57.00), ChipRevision(0x05), BiosVersion(07.25.00.00)
mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
mpt2sas0: sending port enable !!
mpt2sas0: host_add: handle(0x0001), sas_addr(0x50030480023c6b00), phys(8)
mpt2sas0: port enable: SUCCESS

NOT WORKING comp.

localhost.root 4> dmesg | grep mpt2sas0
mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (99029620 kB)
mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 144
mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 145
mpt2sas0-msix2: PCI-MSI-X enabled: IRQ 146
mpt2sas0-msix3: PCI-MSI-X enabled: IRQ 147
mpt2sas0-msix4: PCI-MSI-X enabled: IRQ 148
mpt2sas0-msix5: PCI-MSI-X enabled: IRQ 149
mpt2sas0-msix6: PCI-MSI-X enabled: IRQ 150
mpt2sas0-msix7: PCI-MSI-X enabled: IRQ 151
mpt2sas0-msix8: PCI-MSI-X enabled: IRQ 152
mpt2sas0-msix9: PCI-MSI-X enabled: IRQ 153
mpt2sas0-msix10: PCI-MSI-X enabled: IRQ 154
mpt2sas0-msix11: PCI-MSI-X enabled: IRQ 155
mpt2sas0-msix12: PCI-MSI-X enabled: IRQ 156
mpt2sas0-msix13: PCI-MSI-X enabled: IRQ 157
mpt2sas0-msix14: PCI-MSI-X enabled: IRQ 158
mpt2sas0-msix15: PCI-MSI-X enabled: IRQ 159
mpt2sas0: iomem(0x00000000bb600000), mapped(0xffffc9001cf00000), size(65536)
mpt2sas0: ioport(0x0000000000006000), size(256)
mpt2sas0: _base_wait_for_doorbell_int: failed due to timeout count(10000), int_status(c0000000)!
mpt2sas0: doorbell handshake int failed (line=3052)
mpt2sas0: _base_get_ioc_facts: handshake failed (r=-14)
mpt2sas0: sending diag reset !!
mpt2sas0: diag reset: FAILED
mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8104/_scsih_probe()!

/Fredrik

Post by **TrevorH** » 2013/10/24 08:51:49

It almost certainly [u]is[/u] the RAID card since that's what mpt2sas does. Looks like a hardware error to me.

fkaws · Post by **fkaws** » 2013/10/25 07:41:18

It was a firmware problem. Got new firmware for that controller and it solved the whole thing.

CentOS