This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1655437
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1655437
Title:
16.04 fails to boot with kernel 4.4.0-22-generic
Status in linux package in Ubuntu:
Incomplete
Bug description:
During ENIC driver development on our end, there was a mistake and the
driver was built on the 4.4.0-22-generic kernel but we intended it to
be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
testing the ENIC driver, it required a kernel upgrade and afterwards
we found it wasn't able to boot due to some volume group issues it
appears from the error messages.
We fixed the driver issue on our end to target the correct inbox
kernel version and it's working fine. We also haven't seen any issues
with 16.04 and newer kernels. However, management is still concerned
about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
it possible to look into this issue? Or maybe would it be possible to
get that kernel version removed from the package so a customer doesn't
upgrade to that kernel after an offline install?
I am able to replicate the issue easily by doing an offline install of
16.04 so the kernel does not get automatically upgraded, then
upgrading to 4.4.0-22-generic and rebooting after install.
1. If I install 16.04 with auto partitioning, after updating the
kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
errors. I’ve attached ubuntu.jpg for this.
2. If I install 16.04 with manual partitioning, I don’t see the vg not
found, but OS still fails to boot and goes to shell. I’ve attached
ubuntu2.jpg for this.
Thanks,
Jeff
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655437/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
