Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
"do_IRQ: x.y No irq handler for vector (irq -1)" messages appear regularly at /var/log/messages on AMD systems even when booting with intremap=off in the kernel boot command line.

Version-Release number of selected component (if applicable):
2.6.32-358.11.1.el6

How reproducible:
Several times per day.

Steps to Reproduce:
1. Unknown.
2.
3.

Actual results:
"do_IRQ: x.y No irq handler for vector (irq -1)" messages appear regularly at /var/log/messages on AMD systems.

Expected results:
No such messages appear at /var/log/messages.

Additional info:
LKML thread at https://lkml.org/lkml/2012/8/8/458 seems related to the issue.

It certainly looks like interrupts are incorrectly routed after looking at the messages file.

The current BIOS version is

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: HP
        Version: A15
        Release Date: 05/02/2011

on this system.  There is a slightly newer version available on the HP website and I'd like that to be used before we continue further.  In many cases we've seen that these routing issues are due to BIOS issues, and the update is marked *CRITICAL* on the HP website.

Beyond that, what happens if you blacklist the USB driver?  Does the system still encounter these errors?

P.

Problem was solved by:

- Updating iLO to the latest firmware (2.22 at [1]).

*and*

- changing the iLO 2 Virtual Keyboard and Mouse setting from 'UHCI' to 'System USB'.

[1] http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=3716073&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D%257CswItem%253DMTX_90268fc786c4448ead5ca5bd3f%257CswEnvOID%253D4004%257CitemLocale%253D%257CswLang%253D%257Cmode%253D5%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken