From: Robert Hancock <hancockr@shaw.ca>
To: Steven DuChene <tevend@yahoo.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Peer Chen <pchen@nvidia.com>,
Kuan Luo <kluo@nvidia.com>,
linux-ide@vger.kernel.org
Subject: Re: SATA hard drive problem when MSI enabled (ahci.c)
Date: Tue, 30 Dec 2008 13:28:21 -0600 [thread overview]
Message-ID: <495A7655.5040702@shaw.ca> (raw)
In-Reply-To: <320569.63272.qm@web30708.mail.mud.yahoo.com>
Steven DuChene wrote:
> Robert:
>
> See the attached file for the lspci output.
>
> As far as only the MCP65 being the only known chipset with
> problems see below.
>
> If you search for either "pci=nomsi ahci" or groups of keywords
> like "SATA failed to IDENTIFY ahci" you wll see others having
> the same issues. For instance here is a person writing to the
> lkml with the same problem with a NVidia MCP78B chipset on a
> FSC Esprimo P5625 motherboard.
>
> http://lkml.org/lkml/2008/7/30/74
That was a different problem - there the BIOS did not assign an IRQ to
the controller since it was not properly in AHCI mode in the BIOS. I
believe they fixed that by enabling AHCI.
>
> Here is a bug on the Ubuntu Launchpad where the same problem
> is showing up on several people's systems with NVidia chipsets
> like the 780a (GeForce 8200 again) and nforce 730a chipset.
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/199573
This one has the reporter saying that a later kernel worked properly
without disabling MSI. It is hard to say what might have been going on
with the other posters in that bug report as they didn't post any output.
>
> Here is the same thing with an AHCI SATA controller on a VIA
> K8T890 motherboard:
>
> http://forums.opensuse.org/install-boot-login/394883-opensuse-installation-cant-find-my-sata-drives.html
>
> It seems the common ways for people to resolve these issues
> is to globally set pci=nomsi both during and after the install.
> I am not sure if globally turning off MSI for the whole system
> should be the "right" answer for these folks.
There wasn't any output posted there or exact PCI IDs there either.
(Really wish people would encourage these bugs to be reported upstream,
using pci=nomsi is no good permanent solution.) If a chipset is
confirmed to not have working MSI then it can be disabled in the driver
but we really need to narrow down specific device IDs.
Curious thing is that Vista should presumably be using MSI as well, so
it should hit the same problem, unless it's using an NVIDIA-specific
driver that knows about it.. Seems unlikely that wouldn't have been
noticed, though..
> --
> Steve DuChene
>
> --- On Tue, 12/30/08, Robert Hancock <hancockr@shaw.ca> wrote:
>
>
>> Hmm.. Can you post lspci -vvn output?
>>
>> CCing some NVIDIA people. Is there anything known about MSI
>> being broken on MCP78S AHCI controller? Currently the only
>> known NVIDIA AHCI problems with MSI are with MCP65 revisions
>> A1 and A2. I'm not actually sure what chipset listed in
>> the driver would match with MCP78S, that particular one
>> isn't listed..
>
>
>
>
prev parent reply other threads:[~2008-12-30 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 16:12 SATA hard drive problem when MSI enabled (ahci.c) Steven DuChene
2008-12-30 18:04 ` Robert Hancock
2008-12-30 18:44 ` Steven DuChene
2008-12-30 19:28 ` Robert Hancock [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=495A7655.5040702@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=tevend@yahoo.com \
/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).