| Summary: | NOT Rebooting | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | chimilchim |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The Reboot signal is not sent to hardware.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-01 08:40:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
chimilchim
2012-01-26 09:29:30 UTC
dmesg prompts me with the error "add reboot signal not sent to hardware". Also, the "shutdown now" command does not yield any errors.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The Reboot signal is not sent.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-The Reboot signal is not sent.+The Reboot signal is not sent to hardware.
can you try booting with the option reboot=k ? (In reply to comment #4) > can you try booting with the option reboot=k ? I haven't tried that. But the solution from http://www.expertcore.org/viewtopic.php?f=20&t=3009 seemed to work. |