public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux IDE bug in 2.4.21 and 2.4.22 ?
Date: Tue, 09 Sep 2003 07:33:02 -0700	[thread overview]
Message-ID: <3F5DE49E.50500@ipom.com> (raw)
In-Reply-To: <200309091448.36231.bzolnier@elka.pw.edu.pl>

Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 09 of September 2003 00:51, Phil Dibowitz wrote:
> 
>>Hey folks,
>>
>>I think I may have found a bug in the Linux IDE subsystem
>>introduced in 2.4.21 and still present in 2.4.22.
> 
> 
> Nope, user error :-).

I thought there was a reasonable chance of that! =)

> Nope, your CMD649 was handled by generic PCI IDE driver.

Ah, OK. Makes sense.

>>As of 2.4.21, this configuration no longer works -- which is not
>>necessarily a bug. I'm almost there, stay with me. =)
> 
> Assumption that current .config will work with future kernel versions is *false*.

Agreed. I said that wasn't a bug. =)

> Just add these two lines to your .config:
> CONFIG_BLK_DEV_VIA82CXXX=y
> CONFIG_BLK_DEV_CMD64X=y

Doh!! Didn't see the VIA driver down there at the bottom. Double doh! My 
appologies, I should have been able to figure that out.

That works quite well, thank you! Still have a question though...

> Your VIA IDE controller was handled by generic IDE chipset driver which
> did probe devices *after* PCI controllers are probed, so CMD649 took
> ide0 and ide1 first.

But, what about the case when I built in the generic driver, but made 
the CMD649 driver a module, and loaded it after boot. That shouldn't 
have *changed* what ide0 and ide1 are, right? I had ide0 and ide1 
assigned, did a modprobe, and CMD649 changed what ide0 adn ide1 where, 
and then forgot about the previous ones.. like all of a sudden it told 
the generic driver "no, no, you were wrong, there's no VIA chipset here, 
go back to sleep."

I may well be misunderstanding something precedence in the kernel here, 
but I figured while I'm bugging you, I might as well get the full picture.

Thanks for your time!
-- 
Phil Dibowitz                             phil@ipom.com
Freeware and Technical Pages              Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
  - Benjamin Franklin, 1759



  reply	other threads:[~2003-09-09 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 22:51 Linux IDE bug in 2.4.21 and 2.4.22 ? Phil Dibowitz
2003-09-09 12:48 ` Bartlomiej Zolnierkiewicz
2003-09-09 14:33   ` Phil Dibowitz [this message]
2003-09-09 15:01     ` Bartlomiej Zolnierkiewicz
2003-09-09 15:13       ` Phil Dibowitz
2003-09-10  3:52       ` Phil Dibowitz

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=3F5DE49E.50500@ipom.com \
    --to=phil@ipom.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --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