[Lenovo IdeaPad Flex 14 NoteBook] Full System freeze

[hcbdhattem]

System completely freezes randomly, mostly when running firefox.

without intervention It happens in 2 stages:

1. first it locks everything up, except for my mouse and keyboard.
2. shortly after that the mouse and keyboard lock up and my system freezes.

If i can still use my keyboard in stage 1 and press ctr + alt + F2 I get these messages in the console:

Feb 28 14:07:21 Shinobu kernel: [ 1625.147864] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
Feb 28 14:07:21 Shinobu kernel: [ 1625.147868] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state
Feb 28 14:07:21 Shinobu kernel: [ 1625.152227] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152242] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152256] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152281] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152294] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152307] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152320] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152334] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152347] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152360] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152385] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152399] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152423] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152437] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152462] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152475] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152488] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152513] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152526] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152540] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152553] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152578] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152603] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152628] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152642] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152655] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152668] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt
Feb 28 14:07:21 Shinobu kernel: [ 1625.152682] [drm:ivybridge_irq_handler] *ERROR* Unclaimed register before interrupt

After switching back to the gui with ctr+alt+F7 the system will again continue to run normally (I no expert but i looks like it).

Added the full kernlog file

If you need more info let me know.

I have run memtest86+

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-17-generic 3.11.0-17.31
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tim 2110 F.... pulseaudio
 /dev/snd/controlC0: tim 2110 F.... pulseaudio
CRDA:
 country EU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Fri Feb 28 16:14:30 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=16b344f2-3571-48f1-b3b8-05ae5d1fdd41
InstallationDate: Installed on 2014-01-30 (28 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 20308
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=b9e3017d-62f9-4be2-8815-30a30f6b9e88 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-17-generic N/A
 linux-backports-modules-3.11.0-17-generic N/A
 linux-firmware 1.116.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8ACN07WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Strawberry 4A
dmi.board.vendor: LENOVO
dmi.board.version: 31900003Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Ideapad Flex 14
dmi.modalias: dmi:bvnLENOVO:bvr8ACN07WW:bd07/31/2013:svnLENOVO:pn20308:pvrLenovoIdeapadFlex14:rvnLENOVO:rnStrawberry4A:rvr31900003Std:cvnLENOVO:ct10:cvrLenovoIdeapadFlex14:
dmi.product.name: 20308
dmi.product.version: Lenovo Ideapad Flex 14
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.13 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.14-rc4-trusty/

[hcbdhattem (hardcorebarbiedoll)]

I have installed the latest upstream kernel and will see if it will crash again in the next couple of days.

[hcbdhattem (hardcorebarbiedoll)]

System/screen froze again with latest mainline kernel. (3.14rc4)
It did not lock up my keyboard and mouse this time.
This time is was recoverable by restarting lightdm via a terminal (ctrl + alt + F1)

the lines from kern.log:

Mar 4 16:11:36 Shinobu kernel: [ 2398.639803] [drm] stuck on render ring
Mar 4 16:11:36 Shinobu kernel: [ 2398.639814] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar 4 16:11:36 Shinobu kernel: [ 2398.639815] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 4 16:11:36 Shinobu kernel: [ 2398.639816] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 4 16:11:36 Shinobu kernel: [ 2398.639818] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 4 16:11:36 Shinobu kernel: [ 2398.639819] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Attached the gpu crash dump file

[Felix Moreno (info-justdust)]

this bug is still present in ubuntu 14.10 and ubuntu 15.04 beta, if you open two o three apps it will stop working, it happened to me with telegram, and firefox opening new tabs...

[Felix Moreno (info-justdust)]

it happens on mi flex x10, it seems some lenovo laptos affected.

[Joseph Salisbury (jsalisbury)]

@hcbdhattem, are you still seeing this bug as well in the latest release?

@Felix Moreno, are there any errors or traces in /var/log/syslog when this happens? If so, please post them.

[hcbdhattem (hardcorebarbiedoll)]

I'm currently running 14.04LTS with kernelversion 3.17.0-031700rc6-generic on my lenovo flex 14.

I haven't encountered the bug since my latest update (and maybe some before that, but I don't remember).

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Launchpad Janitor (janitor)]

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