Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 000000000000011f; RIP: 0018:[<ffffffff81032919>] [<ffffffff81032919>] __ticket_spin_lock+0x9/0x20

[Anton]

On my HP EliteBook 6930p, running Ubuntu 11.10 (Oneiric) suspend and resume does not work properly.

Sometimes on suspend, and sometimes on resume, the machine completely freezes. Symptoms are:
- black screen
- cannot switch virtual terminals (aka Ctrl+Alt+F1)
- no response on Caps-Lock (Caps light does not change status)
- cannot reboot using Ctrl+Alt+Del
- kernel hotkeys do not work (e.g., Ctrl+Alt+SysRq+S does not lead to disk activity)
- sometimes, kernel 'boot' hotkey (Ctrl+Alt+SysRq+B) still works (but sometimes not)
- no flashing Caps lock (i.e., not a kernel panick)

It doesn't always happen, and it seems like the chances are higher if I use the machine more intensely. For example, yesterday after a day of video editing, the first resume already froze. Normally, I can get a number of suspend/resume cycles before the freeze.

So it was in lucid (10.4) , maverick, natty, and now oneiric (11.10).

Works in Precise.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: feenstra 2081 F.... pulseaudio
 /dev/snd/pcmC0D0p: feenstra 2081 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd8420000 irq 47'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30dc,00100400'
   Controls : 18
   Simple ctrls : 11
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=92c92b0a-05c8-423e-a01a-5e80e3b0af85
MachineType: Hewlett-Packard HP EliteBook 6930p
NonfreeKernelModules: fglrx
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron:
 LC_TIME=en_GB.utf8
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=d1d4f1ea-771e-4544-9e04-6e9a64bd9d84 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
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
StagingDrivers: mei
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-16 (22 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCD Ver. F.12
dmi.board.name: 30DC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.27
dmi.chassis.asset.tag: CZC9351JJ6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 6930p
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 887171

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

apport information

[Anton (feenstra)]

Did some testing yesterday as per https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume .

I can reproducibly get the hangup after 4-6 suspend/resume cycles, also from VT1 (using sudo pm-suspend). It does not matter whether I'm logged in to X or not, or how much memory is in use (tested by starting 2Gig Vbox Windows).

In most cases, the screen first blanks and then the freeze occurs. In one case, the freeze was first, and I could catch the kernel oops - see attached blurry photo (blame Samsung for the crappy camera in the Galaxy Mini). I'm assuming the other cases also involve an oops, but not visible. In both cases, the emergency sync hotkey (Ctrl+Alt+SysReq+S) does not trigger disk activity, and caps-lock is unresponsive (which are about the the only feedbacks one might still get with a blanked screen).

Also, when resuming after suspend from VT1, the screen remains blank till I switch to VT7 (X).

In several cases, I saw a 'Battery Critical, going to Hybernate' message, though my battery at that moment was still >60%.
In one case, after the Battery Critical, I got the oops. In another case, I got a spontaneous reboot. In yet another case, it actually did hibernate. But in most cases, there was only the message and no hybernation...

I've captured dmesg three times after boot after the freeze.

1) after Battery Critical -> kernel oops; suspend/resume 4 times from VT1 while logged in on X
2) after black screen and freeze (could be another oops); suspend/resume 5 times from VT1 while not logged in on X
3) after spontaneous reboot; suspend/resume 4 times from VT1 while not logged in on X

[Anton (feenstra)]

Next, I'm gonna try a suggested workaround from
http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug
This inserts a script in pm/sleep.d to unload ehci and xhci drivers (whatever they may be) on suspend (and presumable reload them on resume). Will get back with that!

[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 . If possible, please test the latest 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.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

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

Thanks in advance.

[Anton (feenstra)]

I'll give it a try. Just to be sure, 'latest' means downloading from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

Except for the obvious point of eliminating possibilities, are there any concrete reasons to hope that this kernel version will solve the problem? - seeing that it's been there for a number of Ubuntu releases already...

[Anton (feenstra)]

I just tested the mainline kernel (as per #31) - 3.2.0-999.201111080407 doesn't boot - any other options there?

I also tested the ehci/xhci workaround - did not make a difference as far as I can see.

Next I can think of is disabling hibernate - in a number of cases (about 1 in 4) I see a message "Battery Critical -> going to Hybernate" perhaps that screw things up. (Now I just have to remember how to do that.)

[Joseph Salisbury (jsalisbury)]

Anton,

Can you try the mainline kernel available at:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc1-oneiric/

The release candidates are generally tested more than the daily builds.

[jms (jmschlenker)]

I have a very similar problem -- actually it seems to be the same -- on an EliteBook 2540p runing Oneiric.

[toey (toey)]

I am having the same problem on an EliteBook 8440p running Linux Mint Debian Edition.

toey@toey-work ~ $ uname -a
Linux toey-work 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux

[toey (toey)]

Are you guys running with SSD's?

[Scott Garman (sgarman)]

I'm happy to report that I can no longer reproduce this bug with the Beta1 release of Precise Pangolin on my HP Elitebook 6930p, which includes kernel 3.2.

Additionally, users of Oneiric can install this kernel using this PPA repository - ppa:francisbrwn9/kernels

[toey (toey)]

LMDE Update Pack 4 will include kernel 3.2.... waiting patiently for that :)

[toey (toey)]

I lost my patients and added the relevant sources in order in update my system to LMDE Update Pack 4 which includes kernel version 3.2.

I'm happy to announce that the issue is no longer present since the update :)

Sources for LMDE Update Pack 4 can be found at: http://www.webupd8.org/2012/03/linux-mint-debian-update-pack-4-on-way.html

Now I just need to get used to gnome3 :( not liking it so far... ill give her a bit of a chance though :P

[penalvch (penalvch)]

Anton, thank you for reporting this and helping make Ubuntu better. 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Anton (feenstra)]

Dear Christopher, as of two weeks I am running Ubuntu Precise beta 2. As Scot wrote in #37, the bug does not occur anymore. I think that means it is fixed in mainline, but would like a confirmation of that before I add the tag as you describe.

Is there any other information that I should submit for reference?

[Anton (feenstra)]

Just tried mainline kernel, but could not suspend. The menu button did not work, and neither did sudo pm-suspend.

(I had all sorts of other glitches as well running mainline, like unity reverting to 2D, and after reboot into normal kernel, I could not connect to wireless. Another reboot just fixed that...)

So, I suppose I should now add 'kernel-unable-to-test-upstream'?
I guess I'll just do it, please correct if wrong.

[Anton (feenstra)]

Just to be complete, I tested linux-image-3.4.0-999-generic_3.4.0-999.201205060405_amd64

[penalvch (penalvch)]

Anton, 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc5

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.

[penalvch (penalvch)]

Hi Christopher, Thanks for getting back on this. I can add that the problem, unfortunately, still occurred in the 12.04 LTS of Ubuntu on that laptop (HP Elitebook). Since the problem is related to (excessive) swapping, I thought simply adding more RAM would be a workaround (it had 4Gb). But my University didn't want to buy new ram for an old laptop, so they got me a Dell Precision with 8Gb. I'm still running 12.04 LTS, and even with memory more or less maxed out I never had the problems I had with the HP Elitebook. The HP Elitebook is with a coleague now, so if this really needs tracking down, I could ask him to do some tests. Will that be worth the effort?

It would be up to your colleague, if the problem is still reproducible. This bug report is being closed due to your last comment regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.