Version:           1.0 (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Michael Schmitt <mschmitt@unixkiste.org> reported this problem on the Debian bug tracker (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419280).

I originally thought that this bug was not related to K3b, but I'm not so sure anymore since he can always reproduce it on K3b 1.0 (which is in Debian Sid) but 0.12.17 (in Debian Lenny and Etch) doesn't seem to be affected.  Maybe you'd have more ideas as to what Michael could do to figure out whether it's K3b or something else in his machine?

Here's what's he done so far:

  burning goes well, no errors, but immediately when the media is 
  ejected after burning, the tray stays open, this is logged:

    Apr 14 21:39:22 localhost kernel: hdc: irq timeout: status=0xd0 { Busy }
    Apr 14 21:39:22 localhost kernel: ide: failed opcode was: unknown
    Apr 14 21:39:22 localhost kernel: hdc: DMA disabled
    Apr 14 21:39:22 localhost kernel: hdc: ATAPI reset complete

  eventually if I try to enable DMA with hdparm -d 1 again I also get a 
  lost interrupt message:

    Apr 14 21:50:38 localhost kernel: hdc: lost interrupt

  I can absolutely reproduce this behaviour with the current sid version,
  that is: If burning completes and media got ejected and k3b is trying to
  retract it again to begin the verify process, the tray stays open,
  eventually k3b reports "can't close tray" or something (got it just once
  I think).

  I could just test it with lenny's version once (I just
  had 2 blank CDs left I thought) and there I did not have the issue. Back
  with sids version I had it instantly again... so I tested to kill hald
  befor burning and... no IDE reset, no DMA lost. But as I took another CD
  I luckily found, even without hald running, tray opens, did not close,
  k3b complains "could not close tray...", DMA lost again...