Bug 904525 – plasma-desktom: Random crashes with SIGBUS

Bug 904525 - plasma-desktom: Random crashes with SIGBUS


Summary:	plasma-desktom: Random crashes with SIGBUS

Status:	RESOLVED DUPLICATE of bug 905832

Classification:	openSUSE
Product:	openSUSE Tumbleweed
Classification:	openSUSE
Component:	KDE Workspace (Plasma)
Version:	NO 13.2 BUGS!!
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assigned To:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2014-11-08 21:44 UTC by Erwin Van de Velde
Modified:	2014-12-03 18:20 UTC (History)
CC List:	4 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erwin Van de Velde 2014-11-08 21:44:29 UTC

When running KDE, sometimes plasma-desktop crashes with signal 7, SIGBUS.

The crashes appear random and after a couple of hours of running KDE. When the crash occurs, restarting plasma-desktop does not work, keeps crashing over and over again. Best fix right now: restart KDE.

No special actions preceding the crash.

Comment 1 Christoph Feck 2014-11-17 18:31:16 UTC

This could be a kernel issue with btrfs, which is supposed to be fixed in 3.17.2. More information at the KDE bug https://bugs.kde.org/show_bug.cgi?id=340657

Comment 2 Erwin Van de Velde 2014-11-17 19:00:39 UTC

You are at least right that I am running on btrfs... did the same on 13.1 with same issue :)

Thanks for the follow-up and pointer to the other bug report, will update my findings when the 3.17.2 kernel hits Tumbleweed.

Comment 3 Josua Mayer 2014-11-20 08:37:38 UTC

This just happened to me on a fresh suse 13.2 install; it crashed, and then on every login;
update to kernel 3.16.7 from Kernel:/openSUSE-13.2 got me back in working mode.

Comment 4 Hrvoje Senjan 2014-11-21 18:25:01 UTC

let's watch what our kernel masters will say ;-)

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

Comment 5 David Sterba 2014-12-03 17:22:30 UTC

For the record, the crash is not caused by btrfs. The applications crash when using string functions that are implemented using the SSE instructions.

Comment 6 Christoph Feck 2014-12-03 18:20:40 UTC

David, then it would be SIGILL (illegal instruction), not SIGBUS (bus error). The crash is caused by a bug in btrfs not correctly handling mappings of sparse files. We also get this crash on 64 bit systems, which certainly handle all SSE instructions.