Bug 1029849

Summary: [abrt] systemd-204-16.fc19: crash: Process /usr/lib/systemd/systemd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: rh
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: johannbg, lnykryn, mschmidt, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:fbe821b19b85d17c6c98bbde6d6e77f80416b580
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-13 12:13:47 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 rh 2013-11-13 11:09:52 UTC 
Description of problem:
Occurs every once in a while on/after suspend-to-RAM. System shutdown/reboot is impossible afterwards.

Version-Release number of selected component:
systemd-204-16.fc19

Additional info:
reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd --switched-root --system --deserialize 20
crash_function: crash
executable:     /usr/lib/systemd/systemd
kernel:         3.11.4-201.fc19.i686
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 crash at ../src/core/main.c:142
 #4 log_struct_internal at ../src/shared/log.c:726
 #5 process_event at ../src/core/manager.c:1641
 #6 manager_loop at ../src/core/manager.c:1755
Comment 1 rh 2013-11-13 11:09:57 UTC 
Created attachment 823354 [details]
File: backtrace
Comment 2 rh 2013-11-13 11:10:02 UTC 
Created attachment 823355 [details]
File: cgroup
Comment 3 rh 2013-11-13 11:10:08 UTC 
Created attachment 823356 [details]
File: core_backtrace
Comment 4 rh 2013-11-13 11:10:12 UTC 
Created attachment 823357 [details]
File: dso_list
Comment 5 rh 2013-11-13 11:10:17 UTC 
Created attachment 823358 [details]
File: environ
Comment 6 rh 2013-11-13 11:10:22 UTC 
Created attachment 823359 [details]
File: limits
Comment 7 rh 2013-11-13 11:10:26 UTC 
Created attachment 823360 [details]
File: maps
Comment 8 rh 2013-11-13 11:10:30 UTC 
Created attachment 823361 [details]
File: open_fds
Comment 9 rh 2013-11-13 11:10:38 UTC 
Created attachment 823362 [details]
File: proc_pid_status
Comment 10 rh 2013-11-13 11:10:42 UTC 
Created attachment 823363 [details]
File: var_log_messages
Comment 11 Michal Schmidt 2013-11-13 12:13:47 UTC 
This looks like a kernel bug recently fixed in updates.

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