mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arnuschky <arnuschky@xylon.de>, linux-kernel@vger.kernel.org
Subject: Re: Dropped IRQ disables Radeon 3D
Date: Fri, 15 Jul 2011 10:53:41 -0000	[thread overview]
Message-ID: <15f2d51a1ab5412a9d7c327ab67b8166-mfwitten@gmail.com> (raw)
In-Reply-To: <1310720984.4968.313.camel@pasglop>

On Fri, 15 Jul 2011 19:09:44 +1000, Benjamin Herrenschmidt wrote:

> 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.

So, you want me to boot my Linux version that doesn't have MSI support
and check whether `sudo lspci -vv' says that it is using MSIs?

  reply	other threads:[~2011-07-15 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 20:19 Michael Witten
2011-07-15  8:20 ` Michael Witten
2011-07-15  9:09   ` Benjamin Herrenschmidt
2011-07-15 10:53     ` Michael Witten [this message]
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=15f2d51a1ab5412a9d7c327ab67b8166-mfwitten@gmail.com \
    --to=mfwitten@gmail.com \
    --cc=arnuschky@xylon.de \
    --cc=benh@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®