Bug 14432 - 'systemctl poweroff' no longer shuts down system
Summary: 'systemctl poweroff' no longer shuts down system
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL: https://bugs.freedesktop.org/show_bug...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-02 16:23 CET by Luc Menut
Modified: 2014-11-07 20:19 CET (History)
0 users

See Also:
Source RPM: systemd-217-2.mga5
CVE:
Status comment:


Attachments

Description Luc Menut 2014-11-02 16:23:45 CET
Description of problem:
Since update to systemd 217 today, poweroff or 'systemctl poweroff' doesn't shutdown the system, instead, it reboots. This happens on two systems (2 Dell computers, one desktop and one laptop) where I have Cauldron.
This bug is already reported on systemd-devel ML
http://lists.freedesktop.org/archives/systemd-devel/2014-October/024707.html


Version-Release number of selected component (if applicable):
systemd 217


Reproducible: 

Steps to Reproduce:
Comment 1 Luc Menut 2014-11-02 16:28:35 CET
oups, first mail in the thread is
http://lists.freedesktop.org/archives/systemd-devel/2014-October/024704.html
Comment 2 Luc Menut 2014-11-02 19:33:44 CET
upstream bug report
https://bugs.freedesktop.org/show_bug.cgi?id=85724

URL: (none) => https://bugs.freedesktop.org/show_bug.cgi?id=85724

Comment 3 Colin Guthrie 2014-11-03 10:17:36 CET
Hmm, interesting... Seems from the ML that the user reporting it is on v210 of systemd... but the bug report definitely mentioned 216 and 217 versions, so I guess we have to assume systemd indeed is to blame here. I'll see what i can find.
Colin Guthrie 2014-11-03 10:17:49 CET

See Also: (none) => https://bugs.freedesktop.org/show_bug.cgi?id=85724

Comment 4 Colin Guthrie 2014-11-04 10:50:42 CET
So annoyingly I cannot reproduce here, with latest systemd+kernel. Tried a few times this morning and all poweroff's were real poweroffs. I am using UEFI tho', which might change these things. Will keep an eye on things as the upstream bug report seems to have a user who is pretty good at poking around at things. If you can help out in that regard comments here or there are appreciated that might offer any insights :)
Comment 5 Colin Guthrie 2014-11-07 11:46:53 CET
So, at least one cause was found upstream for this behaviour. I'm not 100% sure I'm convinced it's the only cause, but could you check the latest build and see if it works for you.

If you are using systemd in your initrd, (which, if I read the upstream report correctly, is a pre-requisite for this behaviour), then don't forget to rebuilt it with dracut -f.

Let me know how you get on.
Comment 6 Luc Menut 2014-11-07 16:36:18 CET
(In reply to Colin Guthrie from comment #5)
> So, at least one cause was found upstream for this behaviour. I'm not 100%
> sure I'm convinced it's the only cause, but could you check the latest build
> and see if it works for you.

I've just tested on the laptop, and poweroff works fine now with systemd-217-6.mga5. I will test tonight the other affected computer at home.

> 
> If you are using systemd in your initrd, (which, if I read the upstream
> report correctly, is a pre-requisite for this behaviour), then don't forget
> to rebuilt it with dracut -f.
> 
> Let me know how you get on.

It is fixed even without rebuilding the initrd.

Thanks for your help.
Comment 7 Luc Menut 2014-11-07 20:19:01 CET
poweroff works fine on my second system, so closing.

Thanks.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.