Bug 139765 - Kernel oops on usb disconnect
Summary: Kernel oops on usb disconnect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-17 22:00 UTC by Brian Daniels
Modified: 2016-03-27 14:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-05 05:48:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Log of kernel oops (3.95 KB, text/plain)
2004-11-17 22:00 UTC, Brian Daniels 		no flags Details
dmesg log (2.08 KB, text/plain)
2004-11-24 10:46 UTC, vvs 		no flags Details
View All

Description Brian Daniels 2004-11-17 22:00:02 UTC 
Description of problem:
Disconnecting external usb 2.0 dvd-burner causes oops.  Log attached.


How reproducible:
always

Steps to Reproduce:
1. Attach external DVD burner
2. mount, read files, umount
3. Unplug from usb port
4. boom.
  
Actual results:
Oops!

Expected results:
Disconnection and removal of mount point, system keeps working.

Additional info:
Motherboard is a MSI Neo2 Platinum plus (Socket 939) with Athlon 64
cpu.  Burner is a Sony DRX-510UL.  Kernel is stock 2.6.9-1.667
Comment 1 Brian Daniels 2004-11-17 22:00:54 UTC 
Created attachment 106919 [details]
Log of kernel oops
Comment 2 vvs 2004-11-24 10:45:15 UTC 
I have a similar situation with Plextor PX-708UF (firmware 1.08). When
I blank or write a RW disc and power off the writer after that, I get
a kernel oops.
Comment 3 vvs 2004-11-24 10:46:30 UTC 
Created attachment 107386 [details]
dmesg log
Comment 4 vvs 2004-11-24 10:47:52 UTC 
Forgot to mention that this happens with stock kernel and
2.6.9-1.681_FC3 as well.
Comment 5 Sitsofe Wheeler 2004-12-02 19:06:50 UTC 
This looks like a dup of bug 139665
Comment 6 petrosyan 2005-01-05 05:41:12 UTC 
this has been fixed in kernel-2.6.9-1.724_FC3
Note You need to log in before you can comment on or make changes to this bug.