From: Jens Axboe <axboe@suse.de>
To: David Dyck <dcd@tc.fluke.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2 / IDE cdrom_read_intr: data underrun / end_request: I/O error
Date: Tue, 15 Jan 2002 10:19:51 +0100 [thread overview]
Message-ID: <20020115101951.A31257@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201120834140.672-100000@dd.tc.fluke.com> <Pine.LNX.4.33.0201141938480.214-100000@dd.tc.fluke.com>
In-Reply-To: <Pine.LNX.4.33.0201141938480.214-100000@dd.tc.fluke.com>
On Mon, Jan 14 2002, David Dyck wrote:
>
> I'm still getting data underrun errors using 2.5.2
> that don't occur using 2.4.18-pre3.
I'll check up on that, mind checking when this happened exactly in the
2.5 series?
--
Jens Axboe
next prev parent reply other threads:[~2002-01-15 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 1:24 Patch: linux-2.5.2-pre7/drivers/cdrom additional kdev_t fixes Adam J. Richter
2002-01-12 2:55 ` IDE cdrom cdrom_read_intr: data underrun / end_request: I/O error --- was " David Dyck
2002-01-12 16:37 ` 2.5.2-pre11 / IDE cdrom_read_intr: data underrun / end_request: I/O error David Dyck
2002-01-15 3:46 ` 2.5.2 " David Dyck
2002-01-15 9:19 ` Jens Axboe [this message]
2002-01-15 15:47 ` David Dyck
2002-03-12 12:18 ` BIO broke non-DMA cdrom all 2.5.x kernels from BIO start till 2.5.6 affected! Anton Altaparmakov
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=20020115101951.A31257@suse.de \
--to=axboe@suse.de \
--cc=dcd@tc.fluke.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