Re: 2.4.10ac10, cdrecord 1.9-6, Mitsumi CR-4804TE: lock up burning too large image

[Ville Herva <vherva@niksula.hut.fi>]

On Sun, Oct 21, 2001 at 01:37:01PM +0200, you [Joerg Schilling] claimed:
> 

Thanks for the timely reply!

> This must be a broken drive....

Hmm. It used to work with 2.2-kernel. With too large image, it just gave an
error.
 
> >a short while, the whole system locked up, no mouse, keyboard, caps lock,
> >ctrl-alt-del, alt-sysrq-{s,u,b}.
> 
> This is a broken kernel!

Yep.
 
> >It used to give a nice error when disk size was exceeded with 2.2.18pre19
> >and a tad older cdrecord (1.9-something (1.10-4 failed on 2.2 BTW, giving
> >error on mmapping /dev/null)).
> 
> Don't use outdated cdrecord versions, I cannot support them!

Ok. I updated to 1.10 from redhat rawhide, but as said it didn't work at all
with 2.2 ("failed to mmap /dev/null" or something) so I went back to 1.9. I
could retry now that I've updated the machine in question to 2.4. (I can
also see if the 2.2 /dev/null error reproduces if you are interested.) I'll
retry too large image with 1.10 and report back to you, but I fear it is a
kernel bug.
 
> http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html
>
> 1.9 is outdated for a long long time, it obviously cannot contain workarounds
> for Linux kernel bugs introduced after cdrecord-1.9 came out.

;)
 
> It looks like there is still a timeout bug in the kernel.
> If the kernel handles timeouts correctly, then cdrecord will return.

I see.


-- v --

v@iki.fi