Bug 11751
Summary: | libata: sata_nv: enabling SWNCQ causes errors | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Chuck Ebbert (cebbert) |
Component: | Serial ATA | Assignee: | Tejun Heo (tj) |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | alan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.26 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
output of smartctl -a
output of hdparm -I |
Description
Chuck Ebbert
2008-10-13 12:57:10 UTC
Please post the results of "hdparm -I" and "smartctl -a" on the drive. Created attachment 18307 [details]
output of smartctl -a
Created attachment 18309 [details]
output of hdparm -I
Eh... the above attachments contain links to redhat attachments. That's a weird way to post files. Please don't do that. I have a HD160JJ and it's a pretty well behaved drive. It never had any problem with NCQ. Till now, many (but not all) cases of FLUSH(_EXT) timeouts were caused by power problems. Can you please connect the hard drive to a separate power supply and see whether it makes any difference? Thanks. From the comments in the Red Hat bug, I gather the array worked perfectly until sata_nv SWNCQ got enabled in 2.6.26. So I doubt this is caused by power problems. Unless it's too difficult to try, I would really like to rule that out as this wouldn't be the first time NCQ enabling and power problem show correlation and drivers really can't do much wrong for FLUSH(_EXT) commands. It's just a non-data command which tells the drive to flush. Timeouts on it usually indicate that the problem is on the drive's side. libata.force=noncq kills the problem too, right? |