From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754130Ab2AJKp4 (ORCPT ); Tue, 10 Jan 2012 05:45:56 -0500 Received: from re04.intra2net.com ([82.165.46.26]:51127 "EHLO re04.intra2net.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752613Ab2AJKpz (ORCPT ); Tue, 10 Jan 2012 05:45:55 -0500 From: Thomas Jarosch Organization: Intra2net AG To: linux-pci@vger.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 User-Agent: KMail/1.13.7 (Linux/2.6.41.4-1.fc15.x86_64; KDE/4.6.5; x86_64; ; ) Cc: Jesse Barnes , linux-kernel@vger.kernel.org, Charlie Suffin , stable@kernel.org References: <4EDFD5BB.1050906@intra2net.com> In-Reply-To: <4EDFD5BB.1050906@intra2net.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201201101145.52640.thomas.jarosch@intra2net.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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