Bug 82961 - Disabling VT-d leads to do_IRQ: X.XXX No irq handler for vector (irq -1)
Summary: Disabling VT-d leads to do_IRQ: X.XXX No irq handler for vector (irq -1)
Status: NEW
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-21 15:44 UTC by Anthony DeRobertis
Modified: 2014-08-21 15:46 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.16.1
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg from 3.16.1 (74.35 KB, text/plain)
2014-08-21 15:45 UTC, Anthony DeRobertis
Details
lspci -vv from 3.16.1 (55.67 KB, text/plain)
2014-08-21 15:45 UTC, Anthony DeRobertis
Details
/proc/interrupts from 3.16.1 (4.49 KB, text/plain)
2014-08-21 15:45 UTC, Anthony DeRobertis
Details
dmidecode (23.42 KB, text/plain)
2014-08-21 15:46 UTC, Anthony DeRobertis
Details

Description Anthony DeRobertis 2014-08-21 15:44:37 UTC
NOTE: Previously sent to the IOMMU list; see <http://thread.gmane.org/gmane.linux.kernel.iommu/3946/focus=3969>. That was in 3.12.

Linux 3.12 added a quirk to disable VT-d due to an Intel errata. However, having VT-d disabled on this machine (whether by the BIOS setting or by the kernel disabling it, all the permutations are in that email thread) results in IRQ errors like these:

[70090.499038] do_IRQ: 2.104 No irq handler for vector (irq -1)
[80893.648397] do_IRQ: 2.109 No irq handler for vector (irq -1)
[81293.703732] do_IRQ: 3.79 No irq handler for vector (irq -1)
[83814.393615] do_IRQ: 3.188 No irq handler for vector (irq -1)
[85504.918101] do_IRQ: 1.229 No irq handler for vector (irq -1)
(etc.)

Since 3.12, I've been building kernels with a local patch to leave VT-d enabled, which gets rid of the IRQ errors (and, also, the machine is perfectly stable).

Tests of 3.12 w/ both VT-d settings in bios and nointremap are at <http://news.gmane.org/find-root.php?message_id=52D83BF9.7040502%40metrics.net>; note the test dmesg's are in 1-3-2 order.
Comment 1 Anthony DeRobertis 2014-08-21 15:45:15 UTC
Created attachment 147641 [details]
dmesg from 3.16.1
Comment 2 Anthony DeRobertis 2014-08-21 15:45:34 UTC
Created attachment 147651 [details]
lspci -vv from 3.16.1
Comment 3 Anthony DeRobertis 2014-08-21 15:45:53 UTC
Created attachment 147661 [details]
/proc/interrupts from 3.16.1
Comment 4 Anthony DeRobertis 2014-08-21 15:46:15 UTC
Created attachment 147671 [details]
dmidecode

Note You need to log in before you can comment on or make changes to this bug.