linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Drew Weaver <drew.weaver@thenap.com>
To: "'Thomas Jarosch'" <thomas.jarosch@intra2net.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Charlie Suffin <charlie.suffin@stratus.com>
Subject: RE: [PATCH] pci: Add quirk for still enabled interrupts on Intel Sandy Bridge GPUs
Date: Wed, 25 Apr 2012 11:23:27 -0400	[thread overview]
Message-ID: <F3318834F1F89D46857972DD4B411D7005324C00C5@exchange> (raw)
In-Reply-To: <201204251722.14877.thomas.jarosch@intra2net.com>

Yeah it is very unfortunate that this hasn't been fixed in the BIOS.

-----Original Message-----
From: Thomas Jarosch [mailto:thomas.jarosch@intra2net.com] 
Sent: Wednesday, April 25, 2012 11:22 AM
To: linux-pci@vger.kernel.org
Cc: Jesse Barnes; linux-kernel@vger.kernel.org; Drew Weaver; Charlie Suffin
Subject: Re: [PATCH] pci: Add quirk for still enabled interrupts on Intel Sandy Bridge GPUs

On Wednesday, 7. December 2011 22:08:11 Thomas Jarosch wrote:
> Some BIOS implementations leave the Intel GPU interrupts enabled, even 
> though no one is handling them (f.e. i915 driver is never loaded).
> Additionally the interrupt destination is not set up properly and the 
> interrupt ends up -somewhere-.
>
> These spurious interrupts are "sticky" and the kernel disables the 
> (shared) interrupt line after 100.000+ generated interrupts.

Just a small heads up: Boards with the new Intel Ivy bridge chipset are affected, too. Currently known to be affected is

    Intel Desktop Board DH77EB


Would be nice if Intel fixes the shared BIOS code...

Thanks to Drew Weaver for reporting the issue. I currently don't have time to prepare another quirk.

Best regards
Thomas Jarosch

      reply	other threads:[~2012-04-25 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 21:08 [PATCH] pci: Add quirk for still enabled interrupts on Intel Sandy Bridge GPUs Thomas Jarosch
2011-12-07 21:30 ` Jesse Barnes
2011-12-08  8:27   ` Thomas Jarosch
2012-01-10 10:45 ` Thomas Jarosch
2012-01-27 17:28   ` Jesse Barnes
2012-01-31  8:20     ` Thomas Jarosch
2012-02-10 19:45 ` Jesse Barnes
2012-04-25 15:22 ` Thomas Jarosch
2012-04-25 15:23   ` Drew Weaver [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=F3318834F1F89D46857972DD4B411D7005324C00C5@exchange \
    --to=drew.weaver@thenap.com \
    --cc=charlie.suffin@stratus.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=thomas.jarosch@intra2net.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).