Comment 11 for bug 110484

I also have a DG965WH motherboard (and a Pioneer DVR-111D, firmware 1.29). It uses the Intel g965 chipset, which doesn't include any IDE ports. The board has a Marvell IDE controller chip, which is driven by the pata_marvell kernel module. This is a relatively new driver in the kernel, and I think not totally bug-free yet. e.g. running AMD64 Feisty with the stock kernel, my system would lock up if k3b was running while I closed the tray with a blank dvd-r (or was it +r) in it.

 I'm currently running Gutsy's kernel (and the latest git versions of DRM and mesa for better g965 support; I made a script to download and hack linux-headers...-generic so they don't depend on gutsy's libc, because the headers themselves don't. I guess some of the shipped progs in /usr/src/.../scripts do. BTW, Gutsy's xorg isn't a big improvement for opengl performance or stability if you were using Feisty with mesa from git. They still haven't fixed the tearing (no vsync). I think Feisty's mesa still crashed sometimes on g965, though, and gutsy's mesa is newer and better.)

 Anyway, I can burn DVDs all day without any problems, and the crash while k3b recognized a freshly inserted disc doesn't happen anymore. (I used to have to quit k3b, load a disc, and run it again.)

 So some people's lockups might be the fault of their PATA driver. Try a newer kernel if you have a motherboard with an Intel 965 chipset and a funky PATA controller. BTW, SATA burners are not much more expensive these days, if you're in the market for a new one anyway.

 Usually system lockups are not directly k3b's fault. Locking up the whole system requires messing with hardware (usually), so it's more often a driver or the X server or something else that directly controls hardware that needs to be fixed. Or other software can avoid doing whatever makes the driver cause a lockup.