Bug 1542450

Summary:	If IRQ disappears and reappears later the IRQ is not balanced correctly due to overflow in irq_count [rhel-7.4.z]
Product:	Red Hat Enterprise Linux 7	Reporter:	Oneata Mircea Teodor <toneata>
Component:	irqbalance	Assignee:	Kairui Song <kasong>
Status:	CLOSED ERRATA	QA Contact:	Jiri Dluhos <jdluhos>
Severity:	high	Docs Contact:	Petr Bokoc <pbokoc>
Priority:	urgent
Version:	7.5	CC:	amanduch, bwelterl, fkrska, jbastian, jeder, jreznik, kasong, kernel-qe-hw, pbokoc, rwright, skozina, yozone
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	irqbalance-1.0.7-10.el7_4.1	Doc Type:	Bug Fix
Doc Text:	Previously, if a device disappeared and then reappeared, the "irq_count" interrupt request (IRQ) counter in irqbalance overflowed, which resulted in a failure to balance IRQs. This update adds a check which triggers a rescan of the IRQ database if the counter decreases. As a result, IRQs remain correctly balanced for disappearing and reappearing devices.	Story Points:	---
Clone Of:	1536373	Environment:
Last Closed:	2018-11-06 15:58:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1536373
Bug Blocks:	1507952, 1507957

Description Oneata Mircea Teodor 2018-02-06 11:30:25 UTC

This bug has been copied from bug #1536373 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 7 Kairui Song 2018-09-06 02:44:31 UTC

*** Bug 1503800 has been marked as a duplicate of this bug. ***

Comment 12 Jiri Dluhos 2018-09-25 12:39:17 UTC

Confirming that after removing and re-adding the audio driver, "irqbalance --onetime --debug" rebuilds the database (produces a list of Adding IRQ nn to database" messages).

Thanks kasong!

Comment 14 errata-xmlrpc 2018-11-06 15:58:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3508