Indan Zupancic wrote: > On Sat, May 19, 2007 21:04, Tejun Heo wrote: >> Tejun Heo wrote: >>> Yeah, if SCR registers are accessible, 0xff doesn't indicate the device >>> isn't there, so the whole skip-0xff logic probably shouldn't apply in >>> such cases, but we can also achieve pretty good result by just making >>> the first reset tries a bit more aggressive. >> So, here's the patch. >> >> Paul, can you please test this patch without the previous patch? Indan, >> this should reduce the resume delay. Please test. But you'll still >> feel some added delay compared to 2.6.20 due to the mentioned >> suspend/resume change. > > This removed the COMRESET errors indeed, and with sd_resume() > disabled everything is speedy again (2s or so. Still a desktop pc). > I didn't try with sd_resume enabled. Can you try to measure with sd_resume in place? > Everything seems to work fine without sd_resume(), so why is it needed? Because not all disks spin up without being told to do so and like it or not spinning disks up on resume is the default behavior. As I wrote in the other reply, it would be worthwhile to make it configurable. -- 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
