Bug 1404049 - /usr/sbin/irqbalance: irq 35 affinity_hint and banned cpus confict
Summary: /usr/sbin/irqbalance: irq 35 affinity_hint and banned cpus confict
Keywords:
Status: CLOSED DUPLICATE of bug 1393539
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: irqbalance
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Andrej Manduch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 23:51 UTC by Vishal Agrawal
Modified: 2019-02-15 03:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 08:33:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vishal Agrawal 2016-12-12 23:51:16 UTC
Description of problem:

After updating to irqbalance-1.0.7-6.el7.x86_64 getting 
"/usr/sbin/irqbalance: irq 35 affinity_hint and banned cpus confict" 
warnings in log messages

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

irqbalance-1.0.7-6.el7.x86_64

How reproducible:

On customer's system. If he downgrades to irqbalance-1.0.7-5.el7.x86_64
warnings does not appear.

Steps to Reproduce:
1. update irqbalance to irqbalance-1.0.7-6.el7.x86_64.


Actual results:

Log messages are flooded with below message:

Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 33 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 40 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 41 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 42 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 43 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 44 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 45 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 46 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 47 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 48 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 49 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 50 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 51 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 52 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 53 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 54 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 55 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 56 affinity_hint and banned cpus confict
Dec  6 14:54:24 sfabric1 /usr/sbin/irqbalance: irq 57 affinity_hint and banned cpus confict


Expected results:

No such messages should appear

Additional info:

# cat etc/sysconfig/irqbalance|grep -v '#'
IRQBALANCE_ARGS= --hintpolicy=exact

If customer downgrades to 'irqbalance-1.0.7-5.el7.x86_64' , messages go away,
however after updating again, messages again start to appear

Hardware info:
--------------

Dell PowerEdge R430

CPU
  4 logical processors (4 CPU cores)
  1 Intel Xeon CPU E5-2623 v3 @ 3.00GHz (flags: aes,constant_tsc,ht,lm,pae,rdrand,vmx) 
  └─4 threads / 4 cores each

# cat proc/interrupts
            CPU0       CPU1       CPU2       CPU3       
   0:         66          0          0          0   IO-APIC-edge      timer
   8:          1          0          0          0   IO-APIC-edge      rtc0
   9:         80         41          0          0   IO-APIC-fasteoi   acpi
  10:        247          0          0          0   IO-APIC-edge      ipmi_si
  18:        111          0          0          0   IO-APIC-fasteoi   ehci_hcd:usb1, ehci_hcd:usb2
  25:          0          0          0          0   PCI-MSI-edge      PCIe PME
  26:          0          0          0          0   PCI-MSI-edge      PCIe PME
  27:          0          0          0          0   PCI-MSI-edge      PCIe PME
  28:          0          0          0          0   PCI-MSI-edge      PCIe PME, pciehp
  29:          0          0          0          0   PCI-MSI-edge      PCIe PME
  30:          0          0          0          0   PCI-MSI-edge      PCIe PME
  31:          0          0          0          0   PCI-MSI-edge      PCIe PME
  33:       4149          0          0          0   PCI-MSI-edge      megasas
  34:       1550       2109          0          0   PCI-MSI-edge      megasas
  35:       2087          0       2476          0   PCI-MSI-edge      megasas
  36:       5378          0          0       1594   PCI-MSI-edge      megasas
  37:          0          0          0          0   PCI-MSI-edge      0000:00:11.4
  39:          0          0          0          0   PCI-MSI-edge      0000:00:1f.2
  40:        184          0          0          0   PCI-MSI-edge      hfi1_0
  41:      80411          0          0          0   PCI-MSI-edge      hfi1_0 sdma0
  42:         11          0          0          0   PCI-MSI-edge      hfi1_0 sdma1
  43:         96          0          0          0   PCI-MSI-edge      hfi1_0 sdma2
  44:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma3
  45:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma4
  46:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma5
  47:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma6
  48:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma7
  49:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma8
  50:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma9
  51:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma10
  52:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma11
  53:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma12
  54:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma13
  55:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma14
  56:          0          0          0          0   PCI-MSI-edge      hfi1_0 sdma15
  57:      18753          0          0          0   PCI-MSI-edge      hfi1_0 kctxt0
  58:         18      77302          0          0   PCI-MSI-edge      hfi1_0 kctxt1
  59:          0          0          0          0   PCI-MSI-edge      hfi1_0 kctxt2
  60:          2          0          0          0   PCI-MSI-edge      hfi1_0 kctxt3
  61:          0          0          0          0   PCI-MSI-edge      hfi1_0 kctxt4
  62:         60         12          0        684   PCI-MSI-edge      em1-tx-0
  63:        232       2014         31          0   PCI-MSI-edge      em1-rx-1
  64:         20          0          0        311   PCI-MSI-edge      em1-rx-2
  65:         20         10        116          0   PCI-MSI-edge      em1-rx-3
  66:         19          0        154          0   PCI-MSI-edge      em1-rx-4
  67:          1          0          0          0   PCI-MSI-edge      em3-tx-0
  68:          1          0          0          0   PCI-MSI-edge      em3-rx-1
  69:          1          0          0          0   PCI-MSI-edge      em3-rx-2
  70:          1          0          0          0   PCI-MSI-edge      em3-rx-3
  71:          1          0          0          0   PCI-MSI-edge      em3-rx-4
  72:          1          0          0          0   PCI-MSI-edge      em2-tx-0
  73:          1          0          0          0   PCI-MSI-edge      em2-rx-1
  74:          1          0          0          0   PCI-MSI-edge      em2-rx-2
  75:          1          0          0          0   PCI-MSI-edge      em2-rx-3
  76:          1          0          0          0   PCI-MSI-edge      em2-rx-4
  77:          1          0          0          0   PCI-MSI-edge      em4-tx-0
  78:          1          0          0          0   PCI-MSI-edge      em4-rx-1
  79:          1          0          0          0   PCI-MSI-edge      em4-rx-2
  80:          1          0          0          0   PCI-MSI-edge      em4-rx-3
  81:          1          0          0          0   PCI-MSI-edge      em4-rx-4
 NMI:          1          1          1          1   Non-maskable interrupts
 LOC:      60121      63185      71641      68522   Local timer interrupts
 SPU:          0          0          0          0   Spurious interrupts
 PMI:          1          1          1          1   Performance monitoring interrupts
 IWI:       1049        948       1072        849   IRQ work interrupts
 RTR:          3          0          0          0   APIC ICR read retries
 RES:      16548      12480       6069       4109   Rescheduling interrupts
 CAL:       1244       1266       1409       1537   Function call interrupts
 TLB:        842       1038        836        907   TLB shootdowns
 TRM:          0          0          0          0   Thermal event interrupts
 THR:          0          0          0          0   Threshold APIC interrupts
 DFR:          0          0          0          0   Deferred Error APIC interrupts
 MCE:          0          0          0          0   Machine check exceptions
 MCP:          4          4          4          4   Machine check polls
 ERR:          0
 MIS:          0
 PIN:          0          0          0          0   Posted-interrupt notification event
 PIW:          0          0          0          0   Posted-interrupt wakeup event

Thanks,

- Vishal Agrawal.

Comment 1 Petr Oros 2016-12-13 08:33:26 UTC
This was introduced in irqbalance-1.0.7-6.el7.x86_64 and fixed in irqbalance-1.0.7-7.el7.x86_64, bz:1393539

*** This bug has been marked as a duplicate of bug 1393539 ***

Comment 2 Pragyan Pathi 2017-03-20 17:12:43 UTC
Red Hat, Tao, Zhiqi <zhiqi.tao> wants to test the RPM. Could you please provide the package? Thank you Pragyan


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