| Summary: | after system halting there is a need for hard reset | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kamil Rytarowski <n54> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | csablak, davidwhodgins, mageia, wilcal.int |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Kamil Rytarowski
2012-04-01 22:40:54 CEST
William Kenney
2012-05-13 17:54:10 CEST
CC:
(none) =>
wilcal.int Confirmed Actually it goes to the Mageia Logo screen and hangs there. Only way out is via system warm reboot. Is this an upgrade, or a clean install. Have all updates been installed (urpmi --auto-select, not just those shown by mgaapplet)? CC:
(none) =>
davidwhodgins (In reply to comment #2) > Is this an upgrade, or a clean install. For me this is a brand new yesterday install on my SandyBridge i7 64-bit platform. Updated my local repo from mirrors.kernel.org just now then updated this install. Open a terminal, type halt and immediately, I think, it goes forever into suspend. Hard drives even spin down. Requires a warm boot ( reset button ) to get out of it. No harm seems to be done to the install. ctrl-alt-f2 is not responsive. can you boot without the option 'splash quiet' in grub and the shutdown the system if you see some errors ? (In reply to comment #4) > can you boot without the option 'splash quiet' in grub and the shutdown the > system if you see some errors ? Here's the last comment on the screen just before it locks up: [ 83.911131 ] System halted. Everything before it looks fine. colin, a systemd issue or another one ? CC:
(none) =>
mageia I can confirm it, it's valid here. Erm,,,, that's not a bug that's what's supposed to happen. If you want to power down your machine (e.g. turn it of via ATX style stuff) you should use "poweroff" not "halt". Status:
NEW =>
RESOLVED (In reply to comment #8) > Erm,,,, that's not a bug that's what's supposed to happen. If you want to power > down your machine (e.g. turn it of via ATX style stuff) you should use > "poweroff" not "halt". I actually don't have a problem with that. I just don't think it was widely used. (In reply to comment #8) > Erm,,,, that's not a bug that's what's supposed to happen. If you want to power > down your machine (e.g. turn it of via ATX style stuff) you should use > "poweroff" not "halt". I believe if there is a need to pull power cable to shutdown my computer after "halt", then there is something really wrong. (In reply to comment #11) > I believe if there is a need to pull power cable to shutdown my computer after > "halt", then there is something really wrong. Why? It is a specifically different command from "poweroff". Perhaps you're too young to remember but I remember the days when there was a physical button on my PC before the ATX power supply days. This is why there is a difference between the "halt" and "poweroff" commands today with the former providing a halt function (similar to the old days) and the latter a full halt+poweroff to make use of the new fangled ability to switch themselves off! :) I could patch systemd to make halt == poweroff but then there would be no distinction between the two commands and I'd need to find another way to debug shutdown issues for which the halt command is very useful. I consider it a bug that "halt" ever actually turned the power off. Read the man page of "poweroff" (or "halt") at level 8 of the manual for a description of the commands. I cannot fathom from this description why the three commands covered there (the third being "reboot") would be distinct and separate if the halt and poweroff did the same things. Anyway, I do not consider this a bug, but if you feel really strongly, please bring up this topic on the systemd mailing list and I'll happily honour the outcome of the discussions there. |