public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Dave Jones <davej@redhat.com>, Jens Axboe <axboe@suse.de>,
	Edward Angelo Dayao <edward.dayao@gmail.com>,
	"Bryan O'Sullivan" <bos@serpentine.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Recent 2.6 kernels can't read an entire ATAPI CD or DVD
Date: Wed, 28 Jul 2004 16:55:47 +0200	[thread overview]
Message-ID: <20040728145543.GB18846@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040728145228.GA9316@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Wed, Jul 28, 2004 at 03:52:28PM +0100, Dave Jones wrote:
> On Wed, Jul 28, 2004 at 08:53:19AM +0200, Jens Axboe wrote:
>  > On Wed, Jul 28 2004, Edward Angelo Dayao wrote:
>  > > yeah i get this kind of error in my logs as well from my liteon
>  > > dvd-rom at home. thats like 6 months old and happened on fc2 when i
>  > > had that installed on it. haven't noticed anything on mandrake 10 (the
>  > > current distro i use at home) with 2.6.7.
>  > > 
>  > > i got the same error on my old notebook, a compaq presario... that was
>  > > prior to the drive being sent to that big junk yard in the sky.  i
>  > > forget what model that was.  but i was running then...  rh9.
>  > > 
>  > > hope this bit helps guys resolve this. 
>  > 
>  > (dont top post!)
>  > 
>  > Sounds like something fc2 is doing, I'd suggest filing a bug report with
>  > them.
> 
> Curious. The relevant code should match mainline 1:1 there unless I'm
> mistaken. Arjan ?

we don't patch the ide layer, ide-cd or isofs... so really curious.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-28 14:59 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 [this message]
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
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=20040728145543.GB18846@devserv.devel.redhat.com \
    --to=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