On Sat, May 27 2006, Mark Lord wrote: > Jeff Garzik wrote: > >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? > > Nothing useful --> only the suspend-time messages from USB and whatnot. > > I'll crash it again now just to confirm that, though. > Give me another 10 minutes for the two reboots.. I'll go over this thread when I have better connectivity, but I cna say that the non-working solutions for me all involve the 0xef command first issued failing. The scsi messages above is just a result of the device being taken offline after failing, so not very interesting by themselves. -- Jens Axboe - : 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
