Hard hang on resume from suspend

[Michael Thayer]

Every so often, I will suspend my laptop and get a hard hang with a blank screen when I resume. Last time but one Alt-Sysrq-C worked (judging by the flashing keyboard LEDs), last time (a few minutes ago) it didn't. So far I have failed to get any information on the hang. I tried installing a crash kernel, but it hasn't got me a crash dump yet (though I was able to trigger one manually), and needless to say there is nothing in the system log.

There is a chance that this is related to VirtualBox, as I have the current development code running on this system. At the moment I would most appreciate clues as to how to debug this (unfortunately netconsole isn't really an option as it happens so unpredictably, and most often when I don't have a second system available anyway).

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 1892 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6960000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:111d76d5,1028040a,00100104 HDA:14f12c06,14f1000f,00100000 HDA:80862804,80860101,00100000'
   Controls : 19
   Simple ctrls : 11
Date: Thu Nov 10 22:15:11 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Dell Inc. Latitude E6410
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=062b1769-7309-4422-a59c-ad30b109d53c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (44 days ago)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/23/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

Do you know if this issue happened in previous version of Ubuntu, or is this a new issue?

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 . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[Michael Thayer (michael-thayer)]

Certainly, I will do that, though it may take a while as the problem is rather irregular, so I won't just be able to say straight off that it is solved or not (plus there is always the Heisenbug factor). And as I said, if you can think of any ways I could get more information about this to debug it myself please let me know! I do have some kernel debugging and development experience.

[Michael Thayer (michael-thayer)]

That went a bit faster than I expected - I had a hang with at least what looked like the same symptoms within an hour of trying out 3.2.0rc1.

[Michael Thayer (michael-thayer)]

Afraid I can't seem to add or remove tags myself.

[Michael Thayer (michael-thayer)]

I didn't realise that the Ubuntu kernels don't enable the lockup detectors. I have recompiled a kernel with the detectors enabled and no other changes (I hope) and will see if that produces more information.

[Michael Thayer (michael-thayer)]

Finally had the problem with my self-built kernel, and ran into the error shown here [1]. Perhaps you should work on making this a bit easier (as in the lockup detector enabled by default and the crash kernel correctly (!) installed), so that it works automatically when Apport is enabled.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/14

[Michael Thayer (michael-thayer)]

I tried applying the workaround from this comment [1] and will see if I get a core next time.

[1] https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/785425/comments/13

[Michael Thayer (michael-thayer)]

By the way, I take it that I shouldn't need to enable Apport to get the crash dump, should I? Apport just automatically reports it.

[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 [1]? 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.

The bugzilla.kernel.org site may still be unavailable due to the recent break-in. If that is the case, please add the tag: kernel-needs-upstream-bug-report

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[jhoechtl (johann-hoechtl)]

I had suspend/hibernate resume kernel OOOps on a DELL E6410 with Intel display chipset and i5 processor.

As of kernel 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64
I can reliably suspend/hibernate resume.

[Lazy (ubuntu-bugs-oittaa)]

This started to happen on my Lenovo X220 after upgrading from 11.10 to 12.04. I didn't see this bug report first so I created a new one: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/977135

[Michael Thayer (michael-thayer)]

Just got a hang after resume on 3.5.0-17-generic on Precise. Rather unfortunate that CONFIG_BOOTPARAM_*LOCKUP_PANIC are not set in the default kernel configuration - is there a reason why you consider it better to hang the machine than to panic it? It seems to me that enabling those options and installing a crash kernel by default might be a good idea for preventing this sort of problem. Is there any chance of you changing these options in the near future before Precise is actually released? Otherwise I will build a kernel again and hope that I see the hang again in the near future.

[Michael Thayer (michael-thayer)]

Created bug #1090488 for this.

[penalvch (penalvch)]

Michael Thayer, 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, but the one all the way at the bottom) 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.]