kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Jacob M. Carson]

This occurred after rebooting after running Kubuntu's Update Manager 5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last update that required me to do so, and thus I don't know if the problem was from that update or this one.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jacob 1494 F.... pulseaudio
 /dev/snd/controlC0: jacob 1494 F.... pulseaudio
CurrentDesktop: KDE
Date: Wed Oct 12 19:54:03 2016
HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
InstallationDate: Installed on 2016-05-25 (140 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.4
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to identify the commit that introduced this regression. Can you test the following kernels and see which ones exhibit the bug:

4.4.19: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
4.4.20: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.20/
4.4.21: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.21

You don't have to test all of them, just up until the first one shows the bug.

Thanks in advance!

[Joseph Salisbury (jsalisbury)]

This could be related to bug 1633391

[Tommy_CZ (t-kijas)]

"kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36"
I thought the same, but I realised it is somehow "random". Only 1 of 8 attempt to boot is succesfull, no matter what kernel (despite what I thought).

It all happened after update of packages few days ago.
Before that all kernels worked without problem.

Just test it, you'll see I am right.
Bug #1633391

[Joseph Salisbury (jsalisbury)]

Does this bug sill happen with the latest Xenial updates?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]