Bug 1902819 - systemd (pid 1) segfaults at system shutdown or reboot
Summary: systemd (pid 1) segfaults at system shutdown or reboot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks: F34BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2020-11-30 18:57 UTC by Adam Williamson
Modified: 2020-12-01 11:34 UTC (History)
13 users (show)

Fixed In Version: systemd-247.1-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-01 11:34:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2020-11-30 18:57:33 UTC
In current Rawhide, with systemd-247-1.fc34, systemd (pid 1) frequently segfaults on system shutdown or reboot.

openQA is running into this in several tests. Most obviously base_service_manipulation, which involves enabling/disabling services and rebooting several times, e.g. here's one such failure:

https://openqa.fedoraproject.org/tests/732376#step/base_service_manipulation/11

but it's also hitting other tests too sometimes. Several tests have to do a clean shutdown so they can upload disk images for other tests to use, and these are frequently hitting this bug too.

damjan says it's likely upstream issue https://github.com/systemd/systemd/issues/17768 that should be fixed by https://github.com/systemd/systemd/pull/17785 , but this is such a critical issue I don't really want to backport an unreviewed PR myself.

Proposing as a Beta blocker per "It must be possible to trigger a clean system shutdown using standard console commands" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Shutdown

Comment 1 Adam Williamson 2020-11-30 20:10:48 UTC
In https://openqa.fedoraproject.org/tests/7324005 I believe we hit a segfault on `systemctl isolate graphical.target`.

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-12-01 11:34:47 UTC
Should be OK now.


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