libburn causes hard lockups

[squisher]

libburn 0.4.2 causes a hard lockup on my computer when I burn a CD.

When I use xfburn, it locks up at 99%, most of the fixation seems to be done (as the resulting CD seemed usable, not thoroughly tested).

When I use cdrskin, it locks up right away, during the media check? I had forgotten to put a blank CD in, it locked up anyways.

Kernel: 2.6.24-1-686

[scdbackup]

Hard lockup means necessity for reboot ?

Is it possible to kill cdrskin by external signals ?

If the normal SIGKILL does not kill it, would kill -9 ?

This is the first report of this kind. Given the fact that your drive delivers implausible read error too, i would advise you to try the same with a different drive.

[squisher]

Hard lockup means the machine is completely dead -- no keyboard input anymore, no ssh login over the network anymore.

So I don't have any chance to kill the process.

Now I agree that it's a strange coincidence that it's also my PC which produces the read errors, but I use my drive quite a bit, and I never have problems with other burning software...

[scdbackup]

A stuck machine is beyond the natural powers of libburn. For that it needs some help from the operating system or the hardware.

The worst we can cause is the drive being unwilling to communicate with the operating system. Even that is only possible if the burn program gets killed while the drive is in sequential writing state.

Maybe libburn provides some obscure trigger for the problems. But the environment where this trigger can do harm must be very peculiar to your individual system. Many other systems and drives do not show this behavior.