Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot change IRQ 140 affinity: Invalid argument #7

Open
ghostbuster91 opened this issue Dec 23, 2023 · 1 comment
Open

Cannot change IRQ 140 affinity: Invalid argument #7

ghostbuster91 opened this issue Dec 23, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@ghostbuster91
Copy link
Collaborator

ghostbuster91 commented Dec 23, 2023

after recent update to kernel 6.6 irq keeps spamming with following logs with an error:

		2023-12-23 22:10:41.978	
Selecting irq 141 for rebalancing
2023-12-23 22:10:41.978	
Selecting irq 143 for rebalancing
2023-12-23 22:10:41.978	
Cannot change IRQ 140 affinity: Invalid argument
2023-12-23 22:10:41.978	
Selecting irq 144 for rebalancing
2023-12-23 22:10:41.978	
Selecting irq 124 for rebalancing
2023-12-23 22:10:41.978	
Selecting irq 125 for rebalancing



2023-12-23 22:10:41.978	
-----------------------------------------------------------------------------
2023-12-23 22:10:41.974	
Selecting irq 144 for rebalancing
2023-12-23 22:10:41.974	
Selecting irq 124 for rebalancing
2023-12-23 22:10:41.974	
Selecting irq 125 for rebalancing
2023-12-23 22:10:41.974	
-----------------------------------------------------------------------------

Not sure if there is indeed something wrong or if this is just an information message.
Should be investigated.

# The service irqbalance is useful as it assigns certain IRQ calls to specific CPUs instead of letting the first CPU core to handle everything. This is supposed to increase performance by hitting CPU cache more often.
services.irqbalance.enable = true;
@ghostbuster91 ghostbuster91 added the bug Something isn't working label Dec 23, 2023
@steveej
Copy link

steveej commented Dec 24, 2023

might be related to Irqbalance/irqbalance#271. either way it's probably safe to keep it enabled. ideally we identify the IRQs and ban them from balancing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants