Bug 786164 - CD/DVD-Rom stop working after a while
Summary: CD/DVD-Rom stop working after a while
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-31 15:59 UTC by G. Michael Carter
Modified: 2012-09-04 15:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-04 15:51:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
System Details (12.64 KB, text/plain)
2012-01-31 15:59 UTC, G. Michael Carter
no flags Details

Description G. Michael Carter 2012-01-31 15:59:52 UTC
Created attachment 558638 [details]
System Details

Description of problem:

I'm doing format shifting of a pile of DVD's.    One of the internal drives just disappears after a while.   Only way to get it back is to reboot.  No messages in dmesg (other than IRQ19 disables around the same time... but I've determined it's not the cause)

The other is the two USB drives I have connected they stop working and I get flooded with  "sr 10:0:0:0: rejecting I/O to offline device" messages


The main CDROM seems to always work.  Which is started to make me thing it's a driver issue or something.

Comment 1 Harald Hoyer 2012-02-08 17:17:58 UTC
devices -> kernel
device nodes in /dev -> udev

Comment 2 Dave Jones 2012-03-22 17:00:02 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 3 Dave Jones 2012-03-22 17:03:52 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 Dave Jones 2012-03-22 17:14:45 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.


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