Mark Lord wrote:
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
what is in dmesg _before_ that, though?
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.
Thanks.
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.
I resent it inline. Stupid Thunderbird, its never done that before.
Sorry about that.
If mine works, it is preferred, because that's what we need for 2.6.18+.
Jeff
-
: 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
