Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1542450 - If IRQ disappears and reappears later the IRQ is not balanced correctly due to overflow in irq_count [rhel-7.4.z]
If IRQ disappears and reappears later the IRQ is not balanced correctly due t...
Status: VERIFIED
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: irqbalance (Show other bugs)
7.5
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Kairui Song
Jiri Dluhos
Petr Bokoc
: ZStream
: 1503800 (view as bug list)
Depends On: 1536373
Blocks: 1507952 1507957
  Show dependency treegraph
 
Reported: 2018-02-06 06:30 EST by Oneata Mircea Teodor
Modified: 2018-09-25 08:39 EDT (History)
11 users (show)

See Also:
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:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Oneata Mircea Teodor 2018-02-06 06:30:25 EST
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-05 22:44:31 EDT
*** Bug 1503800 has been marked as a duplicate of this bug. ***
Comment 12 Jiri Dluhos 2018-09-25 08:39:17 EDT
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!

Note You need to log in before you can comment on or make changes to this bug.