With edgy resume from suspend to disk worked fine on my laptop.
With feisty (hda is now sda with ata_piix), it comes up, but pauses exactly 30 seconds:
Trying to resume from
/dev/disk/by-uuid/57d93b3d-299d-4731-becb-9bd598f0289f
# which is my swap space
[ 6.972000] Attempting manual resume
[ 6.972000] Disabling non-boot CPUs ...
[ 6.972000] Stopping tasks ... done
[ 7.172000] Shrinking memory... done (0 pages freed)
[ 7.192000] Freed 0 kBytes in 0.04 seconds (0.00 MB/s)
# Nothing seems to happen here - disk is busy
[ 37.192000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 37.192000] ata1.00: cmd c8/00:08:10:27:01/00:00:00:00:00/e2 tag 0cdb 0x0 data 4096 in
[ 37.192000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 37.192000] ata1: soft resetting port
[ 37.356000] ata1.00: ata_hpa_resize 1: sectors = 1563001488, hpa_sectors = 156301488
[ 37.364000] ata1.00: ata_hpa_resize 1: sectors = 1563001488, hpa_sectors = 156301488
[ 37.364000] ata1.00: configured for UDMA/100
[ 37.364000] ata1: EH complete
[ 37.372000] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[ 37.372000] sda: Write Protect is off
[ 37.372000] Loading image data pages (122967 pages) ...
<5>SCSI device sda: write cache: enabled, read cache: enabled, doesn't suppport DPO or FUA
There MAY be in typos in here, as these messages are NOT in the logs
when the system is up and running gain - I will file another bugreport
for this issue. Had to take a picture of my screen to get hold of
these messages.
Kind regards
Gerd
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Could you please also add the picture you took as an attachment to your bug report?
For your reference, the full description of procedures for kernel-related bug reports is available at https:/