Ubuntu 12.04 hangs on shutdown

Bug #1002798 reported by Neil C Smith
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Extra information requested as per #991977

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-lowlatency 3.2.0-23.31
ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency 3.2.14
Uname: Linux 3.2.0-23-lowlatency x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 22 11:41:45 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lowlatency
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Neil C Smith (neilcsmith-net) wrote :
Revision history for this message
Neil C Smith (neilcsmith-net) wrote :

Extra info -

* System is a Dell Studio 1558 laptop.
* I'm using low-latency but get same behaviour with generic kernel.
* Only seems to happen when using fglrx. Open-source radeon driver hasn't triggered though has other issues for me.
* Seems far more likely to happen when on battery power than mains.
* Have switched off splash. When this bug happens there is a kernel oops and mention of DBus and flgrx. Will attempt to upload a photograph of the screen if/when it happens again.

Revision history for this message
penalvch (penalvch) wrote :

Neil C Smith, 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/daily/current/ . If the issue remains, please 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.

tags: added: needs-upstream-testing
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Neil C Smith (neilcsmith-net) wrote :

Screenshot of kernel panic message when this happens.

As mentioned, I'm now using the low-latency kernel, and have threadirqs set. It may be coincidence, but this error now hardly ever happens on mains power. Reproducible consistently on battery though.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.