Bug 1012448

Summary:	do_IRQ: x.y No irq handler for vector (irq -1) but with AMD cpus
Product:	Red Hat Enterprise Linux 6	Reporter:	Julio Entrena Perez <jentrena>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	jentrena, prarit
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-21 14:54:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Julio Entrena Perez 2013-09-26 13:37:17 UTC

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.

Comment 5 Prarit Bhargava 2013-09-27 10:48:44 UTC

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.

Comment 12 Julio Entrena Perez 2013-10-21 14:54:28 UTC

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