linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank-Michael Fischer <fmfischer@gmx.net>
To: linux-ide@vger.kernel.org
Cc: celestar <celestar@t-online.de>
Subject: ATA burner problem under 2.6
Date: Tue, 10 Aug 2004 09:53:57 +0200	[thread overview]
Message-ID: <41187F15.4040706@gmx.net> (raw)

when using kernel 2.6.5 the following command on any DVD:

dd if=/dev/hdc of=test.iso bs=2048

uses almost 6 times as much system time compared to:

dd if=/dev/sr0 of=test.iso bs=2048 under 2.4.21 (ide-scsi, identical 
hardware)

Moreover: when repeating the 2.6.5 dd command a couple of times the 
system comes to a complete lockup, with no logged error messages 
whatsoever. This never happens under 2.4.21. But I can reproduce this 
behaviour on another PC.

Another related problem:

When ripping an audio CD under 2.4.21 I get perfect results using cdrdao 
with --paranioa-mode 0. Ripping the same CD under 2.6.5 requires 
--paranioa-mode 3.

Is this a known bug of 2.6 kernels?

Regards,

Frank-Michael Fischer


                 reply	other threads:[~2004-08-10  7:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41187F15.4040706@gmx.net \
    --to=fmfischer@gmx.net \
    --cc=celestar@t-online.de \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).