public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Witten <mfwitten@gmail.com>
Cc: linux-kernel@vger.kernel.org, Arnuschky <arnuschky@xylon.de>
Subject: Re: Dropped IRQ disables Radeon 3D
Date: Fri, 15 Jul 2011 19:09:44 +1000	[thread overview]
Message-ID: <1310720984.4968.313.camel@pasglop> (raw)
In-Reply-To: <0fe54f4a77b64475b9e6041d9ef5772b-mfwitten@gmail.com>

On Fri, 2011-07-15 at 08:20 +0000, Michael Witten wrote:
> 
> Arnuschky wrote to me about this related Debian bug report:
> 
>   Fri, 2010-06-18 10:21:05 +0000
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586312
> 
> I popped over to #radeon on freenode where user agd5f told me to
> try the following on the kernel command line:
> 
>   pci=nomsi
> 
> After reading about MSIs and the requisite CONFIG_* settings, I
> realized that I didn't even have MSI support in the kernel anyway.
> Then agd5f suggested the following patches by Benjamin Herrenschmidt
> might be of help:

Another problem I noticed is some cards, when not using MSIs, still seem
to shoot an MSI with whatever value was last programmed into the MSI
configuration space. Can you check with lspci -vv if there's a non-0
value in there ? It -could- be that your get bogus MSIs.

Cheers,
Ben.

> 
> http://lists.freedesktop.org/archives/dri-devel/2011-July/012980.html
> 
> http://lists.freedesktop.org/archives/dri-devel/2011-July/012981.html
> 
> the latter of which fixes a syncronization bug on systems that use
> non-MSI IRQs (presumably pin-based IRQs) for the radeon device/driver.
> 
> For my system, I decided to enable MSI/MSI-X support by building
> Linux with the following configuration variables set:
> 
>   CONFIG_PCI=y
>   CONFIG_X86_LOCAL_APIC=y
>   CONFIG_X86_IO_APIC=y
>   CONFIG_PCI_MSI=y
> 
> and making sure I get the following:
> 
>   $ dmesg | grep MSI | grep radeon 
>   radeon 0000:01:00.0: irq 42 for MSI/MSI-X
>   radeon 0000:01:00.0: radeon: using MSI.
> 
> I'm not sure if this will avoid the problem, but it sure seems like
> a good bet.
> 
> 


  reply	other threads:[~2011-07-15  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 20:19 Dropped IRQ disables Radeon 3D Michael Witten
2011-07-15  8:20 ` Michael Witten
2011-07-15  9:09   ` Benjamin Herrenschmidt [this message]
2011-07-15 10:53     ` Michael Witten
2011-07-15 11:11       ` Arnuschky

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=1310720984.4968.313.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=arnuschky@xylon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfwitten@gmail.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