Resume from hibernate does not work

[Buddha001]

This is a new bug filed after commenting on bug #708286. My comments there were:

After upgrading from 10.10 to 11.04 this morning, I have the same
problem on a desktop system with an Intel Core-i7 920. Suspending to
disk works fine, but resuming hangs with a blank blue screen. The hard-
drive light is steady for a while as it presumably loads the hibernate
image, but then goes off and nothing happens. I have to hit Ctrl+Alt+Del
to reset the system, at which point it does a fresh boot and comes up
normally. Suspend to RAM works just fine. Suspend to disk used to work
fine with the grub command-line option of acpi_mode=nonvs. However, that
doesn't seem to work with Natty. Adding "nomodeset" doesn't help either.

It seems that everytime I do a distro upgrade either Resume from Sleep or Resume from hibernate does not work. It's either one or the other, so it's not the hardware because at various points, both have worked, just not simultaneously.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nigel 3054 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7ff8000 irq 45'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,14627593,00100004'
   Controls : 37
   Simple ctrls : 22
Date: Sat May 28 16:03:55 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e72b1a02-be53-4e4a-b746-a49f25b8640e
MachineType: MSI MS-7593
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=2a105d39-28d4-46c7-9136-f8cdce22a9c4 ro quiet nomodeset
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-05-07 (21 days ago)
WpaSupplicantLog:

dmi.bios.date: 05/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MSI X58M SLI (MS-7593)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd05/04/2009:svnMSI:pnMS-7593:pvr1.0:rvnMSI:rnMSIX58MSLI(MS-7593):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7593
dmi.product.version: 1.0
dmi.sys.vendor: MSI

[Buddha001 (ndrego)]

Update after upgrading to 11.10. The problem still exists (Suspend to RAM works and resumes no problem, Suspend to Disk works, but resume does NOT). The only difference is that now it actually says that it's loaded up the resume image successfully, but then sits there on that screen and never gets any further.

Any ideas?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Buddha001 (ndrego)]

Yup, I will try later this evening when I get home. Thanks.

[Buddha001 (ndrego)]

So I've tried 3.1-rc9 and 3.1.0-999-201110171146 (today's daily build) and both produce the exact same results as 2.6.38 and 3.0.1. I assume that trying older daily builds and release candidates will give the same results as well, so is it worth trying them?

I have a feeling this is video-driver (nvidia binary) related since I remember having to use various kernel options to make it work when it did work way back in 10.10. What sorts of debugging can be done related to the video driver? I've tried the nouveau driver in the past and just found it unacceptably slow to use.

[Buddha001 (ndrego)]

Well, I tried the nouveau driver last night as well after completely uninstalling the nvidia binary drivers and it only got worse. Resuming after a Suspend to RAM caused everything but the display to resume. I could SSH into the machine and do whatever, but the display would not return.

As for resuming after a Suspend to Disk, it behaved identically as to when I was using the nvidia binary drivers. Given that I went back to the nvidia binary since at least Suspend to RAM completely worked.

So maybe video card and driver interaction issue? Anything I might try along these lines? I currently have "nomodeset" as a kernel command line option. Any other options that might help?

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[Buddha001 (ndrego)]

I will try to. However, it seems bugzilla.kernel.org is down right now...

[penalvch (penalvch)]

Buddha001, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]