Bug 724928
| Summary: | Reboot ends with kernel panic on systemd abort() | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zdenek Kabelac <zkabelac> | ||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | clydekunkel7734, harald, johannbg, lpoetter, mads, mailings, metherid, michal, mschmidt, nicolas.mailhot, notting, plautrba, robatino, sergei.litvinenko, tflink | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | AcceptedBlocker | ||||||
| Fixed In Version: | systemd-31-2.fc16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-08-05 18:36:44 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 713560 | ||||||
| Attachments: |
|
||||||
|
Description
Zdenek Kabelac
2011-07-22 10:44:28 UTC
upstream fix: http://cgit.freedesktop.org/systemd/commit/?id=3b8a1f3fee7bf83af5bbae541166508cf172b67c Discussed at the 2011-07-22 alpha blocker bug review meeting. Tentatively accepted as a Fedora 16 alpha blocker assuming that a proposal to modify the alpha release criteria is accepted. The installer must be able to complete an installation using the entire disk, existing free space, or existing Linux partitions methods, with or without encryption or LVM enabled. (In reply to comment #2) > Discussed at the 2011-07-22 alpha blocker bug review meeting. Tentatively > accepted as a Fedora 16 alpha blocker assuming that a proposal to modify the > alpha release criteria is accepted. > > The installer must be able to complete an installation using the entire disk, > existing free space, or existing Linux partitions methods, with or without > encryption or LVM enabled. I put the wrong proposed criterion in the previous comment. It was supposed to read: The systems' mechanisms for shutting down, logging out and rebooting from a virtual console must work. *** Bug 725158 has been marked as a duplicate of this bug. *** *** Bug 725253 has been marked as a duplicate of this bug. *** Created attachment 514935 [details]
shutdown panic from 3.0.0-1.fc16 kernel
Hm, got hit by the same but with kernel-3.0.0-1.fc16. Call trace is somewhat diffrent but pretty similar. Attached just in case. For one reason or another systemd is not crashing if I am rebooting with older kernels.
*** Bug 725999 has been marked as a duplicate of this bug. *** The proposed criterion under which this was accepted as a blocker has changed to: It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system. Since the criterion has changed, moving back to proposed blocker from accepted. Does this affect shutdown as well or is this just an issue with reboot? If I'm reading this right, it sounds like the systemd crash happens after storage devices have been taken offline safely. Can someone confirm this? Shutdown and reboot affected. Fixed with systemd-31-2.fc16. *** Bug 726462 has been marked as a duplicate of this bug. *** Discussed in the 2011-07-29 blocker review meeting. Accepted as F16 alpha blocker due to violation of the following alpha release criterion [1]: It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system. [1] https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria Verified as fixed in systemd-31-2.fc16. If the problem should re-appear, please re-open this bug. How can a kernel panic be fixed in systemd? I agree that a workaround in systemd is fine for an alpha release criteria, but is it really acceptable that systemd can cause the kernel to panic? Isn't that the real bug that should be solved? (In reply to comment #13) > How can a kernel panic be fixed in systemd? > > I agree that a workaround in systemd is fine for an alpha release criteria, but > is it really acceptable that systemd can cause the kernel to panic? Isn't that > the real bug that should be solved? Well aborting pid == 1 isn't really good idea, what should kernel do... The bug is already fixed in upstream systemd package. It's been obviously userspace problem. |