From: Ondrej Zary <linux@rainbow-software.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: disable MSI on SiS 761
Date: Thu, 24 Sep 2015 21:21:33 +0200 [thread overview]
Message-ID: <201509242121.33509.linux@rainbow-software.org> (raw)
In-Reply-To: <20150924182115.GB3648@localhost>
On Thursday 24 September 2015 20:21:16 Bjorn Helgaas wrote:
> Hi Ondrej,
>
> On Fri, Sep 11, 2015 at 11:12:17PM +0200, Ondrej Zary wrote:
> > MSI is broken on SiS 761 chipset at least on PC Chips A31G board.
> > No interrupts are delivered once MSI is enabled for a device. This causes
> > hang on X11 start with a nVidia card installed (with nouveau driver).
> >
> > Disable MSI completely for this chipset.
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
>
> This is a pretty old chipset, isn't it? Google finds a reference to
> SiS 761GX from 2005. I wonder why we're only finding this problem
> now. Is there a problem report? I wonder if the problem is really
> elsewhere, and turning off MSI just avoids the real problem.
Yes, it's an old chipset and board (Socket 754) and not very common. Nouveau
was not usable back then, MSI support was added to Nouveau in 2010 and
enabled by default only in 2013. Maybe I'm the only one who tested MSI on
this board/chipset...
The facts are:
- zero interrupts in /proc/interrupts with MSI enabled and X11 hangs
- everything works fine with MSI disabled
- tested with two different nVidia cards (don't have any other PCIe card to
test)
I guess that either the MSI support in the chipset is broken or the BIOS does
not set up some secret chipset register(s) correctly.
--
Ondrej Zary
next prev parent reply other threads:[~2015-09-24 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 21:12 [PATCH] PCI: disable MSI on SiS 761 Ondrej Zary
2015-09-24 18:21 ` Bjorn Helgaas
2015-09-24 19:21 ` Ondrej Zary [this message]
2015-09-24 20:40 ` Bjorn Helgaas
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=201509242121.33509.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).