All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: linux-pci@vger.kernel.org
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-kernel@vger.kernel.org,
	Charlie Suffin <charlie.suffin@stratus.com>,
	stable@kernel.org
Subject: Re: [PATCH] pci: Add quirk for still enabled interrupts on Intel Sandy Bridge GPUs
Date: Tue, 10 Jan 2012 11:45:52 +0100	[thread overview]
Message-ID: <201201101145.52640.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <4EDFD5BB.1050906@intra2net.com>

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.
> 
> Fix it by disabling the still enabled interrupts.
> This resolves crashes often seen on monitor unplug.

Happy new year 2012!

Any news on the status of this patch?

Cheers,
Thomas

  parent reply	other threads:[~2012-01-10 10:45 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 [this message]
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

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=201201101145.52640.thomas.jarosch@intra2net.com \
    --to=thomas.jarosch@intra2net.com \
    --cc=charlie.suffin@stratus.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.