[regression 13.10] Can't reboot (but can shut down)

Bug #1244312 reported by Rebecca Palmer on 2013-10-24
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
upstart (Ubuntu)
Undecided
Unassigned

Bug Description

Since upgrading to 13.10, attempting to restart (with either "shutdown -r now" or the system menu item) hangs with a "reboot: restarting system" message instead of actually rebooting, but shutting down still turns the system off.

WORKAROUND: adding reboot=p to the kernel command line (https://wiki.ubuntu.com/Kernel/KernelBootParameters) avoids this bug.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: upstart 1.10-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Thu Oct 24 17:25:08 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-01-25 (637 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
SourcePackage: upstart
UpgradeStatus: Upgraded to saucy on 2013-10-21 (2 days ago)
UpstartBugCategory: System
UpstartRunningSessionVersion: init (upstart 1.10)
UpstartRunningSystemVersion: init (upstart 1.10)
modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny']
modified.conffile..etc.init.d.networking: [modified]
mtime.conffile..etc.init.d.networking: 2013-08-26T23:19:11
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: palmer 2534 F.... pulseaudio
 /dev/snd/controlC0: palmer 2534 F.... pulseaudio
 /dev/snd/pcmC0D0p: palmer 2534 F...m pulseaudio
DistroRelease: Ubuntu 13.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-01-25 (638 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Latitude E6520
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-10-21 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0J4TFW
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Rebecca Palmer (rebecca-palmer) wrote :
James Hunt (jamesodhunt) wrote :

Hi Rebecca,

Thanks for reporting this. The screenshot shows this to be a kernel issue, not an Upstart one. Reassigning...

affects: upstart (Ubuntu) → linux (Ubuntu)

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

apport-collect 1244312

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.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

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

description: updated

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

The reboot(8) man page says to file bugs against upstart; should that be changed?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete

I'm not comfortable with downloading a kernel from an insecure site (why isn't kernel-ppa a real PPA, where it would have https and signatures?), so I tested the upstream git head instead (https://wiki.ubuntu.com/KernelTeam/GitKernelBuild); it also had this bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream

Kernel 3.8.0-32 (the next newest on my boot menu, probably the Raring kernel) does not have this bug.

Both 3.8 and 3.11 work with reboot=p (https://wiki.ubuntu.com/BIOSandUbuntu#Reboot_Methods); 3.8 doesn't work with any other reboot=, which suggests the regression is caused by a change of default.

description: updated
James Hunt (jamesodhunt) wrote :

@Rebecca: yes, but the man page is referring to bugs in the reboot command. That commands calls the reboot system call and that is where the problem lies (in the kernel).

tags: added: bios-outdated-a18

Rebecca Palmer, as per http://www.dell.com/support/drivers/us/en/19/Product/latitude-e6520 an update is available for your BIOS (A18). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
description: updated
tags: added: regression-release

Closing the bug as I prefer not to risk bricking my system to fix something that has an easy workaround (and rumour suggests the FreeDOS method no longer works with recent Dell BIOS updates: http://askubuntu.com/questions/100945/how-do-i-update-the-bios-of-a-dell-laptop/237742#237742).

Changed in upstart (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.