Bug 716703 - Kernel panic after copying data to USB then ejecting
Summary: Kernel panic after copying data to USB then ejecting
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-26 14:19 UTC by David J. Fiddes
Modified: 2011-07-05 23:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-05 23:17:55 UTC
Type: ---


Attachments (Terms of Use)
Kernel oops when copying to USB stick then unmounting (13.85 KB, text/plain)
2011-06-26 14:19 UTC, David J. Fiddes
no flags Details
Second crash (3.80 KB, text/plain)
2011-06-26 18:07 UTC, David J. Fiddes
no flags Details

Description David J. Fiddes 2011-06-26 14:19:28 UTC
Created attachment 509964 [details]
Kernel oops when copying to USB stick then unmounting

Description of problem:

My machine has been experiencing regular hangs during operation since installing F15 (previously it's been rock solid). Been struggling to find a good way to reproduce. Seems that copying a large video file to a USB stick using GNOME the hitting Eject in Nautilus works best. Running Google Chrome or Thunderbird increase the likelihood of hitting the problem. Running complex compiles or watching HD video doesn't cause any problems.

The machine locks solid. Sometimes it ends up with a kernel oops backtrace on the console other times it just locks solid in X.

Version-Release number of selected component (if applicable):

kernel-2.6.38.8-32.fc15.x86_64

I've been able to hook up a serial connection to another machine to capture oops. I've attached a copy of the latest oops.

Comment 1 David J. Fiddes 2011-06-26 18:07:11 UTC
Created attachment 509984 [details]
Second crash

A further oops which looks to be the same bug but with a different backtrace. This occurred during ongoing use of the system which doggedly wouldn't crash using the mechanisms I was able to use earlier.

Comment 2 David J. Fiddes 2011-07-05 23:17:55 UTC
Oops. Ran memtest86+ found a dodgy DIMM. Removing the faulty parts seem to fix the problem.


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