Unexpected power-off during boot or when resuming from suspend

Hi Anoop,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, 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 588194

Also, please be sure to take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . If you can provide any additional information outlined there it would be much appreciated.

Additionally, if you could try to reproduce this with the upstream mainline kernel 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. Thanks in advance.

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

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

On Karmic, upgrading from kernel 2.6.31-21 to the recently available 2.6.31-22 causes the bug to appear in Karmic as well.

I also confirm that this happens in the latest Fedora 13 (Live CD), so it appears to be an upstream bug.

The problem seems related to the way ubuntu hibernation work.
The problem disappeared after installing "tux on ice" version of kernel suspend to disk implementation (using version at ppa:tuxonice/ppa):

$> uname -r -v
2.6.32-22-generic-tuxonice #36~ppa2-Ubuntu SMP Sat Jun 5 02:21:24 UTC 2010

It appears to be an acpi issue since passing acpi=off has made the problem go away (at least so far). I've also tried passing acpi=noirq , acpi=oldboot , noapic , nolapic , noirq (of course one at a time) - but none of those helped. Turning off the entire acpi stack seems extreme and I'd rather not do it. Besides, turning off acpi causes my touchpad to stop working.

Tried the latest mainline kernel 2.6.34-lucid with no luck.
The 'tux on ice' kernel also has the same problem.

Hi, I have to confirm this bug on a Dell Vostro V13. I'm running Arch Linux however (kernel 2.6.35.5-1 / 2.6.35-ARCH). Just to inform that it's not a strictly ubuntu-bug :). I'll keep searching and looking to this thread.

Same problem on a freshly installed & updated Maverick beta (AMD64 version).

I forgot to mention two things:
- it is on the same hardware than the original reporter (Dell Vostro V13)
- in my case it is much more frequent than once every 7 or 8 suspends, actually I've never been able to successfully suspend more than twice.

Confirm problem. But this problem not only hibernate and suspend but on usual loading after shutdown.
dell vostro v13, ubuntu 10.04

Using the debugging procedure outline here: https://wiki.ubuntu.com/DebuggingKernelSuspend
I got the following lines in dmesg:
[ 0.713876] Magic number: 0:898:740
[ 0.713880] hash matches /build/buildd/linux-2.6.35/drivers/base/power/main.c:586

Anybody knows what it means?

I did some more testing and although it seems several devices cause suspend/resume problems, the biggest issue is with bluetooth and usb.
I went to the bios settings and disabled all the integrated devices. In that configuration I did 10 suspend/resume cycles without problem.
Then I started enabling a few devices. With WLAN enabled I had one lock-up out of 10 suspend/resume cycles, but it was a lockup during suspend, not during resume, so it is probably another issue.
However enabling bluetooth makes it impossible to suspend/resume more than once or twice (after the second resume, the machine powers off during resume).
But the strangest thing is this: disabling bluetooth but enabling outside USB ports systematically triggers the unexpected power off during boot, the system becomes unbootable.

Seems like this issue has fixed itselfs. Since my latest system update, the computer boots up perfect again. It's not like I'm rebooting my laptop every day, but the few times I started it from halt steed up again, it went perfect.

The updates that fixed it:
upgraded cairo (1.8.10-1 -> 1.10.0-2)
upgraded libgl (7.8.2-1 -> 7.8.2-3)
upgraded intel-dri (7.8.2-1 -> 7.8.2-3)
upgraded kernel26 (2.6.35.6-1 -> 2.6.35.7-1)
upgraded kernel26-headers (2.6.35.6-1 -> 2.6.35.7-1)
installed glproto (1.4.12-1)
upgraded mesa (7.8.2-1 -> 7.8.2-3)
upgraded qt (4.6.3-1 -> 4.7.0-2)
upgraded xf86-input-evdev (2.4.0-2 -> 2.5.0-1)
upgraded xf86-input-synaptics (1.2.2-2 -> 1.3.0-1)
upgraded xf86-video-intel (2.12.0-1 -> 2.12.0-3)
upgraded xf86-video-vesa (2.3.0-2 -> 2.3.0-3)
upgraded xkeyboard-config (1.8-1 -> 1.9-1)
installed xorg-server-common (1.9.0-1)
upgraded xorg-server (1.8.1.902-1 -> 1.9.0-1)
upgraded xterm (261-1 -> 262-1)

Kenneth: your comment that the issue is fixed is for Arch Linux, right?
On Ubuntu I've tried mainline kernels, and the good news is that the currently available 2.6.36-rc6 kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc6-maverick/) almost fixes the issue: I still observe these unexpected poweroffs during resume, but much less often; and the bluetooth-applet disappears after resume, although bluetooth is working fine.
I also tried the 2.6.35.7 mainline kernel, which does not fix the problem.

Yep, so I'm guessing it has something to do with the kernel or the intel videodrivers (as the problem did not occur when I put i915.modeset=0 in grubs kernelline). As you didn't get a fix with your 2.6.35.7 it might be the intel videodriver that is causing our trouble. Maybe you can try the very latest intel driver available for Ubuntu?

It didn't fix it completely, it's just less frequent now :(.

Same here, with the 2.6.36 mainline kernel, in real-world usage I still observe the unexpected poweroff quite often, around once in two or three suspend/resume cycles. It seems that if the machine remains suspended for a while it is much more likely to occur.

I've been testing the 2.6.31-22-generic kernel (from Karmic) on my Maverick install, up to now I've *not* observed a single poweroff. I'll update this bug in a few days to confirm it really works with that kernel.
(the only issue is that the internal microphone doesn't seem to work with that kernel).

I can confirm that the problem occurs on 2.6.31-22-generic kernel on my Karmic (as I have mentioned earlier in comment #18). I have at times experienced a dozen good resumes before the problem appears again. It does not occur at the same frequency. So even after several successive good resumes, I have experienced the bug in quick succession afterwards.

Currently, the only good config that works for me is 2.6.31-14-generic on Karmic. Installing linux-backports-modules-alsa-2.6.31-14-generic makes the internal microphone work on that kernel.

Thanks for the tip, indeed the alsa backport fixes the mic. I'll keep testing the kernels.

Also note that this machine is Ubuntu Certified:
http://webapps.ubuntu.com/certification/hardware/201004-5578/

The page says that it is certified for 10.04 LTS, but the 2.6.31 Karmic kernel is the last known to work. I think the certificacion should be removed while this bug is not fixed.

I just tested with the recently uploaded 2.6.35.22 maverick kernel: I've not experienced the poweroff issue, but that's because the machine fails to suspend... Either it hangs in a semi-suspended state (but the LCD backlight is still on) and has to be hard-reset, or it just attempts to suspend and immediately wakes up.

gpothier: Are the unexpected poweroffs during boot gone with 2.6.35.22 maverick kernel?

Yes, they still occur during boot with 2.6.35.22.
I've still not had a single problem with Karmic's 2.6.31-22, though.

I have the problem on my Dell Vostro v13 with Ubuntu 10.04 and 10.10.
In the 10.10 release the bug is less frequent.

I just tested the 2.6.37-rc1 mainline kernel, the problem still occurs.
I created an upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=22462

has anybody seen this issue before upstream kernel 2.6.33.1?
(ie the stable upstream release, not the ubuntu release)
if yes, can you tell us about it at the upstream bug report?

https://bugzilla.kernel.org/show_bug.cgi?id=22462

hi, the same problem with 3 V13 with ubuntu 10.10!!! How can help you!!!

I put the results of a kernel bisect in the upstream bug report.

same issue on my dell vostro v13, I just submitted this kernel bug, cause I've seen this later:
https://bugzilla.kernel.org/show_bug.cgi?id=24192

My team find a solution, but it is not the solution to the error, it may hibernate:

sudo apt-get install hibernate uswsusp

then edit

vim /etc/uswsusp.conf

resume device = /dev/sda5 "swap space"
splash = n
compress = y
early writeout = y
RSA key file = /etc/uswsusp.key
shutdown method = shutdown

then

sudo s2disk

not is nice but working!!!!

I also have the same problem.

actual kernel 2.6.32.25 + 2.6.32.26 (tried both)

It took me some month to realize the problem, because for me the "power off" at boot came very sporadically. Until today the 2nd try was always successful, but a few moments ago I had to boot 10 times to see the login-screen only at the last attempt.

From my observations the problem seems to get worse with any kernel update.

sorry, forgot to add:

I have of course also a Dell Vostro V13.

In order to solve the problem I upgraded the bios version from A01 to A05, no effect.

in natty, with latest kernels (i guess the last two maybe), the computer NEVER resumes from suspend, and I can't get the login screen much more times.
This is a huge problem, the Ubuntu Certification should be removed until this is fixed, or people (like me) continue to buy laptops and they become unsatisfied from Ubuntu once they understand that they bought incompatible hardware.

Same bug with my Dell Vostro V13 and Ubuntu 10.10 64 bits.

I'm very disappointed because of the certification wich is visible on your website. I hope that you are resolving this important bug.

With a more recent Linux Kernel (2.6.37), the bug doesn't appear as frequently as with the standard kernel. Since I install this new RC Kernel, I don't have the bug when I start my computer, only one time when resuming from suspend.

I install this Kernel from this website : http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-rc2-maverick/

I have the same problem. My kernel version is 2.6.35.24-generic on Ubuntu 10.10. I recently upgraded from 2.6.35-22-generic. I have not really found a pattern when it suspend forces a power down and when not.

I experience the same bug on my Dell Vostro V13 laptop. I installed Ubuntu 10.10 on an external USB hard drive.
On boot, I have to try on average three times to have a succesful boot. The two other times, the computer shut downs unexpectedly before displaying the Ubuntu splashscreen.
I tried several kernel version, to no avail (currently running 2.6.37 rc2).

This bug was solved for me when applying a patch proposed for a different bug : https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/380126 (problem with the synaptic touchpad on the same computer model.
Apparenlty it is due to bad interrupts by the touchpad.
Hope this helps.

Thanks a lot for the link Nicolas.

If someone is interrested, you can find the kernel 2.6.35-25.43 compiled with this patch in my website : https://www.isorez.fr/ftp

Kernel packages are for amd64 (compiled in my vostro v13 with Intel T7300). There is also a synaptics package in order to enable the multi touch of the touchpad.

Hope this helps. ;)

After the upgrade to Kernel 2.6.32-27 the bug didn't occure for some time, but today the powerdown happened once more.

Sorry, the bug also effect:

Ubuntu Kernel 2.6.32-27-generic

Hope the bug is fixed soon...
If I can help by testing a new patch for Kernel 2.6.32, please contact me.

I have a V13 notebook and the same problem happen using Debian 6.0 (kernel 2.6.32 AMD64) in power on and back to suspend and hibernate.
During the boot messages, I see an ACPI error:
ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]

A "lspci" show:
00:1f.3 SMBus: Intel Corporation 82801I (IHC9 Family) SMBus Copntroller (rev 03)

Other references to 0000:00:1f.3 on dmesg:
[ 0.203876] pci 0000:00:1f.3: reg 10 64bit mmio: [0x000000-0x0000ff]
[ 0.203899] pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
[ 3.688520] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 19 (level, low) -> IRQ 19
[ 3.688529] ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]

Since I added "acpi=off" in kernel line (on grub conf), this problems (power off during boot and ACPI error message) was solved. But I can't suspend/hibernate anymore... =/

I'm downloadind natty-alpha1 to test.

Forgot to mention: the touchpad does not work in Xorg with "acpi = off" - probably something related to comment 54

I've installed the kernel from #55 (thanks!) and it seems to have cured the boot problem as well as providing synaptic support.
Suspend/hibernate are both working. (V13, SU3500)

It seems that this bug is triggered by the following commit, which has been tested to fix the issue on Maverick. This fix is already in Natty, and has been proposed for SRU to Maverick:

  commit f8313ef1f448006207f12c107123522c8bc00f15
  Author: Jiri Kosina <email address hidden>
  Date: Sat Jan 8 01:37:26 2011 -0800

    Input: i8042 - introduce 'notimeout' blacklist for Dell Vostro V13

    i8042 controller present in Dell Vostro V13 errorneously signals spurious
    timeouts.

    Introduce i8042.notimeout parameter for ignoring i8042-signalled timeouts
    and apply this quirk automatically for Dell Vostro V13, based on DMI match.

    In addition to that, this machine also needs to be added to nomux blacklist.

    Signed-off-by: Jiri Kosina <email address hidden>
    Signed-off-by: Dmitry Torokhov <email address hidden>

This fix is being rolled out under Bug #380126.

The poweroff bug still occurs on Natty as of today, so the touchpad fix doesn't seem to also fix the poweroff bug.

Same error appear after fix touchpad bug.

Here, no more problems using kernel 2.6.35-25-dellv13 (thanks Nicolas Becker and Burin_Khazad - comments 54 and 55) and the multitouch trackpad works fine. Using the official natty kernel, it poweroff again and the multitouch doesn't work.

I have the same problem using Kubuntu 10.10 64bit with kernel 2.6.35-25 on my Dell Vostro v13.
About each second boot fails with a power-off.
When I find the time, I'll test Burin_Khazeds kernel, too.

The kernel from maverick-proposed seems to have solved this issue for me, but has also introduced an occurrence of the symptoms described at bug #34501