From: Robert Love <rml@ximian.com>
To: Jens Axboe <axboe@suse.de>
Cc: "Bryan O'Sullivan" <bos@serpentine.com>,
Arjan van de Ven <arjanv@redhat.com>,
Dave Jones <davej@redhat.com>,
Edward Angelo Dayao <edward.dayao@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Recent 2.6 kernels can't read an entire ATAPI CD or DVD
Date: Fri, 30 Jul 2004 01:57:11 -0400 [thread overview]
Message-ID: <1091167031.1982.13.camel@localhost> (raw)
In-Reply-To: <20040730055333.GC7925@suse.de>
On Fri, 2004-07-30 at 07:53 +0200, Jens Axboe wrote:
> read-ahead doesn't matter on ripping audio, just for fs work.
This isn't ripping, just playing.
> The audio problems might be fixed in 2.6.8-rc1-mm1 + the bounce patch
> posted a few times (unfortunately 2.6.8-rc2-mm1 drops the patch for some
> reason).
Yah, I will retest with 2.6.8-rc2-mm1.
> > [1]
> > hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: command error: error=0x54
> > end_request: I/O error, dev hdc, sector 8
> > Buffer I/O error on device hdc, logical block 1
>
> So this happens during ripping, or?
During playback. Or any poking of the drive whatsoever, actually.
There will be multiple errors on different blocks, until ultimately IDE
times out and does an ATAPI reset.
> The problem with the errors like the above is that they don't
> indicate a specific problem. I can't just look at the error and see
> what causes it, it could be a million things.
I know :P
Robert Love
next prev parent reply other threads:[~2004-07-30 5:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 4:30 Recent 2.6 kernels can't read an entire ATAPI CD or DVD Bryan O'Sullivan
2004-07-28 5:31 ` Jens Axboe
2004-07-28 6:51 ` Edward Angelo Dayao
2004-07-28 6:53 ` Jens Axboe
2004-07-28 14:52 ` Dave Jones
2004-07-28 14:55 ` Arjan van de Ven
2004-07-28 16:33 ` Jens Axboe
2004-07-28 17:05 ` Jens Axboe
2004-07-28 21:57 ` Bryan O'Sullivan
2004-07-29 8:49 ` Jens Axboe
2004-07-30 5:49 ` Robert Love
2004-07-30 5:53 ` Jens Axboe
2004-07-30 5:57 ` Robert Love [this message]
2004-07-30 6:10 ` Jens Axboe
2004-07-30 6:26 ` Prakash K. Cheemplavam
2004-07-30 6:30 ` Robert Love
2004-07-30 6:39 ` Jens Axboe
2004-07-30 6:28 ` Robert Love
2004-07-30 6:38 ` Jens Axboe
2004-07-30 15:33 ` Robert Love
2004-08-01 5:29 ` Bryan O'Sullivan
2004-07-28 16:53 ` Claudio Martins
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 17:30 Lukas Hejtmanek
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=1091167031.1982.13.camel@localhost \
--to=rml@ximian.com \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=bos@serpentine.com \
--cc=davej@redhat.com \
--cc=edward.dayao@gmail.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