public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Fluhr <mfluhr@nero.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 brings buffer underruns when burning DVDs at high speeds (16x)
Date: Mon, 12 Sep 2005 20:07:56 +0200	[thread overview]
Message-ID: <1126548476.1991.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1126527113.2169.6.camel@localhost.localdomain>

Hummm Okay. After making some ugly changes (I basically reverted all
the /drivers/block subdir to version 2.6.12.6), I still have buffer
underruns.

Does anyone know where it could come from ? I would say that I am a
little bit stuck now. I am quite sure that it is also not comming from
the devices driver (ide-cd, usb-storage...) as I tried with different
devices on different ports (mostly IDE and emulated SCSI via USB) with
the same result.

Note: This is also happening with k3b ;-)

On Mon, 2005-09-12 at 14:11 +0200, Mathieu Fluhr wrote:
> Hello all,
> 
> It seems that something has been broken when passing from 2.6.12 to
> 2.6.13 regarding the SCSI burning engine. When burning a DVD at 16x
> (with ide-cd SEND_PACKET command, or with the SG interface, no matter
> the driver used), you get tons of buffer underruns. This was not
> appearing in 2.6.12.
> 
> I would suspect something in the block devices driver, but I am not
> really sure... and I did not have enough time yet to look deeply in the
> source code ;-)
> 
> Best Regards,
> Mathieu
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2005-09-12 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 12:11 2.6.13 brings buffer underruns when burning DVDs at high speeds (16x) Mathieu Fluhr
2005-09-12 18:07 ` Mathieu Fluhr [this message]
2005-09-13 16:23 ` Alexey Dobriyan

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=1126548476.1991.4.camel@localhost.localdomain \
    --to=mfluhr@nero.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox