K3B is freezing system AFTER burning DVD

[gudwin]

Binary package hint: k3b

I have Kubuntu Feisty with all the upgrades up to today in a Core 2 Duo E6400 - MB Intel DQ965GF (which uses the PATA Marvell to control IDE), with 1GB RAM, DVD+RW LG GSA-H22N.
Using K3B to burn a DVD+R causes the system to freeze just after concluding the burning process. The system simply hangs and do not come back anymore. The mouse freezes too, and no combinations like CTRL-ALT-BS or CTRL-ALT-F1 ... F6 do work. The only solution to come back is the RESET button. Ping from the network do not work either ... the machine simply freezes completely.
Burning CDs instead of DVDs do not result in the same thing. They conclude without problem (even though it does not eject the CD as in the past).
I read some of the other bugs which seem to be similar to this one, but I decided to report, because neither of them are exactly like mine. In bug 104345 the reporter can still shutdown the system. In bug 110484, the reporter reports the crash only in its second trial of burning a DVD. In bug 91200 the system freezes just after the DVD is inserted. My case is different because it only freezes AFTER the burning process ends (I have the impression that it freezes while trying to EJECT the drive tray but this is just an impression). The DVD is successfully burned (it works, after all). I'm using the last kernel 2.6.20-16, but the same was happening with the 2.6.20-15. The K3b package is the 1.0-0ubuntu2
To repeat the bug is just a matter of burning another DVD ... I tried that 3 times. Just after concluding the burning process (using 16x - decided automatically) the system hangs on and dies. The burning process concludes with sucess ... the media is correctly burned and works perfectly. I'm using a Philips media 1-16x. In each trial I used a different content (just to assure that the problem was not due to something in the content being burned).
I'm marking this bug as a security vulnerability, because the integrity of the system is compromised. The system simply get paralized.

[Kees Cook (kees)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Mario Đanić (mario-danic)]

Sadly I cannot reproduce the bug. Could you please try to reproduce on gutsy?

[gudwin (gudwin)]

I burned a CD with Gutsy and booted on it. But how can I try K3B and burn a new DVD if the Gutsy Cd is within the drive ? Is there a way in which I can try Gutsy without having to install it on the HD ? Having an updated system through Adept is the same as having Gutsy ?

Meanwhile, I discovered more things about this bug. If I go to Settings->Configure K3B, in the Advanced session, the checkbox in "Do not eject medium after write process" was checked by default. If I UNCHECK this, and then try to burn the DVD, the problem disappears. So, apparently, the problem has to do with NOT EJECTING the media after the burn process is over. So, whether I maintain this box unchecked, apparently I am safe. I hope this tip is valuable for someone else having this same problem.

[Mario Đanić (mario-danic)]

Seems like we have a lot of problems with ejecting medium. About the gutsy ... you don't have secondary drive?
Updating with adept (with modification of all instances of "feisty" in /etc/apt/sources.list to "gutsy") and then upgrading may work,
but it still means you'll have gutsy on your Hard disk.

[AllesMeins (spam-startrekarchiv)]

I've a similar problem here. System is Kubuntu Feisty with an LiteOn DVD burner. After finishing the burning-process the system freezes every few seconds for abhout 10 seconds. One time i managed to switch to text-login and got "hdc: drive not ready for command" over and over again.

[bogolisk (dang-linh)]

I've had same problem as AllesMeins. DVD burning was working fine with Dapper and Edgy but became unreliable and cause system freeze 1 time out 2 tries. Some times the system just froze, sometimes it would freeze for a dozen of seconds then came back for 1 sec then froze again for a dozen of seconds then came back then freeze... Some times the burning would finished but the disc is unusable.

It would occured regardless of the tools: growisofs or nautilus-burner. This system run Ubuntu (not Kubuntu).

Package: linux-image-2.6.20-16-generic

/var/log/kernel

Jul 9 17:56:58 hanhi kernel: [ 4320.668000] hdd: DMA timeout retry
Jul 9 17:56:58 hanhi kernel: [ 4320.668000] hdd: timeout waiting for DMA
Jul 9 17:57:03 hanhi kernel: [ 4325.672000] hdd: status timeout: status=0xd0 { Busy }
Jul 9 17:57:03 hanhi kernel: [ 4325.672000] ide: failed opcode was: unknown
Jul 9 17:57:03 hanhi kernel: [ 4325.672000] hdd: drive not ready for command
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] BUG: soft lockup detected on CPU#0!
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [update_process_times+51/128] update_process_times+0x33/0x80
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [smp_apic_timer_interrupt+112/128] smp_apic_timer_interrupt+0x70/0x80
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [ide_inb+3/16] ide_inb+0x3/0x10
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [ide_wait_stat+240/320] ide_wait_stat+0xf0/0x140
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [ide_do_request+769/2528] ide_do_request+0x301/0x9e0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [unmask_IO_APIC_irq+31/64] unmask_IO_APIC_irq+0x1f/0x40
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [default_enable+18/32] default_enable+0x12/0x20
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [check_irq_resend+29/112] check_irq_resend+0x1d/0x70
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [enable_irq+197/208] enable_irq+0xc5/0xd0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [__ide_dma_end+91/144] __ide_dma_end+0x5b/0x90
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [__ide_dma_host_off+71/96] __ide_dma_host_off+0x47/0x60
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [ide_timer_expiry+201/704] ide_timer_expiry+0xc9/0x2c0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [ide_timer_expiry+0/704] ide_timer_expiry+0x0/0x2c0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [run_timer_softirq+303/416] run_timer_softirq+0x12f/0x1a0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [timer_interrupt+89/176] timer_interrupt+0x59/0xb0
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [__do_softirq+130/256] __do_softirq+0x82/0x100
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [do_softirq+85/96] do_softirq+0x55/0x60
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [smp_apic_timer_interrupt+117/128] smp_apic_timer_interrupt+0x75/0x80
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jul 9 17:57:07 hanhi kernel: [ 4330.408000] [default_idle+0/96] default_idle+0x0/0x60
Jul ...

[TestingTesting (sheldonc4)]

Same thing happens for me.

linux-image-2.6.20-16-generic as well.

Disabling/enabling eject doesn't seem to help matters in all situations.

LG DVDRW, one that I've had a lot of issues with - it didn't even work in dapper. (or the version before)

[Steven Ellis (steven-openmedia)]

I'm wondering if this is connected to Bug #75295 Feisty freeze, kernel (?) tries to access DVD drive

I'm seeing the problem on the following Hardware
CPU - Athlon XP 2800
Motherboard Gigabyte 7vaxp
DVD - Pioneer 110D
OS - Ubuntu Feisty
Kernel - 2.6.20-16-generic

When I burn a DVD under k3b i get a freeze for about 5 seconds as it switches from burn to verify and the following output in /var/log/messages

[928813.142234] hdc: irq timeout: status=0xd0 { Busy }
[928813.142242] ide: failed opcode was: unknown
[928818.136827] hdc: status timeout: status=0xd0 { Busy }
[928818.136830] ide: failed opcode was: unknown
[928818.136834] hdc: drive not ready for command
[928822.583541] BUG: soft lockup detected on CPU#0!
[928822.583575] [<c015354c>] softlockup_tick+0x9c/0xf0
[928822.583589] [<c0130643>] update_process_times+0x33/0x80
[928822.583598] [<c01154b0>] smp_apic_timer_interrupt+0x70/0x80
[928822.583607] [<c01042f8>] apic_timer_interrupt+0x28/0x30
[928822.583619] [<c0262543>] ide_inb+0x3/0x10
[928822.583625] [<c02639b0>] ide_wait_stat+0xf0/0x140
[928822.583633] [<c0261331>] ide_do_request+0x301/0x9e0
[928822.583643] [<c0116ccf>] unmask_IO_APIC_irq+0x1f/0x40
[928822.583650] [<c0154712>] default_enable+0x12/0x20
[928822.583654] [<c01546ad>] check_irq_resend+0x1d/0x70
[928822.583660] [<c0154345>] enable_irq+0xc5/0xd0
[928822.583668] [<f8a1b6b0>] cdrom_newpc_intr+0x0/0x350 [ide_cd]
[928822.583678] [<c0262349>] ide_timer_expiry+0xc9/0x2c0
[928822.583686] [<c0262280>] ide_timer_expiry+0x0/0x2c0
[928822.583690] [<c012f74f>] run_timer_softirq+0x12f/0x1a0
[928822.583700] [<c012b422>] __do_softirq+0x82/0x100
[928822.583711] [<c012b4f5>] do_softirq+0x55/0x60
[928822.583715] [<c01154b5>] smp_apic_timer_interrupt+0x75/0x80
[928822.583720] [<c01042f8>] apic_timer_interrupt+0x28/0x30
[928822.583725] [<c0101e00>] default_idle+0x0/0x60
[928822.583734] [<c011c092>] native_safe_halt+0x2/0x10
[928822.583742] [<c0101e3d>] default_idle+0x3d/0x60
[928822.583745] [<c0101409>] cpu_idle+0x49/0xd0
[928822.583750] [<c03d97f5>] start_kernel+0x365/0x420
[928822.583759] [<c03d9230>] unknown_bootoption+0x0/0x260
[928822.583770] =======================
[928823.133216] hdc: status timeout: status=0xd0 { Busy }
[928823.133218] ide: failed opcode was: unknown
[928823.133221] hdc: drive not ready for command

I have attached a list of the currently loaded modules.

[wmps (wenceslao-poveda)]

The same problem for me.
If I set the DMA param to "off" with hdparm, I'm able to record DVDs but not at the maximun speed.

My HW is:
CPU: AMD64 3200+
Board: MSI KT8Neo2
DVD: LG 4X.

OS: Kubuntu Feisty.
Kernel: 2.6.20-16-generic

Thanks

[Launchpad Janitor (janitor)]

[Expired for k3b (Ubuntu) because there has been no activity for 60 days.]

[stormzen (stormzen)]

I have noticed the same hard lockup as the original poster in Ubuntu gutsy / 2.6.22-14 generic. My hardware is also similar: Core Duo processor Intel(R) Pentium(R) D CPU 3.60GHz with an Intel 965 motherboard. Can reproduce every time I've tried so far -- which is pretty unpleasant. Doesn't seem to matter whether or not I tell K3b to eject the DVDR. ( It surprised me when it locked up after I had attempted to disable automounting CDs/DVDs, and told K3b not to eject the media. I'm pretty sure that the setting was not selected originally, when I started having problems. Gnome-toaster doesn't can burn the DVDs successfully (without freezing the system), but it doesn't have the features I need (namely, it won't burn "relative" soft links).

[stormzen (stormzen)]

Need to reopen this. Anything that forces a hard reboot is a bad bug...

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

stormzen,
What make & model of optical drive(s) are you using?
Do you get something similar to the following in your dmesg when this problem occurs?
++++++++
[928823.133216] hdc: status timeout: status=0xd0 { Busy }
[928823.133218] ide: failed opcode was: unknown
[928823.133221] hdc: drive not ready for command
++++++++
Does your PC freeze permanently or do you get small windows of opportunity where you can move your mouse pointer briefly before the next freeze cycle begins?
If you don't do any burning do you eventually get this problem with or without media in the drive?
Thanks.

[stormzen (stormzen)]

I did leave that out, sorry: It's an LG model optical drive, that is identified by GnomeBaker as an "HL-DT-ST DVDRRW GSA-4166B". PC freezes permanently: mouse pointer stops moving and Ctrl+Alt+FKeys do not respond. Disk appears to be in process of being accessed. I don't see any error codes in dmesg, but I've attached the log, just in case I'm just not seeing something that I should.

... And I just found out that the crash can happen without burning first. When I put an already burned DVD-R into the drive, it waited for a moment, and then the crash occured (seemingly just after it read the contents of the media.) I had not observed this before you asked... possibly it occured because I put the DVD in either while K3b was running (as I used to ID the drive), or shortly after I closed K3b after identifying the drive.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Can anybody still experiencing this problem test the following possible solution?
http://linux-ata.org/faq.html#combined
The slow down as a result of the PATA/SATA combination may be causing at least some of the above mentioned problems.
This will probably only affect those with Intel chipsets.

Another possible cause maybe an optical drive firmware bug. People may want to check to see if they have the latest firmware for their optical drive.

I don't think this is a k3b bug but will wait to hear back from people before re-assigning.

[stormzen (stormzen)]

I will try out the test later tonight. It does seem that the same device is
trying to be controlled by multiple methods, however. I can say that I've been
able to burn successfully (without rebooting) by using growisofs directly, and
that ejecting the "empty media icon" that appears on the gnome desktop (even
though I told it do nothing automatically) and reinserting the DVD has caused no
lock-ups, either. It seems to happen only when using GUIs... which makes me
wonder if part of the problem is the control that Gnome is exercising over the
device.

I have noticed, at the very least, that I have what looks like four (or five)
different device names in /dev for the same device: /dev/dvd, /dev/cdrom0,
/dev/cdrom, and /dev/sr0 (what Gnomebaker uses to burn an ISO image to DVD),
(and possibly /dev/cdrw -- I noticed that one exists, but haven't seen anything
try to use it. ... Then again, I haven't been burning CDRWs, either.)

Also thinking about booting into fluxbox and see if using K3b poses problems
that way.

Gareth Fitzworthington wrote:
> Can anybody still experiencing this problem test the following possible solution?
> http://linux-ata.org/faq.html#combined
> The slow down as a result of the PATA/SATA combination may be causing at least some of the above mentioned problems.
> This will probably only affect those with Intel chipsets.
>
> Another possible cause maybe an optical drive firmware bug. People may
> want to check to see if they have the latest firmware for their optical
> drive.
>
> I don't think this is a k3b bug but will wait to hear back from people
> before re-assigning.
>

[Frodon (frodon)]

I'm using k3b for a long time on my computer (since dapper) and i have noticed that under gutsy these hardware lock up are really frequent using k3b.
Sometimes it freezes before the end of the burn process, sometimes during the verify written data process but at the end i have really some difficulties to burn. If i bur a CD now under gutsy i have 40% of chances to get hardware lock.

However what is strange is that till use GnomeBaker i never got any problem and already burned 5 DvDs. So from my experience it looks like a bug related to k3b and the way it uses the drive.

Anyone has any infos on known k3b bugs which causes freeze or hardware locks ?

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Does anyone get a crash report recorded in dmesg or in /var/crash or anywhere else??
[Note: Get system to crash then reboot and immediately check these locations]

Another idea is to start k3b from the command prompt and have the terminal window "on-top" while the burn process is occuring. You may get to see something in the terminal window a the freeze point. You could perhaps note any messages by hand or photograph the screen at that point if any useful messages appear.
Thanks.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Anyone having trouble getting an error report/backtrace follow this link:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports

If you use the Ubuntu not Kubuntu use this section
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

Hope this helps. It is important that we get more substantial technical information to be able to progress this bug.

[locust (marineworks)]

Hi, all;
its some time i have the same problem.
I run Hardy
It happens in using more than one time the burner expecially when I ask for verify written data: the driver eject the burned cd
 but is not more able to reclose and proceed with verifying. Driver remains open, I cancel the burning mask and seems that the driver remain in an inconsistency status;
at the next burning try it hangs quite completly the pc. On tty I receive the seguent error message:
hdb: driver not ready for command

where hdb is the cd .
good luck to all
david

When a cover designer inside k3b :-) ?

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

This bug commentary requires the input of substantial technical information. See my previous comment regarding help on this matter.
Without this, the bug report cannot progress!

[Frodon (frodon)]

Thanks Gareth for your links, hope someone can provide a useful backtrace for K3B.

My personal experience led me to the conclusion that K3B doesn't not play well on some configurations, i have now burnt about 10-15 DVDs with gnomebaker without any issue so for me it is definitely related to K3B and the way it uses the drive.
I can also confirm from my past experience that the best way to create such crashes is to burn using the K3B verify feature.
Can someone with the problem confirm this trying gnomebaker or brasero instead of K3B ?

As for me i just don't use K3B anymore which solves all my burning issues.

[cybersekkin (cybersekkin)]

I can confirm I have had the same issue. Switching to GnomeBaker has resolved the issue.

It is too bad I have used k3b for a long time and loved it.

what would happen after k3b has finished burning the disk would not eject nor would it mount.
after ejecting the disk and reinserting it I would get no response from the system.
when attempting to mount the disk via "mount /media/cdrom0" the system would get cpu bound by the "hald-addon-storage".

This would only happen after k3b had successfully burnt the image.

I am using a plextor px-760a and similar specs to above (AMD64, 2G RAM) but have had this happen on my HP laptop and another system at home as well.

If you can't get a crash dump from anyone let me know and I will set aside some time in the next week to run one.

[locust (marineworks)]

On lun, 2008-04-14 at 13:52 +0000, Frodon wrote:
> Thanks Gareth for your links, hope someone can provide a useful
> backtrace for K3B.
>
> My personal experience led me to the conclusion that K3B doesn't not play well on some configurations, i have now burnt about 10-15 DVDs with gnomebaker without any issue so for me it is definitely related to K3B and the way it uses the drive.
> I can also confirm from my past experience that the best way to create such crashes is to burn using the K3B verify feature.
> Can someone with the problem confirm this trying gnomebaker or brasero instead of K3B ?
>
I agree for the "verify" issue.
Using nautilus burn utilities i had no problem. so it seems not related
to the drive ( Asus Quietrack)

I was not able to produce a backtrace. Kde bugtrace crashed too.

Best regards
David

[Vanessa Dannenberg (vanessadannenberg)]

Yet another "me too" here. Exact same symptoms as the OP - the system freezes just after a burn has finished. The mouse and console are dead and I can't ssh in from another box ("no route to host"), but I _can_ use Alt-SysRq-[U,S,B] to restart the computer, so it's not as though the system has hard locked.

This has happened multiple times, and each time it happens, the burned disk is usable afterward - I have yet to end up with a coaster.

There is nothing in /var/crash., but the system did manage to tack these few lines onto the end of /var/log/messages before I forced the restart:

==========
Aug 20 22:35:54 swan kernel: [187390.252345] hdc: irq timeout: status=0xd0 { Busy }
Aug 20 22:35:58 swan kernel: [187390.252351] ide: failed opcode was: unknown
Aug 20 22:36:09 swan kernel: [187398.621151] hdc: irq timeout: status=0xd0 { Busy }
Aug 20 22:36:09 swan kernel: [187398.621158] ide: failed opcode was: unknown
Aug 20 22:36:22 swan kernel: [187407.597348] hdc: irq timeout: status=0xd0 { Busy }
Aug 20 22:36:22 swan kernel: [187407.597356] ide: failed opcode was: unknown
Aug 20 22:36:59 swan kernel: [187427.085845] cdrom: This disc doesn't have any tracks I recognize!
==========

The next lines after these are boot messages from the restart that followed the freeze. This happens with DVD's, but I have not tried burning a CD recently (don't have any blanks handy)

We use K3B to burn with. Per gudwin's suggestion, un-checking the "don't eject when finished" option in the "Advanced" section of the config dialog seems to have worked for me. K3B now properly finishes the burn and ejects the disc without any hangs (except that HAL gets in the way and K3B has to try a couple of times to successfully eject). Just did four completely unique burns in a row without a problem.

The machine is custom-built: Gigabyte K8U-939 mainboard with an AMD 64x2 3800+ CPU, 1 GB RAM, 80 GB no-name SATA hard disk, IDE Lite-On SHW-160P6S burner, nVidia MX4000 video. Using the regular 32 bit version of Hardy, kernel is "2.6.24-19-generic".

For whatever it is worth, this system also suffers from that same annoying problem of not being able to open/eject an empty drive via the front panel button.

Gentoo also experienced both the freeze issue we're talking about here, and the empty-drive-eject issue, so this definitely goes upstream to...well, somewhere! :-)

[Joachim Wilke (jowi24)]

Having upgraded to 9.04, this problem is no longer present for me. Thanks!

[Rohan Garg (rohangarg)]

This bug report is being closed due to your last comment regarding this being fixed with an update. 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 revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.