Jeff Garzik wrote:
Jeff Garzik wrote:
..
Output please? Did you get any failed-to-resume messages?
Same as in my original posting:
On resume from RAM, after a 30-second-ish timeout, the screen comes on
but the hard disk is NOT accessible. "dmesg" in an already-open window
shows this (typed in from handwritten notes):
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
sd 0:0:0:0: SCSI error: return code = 0x40000
end_request: I/O error, /dev/sda, sector nnnnnnn
(the nnnnnnn was actually a real number, different on each message).
..
Since this is claimed to be a regression, what was the last upstream
kernel version that worked for you? 2.6.16.x?
..
Also from the original posting:
My ata_piix based Notebook (Dell i9300) suspends/resumes perfectly (RAM or disk)
with 2.6.16.xx kernels, but fails resume on 2.6.17-rc5-git1 (the first 2.6.17-*
I've attempted on this machine).
It did NOT work any prior unpatched kernels before 2.6.16.xx.
Finally, if you could test the updated patch I posted, and/or the one
that is attached, that would be preferred.
--------------030508080204070708000504
Content-Type: text/plain;
name="patch"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="patch"
ZGlmZiAtLWdpdCBhL2RyaXZlcnMvc2NzaS9hdGFfcGlpeC5jIGIvZHJpdmVycy9zY3NpL2F0
YV9waWl4LmMKaW5kZXggNmRjODgxNC4uOTQ5ZDQ5NiAxMDA2NDQKLS0tIGEvZHJpdmVycy9z
Y3NpL2F0YV9waWl4LmMKKysrIGIvZHJpdmVycy9zY3NpL2F0YV9waWl4LmMKQEAgLTIwMSw3
...
Fix your mailer, please. Meanwhile, I'll try to extract the patch
and apply it, but for informational purposes only.
Linus's one-liner has us all beat.
Cheers
-
: 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
