Greg Freemyer wrote: > On Thu, Feb 19, 2009 at 1:21 AM, Tejun Heo <tj@xxxxxxxxxx> wrote: >> Hello, >> >> Chuck Ebbert wrote: >>>> Yeap, SD_TIMEOUT should be it. But I've never personally seen disk >>>> flushing taking as long as 30 seconds. Does it really happen? It's >>>> not like the drive would be doing random seeking. One full stroke >>>> across the platter should be it. Even with the rotational delay, >>>> going over 30 seconds doesn't seem very likely. >>> I just noticed that the other drive, a Western Digital, was using 1.5Gbps >>> instead of 3.0. So I forced the Samsung to the slower speed and now I >>> can't make the timeout happen anymore. >> Timeouts are much more likely with the higher transfer speed but it's >> kind of strange for flush cache to be affected by it as the command >> doesn't have any data to transfer. :-( > > I have not been following this thread, but those jumpers normally > reduce the feature set from SATA-II to SATA-I as well. > > So it could be an issue with a SATA-II feature. ncq? Hmmm... maybe. Chuck, can you please use "libata.force=1.5Gbps" instead of the jumper and see whether the problem reappears? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
