[Lenovo ThinkPad T430s] Screen freezes

[Kim Laplume]

Screen freezes, can be recovered by ctrl+alt+f1 and ctrl+alt+f7

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kim 2147 F.... pulseaudio
 /dev/snd/pcmC0D0p: kim 2147 F...m pulseaudio
CurrentDesktop: Unity
Date: Sun Jun 15 17:39:31 2014
HibernationDevice: RESUME=UUID=f9e49a5e-1cd3-4e88-8a31-f0ac3036ba93
InstallationDate: Installed on 2014-02-22 (113 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 2356LPG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=0b6dd4c9-b193-4392-b2ca-2d8d5950e350 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-23 (53 days ago)
dmi.bios.date: 04/30/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET94WW (2.54 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2356LPG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro 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:bvrG7ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2356LPG:pvrThinkPadT430s:rvnLENOVO:rn2356LPG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2356LPG
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Kim Laplume (kim-laplume)]

I updated the BIOS via the Lenovo provided boot image.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> G7ET99WW (2.59 )
> 03/18/2014

I will report if the error should reoccur

[Kim Laplume (kim-laplume)]

problem persists. I filed a new bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330696

I don't know if that was appropriate, I wanted to prevent in clutter in this report

[penalvch (penalvch)]

Kim Laplume, could you please test the latest upstream kernel available from the first line at the top page (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.16-rc1

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.

[Kim Laplume (kim-laplume)]

upgraded to kernel 3.16.0-031600rc1-generic, testing right now

[Kim Laplume (kim-laplume)]

after 2 evenings of normal usage without the screen freeze occuring, i'm very confident that the bug has been fixed with the kernel update.

i will of course keep using this kernel and report if it would occur.

[Kim Laplume (kim-laplume)]

bug occurred again just a minute ago. so i will remove the fixed-tags and add the bug-exists-tags.

i will wait for further instructions if i can help in any way or form...

[Kim Laplume (kim-laplume)]

It occurred in saucy, that was the lowest version I used on this machine.

[penalvch (penalvch)]

Ki Laplume, could you please capture the crash following https://wiki.ubuntu.com/DebuggingSystemCrash ? You would be looking for the words "call trace" or "backtrace".

[Kim Laplume (kim-laplume)]

as per https://wiki.ubuntu.com/X/Troubleshooting/Freeze here is the x server log just after a freeze

[Kim Laplume (kim-laplume)]

and the output of dmesg just after the process described below.

what i did as soon as the screen froze:
-push alt+print screen+1
-push alt+print screen+t
-recover from the bug by pressing ctrl+alt+f1 followed by ctrl+alt+f7

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[neon1ks (neon1ks)]

Lenovo Z580. This bug affect me.

[penalvch (penalvch)]

neon1ks, please do not adjust the Bug Title or the Tags, as this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
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.

As well, please do not announce in this report you created a new bug report.

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

Thank you for your understanding.

[neon1ks (neon1ks)]

https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1220426