Bug 762398

Summary:	Panic while writing to SDCARD
Product:	[openSUSE] openSUSE 12.1	Reporter:	Juergen Weigert <jw>
Component:	Kernel	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jeffm
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	357354
Attachments:	screenshot of the panic

Description Juergen Weigert 2012-05-15 19:06:56 UTC

This is on a lenovo x60s, opensuse 12.1, kernel 3.1.9-1.4-desktop

Inserted a brand new 32GB micro-sd-card.
It appeared as /dev/mmcblk0p1 and was automatically mounted.

I used mlabel to change the volume label to JW2012_32GB
then I ran cp with a 5GB file to test write performance.

While the copy was ongoing, I entered a google search in Firefox. Upon hitting Enter the machine crashed.

Comment 1 Juergen Weigert 2012-05-15 19:08:17 UTC

Created attachment 490963 [details]
screenshot of the panic

Comment 2 Jeff Mahoney 2012-06-04 15:25:48 UTC

Can you reproduce this on demand? The problem is that the Oops isn't getting captured by your photo. It's BUG'ing while the fbcon takes a lock, causing the "scheduling while atomic" condition.

One way to track this down is to either not use the fbcon or to set up crash dumps to capture the oops. The current version of kdump in Factory allows the user to configure a mode to *only* capture the oops message, which makes the crash dump cycle that much faster. There's no yast support for it yet, though.

If you change KDUMP_DUMPFORMAT to "none" it will just capture the log.

Comment 3 Juergen Weigert 2012-06-24 15:01:37 UTC

It seems I cannot reproduce on demand.
Which file should contain the KDUMP_DUMPFORMAT setting? I cannot find it in /etc/*:w

Comment 4 Jeff Mahoney 2012-06-25 17:56:57 UTC

You'll need to install the kdump package and then /etc/sysconfig/kdump will exist. You'll also need to enable kdump. yast2-kdump is probably the easiest way -- but it doesn't yet support the "none" format.

Comment 5 Juergen Weigert 2012-08-23 10:02:32 UTC

I can no longer reproduce this with openSUSE 12.2 kernels.
Assuming its fixed.
Thanks for the details anyway, I guess I'll be able to produce proper logs if similar things happen again.