On Thu, May 10, 2012 at 02:03:59PM +0200, maximilian attems wrote: > From: Suresh Siddha <[email protected]> > > 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]> > --- > Compile tested on latest Debian 3.2, got shipped in Fedora 15 3.2. > > arch/x86/kernel/apic/io_apic.c | 40 > ++++++++++++++++++++++++++++++++-------- > 1 file changed, 32 insertions(+), 8 deletions(-)
<formletter> This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read Documentation/stable_kernel_rules.txt for how to do this properly. </formletter> -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
