It's a problem that it's a production server, I cannot play too much with it :-/ It was a freshly installed 16.04LTS according to the operators who did the install. According to the logs, the problematic kernel was:
Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15) It was installed with: Linux version 4.4.0-31-generic (buildd@lgw01-16) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 (Ubuntu 4.4.0- 31.50-generic 4.4.13) The -34- was already a kernel since upgrade packages. Now I have -36-, I haven't experienced with the bug yet since then at least. Additionaly, after the panic msg, every processes was stuck in 'D' state trying to do anything with apparmor (etc profile reload) including the postinst script of lxd which seems does that. After a reboot with -36- kernel, I could finish the upgrade with "dpkg --configure -a" though. If I again experience the bug, I'll try to test with latest upstream as you suggested (unfortunately, as I've told, I cannot "play" with this machine if it seems to be OK ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615082 Title: kernel NULL pointer dereference on apparmor profile update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
