Bug 1178051

Summary: [abrt] systemd: log_assert_failed_unreachable(): udevadm killed by SIGABRT
Product: [Fedora] Fedora Reporter: Henri Paasovaara <hpaasova>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f59b9af1fa270d12ae0b24ab08616f3d7e78b8cb
Whiteboard: abrt_hash:8e4290fbf85ffccf1766b9d2833e2a61b61e2b1b
Fixed In Version: systemd-216-16.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-21 23:02:54 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:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Henri Paasovaara 2015-01-01 20:54:24 UTC
Description of problem:
This happened at background so I am not sure what happened.
I removed encrypted swap partition and then created new on another location with disk tool. It could have caused this problem.

Version-Release number of selected component:
systemd-216-12.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        udevadm settle --quiet
crash_function: log_assert_failed_unreachable
executable:     /usr/bin/udevadm
kernel:         3.17.4-301.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (3 frames)
 #2 log_assert_failed_unreachable at ../src/shared/log.c:723
 #3 adm_settle.lto_priv.198 at ../src/udev/udevadm-settle.c:85
 #4 run_command at ../src/udev/udevadm.c:80

Comment 1 Henri Paasovaara 2015-01-01 20:54:28 UTC
Created attachment 975050 [details]
File: backtrace

Comment 2 Henri Paasovaara 2015-01-01 20:54:29 UTC
Created attachment 975051 [details]
File: cgroup

Comment 3 Henri Paasovaara 2015-01-01 20:54:30 UTC
Created attachment 975052 [details]
File: core_backtrace

Comment 4 Henri Paasovaara 2015-01-01 20:54:32 UTC
Created attachment 975053 [details]
File: dso_list

Comment 5 Henri Paasovaara 2015-01-01 20:54:34 UTC
Created attachment 975054 [details]
File: environ

Comment 6 Henri Paasovaara 2015-01-01 20:54:35 UTC
Created attachment 975055 [details]
File: limits

Comment 7 Henri Paasovaara 2015-01-01 20:54:36 UTC
Created attachment 975056 [details]
File: maps

Comment 8 Henri Paasovaara 2015-01-01 20:54:38 UTC
Created attachment 975057 [details]
File: open_fds

Comment 9 Henri Paasovaara 2015-01-01 20:54:40 UTC
Created attachment 975058 [details]
File: proc_pid_status

Comment 10 Henri Paasovaara 2015-01-01 20:54:41 UTC
Created attachment 975059 [details]
File: var_log_messages

Comment 11 Lennart Poettering 2015-01-08 01:00:37 UTC
Fixed upstream in git 2ac23519d04835e8d8dfbce3d08d9ff76db58a68

Comment 12 Fedora Update System 2015-01-19 19:23:31 UTC
systemd-216-16.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/systemd-216-16.fc21

Comment 13 Fedora Update System 2015-01-20 21:02:35 UTC
Package systemd-216-16.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-216-16.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-0916/systemd-216-16.fc21
then log in and leave karma (feedback).

Comment 14 Fedora Update System 2015-01-21 23:02:54 UTC
systemd-216-16.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.