diff options
| author | Suresh Siddha <suresh.b.siddha@intel.com> | 2012-03-12 11:36:33 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-02 09:27:10 -0700 |
| commit | c2ec63edaf48c90c3495eeb0b75bb05102fbf71a (patch) | |
| tree | 085c4f399818be95bec7931c8dcce482a8082b7f /mm/memcontrol.c | |
| parent | ec97d16dc99a40232f7c6ea7dc36b4819be3790e (diff) | |
| download | kernel_samsung_smdk4412-c2ec63edaf48c90c3495eeb0b75bb05102fbf71a.zip kernel_samsung_smdk4412-c2ec63edaf48c90c3495eeb0b75bb05102fbf71a.tar.gz kernel_samsung_smdk4412-c2ec63edaf48c90c3495eeb0b75bb05102fbf71a.tar.bz2 | |
x86/ioapic: Add register level checks to detect bogus io-apic entries
commit 73d63d038ee9f769f5e5b46792d227fe20e442c5 upstream.
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 <midgoon@gmail.com>
Tested-by: Jon Dufresne <jon@jondufresne.org>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: yinghai@kernel.org
Cc: kernel-team@fedoraproject.org
Cc: Josh Boyer <jwboyer@redhat.com>
Link: http://lkml.kernel.org/r/1331577393.31585.94.camel@sbsiddha-desk.sc.intel.com
[ Performed minor cleanup of affected code. ]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/memcontrol.c')
0 files changed, 0 insertions, 0 deletions