Red Hat Bugzilla – Bug 91684
(IDE)Kernel 2.4.20-13 panic after CD burn
Last modified: 2007-04-18 12:54:01 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 Description of problem: I've installed the kernel-2.4.20-13 by downloading the update and installing it by running "rpm -Uvh kernel-2.4.20-13.8.i686.rpm". Since then, *after* burning a CD (with cdrecord), the kernel panics with blinking leds (Caps Lock & Scroll Lock) and the system hangs. No information is found in the system logs regarding this problem. I'm using a PlexWriter 24/10/40A. I can reproduce the problem using the command "/usr/bin/cdrecord eject speed=10 dev=0,0,0 driveropts=burnproof blank=all". The disc is blanked, then the leds start blinking, and system hangs. Since I ran the update with the -Uvh options, I can no longer choose an older kernel from grub (stupid?!). Version-Release number of selected component (if applicable): kernel-2.4.20-13 How reproducible: Always Steps to Reproduce: 1. run "/usr/bin/cdrecord eject speed=10 dev=0,0,0 driveropts=burnproof blank=all", but probably every burn results in crash (though the cd *is* burned). 2. leds blink 3. system hangs Actual Results: total crash Expected Results: return to prompt Additional info:
I see the same thing with RH 9, kernel 2.4.20-13.9. It seems OK with RH 9, kernel 2.4.20-9. I am using similar hardware with cdrecord's "blank=fast" option. Some details: I am using CD-RW media, 4x write speed. When using bad media, the SCSI layer complains but the system doesn't crash. With good media, reproducability is less than 100%. I am using the "cdbk" backup app (available from SourceForge) which first blanks and then writes a file system to the CD. I have been unable to complete a single back-up because the system crashes either during the blanking or during the file system write. So although reproducability is < 100%, it's high enough that the CD is essentially unusable.
2.4.20-18.9 has the same problem.
I have a similar problem with my RH8.0 (up2dated) when attempting cdrecord on my 2.4.20-18.8 kernel. If I run cdrecord from the console prompt (rather than X) I see a SCSI timeout followed by a kernel panic. In my case it happens 100% of the time, a few seconds after the drive starts writing. Am using a LITE-ON Model: LTR-40125S Rev: ZS0N. Problem is the same whether I have DMA on or off. It was working with an older kernel on RedHat 8.0, and the cdwriter works fine from W2K.
I get a complete hang using gtoaster to burn a data CD with cdrecord. [mlm@carter mlm]$ uname -r 2.4.20-18.8 [mlm@carter mlm]$ rpm -q cdrecord gtoaster cdrecord-1.10-14 gtoaster-1.0beta5-9 [mlm@carter mlm]$
It seems OK with RH 9, kernel 2.4.20-19.9.
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/