diff options
author | Suresh Siddha <[email protected]> | 2012-03-12 11:36:33 -0700 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2012-03-13 05:52:02 +0100 |
commit | 73d63d038ee9f769f5e5b46792d227fe20e442c5 (patch) | |
tree | 8d595eccf1d62bc212ee6bf362e4ee2bf38bd3df /tools/perf/scripts/python/net_dropmonitor.py | |
parent | a5c2edf5765a6efedfd862bce6c616bfec46306a (diff) |
x86/ioapic: Add register level checks to detect bogus io-apic entries
With the recent changes to clear_IO_APIC_pin() which tries to
clear remoteIRR bit explicitly, some of the users started to see
"Unable to reset IRR for apic .." messages.
Close look shows that these are related to bogus IO-APIC entries
which return's all 1's for their io-apic registers. And the
above mentioned error messages are benign. But kernel should
have ignored such io-apic's in the first place.
Check if register 0, 1, 2 of the listed io-apic are all 1's and
ignore such io-apic.
Reported-by: Álvaro Castillo <[email protected]>
Tested-by: Jon Dufresne <[email protected]>
Signed-off-by: Suresh Siddha <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: Josh Boyer <[email protected]>
Cc: <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
[ Performed minor cleanup of affected code. ]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions