Bug 91592 - Kernel hangs writing to CDR or CDRW
Summary: Kernel hangs writing to CDR or CDRW
Keywords:
Status: CLOSED DUPLICATE of bug 91593
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-25 06:26 UTC by Philip Sherman
Modified: 2007-04-18 16:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:53:14 UTC
Embargoed:


Attachments (Terms of Use)
Extracted messages from boot to crash to reboot (18.37 KB, text/plain)
2003-05-25 06:31 UTC, Philip Sherman
no flags Details

Description Philip Sherman 2003-05-25 06:26:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Kernel hangs during cd/cdr creation, after wome writing to the device.
System is IBM TP-T21 using IMB DVD-CDRW

Symptoms observed at hang:
1. Scroll lock and caps lock indicator lights flashing in sync.
2. Keyboard dead.
3. Mouse dead.
4. Clock (in Gnome desktop) has stopped updating.
5. CD activity light is off.

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

How reproducible:
Always

Steps to Reproduce:
1.Attempt to quick-erase a CDRW using burncenter (command line utility) or gtoaster.
    

Actual Results:  System hangs

Expected Results:  CD ejects

Additional info:

Current bypass is to revert to kernel 2.4.18-28.8.0

See attachment to review /var/log/messages

Comment 1 Philip Sherman 2003-05-25 06:31:11 UTC
Created attachment 91950 [details]
Extracted messages from boot to crash to reboot

Comment 2 Philip Sherman 2003-06-08 04:03:07 UTC
Same problem exists with kernel 2.4.20-18.8

Comment 3 Alan Cox 2003-06-08 12:51:40 UTC

*** This bug has been marked as a duplicate of 91593 ***

Comment 4 Red Hat Bugzilla 2006-02-21 18:53:14 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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