Re: 2.4.17 Oops when trying to mount ATAPI CDROM

["Manuel McLure" <manuel@mclure.org>]

----- Original Message -----
From: "Manuel McLure" <manuel@mclure.org>
To: <linux-kernel@vger.kernel.org>
Cc: "Andre Hedrick" <andre@linuxdiskcert.org>
Sent: Sunday, February 03, 2002 10:32 AM
Subject: Re: 2.4.17 Oops when trying to mount ATAPI CDROM


>
> On 2002.02.03 10:21 Manuel McLure wrote:
> >
> > On 2002.02.02 22:04 Andre Hedrick wrote:
> > >
> > > Manuel,
> > >
> > > Would you be kind enough to be a little more specific on the hardware?
> > > The attached devices bu make model and real vender if known.
> > kml/
> >
> > The CD-ROM is detected as a Pioneer CD-ROM ATAPI Model DR-A24X 0104 - I
> > haven't opened the case to look at it but I do recall that it is
> > definitely a 24X Pioneer ATAPI CDROM.
> >
>
> Some more information - if I boot without "hdc=noprobe hdc=cdrom", I don't
> get the oops whel loading the "ide-cd" module - instead I get
>
> hdc: set_drive_speed_status: status=0x00 { }
> hdc: lost interrupt
> hdc: ATAPI 20X CD-ROM drive, 128kB Cache, DMA
> Uniform CD-ROM driver Revision: 3.12
> hdc: lost interrupt
> hdc: lost interrupt
> hdc: lost interrupt
>
> The module eventually finishes initializing but is not usable due to the
> "lost interrupt"s.

After checking through the code, I can't see any way that "noprobe" with an
existing device would ever work on 2.4. Unless I'm missing something the
only place where "drive->id" is allocated is in do_probe() which isn't
called for a device with "noprobe" set, yet all the config_drive_xfer_rate()
functions will oops if "drive->id" is NULL.

Is "noprobe" on an existing device no longer supported in 2.4?
--
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<manuel@mclure.org>     | and significant law, no man may kill a cat.
<http://www.mclure.org> |             -- H.P. Lovecraft