Bug 1052166

Summary:	irqbalance exits early when cpus are restricted to the one cache domain
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Holasek <pholasek>
Component:	irqbalance	Assignee:	Petr Holasek <pholasek>
Status:	CLOSED ERRATA	QA Contact:	Evan McNabb <emcnabb>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	ccui, dhoward, dsulliva, jeder, yozone
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	irqbalance-1.0.4-10.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 07:10:43 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 Petr Holasek 2014-01-13 12:37:19 UTC

Description of problem:
When IRQBALANCE_BANNED_CPUS variable is restricting allowed cpus for just one cache domain, irqbalance exits immediately.

Version-Release number of selected component (if applicable):
irqbalance-1.0.4-6.el6

How reproducible:
With any SMP/NUMA machine with more than one cache domain.

Steps to Reproduce:
1.# service irqbalance stop
2.# IRQBALANCE_BANNED_CPUS=ffffffff,fffffffe /usr/sbin/irqbalance -d

Actual results:
irqbalance exits after a few seconds

Expected results:
irqbalance keeps running

Additional info:
there is need for backporting deepestcache source bits from upstream where is this problem solved already.

Comment 2 Evan McNabb 2014-09-09 17:27:45 UTC

Tested on intel-mahobay-02.lab.eng.rdu.redhat.com with instructions from comment #0:

On irqbalance-1.0.4-6.el6, it terminates after less than 10 seconds. On 1.0.4-10.el6, it runs indefinitely as expected.

Comment 3 errata-xmlrpc 2014-10-14 07:10:43 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.

http://rhn.redhat.com/errata/RHBA-2014-1504.html