Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 162848 - kernel locks up after accessing a blank cdrw (after it was just blanked)
kernel locks up after accessing a blank cdrw (after it was just blanked)
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-07-10 07:23 EDT by Pascal de Bruijn
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-18 08:28:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pascal de Bruijn 2005-07-10 07:23:22 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
My system hangs when I have just blanked a CDRW and I try to access it afterwards, through nautilus.

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

How reproducible:

Steps to Reproduce:
1. Put an already burnt CDRW into the CD Recorder's drive
2. cdrecord dev=/dev/hdc speed=10  blank=fast
3. (do not eject the cdrw)
4. (the empty cdrw doesn't show up on my desktop)
5. Then I go to Places - Computer - CDROM Drive

Actual Results:  The system hangs totally. I can't even use Ctrl-Alt-F1 to get to my text console.

Expected Results:  Nautilus should have presented me the CD Burning dialog.

Additional info:

I couldn't find much suspicious in my /var/log/messages file, except for this:

Jul 10 12:55:09 agamemnon kernel: scsi: unknown opcode 0x01
Comment 1 Andre Robatino 2005-07-10 11:53:24 EDT
  This is probably a dupe of bug #162347.
Comment 2 Pascal de Bruijn 2005-07-10 14:44:56 EDT
Hmmm, I looked at that one, could be the same issue, except that I can't seem to
be able to reproduce the same dmesg as he does...

Also I never have issues while booting. And I only have that issue after trying
to access a just refreshly blanked cdrw. If I blank the cdrw and reboot, and
access it after the reboot, I'm totally fine!

Pascal de Bruijn
Comment 3 Dave Jones 2005-07-15 17:08:44 EDT
[This comment has been added as a mass update for all FC4 kernel bugs.
 If you have migrated this bug from an FC3 bug today, ignore this comment.]

Please retest your problem with todays 2.6.12-1.1398_FC4 update.

If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak

Thank you.
Comment 4 Pascal de Bruijn 2005-07-18 08:28:57 EDT
I've just upgraded to the lastest kernel: 
* 2.6.12-1.1398_FC4

And I can't seem to be able to reprocedure the issue anymore.

Thanks for the help!
Pascal de Bruijn


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