system hangs and CPU heats up in -29 but not -28

[Nick Moffitt]

I filed this bug against linux-image-3.19.0-29-generic and hope that it has attached everything relevant.

With linux-image-3.19.0-29-generic I can only run my thinkpad X240 for a few hours before I invariably trip over this bug and cause it to hang, heating up and driving the fan to full speed. I never have this trouble when I select linux-image-3.19.0-28-generic. Occasionally I'll reboot for updates (such as the recent network manager one) and forget to go down a build number, and I hit this again shortly after reboot.

The screen remains in whatever state it was in, but I am unable to move the mouse or affect X with the keyboard (including trying to switch to a virtual console with Ctrl-Alt-F1). Nothing suspicious shows up in kern.log after the reboot, but I tend to have to do a hard power-off to get back to a useful machine so the journal may not be fully checkpointed in time.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-29-generic 3.19.0-29.31
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nick 2766 F.... pulseaudio
 /dev/snd/controlC1: nick 2766 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Sep 22 10:20:31 2015
HibernationDevice: RESUME=UUID=dae1fd50-2dc0-48b2-bd93-5823478772b6
InstallationDate: Installed on 2014-05-29 (480 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20ALCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-05-05 (139 days ago)
dmi.bios.date: 02/06/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET69WW (2.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ALCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGIET69WW(2.19):bd02/06/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20ALCTO1WW
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Nick Moffitt (nick-moffitt)]

I'm curious if this is related to bug #1495696

[penalvch (penalvch)]

Nick Moffitt, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x240 an update to your computer's buggy and outdated BIOS is available (2.33). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.19.8-ckt6-vivid/

[Joseph Salisbury (jsalisbury)]

If the bug does not happen with 3.19.8-ckt6 it may be due to a SAUCE patch in 3.19.0-29. We can then bisect between -28 and -29 to identify the commit that introduced this regression.