Bug 622711 - after halt hang on cgroup
Summary: after halt hang on cgroup
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd   
(Show other bugs)
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-10 08:34 UTC by Marcela Mašláňová
Modified: 2010-08-11 19:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-11 19:26:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Marcela Mašláňová 2010-08-10 08:34:52 UTC
Description of problem:
After command 'halt' system hangs with this message:
umount2: device or resource busy
umount: /cgroup/systemd device is busy
...
Halting system...
Halting
System halted.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
The command 'reboot' now works fine. If you want fix it in upstream, it's fine but maybe you could create upstream snapshots for testing.

Comment 1 Michal Schmidt 2010-08-10 13:35:08 UTC
'halt' ends with "System halted".
'halt -p' ends with a powered down machine.
'poweroff' is the same as 'halt -p'.

Are you sure this is not the expected behaviour?
What is your expected behaviour of the 'halt' command?

Comment 2 Marcela Mašláňová 2010-08-11 06:21:55 UTC
Ok, man (written for upstart) says halt doen't poweroff. But 'halt' worked for me on all other F-13 machines ;-)

Comment 3 Bill Nottingham 2010-08-11 19:26:01 UTC
shutdown -h is supposed to alias to 'halt -p', IIRC. But if you just call 'halt', halting without poweroff is the standard behavior.


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