[Lenovo Thinkpad T430u] randomly locks up/freezes

[bmaupin]

System randomly locks up completely. Screen is frozen, system is completely unresponsive. No key combos have any effect (Ctrl-Alt-Del, Ctrl-Alt-Backspace, Ctrl-Alt-F1). The only thing that works is holding down the power button until it turns off.

I tried Alt + SysReq + REISUB (http://askubuntu.com/a/36717/18665) when it locks up, but it has no effect either.

It normally does it about once a day, but this morning it locked up 3 times in the past hour or so.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-48-generic 3.2.0-48.74
ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
Uname: Linux 3.2.0-48-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bryan 1922 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf1810000 irq 47'
   Mixer name : 'Intel PantherPoint HDMI'
   Components : 'HDA:10ec0269,17aa500c,00100203 HDA:80862806,80860101,00100000'
   Controls : 31
   Simple ctrls : 13
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
CheckboxSubmission: 0f4e55dc6f3e211b5e23a7a40efd98d8
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Thu Jul 4 10:18:48 2013
HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: LENOVO 3351CTO
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-48-generic root=UUID=2d445ceb-b77f-4a11-b57b-9a9a7f59c222 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-48-generic N/A
 linux-backports-modules-3.2.0-48-generic N/A
 linux-firmware 1.79.4
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H6ET61WW (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3351CTO
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrH6ET61WW(2.02):bd08/27/2012:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3351CTO
dmi.product.version: ThinkPad T430u
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[bmaupin (bmaupin)]

I did figure out how to do Alt + SysReq + REISUB; I just use Alt + PrtSc + REISUB. It works when my system is up and running, but when it's frozen as detailed in this bug, it has no effect.

[bmaupin (bmaupin)]

Apparently it also freezes when I'm not running on the battery. I guess I didn't realize it because I normally use the battery, but it's locked up on me 3 times in the last hour running on AC power. Alt + SysReq + REISUB still has no effect when it locks up...

[Joseph Salisbury (jsalisbury)]

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

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.10-saucy/

[Jacob Bartlett (jacobt777)]

I also ran into this same issue as described above on my Lenovo T430u.

[bmaupin (bmaupin)]

Joseph,

I've tested it using the latest kernel, and it hasn't locked up yet. However...

1. I haven't used it much with the latest kernel, because my wireless doesn't work with the latest kernel. Should I file a separate bug for this?
2. I'm still not sure if the bug is fixed in the latest kernel, because it's an intermittent bug and I haven't figured out how to trigger it. And nearly everything I do on my laptop requires internet, so I haven't tested it extensively yet.

[Duncan de Wet (duncandewet)]

I am affected by this bug too, on a new Lenovo ThinkPad E531.

[bmaupin (bmaupin)]

Duncan, could you go near the top left of this page and mark that it affects you too? That might help bring more attention to it. Thanks!

[Duncan de Wet (duncandewet)]

I fixed this problem for my Lenovo E531 by upgrading to kernel 3.9 or 3.10 (both work for me) using the Ubuntu mainline kernels [ http://kernel.ubuntu.com/~kernel-ppa/mainline/ ]. However, the Broadcom wireless driver bcmwl-kernel-source in the repos is not the latest version and fails to work on kernels newer than 3.8, so I had to update that too with the latest .deb file [ http://packages.ubuntu.com/saucy/amd64/bcmwl-kernel-source/download ]. My system now works well.

[bmaupin (bmaupin)]

Excellent! I guess I don't need to file a bug about the wireless drivers. And now I can thoroughly test the new kernel. I'll go ahead and mark this as fixed in the latest upstream kernel. Thanks, Duncan!

[Jacob Bartlett (jacobt777)]

That is good news, please let us know how the testing goes,

[bmaupin (bmaupin)]

Jacob,

Since updating to the latest kernel, I haven't had one single lockup, so it seems like that did the trick.

[Jacob Bartlett (jacobt777)]

bmaupin,

Thanks, I'm very happy that solved the issue. I will give it a try myself this weekend.

[rpisharody (rpisharody)]

Jacob, bmaupin, Duncan,

I had the same problem and have updated to the mainline kernel. Been testing the laptop for about a week now.
I want to let you guys know that I had one lockup.

I am still testing, been not able to reproduce the bug. Will let you how it goes.

[penalvch (penalvch)]

bmaupin, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[bmaupin (bmaupin)]

Christopher,

I tried the version of Ubuntu you mentioned for a few hours and didn't see the bug. I was running it from a USB drive, however, because I didn't want to put a development release of Ubuntu on my computer. So I'm not sure if that makes a difference in triggering the bug.

[penalvch (penalvch)]

bmaupin, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

[Michael (mstobb)]

I too am affected. Thinkpad T430u with Ubuntu Linux. Trying out kernel v3.10 now. Will see how it goes!

[penalvch (penalvch)]

Michael, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[bmaupin (bmaupin)]

Christopher, do you think there's any chance the upgraded BIOS from bug 1157909 would affect this issue? If so, I can use the default 12.04 kernel instead of the latest and test it out.

My thought is that if the 12.04 kernel triggers this bug, it'd be best to fix it, especially since 12.04 is an LTS release and supported for the next 4+ years. It'd be bad if everyone with certain Thinkpad models that installs 12.04 is affected by this bug, especially since at least in my mind LTS versions are supposed to generally be more reliable.

Thanks!

[penalvch (penalvch)]

bmaupin, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197869/comments/21 :
>"... do you think there's any chance the upgraded BIOS from bug 1157909 would affect this issue? If so, I can use the default 12.04 kernel instead of the latest and test it out."

Following up on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197869/comments/18 if you want a backport to a release prior to Saucy, you would want to test it out in that release to see if it is still valid after the BIOS update.

[the_vorpal_blade (the-vorpal-blade)]

I've confirmed that the bug is still an issue with the latest (2.08) version of the BIOS, under 12.04 (LTS).
It would certainly be good to backport a fix.

[penalvch (penalvch)]

the_vorpal_blade, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[bmaupin (bmaupin)]

Confirmed with latest 12.04 kernel (linux-image-3.2.0-54-generic) and latest BIOS:

$ sudo dmidecode --type 0 | head -n 8
# dmidecode 2.11
SMBIOS 2.7 present.

Handle 0x000E, DMI type 0, 24 bytes
BIOS Information
 Vendor: LENOVO
 Version: H6ET90WW (2.08 )
 Release Date: 01/11/2013

[penalvch (penalvch)]

bmaupin, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197869/comments/17 because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure