GPU hangs during login to rotated display

[Christopher Barrington-Leigh]

This is occuring when I change users, and when I log in from the login GUI, but not 100% of the time (!).
It just started yesterday.

Boot brings up the graphical login screen normally. I log in with the primary/only user, and the screen goes very dark and I get just a mouse pointer which appears and moves if I use the mouse (trackpad or etc).
I don't seem to be able to get windows to work, but if I could I couldn't see them, since the screen stays black except for that pointer.

If I type Ctrl-Alt-F1, it takes a few seconds rather than less than 1 to get to a TTY. There, there is a steady but slow stream of errors coming up that look like this:

*ERROR* render ring hung inside bo (0xxxx) at (0xxxx)
drm:i915_hangcheck_elapsed
i915_set_reset_status *ERROR* render ring hung inside bo

I can however, log in fine in TTY and access my files. It looks like nothing much is running (top), and I don't see the normal X processes.

This is making my computer unusable. I'm running on the latest 13.10 on a Lenovo thinkpad X230tablet.
I don't think I made any changes. There was one update that occurred shortly before this started yesterday, but it doesn't have anything suspicious-looking in it. It was:

Start-Date: 2014-01-06 15:34:15
Commandline: apt-get dist-upgrade
Upgrade: libnautilus-extension1a:amd64 (3.8.2-0ubuntu2.1, 3.8.2-0ubuntu2.2), libjavascriptcoregtk-3.0-0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), libwe
bkitgtk-1.0-0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), gir1.2-javascriptcoregtk-3.0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), ubuntu-release-upgrader-
gtk:amd64 (0.205.2, 0.205.4), usb-creator-common:amd64 (0.2.50, 0.2.50.1), nautilus:amd64 (3.8.2-0ubuntu2.1, 3.8.2-0ubuntu2.2), libwebkitgtk-3.0-0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), nautilus-data:amd64 (3.8.2-0ubuntu2.1, 3.8.2-0ubuntu2.2), python3-distupgrade:amd64 (0.205.2, 0.205.4), libwebkitgtk-3.0-common:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), libwebkitgtk-1.0-common:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), usb-creator-gtk:amd64 (0.2.50, 0.2.50.1), ubuntu-release-upgrader-core:amd64 (0.205.2, 0.205.4), libjavascriptcoregtk-1.0-0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3), gir1.2-webkit-3.0:amd64 (1.10.2-0ubuntu2, 1.10.2-0ubuntu3)
End-Date: 2014-01-06 15:35:01

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jan 7 09:03:14 2014
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2203]
InstallationDate: Installed on 2013-12-13 (24 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 34372VU
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=33e2b43f-d28c-4bf2-ae8b-17e29f42082a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET21WW (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 34372VU
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGCET21WW(1.10):bd07/25/2012:svnLENOVO:pn34372VU:pvrThinkPadX230Tablet:rvnLENOVO:rn34372VU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 34372VU
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Tue Jan 7 08:26:34 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728
 vendor LGD
xserver.version: 2:1.14.3-3ubuntu2

[Launchpad Janitor (janitor)]

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

[Simon SimonG (simongmilsimon)]

I'm having very similar issues and I noticed that the same symptoms appear when I change my screen orientation, log out and log back in. For some reason, If I keep the rotation normal and use xrandr to manually rotate the screen, I don't get these problems.

Christopher, are you changing the screen rotation by any chance?

[Chris Wilson (ickle)]

He is - a rotated secondary display.

Please note that with these bugs, the /sys/class/drm/card0/error file is vital for debugging the issue.

[Christopher Barrington-Leigh (cpbl)]

Whoo. By what means, if not xrandr? I'm certainly changing screen rotation
sometimes, though not by choice. One of the many things that's buggy or
become buggy on this wretched machine (ie combo of hardware and software)
is that when I undock my laptop from its dockingstation (and possibly in
other circumstances too?), the screen sometimes rotates the way it might if
I were converting to tablet mode (It's an X230 tablet).
 However, I don't think I've noticed anything like a 1-to-1 relationship
between that problem (fixed simply by pushing a rotate-screen hardware
button next to the display) and the can't-login problem. I don't know how
to initiate the problem, in fact.

Is yours fully reproducible?

On Fri, Feb 21, 2014 at 3:44 PM, Simon SimonG <email address hidden>wrote:

> I'm having very similar issues and I noticed that the same symptoms
> appear when I change my screen orientation, log out and log back in.
> For some reason, If I keep the rotation normal and use xrandr to
> manually rotate the screen, I don't get these problems.
>
> Christopher, are you changing the screen rotation by any chance?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1266784
>
> Title:
> i915_set_reset_status *ERROR* render ring hung inside bo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1266784/+subscriptions
>

[Christopher Barrington-Leigh (cpbl)]

Oh, well, that's true that it has happened when I'm docked to an external display, but it has also happened when I'm not connected to anything.

The title of this bug has apparently been changed to relate only to the rotated display. From my pov, that's premature.

Chris Wilson, there's no /sys/class/drm/card0*/error right now. Next time I'm shut down with this, I'll look for such a file.

[Chris Wilson (ickle)]

Possibly... Deliver distinct error states and I might reconsider ;-)

[Simon SimonG (simongmilsimon)]

Chris W.:

There are no 'error' files under any (sub)directory in /sys/class/drm. I can constantly reproduce the symptoms described in this bug on my system.

Steps to reproduce:
I create a new user account
log into this account via graphical interface
rotate the display using the Screen Display panel.
log out
log in with this new account

As soon as the display is rotated, my session seems to freeze but the mouse still moves. When I go to the text console (crtl-alt-f1), I see the kernel messages about i915 hang check and render ring hung inside bo.

Should I create a new bug report with my config files?

[Christopher Barrington-Leigh (cpbl)]

I had another (long) episode of this bug, and there were no files matching
/sys/class/drm/card0*/error

Also, this was on a laptop without any external display whatsoever.
However, it is true that the internal display, which comes up black with only a useless mouse cursor, was rotated for some reason.

Simon SimonG: When you say "rotate the display" does that mean the only/internal one? Or are you rotating something external?

Thanks for the reproduction steps! I'll try them when you specify that detail

[Simon SimonG (simongmilsimon)]

I'm using a 2011 MAC Mini system running Ubuntu 13.10 with legacy boot mode (non-EFI). I only have one display, which is the HDMI output (with an HDMI to DVI converter).

[Simon SimonG (simongmilsimon)]

FYI Christopher,

If you manage to reproduce the bug using my steps, you can undo the monitor settings by deleting your ~/.config/monitors.xml file. The Screen Display application stores it's settings in that file.

[Christopher Barrington-Leigh (cpbl)]

I tried your steps and they were not sufficient to cause the problem on my machine.

[Paweł Stołowski (stolowski)]

I get this error pretty consistently when having desktop effects enabled and using google hangouts at the same time; it makes my screen freeze for several seconds, sometimes it recovers after a while (and freezes again some time later), but sometimes it freezes completely and I'm forced to do hard reset. When this happens, I see same i915 error messages as in the description of this bug.

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]