Bug 819520 - ext4 softlockup
Summary: ext4 softlockup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-07 13:20 UTC by fernandosj2k4
Modified: 2012-07-11 17:52 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-11 17:52:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
System messages (116.67 KB, application/octet-stream)
2012-05-07 13:20 UTC, fernandosj2k4
no flags Details

Description fernandosj2k4 2012-05-07 13:20:18 UTC
Created attachment 582662 [details]
System messages

Description of problem:
I have a 12core I7 PC, to run physics simulation, if I run a long time simulation, that bug occur. 
The system froze with a kernel message, and I need restart.
 
Version-Release number of selected component (if applicable):
 kernel 2.6.42.12-1.fc15.x86_64

How reproducible:

Just put a simulation code to run, after 10 days (more or less) that bug occur.

Steps to Reproduce:
1. run the simulation code
2. wait
3.
  
Actual results:


Expected results:


Additional info: 

Just to clarify, the pc configuration is: 12G memory, 12core, intel I7 and 4T hard disk. The simulation code use  16% of memory, the problem occur even I run in a single or multi core (parallel).

Comment 1 Dave Jones 2012-05-07 18:46:27 UTC
there are two separate problems here.

The first is that ext4 seems to have stalled doing io.
Added Eric to cc for his thoughts on that.


The second problem is the oops at the bottom of the logfile.
That one looks like it might be a random bitflip. We tried dereferencing something at 0x208, using an offset of 0x200 from register RAX which is '8'.
I think this was actually a zero that got corrupted, which got us passed a if (!null) test.

You might want to try running memtest86 on that hardware to rule out bad ram/power/cooling issues.

Comment 2 Josh Boyer 2012-06-07 18:06:50 UTC
Also, do you see this with 2.6.43/3.3?

Comment 3 Josh Boyer 2012-07-11 17:52:48 UTC
Fedora 15 has reached it's end of life as of June 26, 2012.  As a result, we will not be fixing any remaining bugs found in Fedora 15.

In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with.  Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered.

Thank you for taking the time to file a report.  We hope newer versions of Fedora suit your needs.


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