@tyhicks
I can confirm that adding 'apparmor=0' to the kernal boot parameters resolved the issue on an effected system.
This was tested on 4.13.0-37-generic, with intel microcode 3.20180312.0
I will proceed with testing kernel: need linux-image-4.13.0-38-generic_4.13.0-38.43+lp1759920.1
@tyhicks
I can confirm that adding 'apparmor=0' to the kernal boot parameters resolved the issue on an effected system.
This was tested on 4.13.0-37-generic, with intel microcode 3.20180312.0
I will proceed with testing kernel: need linux-image- 4.13.0- 38-generic_ 4.13.0- 38.43+lp1759920 .1