Bug 1297229

Summary: [abrt] systemd: __memcpy_sse2_unaligned(): systemd-journald killed by SIGABRT
Product: [Fedora] Fedora Reporter: Milan Bouchet-Valat <nalimilan>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bc6e1f7dec54426f135cbd7be994be4a4643308d
Whiteboard: abrt_hash:870ed33532787647e0e8a701a59ab91c9eff7be7;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-25 08:29:37 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Milan Bouchet-Valat 2016-01-10 21:51:28 UTC 
Description of problem:
When this happens, the whole GNOME session is suddenly closed.

Version-Release number of selected component:
systemd-222-12.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: __memcpy_sse2_unaligned
executable:     /usr/lib/systemd/systemd-journald
global_pid:     475
kernel:         4.3.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
 #1 memcpy at /usr/include/bits/string3.h:53
 #2 journal_file_append_entry_internal.constprop.119 at src/journal/journal-file.c:1356
 #3 journal_file_append_entry.constprop.111 at src/journal/journal-file.c:1450
 #4 write_to_journal at src/journal/journald-server.c:513
 #5 dispatch_message_real.lto_priv.238 at src/journal/journald-server.c:820
 #6 server_dispatch_message at src/journal/journald-server.c:918
 #7 stdout_stream_log at src/journal/journald-stream.c:266
 #8 stdout_stream_line.lto_priv.169 at src/journal/journald-stream.c:364
 #9 stdout_stream_scan at src/journal/journald-stream.c:394
Comment 1 Milan Bouchet-Valat 2016-01-10 21:51:35 UTC 
Created attachment 1113392 [details]
File: backtrace
Comment 2 Milan Bouchet-Valat 2016-01-10 21:51:36 UTC 
Created attachment 1113393 [details]
File: cgroup
Comment 3 Milan Bouchet-Valat 2016-01-10 21:51:38 UTC 
Created attachment 1113394 [details]
File: core_backtrace
Comment 4 Milan Bouchet-Valat 2016-01-10 21:51:39 UTC 
Created attachment 1113395 [details]
File: dso_list
Comment 5 Milan Bouchet-Valat 2016-01-10 21:51:40 UTC 
Created attachment 1113396 [details]
File: environ
Comment 6 Milan Bouchet-Valat 2016-01-10 21:51:42 UTC 
Created attachment 1113397 [details]
File: limits
Comment 7 Milan Bouchet-Valat 2016-01-10 21:51:43 UTC 
Created attachment 1113398 [details]
File: maps
Comment 8 Milan Bouchet-Valat 2016-01-10 21:51:45 UTC 
Created attachment 1113399 [details]
File: mountinfo
Comment 9 Milan Bouchet-Valat 2016-01-10 21:51:46 UTC 
Created attachment 1113400 [details]
File: namespaces
Comment 10 Milan Bouchet-Valat 2016-01-10 21:51:49 UTC 
Created attachment 1113401 [details]
File: open_fds
Comment 11 Milan Bouchet-Valat 2016-01-10 21:51:50 UTC 
Created attachment 1113402 [details]
File: proc_pid_status
Comment 12 Milan Bouchet-Valat 2016-01-10 21:51:53 UTC 
Created attachment 1113403 [details]
File: var_log_messages
Comment 13 Milan Bouchet-Valat 2016-01-10 22:02:10 UTC 
Upstream said at https://github.com/systemd/systemd/issues/1015 that systemd 223 included some journal-related changes which might fix this bug. Would it be possible to update to that version, or to backport the changes?
Comment 14 Michal Sekletar 2016-01-11 09:47:05 UTC 
Possible fix,

https://github.com/systemd/systemd/commit/dade37d403f1b8c1d7bb2efbe2361f2a3e999613
Comment 15 Milan Bouchet-Valat 2016-01-11 18:13:26 UTC 
I would be happy to test a package for a while if it can help.
Comment 16 Jan Synacek 2016-01-25 08:13:24 UTC 
To me, this looks like another duplicate of bug #1300212, but I'm going to backport the above patch anyway.
Comment 17 Jan Synacek 2016-01-25 08:29:37 UTC 
The patch mentioned in comment 14 is already present in F23.

*** This bug has been marked as a duplicate of bug 1300212 ***
Comment 18 Milan Bouchet-Valat 2016-01-25 09:19:00 UTC 
OK. It really looks like this timeout is a cause of trouble for many people...
Comment 19 Jan Synacek 2016-01-25 11:08:53 UTC 
You can check https://bodhi.fedoraproject.org/updates/FEDORA-2016-3d6ff41417, which contains a batch of fixes including the timeout increase.