For documentation purposes,
(after working on items related to bug 1802021 / 1872021 / this bug)
The stack traces in this issue would suggest a duplicate of bug 1802021,
fixed in kernel 4.15.0-47.50, but this happens in 4.15.0-96, which has
that fix.
So, looking at comments #5 and #6, the issue seems particular to the
MAAS deploy boot/environment, as it doesn't happen on the deployed
system with the same kernel (i.e., same system and kernel, different
boot/environment), even when running similar commands.
As such, this issue doesn't seem to be that kernel bug, but a
manifestation with similar symptoms at the kernel level, due to what
seems to be an underlying system/platform issue.
Supporting 'evidence' seems to be the lack of additional comments on
those bugs after Fix Released, and later on this bug, perhaps due to
some system/firmware upgrade, for example.
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872021
Title:
[Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-
completion
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1872021/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
