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.
Bug 1536370 - If IRQ disappears and reappears later the IRQ is not balanced correctly due to overflow in irq_count
Summary: If IRQ disappears and reappears later the IRQ is not balanced correctly due t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: irqbalance
Version: 6.7
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Evan McNabb
Petr Bokoc
URL:
Whiteboard:
Depends On:
Blocks: 1536373 1541290 1541293
TreeView+ depends on / blocked
 
Reported: 2018-01-19 09:14 UTC by Welterlen Benoit
Modified: 2021-08-30 13:58 UTC (History)
7 users (show)

Fixed In Version: irqbalance-1.0.7-9.el6
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.
Clone Of:
: 1536373 1541290 1541293 (view as bug list)
Environment:
Last Closed: 2018-06-19 05:19:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3366621 0 None None None 2018-03-14 23:37:31 UTC
Red Hat Product Errata RHBA-2018:1896 0 None None None 2018-06-19 05:19:30 UTC

Description Welterlen Benoit 2018-01-19 09:14:43 UTC
Description of problem:

If IRQ disappears and reappears later the IRQ is not balanced correctly due to overflow in irq_count (as the counter got smaller and difference cause overflow).
Rescan if this happens fix the problem.

Version-Release number of selected component (if applicable):
irqbalance-1.0.7-8

How reproducible:
Reproducible when a device disappears and reappears, for example when vm has high network load on aws vms with an enavf device

Steps to Reproduce:
1. Make a device disappears and reappears
2.
3.

Actual results:
the IRQ is not balanced correctly when a device disappears and reappears


Expected results:
the IRQ is balanced correctly


Additional info:
ENA driver resets look like they deassign and reassign the IRQs thus resetting counts.
This is fixed in version 1.0.8 thanks to this patch "Balance correctly IRQs reappearing" :
https://github.com/Irqbalance/irqbalance/commit/93ed80181e0ce7b81bc88a67fabad1ad829fc460

Comment 14 errata-xmlrpc 2018-06-19 05:19:19 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:1896


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