All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: craig duncan <duncan@nycap.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CD burn buffer underruns on 2.6
Date: Mon, 29 Dec 2003 20:42:49 +0100	[thread overview]
Message-ID: <20031229194249.GO3086@suse.de> (raw)
In-Reply-To: <16366.60194.935861.592797@nycap.rr.com>

On Sun, Dec 28 2003, craig duncan wrote:
> My first attempts at burning on 2.6 resulted in a couple of coasters
> (i'm running the "stock" 2.6 Debian kernel: kernel-image-2.6.0-test9-1-386).
> Burn speed was 8x (max speed for my PleXwrite 8/4/32A).  With the 2.4
> kernel (2.4.22-1-k7 on a 1.3 gig Athlon) i never had a problem burning
> at 8x (in fact, when burning completes, it always tells me:
> Buffer fill min 93%/max 100%.
> 
> At 4x, burns on 2.6 work fine, though.  At 8x, the burn always craps out
> shortly after starting.  This is completely consistent... 8x fails, 4x
> works (see cdrdao output below).  Nothing else is going on on my system.
> Running as root or regular user doesn't matter.
> 
> After a few of these failed burns ("cdrdao simulate...", actually) i saw
> this in /var/log/kern.log:
> 
> Dec 24 08:24:44 cdw kernel: cdrom_newpc_intr: 110 residual after xfer
> Dec 24 08:24:57 cdw kernel: cdrom_newpc_intr: 104 residual after xfer
> Dec 24 08:25:43 cdw kernel: cdrom_newpc_intr: 110 residual after xfer
> Dec 24 08:25:55 cdw kernel: cdrom_newpc_intr: 104 residual after xfer
> Dec 24 08:26:52 cdw kernel: cdrom_newpc_intr: 110 residual after xfer
> Dec 24 08:27:03 cdw kernel: cdrom_newpc_intr: 104 residual after xfer
> 
> As a side note, under 2.6, i see these "resid: 110", "resid: 104", etc.
> messages in the cdrdao output (below) which i never saw under 2.4.
> 
> Here's my cdrdao output:
> -----
> Starting write simulation resid: 110
> at speed 8...
> Pausing 10 seconds - hit CTRL-C to abort.
> Process can be aborted with QUIT signal (usually CTRL-\).
> resid: 104
> Writing CD-TEXT lead-in...
> Writing track 01 (mode AUDIO/AUDIO )...
> Writing track 02 (mode AUDIO/AUDIO )...
> ?: Success.  : scsi sendcmd: no error
> CDB:  2A 00 00 00 26 80 00 00 1A 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: F0 00 03 00 00 27 18 0A 00 00 00 00 0C 09 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
> Sense flags: Blk 10008 (valid) 
> resid: 61152
> cmd finished after 0.014s timeout 180s
> ERROR: Write data failed.
> ERROR: Writing failed - buffer under run?
> ERROR: Simulation failed.
> 
> I looked through the kernel archives and didn't see anyone else
> reporting this problem but it seems kind of serious to me.

Maybe cdrdao doesn't align its buffers correctly? Can you send me a
vmstat 1 output while attempting a 8x burn on 2.6?

-- 
Jens Axboe


      parent reply	other threads:[~2003-12-29 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 14:39 CD burn buffer underruns on 2.6 craig duncan
2003-12-28 15:39 ` Dr. David Alan Gilbert
2003-12-29 19:42   ` Jens Axboe
2003-12-29 17:22 ` Claas Langbehn
2003-12-29 20:34   ` Martin Josefsson
2003-12-29 19:42 ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031229194249.GO3086@suse.de \
    --to=axboe@suse.de \
    --cc=duncan@nycap.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.