Janne, good point. There's another possible workaround in certain
circumstances. You can also clear the auditd rules which should allow
you to continue working on a running system. This would be done by
issuing an auditctl -D, after which you should be able to use the
running system, albeit
We've successfully reproduced the error on a newly built instance.
We'll proceed to run the mainline kernel on the same instance.
Worth noting that it took 441529 seconds (5.1 days) since boot for this
to manifest in this case. On our previous instance the time to failure
was in the order of a
Logs are inline. If anything else is needed I'll capture and attach.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We're aiming to reproduce this issue on another instance, then will
switch to the mainline kernel to gather the info you need.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1702910
With the sysctl net.ipv6.conf.all.disable_ipv6=1 we have still seen
another kernel error as follows:
[97989.224382] [ cut here ]
[97989.224395] WARNING: CPU: 1 PID: 19570 at
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159
Public bug reported:
After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel
we are seeing system hangs with the following logs. Prior to this
upgrade there were no crashes or kernel traces of this sort. We have
ruled out physical hardware issues by moving the VM to another
6 matches
Mail list logo
