3.2.1 Unable to reset IRR messages on boot

[Josh Boyer]

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?

josh

[1] https://bugzilla.redhat.com/show_bug.cgi?id=784445
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/