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
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 tools-5. 0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb 5.0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb unsigned- 5.0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb 5.0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb extra-5. 0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb 5.0.0-37- generic_ 5.0.0-37. 40+mnext1_ amd64.deb
linux-cloud-
linux-headers-
linux-image-
linux-modules-
linux-modules-
linux-tools-
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