unable to power off with kernel 2.6.31-21 generic

Bug #551121 reported by Warren
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

This is similar to several bugs reported in the past but just (re)appeared with kernel update from 2.6.31-20 generic to 2.6.31-21. It is clearly attributable to the kernel update. I can reboot the older kernel and it shuts down just fine. Boot the new kernel and the computer won't power off on shutdown.

Running 2.6.31-21 it won't power off from either a terminal window ($ shutdown now -P) or from the GUI.

Computer is a Dell Inspiron 9100 laptop, 2GB ram, Ubuntu 9.10.

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: warren 2433 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2472 @ 40), (3, 27)
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with STAC9750,51 at irq 17'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 38
   Simple ctrls : 24
Date: Mon Mar 29 11:28:01 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=ea6b8674-8863-415b-8dc7-948ca4b4d952
MachineType: Dell Inc. Inspiron 9100
Package: linux-image-2.6.31-21-generic 2.6.31-21.59
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-21-generic root=UUID=e4e7af30-dee4-40c6-8437-88e259a468fd ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-21-generic N/A
 linux-firmware 1.26
SourcePackage: linux
Uname: Linux 2.6.31-21-generic i686
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:2466): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2492): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2527): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:2491): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
 (firefox:2702): GLib-WARNING **: g_set_prgname() called multiple times
dmi.bios.date: 03/08/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0W1450
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd03/08/2005:svnDellInc.:pnInspiron9100:pvr:rvnDellInc.:rn0W1450:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 9100
dmi.sys.vendor: Dell Inc.

Revision history for this message
Warren (wseverin) wrote :
tags: added: karmic
Revision history for this message
Warren (wseverin) wrote :

I've gone back to kernel 2.6.31-20 until this bug gets sorted out. Problem on shutdown is I don't know *why* it won't power down. Is some disk left hanging? (etc.) I much prefer a clean power-down.

Revision history for this message
Steffen Neumann (sneumann) wrote :

Hi,

I can confirm this for my Desktop based on Intel Atom, D945GCLF2 Mainboard.
The computer power light is off, but fans are still running. I removed -21
and things went back to normal.

Yours,
Steffen

summary: - unable to power off from GUI or terminal shutdown
+ unable to power off with kernel 2.6.31-21 generic
Revision history for this message
Thomas Spitzlei (t-spitzlei) wrote :

Same here - after upgrade to 2.6.31-21, after powerdown harddisks going to sleep, system fans still blowing.

System:
CPU: P4 - 3.2GHz
Mainboard: Manufacturer: MICRO-STAR INC. MS-6728
RAM: 2 GB Kingston

When choosing 2.6.31-20 system correctly powers down.

Regards, Thomas

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Warren,

If you could also please 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.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Warren (wseverin) wrote :

Jeremy,

I installed the latest kernel I could find for Karmic and i386, according to the directions on the link provided. These files were installed:

linux-headers-2.6.34-020634rc2_2.6.34-020634rc2_all.deb
linux-headers-2.6.34-020634rc2-generic_2.6.34-020634rc2_i386.deb
linux-image-2.6.34-020634rc2-generic_2.6.34-020634rc2_i386.deb

All installed cleanly. On reboot the 2.6.34rc2 kernel was visible on the GRUB menu. Unfortunately, it was unbootable. Several attempts. Nothing but black screen with CPU running full bore, guessing by the fan speed. Once it got as far as the little black Ubuntu logo in the center of the black screen before hanging.

Perhaps there was a better choice of kernels to test?

-Warren

Revision history for this message
Warren (wseverin) wrote :

Jeremy,

I also tried the latest nightly build:

linux-headers-2.6.34-999_2.6.34-999.201004281008_all.deb
linux-headers-2.6.34-999-generic_2.6.34-999.201004281008_i386.deb
linux-image-2.6.34-999-generic_2.6.34-999.201004281008_i386.deb

That kernel boots fine, but the problem with shutdown persists. With that kernel I get a partial listing of actions on the screen as the kernel shuts down processes, ending with the line:
* Will now halt.

-Warren

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Zhuoluo Clark Yang (clarkyzl) wrote :

CPU: P4 - 3.0GHz
Mainboard: Manufacturer: ASUS P5GD1 Pro
RAM: 3 GB Geil

I also have the same problem, after upgrade to 2.6.31-21, the computer can not power off.
I configure the BIOS "ACPI 2.0 Support" to "Yes".
It is of no use.

Linux kernel 2.6.31-20 has no such a problem.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
Revision history for this message
Warren (wseverin) wrote :

OK, well, today I upgraded to Ubuntu 10.04 (Lucid). Kernel 2.6.32-22 generic. The problem is gone. The computer powers off on shutdown normally. Go figure. I just report the facts.

Revision history for this message
Zhuoluo Clark Yang (clarkyzl) wrote :

The same to Warren. After an upgrade to Ubuntu 10.04 . There is no such problem.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Warren,
     I am optimistically marking this Fix Released. If you encounter it again, please reopen the bug and give me a brief description of what happened.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Steffen Neumann (sneumann) wrote :

Jeremy, are you sure that's "fixed" ?

Both the bug title and karmic kernel are 2.6.31,
the "problem is gone" was after upgrading the full distribution,
including a new kernel 2.6.32 version.

People who continue to use karmic are left in the cold,
especially if security fixes roll in.

I'd vote to re-open this, unless it is fixed in 2.6.31

Yours,
Steffen

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Steffen,
     I understand your concern. My gut reaction is, as always to fix the issue. However, we are impacted in doing this by the SRU policy located here: https://wiki.ubuntu.com/StableReleaseUpdates

This change does not meet the criteria for SRU inclusion in Karmic, so I must consider it Fixed as it is working in Lucid. I hope this helps.

Thanks!

~JFo

Revision history for this message
Steffen Neumann (sneumann) wrote :

Um, but this bug report was on 2.6.31-21.59 back when
it was in -proposed.

It has entered -updates three days ago. Was that a SRU then ?

Should we have made the poweroff issue a blocker
for the SRU, because it is clearly a regression ?

Yours,
Steffen

Revision history for this message
Mustapha Mond (mustaphamond) wrote :

Jeremy,

does this mean that this bug will never be fixed in Karmic? Or do I just have to wait for 2.6.31-22 and revert the machines to 2.6.31-20 in the meantime?

Upgrading to Lucid is not an option right now.

-mustapha

Revision history for this message
Petar Kulić (cooleech-gmail) wrote :

Hi, all!

I'm having same problem with kernel 2.6.31-21-generic-pae, tho that one was yet good comparing it to latest kernel 2.6.31-22-generic-pae for Karmic. With kernel 2.6.31-21-generic-pae i had power down troubles, but not allways, and with kernel 2.6.31-22-generic-pae it is constant. PC just refuses to power down completly, fans keep on running. With kernel 2.6.31-20-generic-pae, everything works as it should (without any BIOS or any other modifications in any kernel case). I've just added acpi=force parameter to kernel 2.6.31-22-generic-pae, so i'm about to check it out now.

Post in few mins. Salut!

Revision history for this message
Petar Kulić (cooleech-gmail) wrote :

Back. Same problem. Parameter acpi=force didn't help, as it helps on some other Linux distros, with other kernels on old PCs.

Kernel 2.6.31-22-generic-pae just refuses constantly to make a complete shutdown, no matter what action i take (shutdown from terminal or GUI). Keeping my fingers crossed for kernel 2.6.31-23-generic-pae to come out soon, as i like to have latest kernel. Since that doesn't happen, im back to kernel 2.6.31-20-generic-pae. Luckely i kept it. :)

Salut from Croatia, Split!

Revision history for this message
Mustapha Mond (mustaphamond) wrote :

2.6.31-22 fixed this problem on half of my machines, the other half still doesn't powerdown properly.

I'd be glad to help by posting configurations, logfiles or by testing - but I have no idea where to go or whom to ask. Can anyone point me in the right direction?

TIA

-mustapha

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.