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 02:28:04 -0400 [thread overview]
Message-ID: <1091168884.2009.1.camel@localhost> (raw)
In-Reply-To: <20040730061005.GF18347@suse.de>
On Fri, 2004-07-30 at 08:10 +0200, Jens Axboe wrote:
> Strange, something else must be accessing the drive at the same time.
Don't see anything.
> If it's just playback, don't bother.
Did not work anyhow.
> So the question is - what else is accessing the drive?
Nothing but the CD player - it is doing CDDB, though, so that is where
the reads are coming from.
It works/fails consistently - for example, I have one CD that never
works and one CD that does, as if the CD is physically damaged. Works
elsewhere, though.
Robert Love
next prev parent reply other threads:[~2004-07-30 6:28 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
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 [this message]
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=1091168884.2009.1.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 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.