I have the same symptoms on Kubuntu Lucid, amd64, kernel
"2.6.32-22-generic #33-Ubuntu SMP".  I also have an Asus K8V Deluxe
motherboard, with a Promise "PDC20378 (FastTrak 378/SATA 378) (rev 02)"
(according to lspci) SATA controller.

Suspending once works.  After resume, everything seems fine.  The following 
message appears in "kern.log" at resume (identical timestamps snipped):
May 16 08:57:37 chade kernel: [23999.040031] ata6.00: exception Emask 0x0 SAct 
0x0 SErr 0x0 action 0x6 frozen
May 16 08:57:39 chade kernel: [23999.040038] ata6.00: failed command: READ DMA 
EXT
[23999.040045] ata6.00: cmd 25/00:08:c0:ee:dc/00:00:39:00:00/e0 tag 0 dma 4096 
in
[23999.040047]          res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 
(timeout)
[23999.040050] ata6.00: status: { DRDY }
[23999.040057] ata6: hard resetting link
[23999.550041] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[23999.621420] ata6.00: configured for UDMA/133
[23999.621425] ata6.00: device reported invalid CHS sector 0
[23999.621430] ata6: EH complete

If I, later, try to suspend again, the screen goes black, but the
computer does not turn off; after several minutes the screen comes back
on at the console, where this message is displayed:

PM: some devices failed to suspend: error 13421773034217730
ata6.00: status { DRDY }
ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.00: failed command: STANDBY IMMEDIATE
ata6.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
 res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

(copied by hand, typos possible).
It sat there for at least 20 minutes. The machine was not responsive to any key 
combos or the soft-off button, so eventually I had to "hard-off."

-- 
Suspend only works once, dmesg shows errors about sata disk
https://bugs.launchpad.net/bugs/510246
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to