Red Hat Bugzilla – Bug 1470646
[abrt] systemd: crash(): systemd killed by signal 11
Last modified: 2018-05-03 03:56:33 EDT
Version-Release number of selected component:
cmdline: /usr/lib/systemd/systemd --switched-root --system --deserialize 25
runlevel: N 5
Thread no. 1 (6 frames)
#1 crash at src/core/main.c:190
#3 set_remove at src/basic/set.h:61
#4 bidi_set_free at src/core/unit.c:428
#5 unit_free at src/core/unit.c:559
#6 manager_clear_jobs_and_units at src/core/manager.c:1052
#7 manager_reload at src/core/manager.c:2796
Created attachment 1297536 [details]
Created attachment 1297537 [details]
Created attachment 1297538 [details]
Created attachment 1297539 [details]
Created attachment 1297540 [details]
Created attachment 1297541 [details]
Created attachment 1297542 [details]
Created attachment 1297543 [details]
Created attachment 1297544 [details]
Created attachment 1297545 [details]
Created attachment 1297546 [details]
*** Bug 1470557 has been marked as a duplicate of this bug. ***
Hm, that's pretty tough. The crash happens during freeing, but really the error was much earlier, when something was improperly set or freed or something like that. Do you maybe have more log messages from before the crash, anything that would indicate some anomalous situation?
Created attachment 1297657 [details]
Journalctl -b -2
I added to the attachments whole output from journalctl from the session, where error occured.
Also I don't know if this information will be helpful, but this error occurred in first boot after update to Fedora 26.
I don't see anything telling in the logs. systemd runs, daemon-reload is requested, it crashes. I'm sorry, we'll just have to wait. If this repeats, then we'll know more.
You've got a lot of thermal throttling going on, so it's *possible* that there's was a hardware fault.
The thermal throttling was caused by gnome-shell using too much CPU on Wayland. After restart I didn't see that high load again, so I'm not sure what caused it.
I will let you know if the error occurs again.
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.