Comment 48 for bug 297058

Exactly the same as Tom Walsh: I get the same message as headlessspider, i.e. a timeout and then reset, during which time there is a level of unresponsiveness. Also exactly like Tom, this occurs fairly reliably a short while after unsuspending or powering on - last time it occurred there was a 4 minute delay between unsuspending and the timeout being reported in syslog. I won't post the output of dmesg unless someone wants it because it's pretty much the same as spider's, with the exception of the following line just before the EH finishes:

ata1.00: device reported invalid CHS sector 0

I am running the Lucid release candidate, 2.6.32-21-generic, the machine is a Samsung N140 netbook, and the disk as a Seagate ST9250315AS.