Bug 1274906

Summary: [abrt] systemd: link_entry_into_array_plus_one(): systemd-journald killed by SIGABRT
Product: [Fedora] Fedora Reporter: Justin Wheeler <fedora>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: fedora, geezuslucifer, johannbg, jsynacek, lnykryn, msekleta, paul.lipps, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bc3dba5ac9866ce88b5213527b3f144e74b35bb9
Whiteboard: abrt_hash:89185508ff95f8035adf28dbbf79317dcbc67f5c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-20 10:35:27 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: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Justin Wheeler 2015-10-23 19:38:34 UTC 
Description of problem:
This occurred while I was trying to use GNOME Boxes to make a Fedora virtual machine. It appears that there are severe issues on this device whenever I try to use Boxes for virtualization, and this time was the most severe of past events.

Steps:
1) Create virtual machine in Boxes
2) Wait while it starets up
3) Computer becomes slow and unresponsive, does not respond to clicks or keyboard presses
4) GNOME shell crashes
5) Later followed by NetworkManager and then systemd crashing (thereby logging me out)

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

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 link_entry_into_array_plus_one at src/journal/journal-file.c:1255
 #1 journal_file_link_entry_item at src/journal/journal-file.c:1284
 #2 journal_file_link_entry at src/journal/journal-file.c:1325
 #3 journal_file_append_entry_internal.constprop.119 at src/journal/journal-file.c:1368
 #4 journal_file_append_entry.constprop.111 at src/journal/journal-file.c:1450
 #5 write_to_journal at src/journal/journald-server.c:513
 #6 dispatch_message_real.lto_priv.238 at src/journal/journald-server.c:820
 #7 server_dispatch_message at src/journal/journald-server.c:918
 #8 server_process_syslog_message at src/journal/journald-syslog.c:377
 #9 server_process_datagram at src/journal/journald-server.c:1202

Potential duplicate: bug 1053292
Comment 1 Justin Wheeler 2015-10-23 19:38:41 UTC 
Created attachment 1085915 [details]
File: backtrace
Comment 2 Justin Wheeler 2015-10-23 19:38:42 UTC 
Created attachment 1085916 [details]
File: cgroup
Comment 3 Justin Wheeler 2015-10-23 19:38:43 UTC 
Created attachment 1085917 [details]
File: core_backtrace
Comment 4 Justin Wheeler 2015-10-23 19:38:44 UTC 
Created attachment 1085918 [details]
File: dso_list
Comment 5 Justin Wheeler 2015-10-23 19:38:45 UTC 
Created attachment 1085919 [details]
File: environ
Comment 6 Justin Wheeler 2015-10-23 19:38:47 UTC 
Created attachment 1085920 [details]
File: limits
Comment 7 Justin Wheeler 2015-10-23 19:38:48 UTC 
Created attachment 1085921 [details]
File: maps
Comment 8 Justin Wheeler 2015-10-23 19:38:49 UTC 
Created attachment 1085922 [details]
File: mountinfo
Comment 9 Justin Wheeler 2015-10-23 19:38:50 UTC 
Created attachment 1085923 [details]
File: open_fds
Comment 10 Justin Wheeler 2015-10-23 19:38:52 UTC 
Created attachment 1085924 [details]
File: proc_pid_status
Comment 11 Jan Synacek 2015-10-26 14:15:02 UTC 
Do you use X11 intel graphic card drivers? Do you still have logs from that boot? The description sounds more like the intel drivers crashes I've seen recently. I guess that abrt got confused when multiple things crashed in succession.
Comment 12 Justin Wheeler 2015-10-26 18:54:57 UTC 
(In reply to Jan Synacek from comment #11)
> Do you use X11 intel graphic card drivers? Do you still have logs from that
> boot? The description sounds more like the intel drivers crashes I've seen
> recently. I guess that abrt got confused when multiple things crashed in
> succession.

Hi Jan,

Yes, I do use the X11 Intel graphic card drivers. This laptop uses an Intel i3 with integrated graphics.

As far as more information goes, I think this bug *might* also be relevant, but I'm not positive. https://bugzilla.redhat.com/show_bug.cgi?id=1253249

Sorry for asking novice questions, but where would it be that I could find more information from the logs related to the graphics? I can probably track down the date and time if I knew where the system logs this and how to extract that info.
Comment 13 Justin Wheeler 2015-11-09 14:32:46 UTC 
Until otherwise stated, I believe requested info was provided. Removing needinfo flag.
Comment 14 Jan Synacek 2016-01-20 10:35:27 UTC 

*** This bug has been marked as a duplicate of bug 1300212 ***
Comment 15 Geezus 2016-04-14 17:22:45 UTC 
*** Bug 1327298 has been marked as a duplicate of this bug. ***