On Tuesday 17 August 2010 10:08:53 Tejun Heo wrote: > Hello, > > On 08/17/2010 09:51 AM, Stephan Diestelhorst wrote: > > On Thursday 05 August 2010 18:08:02 Tejun Heo wrote: > >> Can you please try the following patch and see whether the problem > >> goes away? > > > > I've finally managed to get this to compile and test. (Hit a bug with > > Debian's make-kpkg and other nuisances...) > > > > The problem is still there. On some resumes I get the dreadful dead > > disk again: > > > > end_request: I/O error , dev sda sector ... > > sd 0:0:0:0: [sda] Unhandled error code > > sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > > sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0e a4 77 a8 0 00 08 00 > > (many of those) > > > > Can't access /var/log/messages right now, due to broken I/O. Will try > > to trigger it again and check for the qc timeout messages.. > > Yeah, it would great to have the log. So, it seems like the hardware > is actually buggy then. :-( Indeed. Like I said, I have similar issues on a another Samsung HDD in an AMD system. I have not yet got around to try the fix there, but I suspect it is the same thing. I have attached the full /var/log/messages and /var/log/kern.log with multiple suspend-to-ram runs and the last one failing. Would it make sense to add Rafael's workaround upstream, maybe enabling it only for particular platforms / HDDs / with a parameter? Thanks, Stephan -- Stephan Diestelhorst, AMD Operating System Research Center stephan.diestelhorst@xxxxxxx, Tel. +49 (0)351 448 356 719 Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
Attachment:
messages_kern.log.tar.bz2
Description: application/bzip-compressed-tar
