Messages in this thread | | | From | Alistair John Strachan <> | Subject | Re: CK804 SATA Errors (still got them) | Date | Fri, 2 Mar 2007 15:47:08 +0000 |
| |
On Friday 02 March 2007 02:40, Robert Hancock wrote: > Alistair John Strachan wrote: > > On Thursday 01 March 2007 15:13, Alistair John Strachan wrote: > >> On Thursday 01 March 2007 14:45, Robert Hancock wrote: > >>> This one seems a bit different. This time it's not related to NCQ vs. > >>> non-NCQ (this is a non-NCQ write here), it's in ADMA mode (so it's > >>> presumably not related to switching between ADMA and register mode, > >>> unless perhaps a flush cache or something executed just before), and > >>> from the CPB data it appears the command completed but the controller's > >>> registers aren't indicating that it has. Not sure if I've seen one like > >>> that before.. > >>> > >>> How easily can you reproduce this? > >> > >> It's the first one since -rc2, so apparently not easily. I'm more than > >> willing to find loads that expose it, though, so I might try that this > >> afternoon. > > > > Got another: > > > > ata2: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 > > status 0x500 next cpb count 0x0 next cpb idx 0x0 ata2: CPB 0: ctl_flags > > 0xd, resp_flags 0x1 > > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen > > ata2.00: cmd c8/00:80:85:c4:ed/00:00:00:00:00/e3 tag 0 cdb 0x0 data 65536 > > in res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) ata2: soft > > resetting port > > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > ata2.00: configured for UDMA/133 > > ata2: EH complete > > SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB) > > sdb: Write Protect is off > > sdb: Mode Sense: 00 3a 00 00 > > SCSI device sdb: write cache: enabled, read cache: enabled, doesn't > > support DPO or FUA > > > > Different HD, similar problem. > > Can you try reverting commit 721449bf0d51213fe3abf0ac3e3561ef9ea7827a > (link below) and see what effect that has? > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h >=721449bf0d51213fe3abf0ac3e3561ef9ea7827a
Obviously, I'll let you know if it happens again, but I've reverted this commit and transferred 22.5GB over 45 minutes onto a RAID5 with 4 HDs on an NVIDIA sata controller, and this error hasn't appeared.
So I'm inclined to (very unscientifically) say that this brings it back to 2.6.20's level of stability.
-- Cheers, Alistair.
Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |