Bug 1151776

Summary:	[abrt] systemd: generic_array_bisect.lto_priv.166(): journalctl killed by SIGBUS
Product:	[Fedora] Fedora	Reporter:	Tomasz Torcz <tomek>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:10f588a4d7684ce9ee2354b6afe4235baa56ef98
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-09 02:27: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:

Description Tomasz Torcz 2014-10-11 19:10:16 UTC

Version-Release number of selected component:
systemd-215-19.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        journalctl _UID=1001 -b
crash_function: generic_array_bisect.lto_priv.166
executable:     /usr/bin/journalctl
kernel:         3.17.0-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 generic_array_bisect.lto_priv.166 at ../src/journal/journal-file.c:1631
 #1 generic_array_bisect_plus_one.lto_priv.167 at ../src/journal/journal-file.c:1746
 #2 journal_file_move_to_entry_by_offset_for_data at ../src/journal/journal-file.c:2125
 #3 next_for_match at ../src/journal/sd-journal.c:584
 #8 next_with_matches.lto_priv.164 at ../src/journal/sd-journal.c:812
 #9 next_beyond_location at ../src/journal/sd-journal.c:830
 #10 real_journal_next.lto_priv.184 at ../src/journal/sd-journal.c:887
 #11 sd_journal_next at ../src/journal/sd-journal.c:924

Comment 1 Zbigniew Jędrzejewski-Szmek 2014-10-12 15:04:26 UTC

Are there any disk read errors present in the logs?

Comment 2 Tomasz Torcz 2014-10-12 15:10:20 UTC

No errors in logs or in the filesystem:

$ btrfs dev stats /
[/dev/dm-0].write_io_errs   0
[/dev/dm-0].read_io_errs    0
[/dev/dm-0].flush_io_errs   0
[/dev/dm-0].corruption_errs 0
[/dev/dm-0].generation_errs 0

(it's btrfs over dm-crypt on samsung ssd 830).

Comment 3 Zbigniew Jędrzejewski-Szmek 2014-10-13 00:10:51 UTC

Is this repeatable? systemd-216-4 might improve things.

Comment 4 Lennart Poettering 2014-12-09 02:27:27 UTC


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