Consistent boot time kernel panic

Bug #1659268 reported by Shahar Or
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Joseph Salisbury
Yakkety
Won't Fix
High
Joseph Salisbury

Bug Description

I don't know to provide the necessary crash dump and any other things that may be required to analyze this.

The crash occured consistently on every boot with this kernel.

I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash.

I got this since first reboot after dist-upgrade to 17.04.

BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question:
http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug#

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.9.0-12-generic 4.9.0-12.13
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CurrentDesktop: XFCE
Date: Wed Jan 25 13:35:17 2017
HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1
MachineType: LENOVO 2007GCG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-32-generic N/A
 linux-backports-modules-4.8.0-32-generic N/A
 linux-firmware 1.162
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE6WW (2.26 )
dmi.board.name: 2007GCG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2007GCG
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

Revision history for this message
Shahar Or (mightyiam) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Shahar Or (mightyiam) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you know what kernel version this panic starts happening in?

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Yakkety):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5

tags: added: kernel-da-key yakkety
Revision history for this message
Shahar Or (mightyiam) wrote :

Joseph, regarding what kernel version this panic starts happening in, I know two things:
In 4.8.0-32 it does not.
In 4.9.0-12 it does.

Is this enough information?

I will try the mainline build.

Revision history for this message
Shahar Or (mightyiam) wrote :

Crash does not happen with 4.10.0-041000rc5-generic.

tags: added: kernel-fixed-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

That is good news.

Can you see if this bug happens with the Zesty proposed kernel?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

Changed in linux (Ubuntu Yakkety):
status: Confirmed → Triaged
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Shahar Or (mightyiam) wrote :

The following package from zesty-proposed does not have this crash:

Package: linux-image-4.9.0-15-generic
Priority: optional
Section: kernel
Installed-Size: 67599
Maintainer: Ubuntu Kernel Team <email address hidden>
Architecture: amd64
Source: linux
Version: 4.9.0-15.16
Provides: fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, virtualbox-guest-modules, zfs-dkms
Depends: initramfs-tools | linux-initramfs-tool, kmod
Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo
Suggests: fdutils, linux-doc-4.9.0 | linux-source-4.9.0, linux-tools, linux-headers-4.9.0-15-generic
Filename: pool/main/l/linux/linux-image-4.9.0-15-generic_4.9.0-15.16_amd64.deb
Size: 22942540
MD5sum: 18e0a5ef0cb3ee2f17af575e4f7a6f78
SHA1: d3c740859ed36a440a29217ca36e8716c8953b88
SHA256: 3af0399fcc3038f5286c37936d12cb9a26bec7e5fae5d0e3622e117c93096591
Description: Linux kernel image for version 4.9.0 on 64 bit x86 SMP
Description-md5: b760ff9cdd3fd1409e7e9503f48bea3b
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu

Changed in linux (Ubuntu Yakkety):
status: Triaged → Fix Committed
Changed in linux (Ubuntu):
status: Triaged → Fix Committed
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Yakkety):
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Andy Whitcroft (apw) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Yakkety):
status: Fix Committed → Won't Fix
Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
baptx (b4ptx) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.