This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1709511
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
** Tags added: xenial
--
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/1709511
Title:
Kernel 4.4.0-89 panics on boot on xenial
Status in linux package in Ubuntu:
Incomplete
Bug description:
After applying the 4.4.0-89 kernel update, I get a panic on boot.
4.4.0-87 boots normally.
I expected that 4.4.0-89 would boot normally (as 4.4.0-87) instead of
crashing.
Systemd displays an announcement: "Starting udev Wait for Complete Device
Initialization...", then I get:
* "kobject: can not set name properly!"
* "BUG: unable to handle kernel null pointer dereference at 00000000
* A kernel error backtrace
Part of the backtrace is (I'm having to enter this from a video):
Call Trace:
[ffffffff81258ff3] ep_alloc+0x43/0xe0
[ffffffff81259162] SyS_epoll_create1+0x42/0xe0
[ffffffff81841f32] entry_SYSCALL_64_fastpath+0x16/0x71
RIP [ffffffff811ed65b] kmem_cache_alloc_trace+0x7b/0x1f0
Kernel panic - not syncing: CRED: put_cred_rcu() sees ffff880231fc3cc0
with usage -1
lsb_release -rd:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+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
