[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120503145422.0214a3ad@jbarnes-desktop>
Date: Thu, 3 May 2012 14:54:22 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Jiri Slaby <jslaby@...e.cz>
Cc: Chris Wilson <chris@...is-wilson.co.uk>,
Jiri Slaby <jirislaby@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
dri-devel@...ts.freedesktop.org
Subject: Re: i915_driver_irq_handler: irq 42: nobody cared
On Thu, 03 May 2012 23:16:02 +0200
Jiri Slaby <jslaby@...e.cz> wrote:
> On 05/03/2012 11:15 PM, Daniel Vetter wrote:
> >>> Shot in the dark, let's disable msi a bit. Can you try the below patch?
> >>
> >> Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
> >> busted, either in the card, the chipset or the kernel. Any idea how to
> >> find out?
> >
> > Ok, so MSI is busted. Can you please paste lspci -nn for you intel gpu?
>
> Sure:
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31
> Express Integrated Graphics Controller [8086:29c2] (rev 02)
Ok nevermind about the INTx-; now I'm not sure if it means anything or
not in an MSI context (the spec doesn't require it, but I thought our
devices would toggle it if they were sending interrupts).
But since line level works for you I guess it's ok to blacklist your
chipset until we poke some hw folks internally about this.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists