AHCI timeout

Reid Linnemann lreid at cs.okstate.edu
Tue Dec 6 19:42:39 UTC 2011


On Tue, Dec 6, 2011 at 12:25 PM, C. P. Ghost <cpghost at cordula.ws> wrote:
> On Tue, Dec 6, 2011 at 4:41 PM, Julien Cigar <jcigar at ulb.ac.be> wrote:
>> Hello,
>>
>> I'm running 9.0-RC3 on a HP Proliant Microserver (N40L). A disk died in my
>> graid3 array and I replaced it with a new one, and now have tons of:
>>
>> ahcich3: Timeout on slot 5 port 0
>> ahcich3: is 00000000 cs 00000000 ss 00003f60 rs 00003f60 tfd 40 serr
>> 00000000 cmd 0000ed17
>
> Check the connectors, both on disk and on the controller. They're
> usually the culprit. Sometimes it is also a firmware problem, but
> I'll try to replace the cables first.
>
>> (...)
>>
>> Those are Seagate disks:
>>
>> jcigar at backup conf % sudo camcontrol devlist
>> <VB0250EAVER HPG0>                 at scbus0 target 0 lun 0 (pass0,ada0)
>> <ST31000528AS CC38>                at scbus1 target 0 lun 0 (pass1,ada1)
>> <ST31000528AS CC38>                at scbus2 target 0 lun 0 (pass2,ada2)
>> <ST31000333AS CC1H>                at scbus3 target 0 lun 0 (pass3,ada3)
>>
>> The controller is:
>>
>> ahci0 at pci0:0:17:0:      class=0x010601 card=0x1609103c chip=0x43911002
>> rev=0x40 hdr=0x00
>>    vendor     = 'ATI Technologies Inc'
>>    device     = 'SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]'
>>    class      = mass storage
>>    subclass   = SATA
>>
>> jcigar at backup conf % vmstat -i
>> interrupt                          total       rate
>> irq17: ehci0 ehci1+                    2          0
>> irq18: ohci0 ohci1+                   30          0
>> irq256: bge0                       31354          4
>> irq257: ahci0                   19012658       2477
>> irq258: hpet0:t0                 4926229        641
>> irq259: hpet0:t1                 4635261        603
>> Total                           28605534       3727
>>
>>
>> Any idea what could be the cause of this ... ?
>>
>>
>> Thanks,
>> Julien
>
> -cpghost.
>
> --
> Cordula's Web. http://www.cordula.ws/
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"

I've had similar problems with a failing power supply when I used to
run a gmirror on 7-STABLE. I was not running with AHCI, so I did not
get the same messages; but I did get repeated WRITE_DMA timeouts on my
da disks that eventually resulted in one disk being detached from the
mirror. Cold booting was an arduous process because 9 boots of 10 the
system would start sputtering out on DMA timeouts almost immediately
after mounting the filesystems, and take well over 30 minutes just to
get through rc. I changed cables, swapped the disks around, checked
smartctl over and over to no avail. Eventually I bought a new rig and
hooked it up to the original power supply - the problems persisted. I
swapped in the new power supply and hey presto! the problems went
away. You mentioned hardware failure in the original disk, so it might
not be too far of a stretch to consider the power supply might also
have suffered a failure.


More information about the freebsd-questions mailing list