I am seeing this on 18.04 Linux 5.3.0-1020-azure VM. Sister VM on same
kernel, same patch level, same host does not see the issue.
I isolated it to a Hyper-V integration service difference between the
issue vm and it's non-affect sibling. The issue reliably appears and
goes away if "data exchange
*** This bug is a duplicate of bug 1787127 ***
https://bugs.launchpad.net/bugs/1787127
I have 4 similar trusty virtual machines 3.13.0-155 running on the same
hyper-v 12r2 host on intel e5s.
Three of the four were rebooted after the 155 kernel without issue (so
far). The four were built from
