From: Chuck Ebbert <cebbert@redhat.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jon Masters <jonathan@jonmasters.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, Conke Hu <conke.hu@gmail.com>
Subject: Re: Loading both the pata_atiixp and the ahci driver causes problems
Date: Sun, 18 Mar 2007 17:21:56 -0400 [thread overview]
Message-ID: <45FDAD74.9010402@redhat.com> (raw)
In-Reply-To: <45FCD0FB.70507@gmail.com>
Tejun Heo wrote:
> Jon Masters wrote:
>> Chuck Ebbert wrote:
>>
>>> If you try to load both the pata_atiixp and the ahci driver
>>> (for the same ATI SB600 adapter), very strange things happen.
>>> The AHCI driver churns for three minutes or so, spewing
>>> messages like this, then nothing works:
>>>
>>> <6>ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>> <4>ata3.00: qc timeout (cmd 0xec)
>>> <4>ata3.00: failed to IDENTIFY (I/O error, err_mask=0x104)
>>> Shouldn't it be able to tell the device has already been
>>> claimed by some other driver?
>> One would assume it'd fail to grab the PCI IO ranges twice? I haven't
>> looked at the code but I have seen this bug mentioned elsewhere so I
>> might well end up having to do that yet :-)
>
> Dunno much about sb600 but ahci and pata_atiixp are probably using
> separate IO regions && separate PCI functions.
>
> Conke, care to educate us a bit here?
>
The really funny part is that it works for some if they use:
pci=noacpi,irqpoll
prev parent reply other threads:[~2007-03-18 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 22:08 Loading both the pata_atiixp and the ahci driver causes problems Chuck Ebbert
2007-03-16 1:42 ` Jon Masters
2007-03-18 5:41 ` Tejun Heo
2007-03-18 6:28 ` Jon Masters
2007-03-18 6:38 ` Tejun Heo
2007-03-18 6:56 ` Jon Masters
2007-03-18 6:56 ` Jon Masters
2007-03-18 21:21 ` Chuck Ebbert [this message]
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=45FDAD74.9010402@redhat.com \
--to=cebbert@redhat.com \
--cc=conke.hu@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jonathan@jonmasters.org \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.