problem with sata_sil24: PCI fault or device removal?

problem with sata_sil24: PCI fault or device removal?

[Jonathan Steinert]

I have a box here running 2.6.26 x86_64 normally (also tested with 2.6.29, and going to test with later versions too) that has major issues with SATA. I'm not sure which things are causes and which things are side effects, so I'm just going to list symptoms.

I'm happy to use this machine for debugging, but I'm not subscribed to lkml. If you could please CC me on responses that would help a lot.

- The first error I usually see is:

sata_sil24: PCI fault or device removal?

- In some cases I've had the box hard-lock (no magic SysRq response or anything) with no errors.

- Booting a live OS with 2.6.25 @ 32bit seems to be just fine, but this could be a side effect of 32 vs 64bit. Not sure yet.

- SMART commands might make the situation worse. I was using smartmontools to run long self-tests on the drives every sunday, and tends to crash on sunday around the time of the long test starting. I was also using hddtemp and it got a little less frequent when I removed that.

- Lots of IO does make it worse. dd if=/dev/sdwhatever of=/dev/null can get it to start spewing errors within a minute usually.

- Logs and command outputs are at: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/

    lspci: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/lspci.txt
    lspci -vvv: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/lspci_long.txt
    dmesg: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/dmesg.txt
    console output during a crash: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/crash1.txt

If anyone has time to help, it would be much appreicated. I'm able and willing to collect any other information you might want.

Thanks

--hachi

------------------------------------------------------------------------
"She smiled again, shrugged her shoulders, and became a perfect mirror."
------------------------------------------------------------------------

Re: problem with sata_sil24: PCI fault or device removal?

[Robert Hancock]

Jonathan Steinert wrote:
> I have a box here running 2.6.26 x86_64 normally (also tested with 2.6.29, and going to test with later versions too) that has major issues with SATA. I'm not sure which things are causes and which things are side effects, so I'm just going to list symptoms.
> 
> I'm happy to use this machine for debugging, but I'm not subscribed to lkml. If you could please CC me on responses that would help a lot.
> 
> - The first error I usually see is:
> 
> sata_sil24: PCI fault or device removal?
> 
> - In some cases I've had the box hard-lock (no magic SysRq response or anything) with no errors.
> 
> - Booting a live OS with 2.6.25 @ 32bit seems to be just fine, but this could be a side effect of 32 vs 64bit. Not sure yet.
> 
> - SMART commands might make the situation worse. I was using smartmontools to run long self-tests on the drives every sunday, and tends to crash on sunday around the time of the long test starting. I was also using hddtemp and it got a little less frequent when I removed that.
> 
> - Lots of IO does make it worse. dd if=/dev/sdwhatever of=/dev/null can get it to start spewing errors within a minute usually.
> 
> - Logs and command outputs are at: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/
> 
>     lspci: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/lspci.txt
>     lspci -vvv: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/lspci_long.txt
>     dmesg: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/dmesg.txt
>     console output during a crash: http://hachi.kuiki.net/bug_reports/20090519-linux-sata/crash1.txt
> 
> If anyone has time to help, it would be much appreicated. I'm able and willing to collect any other information you might want.

What is this controller, an add-in card? The fact that you got a status 
register read returning all ones (think that's the usual result of a PCI 
abort), and these errors:

[ 2094.921961] ata12: irq_stat 0x00020002, PCI master abort while 
transferring data
[ 2099.317472] ata12.00: irq_stat 0x00020002, PCI parity error while 
fetching SGT

really suggest you're having some kind of problems on the PCI bus.. 
Could be a hardware fault, power issue, etc.