From: Tejun Heo <tj@kernel.org>
To: xerces8 <xerces8@butn.net>
Cc: linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
stein@hermes.si
Subject: Re: Intel AHCI ICH9R not detecting devices
Date: Mon, 08 Sep 2008 13:54:00 +0200 [thread overview]
Message-ID: <48C51258.5080307@kernel.org> (raw)
In-Reply-To: <WorldClient-F200809081343.AA43510194@butn.net>
xerces8 wrote:
> Tejun Heo wrote:
>
>> xerces8 wrote:
>>> I put more debug in the function that failed and tracked the problem down to setup_irq().
>>> I also enabled CONFIG_DEBUG_SHIRQ. The kernel messages are attached.
>> Aieee... please disable ide-generic.
>
> (you mean CONFIG_IDE_GENERIC, right ?)
>
> Can you elaborate ?
> Is this some bug ?
>
> I can't just a tell distro owner to change a kernel build option
> because someone told me to :-) (remember, this is a problem with the
> kernel of RIPLinux, a small recovery live CD)
Enabling generic by default is a bad bad bad bad bad bad bad idea. It
just grabs legacy IO ports and interrupts and doesn't wanna share
them. Under some configurations, it used to cause two drivers to be
attached to the same device triggering weird problems, which shouldn't
happen anymore, but it still can prevent proper drivers from acquiring
the resources. In your case, USB host controller was also assigned to
the same IRQ and failed to initialize IRQ. It just can't play nice
with modern devices and drivers.
--
tejun
next prev parent reply other threads:[~2008-09-08 11:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 15:29 Intel AHCI ICH9R not detecting devices xerces8
2008-08-30 10:40 ` Tejun Heo
2008-08-30 19:42 ` xerces8
2008-09-01 9:13 ` Tejun Heo
2008-09-01 10:40 ` xerces8
2008-09-06 18:12 ` xerces8
2008-09-06 21:31 ` xerces8
2008-09-08 11:35 ` Tejun Heo
2008-09-08 11:43 ` xerces8
2008-09-08 11:54 ` Tejun Heo [this message]
2008-09-12 7:53 ` xerces8
2008-09-12 8:38 ` [PATCH] ide: note that IDE generic may prevent other drivers from attaching Tejun Heo
2008-09-27 17:13 ` Bartlomiej Zolnierkiewicz
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=48C51258.5080307@kernel.org \
--to=tj@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=stein@hermes.si \
--cc=xerces8@butn.net \
/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;
as well as URLs for NNTP newsgroup(s).