Re: cdrecord kernel problems

From: Thomas Molina (tmolina@home.com)
Date: Wed Apr 05 2000 - 22:10:32 EST


On Wed, 5 Apr 2000, Paul Barton-Davis wrote:

> >From: Thomas Molina <tmolina@home.com>
> >Date: Wed, 5 Apr 2000 15:58:10 -0500 (CDT)
> >Subject: cdrecord kernel problems
>
> >tracks. If I'm on the cdrecord console when one track ends and another
> >track starts then no problem. If I switch consoles, and stay on the
> >other console when one track ends and the next one begins, then BOOM.
>
> if you're talking about virtual terminal switching, which i think you
> are, its not exactly suprising its causing you problems.

I was talking about virtual terminal switching. I apologize for my
confusing terminology. My Unix-like operating system past is kind of
messed up. I went from Interactive IX to Microport to Coherent to
Linux.

>
> as was recently mentioned on this list, the console switch is just
> about the worst place in the kernel in terms of a period of time
> during which interrupts are masked. switching VT's at any point during
> a CD roasting session is just asking for trouble. I can't remember the
> length of the interrupt mask, but it could have been as much as
> 200msec or more.
> even on my dual processor system, and even with a huge FIFO between
> cdrecord and the toaster, i tend to treat a burn session as delicate,
> fragile egg, and sit back or go get a drink. i would certainly not
> switch VT's during the process, ever.

Is this where I ask what's changed recently?

Actually, there were a couple of points I was trying to make. This
is something that just started happening. I've burned a couple of
hundred CDs prior to this. I've always burned CDs in one window while
reading email or something in another. I don't understand why the error
reported would be:

>Sense Code: 0x21 Qual 0x17 (logical block address out of range) [No
>matching qualifier] Fru 0x0

To my eye that looks like an addressing problem rather than a problem
caused by a timeout. I would expect the previously reported "loss of
streaming" error in the case of a timeout too long. Depending on what
I'm doing elsewhere, the FIFO buffer goes up or down. I've had the
buffer down to 18% and had successful burns.

I could be misunderstanding things though.

This was also something which happened while using uisng what Ryan
Weaver termed an "alpha" version of cdrecord. I had the thought that
this could be at the bottom of what I was seeing.

Is it the general consensus that I shouldn't be doing anything but
burning CDs when burning CDs?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:16 EST