After I updated irqbalance to the next major version (shortly after your
last message from 2017) the issue didn't appear anymore since then.
** Changed in: irqbalance (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You
Setting incomplete missing further info, also there were no similar bug
reports since then.
** Changed in: irqbalance (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Hmm,
that seems odd - but it doesn't have enough to recreate and debug.
As irqbalance isn't strictly required you could consider uninstalling or
masking it in systemd.
But that is only a workaround.
For the sake of going forward I merged the latest irqbalance which should show
up soon in 18.04.
I have extended the test a bit by instead of testing if a manual
irqbalance shutdown is fast or slow I have tested if the system shutdown
is also delayed if irqbalance is manually shutdown before a system
shutdown. I have made a few system shutdowns with and without irqbalance
running and in the
> 1. does on the system running also take quite some time if you do like
"systemctl stop irqbalance"?
I have tested this now multiple times by stopping and starting it again
and all looked fine.
> 2. I'd assume that systemd concurrently stops multiple things and irqbalance
> is just the last
Hi,
I doubt it is irqbalance shutdown in your case.
That shutdown is just sending a kill signal and that is it, there is not much
more it does.
I quickly checked but for me it didn't look the same.
Two things to get more details:
1. does on the system running also take quite some time if you do
