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 1541290 - If IRQ disappears and reappears later the IRQ is not balanced correctly due to overflow in irq_count [rhel-6.9.z]
If IRQ disappears and reappears later the IRQ is not balanced correctly due t...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: irqbalance (Show other bugs)
6.7
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Petr Oros
Andrej Manduch
Petr Bokoc
: ZStream
Depends On: 1536370
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-02 03:08 EST by Oneata Mircea Teodor
Modified: 2018-03-14 19:37 EDT (History)
8 users (show)

See Also:
Fixed In Version: irqbalance-1.0.7-8.el6_9.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: 1536370
Environment:
Last Closed: 2018-03-13 14:29:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3366621 None None None 2018-03-14 19:37 EDT
Red Hat Product Errata RHBA-2018:0514 normal SHIPPED_LIVE irqbalance bug fix update 2018-03-13 18:36:57 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-02-02 03:08:37 EST
This bug has been copied from bug #1536370 and has been proposed to be backported to 6.9 z-stream (EUS).
Comment 6 errata-xmlrpc 2018-03-13 14:29:42 EDT
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:0514

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