On Thu, May 10, 2012 at 07:06:23AM -0700, Greg KH wrote:
> On Thu, May 10, 2012 at 02:03:59PM +0200, maximilian attems wrote:
> > From: Suresh Siddha
> >
> > With the recent changes to clear_IO_APIC_pin() which tries to
> > clear remoteIRR bit explicitly, some of the users started to see
> > "Una
On Thu, May 10, 2012 at 02:03:59PM +0200, maximilian attems wrote:
> From: Suresh Siddha
>
> 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 th
From: Suresh Siddha
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
This is a note to let you know that I've just added the patch titled
x86/ioapic: Add register level checks to detect bogus io-apic entries
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the p
This is a note to let you know that I've just added the patch titled
x86/ioapic: Add register level checks to detect bogus io-apic entries
to the 3.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the p
This is a note to let you know that I've just added the patch titled
x86/ioapic: Add register level checks to detect bogus io-apic entries
to the 3.3-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the p
