Public bug reported:
Unbound 1.6.7-1ubuntu2.1 on 18.04 (bionic):
$ sudo systemctl reload unbound
Job for unbound.service failed because a timeout was exceeded.
See "systemctl status unbound.service" and "journalctl -xe" for details.
Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89
I believe I faced this bug too on Xenial with kernel 4.10.0-26-generic
on amd64. We use multiple multiqueue virtual adapters per VM so only
partial connectivity loss occurs.
With systemtap I can see that on host last_used_event from patch equals
to 0x0 on one of the queues, and guest receiving 0x1
Observing the same with HS23. I believe that it has nothing to do with
kernel.
Spotted #1371403 and fixed this by adding /lib/udev/rules.d/95-ibm-amm-
power-workaround.rules file with the following content:
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3",
ATTR{idProduct}=="4002", TEST=="p
Public bug reported:
Ubuntu 14.04.1 (also spotted on 12.04), ifenslave 2.4ubuntu1.
When VLAN interface with MTU > 1500 is created on a bonded interface
(also with MTU > 1500) via /etc/network/interfaces, sometimes that VLAN
interface will be left unconfigured after boot, with message "Waiting
for
