lkml.org 
[lkml]   [2012]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 3.2.1 Unable to reset IRR messages on boot
From
Date
On Tue, 2012-01-24 at 19:04 -0500, Josh Boyer wrote:
> We've had a report [1] from users booting the 3.2.1 kernel and getting a
> large number of KERN_ERR messages that look like:
>
> [ 0.020902] Unable to reset IRR for apic: 2, pin :0
> [ 0.020970] Unable to reset IRR for apic: 2, pin :1
> [ 0.021012] Unable to reset IRR for apic: 2, pin :2
> [ 0.021077] Unable to reset IRR for apic: 2, pin :3
> [ 0.021138] Unable to reset IRR for apic: 2, pin :4
> [ 0.021199] Unable to reset IRR for apic: 2, pin :5
> [ 0.021261] Unable to reset IRR for apic: 2, pin :6
> [ 0.021323] Unable to reset IRR for apic: 2, pin :7
>
> Digging through git, it seems that error message was added to 3.2 with
> commit 1e75b31d63. The commit log mentions kdump, but I don't believe the
> user is doing kexec/kdump of any kind. It seems a normal yum update/reboot
> and they hit this.
>
> Are there any details the user can gather to help debug this, or has
> anyone seen this before?
>

complete dmesg (which will have the platform, io-apic version info etc)
will be useful.

If we are seeing this during a regular boot and for the all the RTE
entries for a specific io-apic, most likely something is wrong with that
io-apic (probably a bogus one listed by the bios?). We should be able to
make the kernel code bit more smart to workaround this.

thanks,
suresh



\
 
 \ /
  Last update: 2012-01-25 02:19    [W:0.115 / U:0.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site