Bug 1021629

Summary: [abrt] systemd-204-16.fc19: crash: Process /usr/lib/systemd/systemd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrew <balabinav>
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, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:da41c0a43b74b1bb02d386bc2bbbd8e256034fcd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-21 18:27:26 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 Andrew 2013-10-21 16:48:05 UTC
Description of problem:
I've got this error, when resume system on my laptop after sleep.

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.PAE
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 crash at ../src/core/main.c:142
 #4 __strnlen_sse2 at ../sysdeps/i386/i686/multiarch/strlen-sse2.S:62
 #5 _IO_vfprintf_internal at vfprintf.c:1635
 #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:746
 #11 process_event at ../src/core/manager.c:1641
 #12 manager_loop at ../src/core/manager.c:1755

Comment 1 Andrew 2013-10-21 16:48:11 UTC
Created attachment 814702 [details]
File: backtrace

Comment 2 Andrew 2013-10-21 16:48:16 UTC
Created attachment 814703 [details]
File: cgroup

Comment 3 Andrew 2013-10-21 16:48:20 UTC
Created attachment 814704 [details]
File: core_backtrace

Comment 4 Andrew 2013-10-21 16:48:25 UTC
Created attachment 814705 [details]
File: dso_list

Comment 5 Andrew 2013-10-21 16:48:34 UTC
Created attachment 814706 [details]
File: environ

Comment 6 Andrew 2013-10-21 16:48:41 UTC
Created attachment 814707 [details]
File: limits

Comment 7 Andrew 2013-10-21 16:48:46 UTC
Created attachment 814708 [details]
File: maps

Comment 8 Andrew 2013-10-21 16:48:53 UTC
Created attachment 814709 [details]
File: open_fds

Comment 9 Andrew 2013-10-21 16:48:58 UTC
Created attachment 814710 [details]
File: proc_pid_status

Comment 10 Andrew 2013-10-21 16:49:04 UTC
Created attachment 814711 [details]
File: var_log_messages

Comment 11 Zbigniew Jędrzejewski-Szmek 2013-10-21 18:27:26 UTC
Yep, known problem.

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