Bug 716703

Summary: Kernel panic after copying data to USB then ejecting
Product: [Fedora] Fedora Reporter: David J. Fiddes <d.j>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-05 23:17:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Kernel oops when copying to USB stick then unmounting
none
Second crash none

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.