aboutsummaryrefslogtreecommitdiffstats
path: root/fs/ext4
diff options
context:
space:
mode:
authorThomas Jarosch <thomas.jarosch@intra2net.com>2011-12-07 22:08:11 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-27 09:51:08 -0700
commitefc7bb83059be55362ef100c9642a091ede6f414 (patch)
tree32eeb91a3ba9893b446c54873b262af174d25cb3 /fs/ext4
parent04b09f662db41a24c9e3e5d40340ad1c17dce347 (diff)
downloadkernel_samsung_smdk4412-efc7bb83059be55362ef100c9642a091ede6f414.zip
kernel_samsung_smdk4412-efc7bb83059be55362ef100c9642a091ede6f414.tar.gz
kernel_samsung_smdk4412-efc7bb83059be55362ef100c9642a091ede6f414.tar.bz2
PCI: Add quirk for still enabled interrupts on Intel Sandy Bridge GPUs
commit f67fd55fa96f7d7295b43ffbc4a97d8f55e473aa upstream. 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. Tested on the following boards: - Intel DH61CR: Affected - Intel DH67BL: Affected - Intel S1200KP server board: Affected - Asus P8H61-M LE: Affected, but system does not crash. Probably the IRQ ends up somewhere unnoticed. According to reports on the net, the Intel DH61WW board is also affected. Many thanks to Jesse Barnes from Intel for helping with the register configuration and to Intel in general for providing public hardware documentation. Signed-off-by: Thomas Jarosch <thomas.jarosch@intra2net.com> Tested-by: Charlie Suffin <charlie.suffin@stratus.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext4')
0 files changed, 0 insertions, 0 deletions