Bug 1027081

Summary: [abrt] systemd-201-2.fc18.8: crash: Process /usr/lib/systemd/systemd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Samuel Sieb <samuel-rhbugs>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a3b6b3a569d0774545dcc6930e39a6043d7b7f1d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-06 06:05:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 Samuel Sieb 2013-11-06 05:49:01 UTC
Description of problem:
systemd sometimes crashes after resuming from suspend.  This removes the systemd message bus and nothing much works after that.  NetworkManager can't communicate so all the network interfaces show up as unmanaged.  I can't even shutdown properly, the laptop has to be hard booted.

I've seen this on both F18 and F19, different laptops.

Version-Release number of selected component:
systemd-201-2.fc18.8

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd --switched-root --system --deserialize 19
crash_function: crash
executable:     /usr/lib/systemd/systemd
kernel:         3.11.4-101.fc18.i686.PAE
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 crash at src/core/main.c:141
 #4 free@plt at /lib/libc.so.6
 #5 _IO_vfprintf_internal at vfprintf.c:1615
 #6 ___vsnprintf_chk at vsnprintf_chk.c:63
 #7 ___snprintf_chk at snprintf_chk.c:35
 #8 snprintf at /usr/include/bits/stdio2.h:64
 #9 log_do_header at src/shared/log.c:441
 #10 log_struct_internal at src/shared/log.c:744
 #11 process_event at src/core/manager.c:1650
 #12 manager_loop at src/core/manager.c:1764

Potential duplicate: bug 1010506

Comment 1 Samuel Sieb 2013-11-06 05:49:06 UTC
Created attachment 820205 [details]
File: backtrace

Comment 2 Samuel Sieb 2013-11-06 05:49:10 UTC
Created attachment 820206 [details]
File: cgroup

Comment 3 Samuel Sieb 2013-11-06 05:49:14 UTC
Created attachment 820207 [details]
File: core_backtrace

Comment 4 Samuel Sieb 2013-11-06 05:49:17 UTC
Created attachment 820208 [details]
File: dso_list

Comment 5 Samuel Sieb 2013-11-06 05:49:23 UTC
Created attachment 820209 [details]
File: environ

Comment 6 Samuel Sieb 2013-11-06 05:49:27 UTC
Created attachment 820210 [details]
File: limits

Comment 7 Samuel Sieb 2013-11-06 05:49:31 UTC
Created attachment 820211 [details]
File: maps

Comment 8 Samuel Sieb 2013-11-06 05:49:34 UTC
Created attachment 820212 [details]
File: open_fds

Comment 9 Samuel Sieb 2013-11-06 05:49:38 UTC
Created attachment 820213 [details]
File: proc_pid_status

Comment 10 Samuel Sieb 2013-11-06 05:49:41 UTC
Created attachment 820214 [details]
File: var_log_messages

Comment 11 Samuel Sieb 2013-11-06 06:05:31 UTC
I guess I only searched systemd bugs...  Oh well, good to know there's a solution!

*** This bug has been marked as a duplicate of bug 1010603 ***