Computer Reboots Instead of Halting

Bug #1499556 reported by Ed Novak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

With Ubuntu 14.04 LTS, everytime I try to shutdown my system reboots instead. I have tried a variety of shutdown methods including:
sudo init 0
sudo shutdown -P now
sudo shutdown now
sudo shutdown -h now
sudo shutdown -H now
sudo shutdown -HP now
(all previous variants with "now" replaced with "1")
shutting down via the KDE menu (clicking the menu, clicking 'leave' section, clicking shutdown in the dialog box).

The system hard shuts down if I hold the power button for 5 seconds.

I have attached a zip of my entire /var/log directory.

---
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: kubuntu
DkmsStatus: fglrx-core, 15.200, 3.16.0-50-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:9832]
InstallationDate: Installed on 2015-08-21 (53 days ago)
InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150219.1)
LightdmGreeterLog:
 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: fglrx
Package: xorg 1:7.7+1ubuntu8.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic root=UUID=13cf69b2-83fd-4907-ba34-fa3e24e8294a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
Tags: trusty kubuntu
Uname: Linux 3.16.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 10/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: QC5000-ITX/PH
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 13 20:01:14 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
xserver.video_driver: fglrx

Revision history for this message
Ed Novak (ejnovak) wrote :
Ed Novak (ejnovak)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Ed Novak, thank you for reporting this and helping make Ubuntu better. Could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1499556

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ed Novak (ejnovak) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Ed Novak (ejnovak) wrote : BootLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : Dependencies.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : DpkgLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : LightdmLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : Lspci.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : Lsusb.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : ProcModules.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : UdevDb.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : UdevLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : XorgLog.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : XorgLogOld.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : Xrandr.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : xdpyinfo.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : xserver.devices.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : xserver.errors.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote : xserver.outputs.txt

apport information

Revision history for this message
Ed Novak (ejnovak) wrote :

Chris,

Sorry I didn't answer sooner. For some reason I didn't get an email when you commented on this thread (probably went to spam or something). Anyway, I ran the suggested command and it barfed the above ~20 comments :). Hopefully that helps!

Also, I noticed a quirk about this bug. If I have done a recent package update/upgrade (via cli or the muon update manager) I will sometimes get a normal shutdown (not a reboot) afterwords. It seems to be if there is an updated kernel, but I can't see that with 100% confidence yet. I haven't been watching the updates / reboot problem closely enough.

penalvch (penalvch)
tags: added: latest-bios-1.00
removed: performance
penalvch (penalvch)
description: updated
Changed in xorg (Ubuntu):
importance: Low → Medium
Revision history for this message
Ed Novak (ejnovak) wrote :

I have installed and tested with 3.19.0-30-generic (and 3.16.0-50-generic, what I had before) and neither have them have solved the problem. Still when I try to shutdown, the system reboots only. Sometimes now it will reboot without my USB mouse / keyboard working. I'm not sure why, or which kernel, but it did happen once or twice. If hard reset / shutdown they come back. It's probably an unrelated quirk, but I like to mention everything I notice since I know what debugging is like.

Revision history for this message
penalvch (penalvch) wrote :

Ed Novak, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

Revision history for this message
Ed Novak (ejnovak) wrote :

Chris,

I have downloaded the 64-bit image from the given link and I can CONFIRM that the bug is present in the daily image (grabbed it just an hour ago). Please advise :)

Also, please call me Ed.

Revision history for this message
penalvch (penalvch) wrote :

Ed, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: wily
Revision history for this message
Ed Novak (ejnovak) wrote :

Chris,

Thank you for working with me so closely on this issue! I know it may seem tedious, but to me it's very annoying and I would love to have the issue fixed.

I have tried Kernels 4.3-rc7, 4.3-rc6, and 4.3-rc5 Unfortunately, all of them exhibited the reboot / shutdown bug. I have not had a chance to move down the list and frankly, I am a bit reluctant to.

When I switched to these kernels, for some reason it introduced some bugs / problems that corrupted my .KDE folder and I had to reset it (which was very annoying). I also had to switch off of the fglrx driver as it is not supported / built for the newest unstable kernels apparently.

Is there anyway I can continue to test the kernels listed here: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D with some live media so that I don't affect my current install of Ubuntu? I would love to aid the community in continuing to help track down and fix this but. Not having a working .kde profile (and messing with the drivers via tty1) is not my idea of usable! :P I'm afraid that continuing to try other kernels will have adverse effects on other parts of my system.

Thank you again, looking forward to your advice on how to move forward.

Ed Novak (ejnovak)
tags: added: kernel-bug-exists-upstream-4.3-rc7
Changed in xorg (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ed Novak (ejnovak) wrote :

I can confirm the bug exists in 4.3 (and 4.3-rc7). I marked the bug as confirmed (as previously directed). Please let me know what I can do next to help solve this problem! :)

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream-4.3
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ed Novak (ejnovak) wrote :

I can confirm the bug exists on 4.4-rc2 To be specific, here is the uname: Linux livingroom 4.4.0-040400rc2-generic #201511231054 SMP Mon Nov 23 10:56:43 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

If you want me to test a different version, like 4.4 (not 4.4-rcX). Please let me know specifically what version and by what day. Or, if there is anything else I can do to avoid this "back and forth" in the future, please let me know.

Thanks again.

tags: added: kernel-bug-exists-upstream-4.4-rc2
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream
removed: kernel-bug-exists-upstream-4.3 kernel-bug-exists-upstream-4.3-rc7
Revision history for this message
penalvch (penalvch) wrote :

Ed, to clarify, if you uninstall fglrx, is this issue still reproducible with the default Ubuntu kernel?

Also, is this issue not reproducible with either an older kernel or release?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ed Novak (ejnovak) wrote :

I am able to reproduce the bug on all of the kernels mentioned in this thread with EITHER the radeon or the fglrx driver. In other words, having fglrx or radeon installed doesn't matter, and it seems that the kernel doesn't matter either. No matter what, I can reproduce the bug. Below is a list of all the kernels I've tested. For every kernel, I tried using radeon and fglrx.

4.4-rc2
4.3-rc7
4.3-rc6
4.3-rc5
4.3

3.16.0-53-generic
3.16.0-52-generic
3.16.0-51-generic
3.16.0-50-generic

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Ed Novak (ejnovak) wrote :

I recently tested this with the latest ubuntu 16.04 beta 2 image and I have the same behaviour.

I've also tested with several variants of the acpi kernel parameter including acpi=off, acpi=strict, and acpi=oldboot none changed the behaviour except for acpi=off. When this parameter was set, I was able to press the power button to shutdown but the system shuts down _immediately_ and I'm fairly certain the OS hasn't even flushed to disk yet, so that's not a good workaround.

Revision history for this message
Ed Novak (ejnovak) wrote :

<b>Workaround</b> and update that may aid in debugging.

I have learned recently (through extensive testing) that pm-hibernate works flawlessly! As a workaround I set KDE to hibernate when the power button is pressed and not ask for a password on resume. Now I can press the power button and the machine "hibernates" which, for some reason, successfully gets the computer to poweroff instead of just rebooting.

I followed this guide to enable hibernation on KDE in Ubuntu 14.04 LTS: https://help.ubuntu.com/14.04/ubuntu-help/power-hibernate.html Don't forget you have to reboot the machine before the settings take effect, and I had to set the .pkla file rwx for everybody (i.e., sudo chmod 777 /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla ). Then it worked great.

The settings for the power button in KDE are in systemsettings -> power management -> energy saving and systemsettings -> power management -> advanced settings

Please keep me posted if this bug every gets fixed, but I'm happy to have found a better workaround than always holding the power button for 5 seconds to force a poweroff.

Revision history for this message
penalvch (penalvch) wrote :

Ed Novak, to keep this relevant to upstream, could you please test the latest mainline kernel (4.7-rc6) and advise to the results?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Ed Novak (ejnovak) wrote : Re: [Bug 1499556] Re: Computer Reboots Instead of Halting
Download full text (4.8 KiB)

The problem seems to have gone away after I switched out my power supply
with a different one. I guess the bug is mobo, psu, and kernel dependent.

The old one was this: http://www.corsair.com/en-us/tx750w

The new one: http://www.newegg.com/Product/Product.aspx?Item=N82E16817256097

--
-Ed

On Sat, Jul 9, 2016 at 2:53 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Ed Novak, to keep this relevant to upstream, could you please test the
> latest mainline kernel (4.7-rc6) and advise to the results?
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1499556
>
> Title:
> Computer Reboots Instead of Halting
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> With Ubuntu 14.04 LTS, everytime I try to shutdown my system reboots
> instead. I have tried a variety of shutdown methods including:
> sudo init 0
> sudo shutdown -P now
> sudo shutdown now
> sudo shutdown -h now
> sudo shutdown -H now
> sudo shutdown -HP now
> (all previous variants with "now" replaced with "1")
> shutting down via the KDE menu (clicking the menu, clicking 'leave'
> section, clicking shutdown in the dialog box).
>
> The system hard shuts down if I hold the power button for 5 seconds.
>
> I have attached a zip of my entire /var/log directory.
>
> ---
> ApportVersion: 2.14.1-0ubuntu3.15
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: kwin
> CurrentDesktop: KDE
> DistUpgraded: Fresh install
> DistroCodename: trusty
> DistroRelease: Ubuntu 14.04
> DistroVariant: kubuntu
> DkmsStatus: fglrx-core, 15.200, 3.16.0-50-generic, x86_64: installed
> GraphicsCard:
> Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330]
> [1002:9832] (prog-if 00 [VGA controller])
> Subsystem: ASRock Incorporation Device [1849:9832]
> InstallationDate: Installed on 2015-08-21 (53 days ago)
> InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150219.1)
> LightdmGreeterLog:
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> such file or directory
> QFileSystemWatcher: failed to add paths:
> /var/lib/lightdm/.config/ibus/bus
> Bus::open: Can not get ibus-daemon's address.
> IBusInputContext::createInputContext: no connection to ibus-daemon
>
> file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
> Unable to assign [undefined] to QString usersession
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: fglrx
> Package: xorg 1:7.7+1ubuntu8.1
> PackageArchitecture: amd64
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic
> root=UUID=13cf69b2-83fd-4907-ba34-fa3e24e8294a ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
> Tags: trusty kubuntu
> Uname: Linux 3.16.0-50-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm c...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Ed Novak, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499556/comments/41 regarding this being resolved by swapping power supplies. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Ed Novak (ejnovak) wrote :
Download full text (5.0 KiB)

Thanks

--
-Ed
On Jul 9, 2016 6:00 PM, "Christopher M. Penalver" <
<email address hidden>> wrote:

> Ed Novak, this bug report is being closed due to your last comment
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499556/comments/41
> regarding this being resolved by swapping power supplies. For future
> reference you can manage the status of your own bugs by clicking on the
> current status in the yellow line and then choosing a new status in the
> revealed drop down box. You can learn more about bug statuses at
> https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
> to report this bug and helping to make Ubuntu better. Please submit any
> future bugs you may find.
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1499556
>
> Title:
> Computer Reboots Instead of Halting
>
> Status in linux package in Ubuntu:
> Invalid
>
> Bug description:
> With Ubuntu 14.04 LTS, everytime I try to shutdown my system reboots
> instead. I have tried a variety of shutdown methods including:
> sudo init 0
> sudo shutdown -P now
> sudo shutdown now
> sudo shutdown -h now
> sudo shutdown -H now
> sudo shutdown -HP now
> (all previous variants with "now" replaced with "1")
> shutting down via the KDE menu (clicking the menu, clicking 'leave'
> section, clicking shutdown in the dialog box).
>
> The system hard shuts down if I hold the power button for 5 seconds.
>
> I have attached a zip of my entire /var/log directory.
>
> ---
> ApportVersion: 2.14.1-0ubuntu3.15
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: kwin
> CurrentDesktop: KDE
> DistUpgraded: Fresh install
> DistroCodename: trusty
> DistroRelease: Ubuntu 14.04
> DistroVariant: kubuntu
> DkmsStatus: fglrx-core, 15.200, 3.16.0-50-generic, x86_64: installed
> GraphicsCard:
> Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330]
> [1002:9832] (prog-if 00 [VGA controller])
> Subsystem: ASRock Incorporation Device [1849:9832]
> InstallationDate: Installed on 2015-08-21 (53 days ago)
> InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150219.1)
> LightdmGreeterLog:
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> such file or directory
> QFileSystemWatcher: failed to add paths:
> /var/lib/lightdm/.config/ibus/bus
> Bus::open: Can not get ibus-daemon's address.
> IBusInputContext::createInputContext: no connection to ibus-daemon
>
> file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
> Unable to assign [undefined] to QString usersession
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: fglrx
> Package: xorg 1:7.7+1ubuntu8.1
> PackageArchitecture: amd64
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic
> root=UUID=13cf69b2-83fd-4907-ba34-fa3e24e8294a ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 3.16.0-50.67~1...

Read more...

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.