CD/DVD burner broken with 2.6.20-15

Bug #110032 reported by Paganini
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Brian Murray

Bug Description

I have a plextor PX-708A CD/DVD burner and am running Feisty with kernel 2.6.20-15.

I went to copy a CD today and I found the following symptoms:

Kaffeine will not play the source CD - it crashes.
(It is also crashing when I try to play DVDs - that may or may not be related)
Sound Juicer will recognize the CD and download CD-DB info.
Nautilus CD Burner will read an image of the disc and ask me to insert a blank target disk.
It will then - evidently - write to the target disk; the status bar will fill up and so on.
During this writing the system becomes very unstable - other applications fail to launch, the input peripherals are severely lagged.
Nautilus CD Burner will eventually report that the writing has finished, and I will close it.
At this point I try to eject the drive using the "eject" command, and using the button on the front of the drive.
The drive will not open.
The system remains unstable as during the writing process - new applications won't launch, I can't get a terminal or any gui controls to shutdown the system.
I use <CTRL> + <ALT> + <BKSPC> to kill X hoping that I can get a terminal login
I can't login, however I see some kernel error messages dumping to the screen:

hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown

So I hit the reset button.
The BIOS hangs up at "DETECTING IDE DRIVES"
I cut the power to the system and wait a few seconds, and then it will boot, and I can open the drive.
When I take the target disk out, a visual inspection does not find anything burned onto it. However, there is a TOC or something, because my other computers and CD players no longer recognize it as a blank disk.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.20.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
Paganini (nebanks) wrote :

As of Gutsy this is no longer an issue for me. I'm currently running kernel 2.6.22-14 with no problems.

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an upgrade to Gutsy. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.20:
assignee: nobody → brian-murray
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.