2.6.30-9 sata softreset failed on AMD SB600
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This seems to be a regression, as this problem went away on the 2.6.28 kernels of Jaunty, but now that I've upgraded to Karmic (2.6.30 kernels, all versions I've tested) I again have to disable the write caching in order for the drives to function under heavy data loads. This happens both on the "root" single disk and my raid5 array of 3 disks, all connected to the ATI SB600 chip.
These are excerpts from my dmesg:
[ 1.864515] ata2: softreset failed (device not ready)
[ 1.864557] ata2: failed due to HW bug, retry pmp=0
[ 1.864574] ata4: softreset failed (device not ready)
[ 1.864613] ata4: failed due to HW bug, retry pmp=0
[ 1.864629] ata3: softreset failed (device not ready)
[ 1.864667] ata3: failed due to HW bug, retry pmp=0
[ 2.436905] ata1.00: ATA-7: SAMSUNG SP2504C, VT100-33, max UDMA7
[39056.481268] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[39056.486260] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[39056.486268] ata1.00: configured for UDMA/133
[39056.486275] ata1: EH complete
[58596.804070] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[58596.804090] ata3.00: cmd ea/00:00:
[58596.804099] ata3.00: status: { DRDY }
[58596.804109] ata3: hard resetting link
[58597.288535] ata3: softreset failed (device not ready)
[58597.288545] ata3: failed due to HW bug, retry pmp=0
[58597.452056] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[58597.457033] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[58597.462059] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[58597.462068] ata3.00: configured for UDMA/133
[58597.462155] ata3: EH complete
I couldn't find this reported linked to the latest Karmic kernels, so I want to make sure it's known that it still exists, and I can reproduce it fairly regularly by simply doing some heavy file operations. Filesystem is ext4 on both the array and the root drive, default options when creating it.
I reported this in the kernel, it may also be part of libata. I don't know for sure.