I attempted to test a boot kernel built by smb, using the same test env filed in the bug originally,
linux-buildinfo-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-cloud-tools-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-headers-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-image-unsigned-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-modules-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-modules-extra-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb linux-tools-5.0.0-37-generic_5.0.0-37.40+mnext1_amd64.deb dmesg attached, I did not see the failure as noted in the original description. Nor any other failures to note. Linux automation-vm1 5.0.0-37-generic #40+mnext1 SMP Mon Dec 2 13:37:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The system booted successfully ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853981/+attachment/5309379/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853981 Title: [Regression] Failed to boot disco kernel built from master-next (kernel kernel NULL pointer dereference) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs