We ran across another instance of this bug today, on a different system.
A production back-end (no GUI) server had been mistakenly configured to pull packages from xenial-proposed, and it updated to kernel 4.4.0-119 this morning. It then failed to boot with the exact same symptoms described above. It boots just fine when manually selecting the 4.4.0-118 kernel.
Now we're down to one release increment...
4.4.0-118: bug is absent, affected systems boot just fine
4.4.0-119: bug is present, affected systems fail to boot
We ran across another instance of this bug today, on a different system.
A production back-end (no GUI) server had been mistakenly configured to pull packages from xenial-proposed, and it updated to kernel 4.4.0-119 this morning. It then failed to boot with the exact same symptoms described above. It boots just fine when manually selecting the 4.4.0-118 kernel.
Now we're down to one release increment...
4.4.0-118: bug is absent, affected systems boot just fine
4.4.0-119: bug is present, affected systems fail to boot