[Intel D945GCLF2] Kernel panic with 3.13.0-27-generic

[roemer2201]

System does not boot after upgrade to kernel "linux-image-3.13.0-27-generic". It crashes with a kernel panic. I was able to boot the default kernel from Ubuntu 14.04 (linux-image-3.13.0-24-generic).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CurrentDmesg: [ 24.371313] init: plymouth-upstart-bridge main process ended, respawning
Date: Tue Jun 10 11:54:29 2014
InstallationDate: Installed on 2014-04-26 (44 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
IwConfig:
 tun0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8282ba3f-5f41-45e6-b9ef-4295c61b70e9 ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0278.2010.0414.2000
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE46416-103
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0278.2010.0414.2000:bd04/14/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF2:rvrAAE46416-103:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

roemer2201, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (the one all the way at the top, and not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc8

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

We would like to review the details of the panic. Do you have a screen shot, digital image or the text details of the panic that you could provide?

[roemer2201 (roemer2201)]

Today I installed the lastest kernel from the repositories: 3.13.0-29-generic. I rebooted and the system boots like it should. After that I reinstalled the faulty 3.13.0-27-generic kernel. Now the system boots up as well, but There was not much working: The network did not come up, my keyboard was not working and the monitor was running on a lower resolution. Other things could not be tested, because I had no access to the system.

Is it ok to drop this issue, now that it seems to be fixed? Or should I investigate further? If so, let me know how.

[penalvch (penalvch)]

roemer2201, keep using the latest kernel available from the repo. If it doesn't happen anymore, feel free to mark this Status Invalid.

[Launchpad Janitor (janitor)]

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