Hello folks. I was trying to burn a cd just now, when my system paniced out. To be honest, I cinda expected it to. The thing is, some cd writing media are of such a bad quallity or have been damaged to such an extend, that I just now the system will panic when I use them.
So you ask, why are you using those media then? The thing is, I feel my system should not panic, no matter what.
I have noticed that other people to have kernel panics when they try to burn a cd. It looks like it's a common problem. So I did some experimenting. Well, not really, but here is the deal:
I put the bad cd in, the one I knew would cause a panic. Then just before the panic, I jumped to a console to see what kind of message I would get from the kernel. And sure enough, the kernel gave detaild info what went wrong. I'm not going to post the entire thing here, but one line caught my attantion:
Code:
rscsi: abording command due to timeout: pid 174 scsi0 channel 0 id 0 luno test unit ready 00000
scsi host abort (pid 174) timed out -reseting
scsi bus is being reset for host 0 channel 0
Kernel bug at ide-iops.c: 1262!
So it seems like there is a bug in the kernel that causes it to panic. I recond ide-iops.c is a kernel source file, and that somthing goes wrong at line 1262. So I looked up the source in that file at that line. Here is a comment I found near that line :
/*
* do_reset1() attempts to recover a confused drive by resetting it.
* Unfortunately, resetting a disk drive actually resets all devices on
* the same interface, so it can really be thought of as resetting the
* interface rather than resetting the drive.
*
* ATAPI devices have their own reset mechanism which allows them to be
* individually reset without clobbering other devices on the same interface.
*
* Unfortunately, the IDE interface does not generate an interrupt to let
* us know when the reset operation has finished, so we must poll for this.
* Equally poor, though, is the fact that this may a very long time to complete,
* (up to 30 seconds worstcase). So, instead of busy-waiting here for it,
* we set a timer to poll at 50ms intervals.
*/
So it seems like the drive is confuesd by a faulty cd recorder media, and because of that, it's trying to reset the drive. Only, because of a bug in the kernel, somthing goes wrong and the kernel panics.
What do you guy's make of this. Is this really a bug in the kernel? Or is this somthing else. Does any body else experiance problems like this?
I just updated my kernel to 2.4.21. Should I send a bug reprot to the kernel guy's?
