Ubuntu wakes up and immediately shuts down

[gpk]

Binary package hint: powernowd

Twice in a row, I've seen this with Karmic:

I use the laptop, plugged in, and close the lid. Put it away, still plugged in and powered.

I unplug it, walk to a chair, open it. I see a blank screen.
I hit the shift key.
Ubuntu then wakes up and immediately begins a shutdown (or perhaps a hibernation). Before my very eyes, it turns off.

I then need to hit the power button (which was darn, *not* blinking), to get it to boot. Soon, I am up and running again, but I should not have needed to reboot.

The bug involves the unintended shutdown.

Settings: In System->preferences->power management-> "On AC Power", "when laptop lid is closed" is set to "suspend".
In "On Battery", "when laptop lid is closed" is set to "shutdown". So, it all makes a fair amount of sense; it's just doing the wrong thing.

I would guess that it senses the laptop lid is closed, and stores that information when suspend happens. When it wakes, it probably still has the "lid closed" flag set, initially. Before it unsets that flag, though, it notices the "On Battery" flag, and says "Whoops! I should be shutting down." In other words, it looks like a race condition between the "On Battery" flag and the "lid closed " flag.

ProblemType: Bug
Architecture: amd64
Date: Sat Jan 2 17:25:31 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: powernowd (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: powernowd
Uname: Linux 2.6.31-17-generic x86_64

[der_vegi (m-may)]

Maybe this is related to bug 449430?

[gpk (gpk-kochanski)]

It does not seem exactly like 449430, but certainly it is similar. I see this in /var/log/syslog:

...
Jan 2 18:58:34 nglap NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Jan 2 18:58:34 nglap NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jan 2 18:58:34 nglap avahi-daemon[812]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.78.
Jan 2 18:58:34 nglap avahi-daemon[812]: New relevant interface wlan0.IPv4 for mDNS.
Jan 2 18:58:34 nglap avahi-daemon[812]: Registering new address record for 192.168.1.78 on wlan0.IPv4.
Jan 2 18:58:34 nglap avahi-daemon[812]: Registering new address record for fe80::21f:3aff:fe7d:bb7e on wlan0.*.
Jan 2 18:58:35 nglap NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Jan 2 18:58:35 nglap NetworkManager: <info> Policy set 'Auto zzzbbbfffgggBF03B7' (wlan0) as default for routing and DNS.
Jan 2 18:58:35 nglap NetworkManager: <info> Activation (wlan0) successful, device activated.
Jan 2 18:58:35 nglap NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 2 18:58:35 nglap ntpdate[2931]: adjust time server 91.189.94.4 offset -0.099688 sec
Jan 2 18:58:43 nglap kernel: [ 5016.362536] wlan0: no IPv6 routers present
Jan 2 18:58:48 nglap wpa_supplicant[919]: CTRL-EVENT-SCAN-RESULTS
Jan 2 18:59:08 nglap kernel: [ 5041.010062] Corrupted low memory at ffff880000001a78 (1a78 phys) = 896a2f0047000000
Jan 2 18:59:08 nglap kernel: [ 5041.010076] Corrupted low memory at ffff880000001a80 (1a80 phys) = f00000000800020
Jan 2 18:59:08 nglap kernel: [ 5041.010083] Corrupted low memory at ffff880000001a88 (1a88 phys) = fff8460ffff846
Jan 2 18:59:08 nglap kernel: [ 5041.010089] Corrupted low memory at ffff880000001a90 (1a90 phys) = 1a00000000763100
Jan 2 18:59:08 nglap kernel: [ 5041.010096] Corrupted low memory at ffff880000001a98 (1a98 phys) = 80000000c00100
Jan 2 18:59:08 nglap kernel: [ 5041.010121] ------------[ cut here ]------------
Jan 2 18:59:08 nglap kernel: [ 5041.010143] WARNING: at /build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xe5/0x100()
Jan 2 18:59:08 nglap kernel: [ 5041.010151] Hardware name: HP G6000 Notebook PC
Jan 2 18:59:08 nglap kernel: [ 5041.010155] Memory corruption detected in low memory
Jan 2 18:59:08 nglap kernel: [ 5041.010160] Modules linked in: cbc cryptd aes_x86_64 aes_generic binfmt_misc ppdev dm_crypt joydev snd_hda_codec_conexant arc4 ecb ath5k mac80211 led_class ath uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy psmouse serio_raw cfg80211 snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device i2c_nforce2 iptable_filter ip_tables x_tables nvidia(P) amd64_edac_mod snd k8temp soundcore snd_page_alloc edac_core lp parport video output forcedeth
Jan 2 18:59:08 nglap kernel: [ 5041.010262] Pid: 9, comm: events/0 Tainted: P 2.6.31-17-generic #54-Ubuntu
Jan 2 18:59:08 nglap kernel: [ 5041.010269] Call Trace:
Jan 2 18:59:08 nglap kernel: [ 5041.010287] [...

[gpk (gpk-kochanski)]

So, I guess it's a kernel bug, not powernowd

[Jeremy Foshee (jeremyfoshee)]

Hi gpk,

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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 502377

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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]