Bug 93886 - GPU Hang "stuck on render ring" (probably userspace)
Summary: GPU Hang "stuck on render ring" (probably userspace)
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-27 14:43 UTC by Erich Schubert
Modified: 2016-09-13 15:06 UTC (History)
3 users (show)

See Also:
i915 platform: SNB
i915 features: GPU hang


Attachments
/sys/class/drm/card0/error (488.01 KB, application/gzip)
2016-01-27 14:43 UTC, Erich Schubert
no flags Details
Example of font corruption (5.17 KB, image/png)
2016-02-01 00:23 UTC, Erich Schubert
no flags Details
font corruption example (91.53 KB, image/png)
2016-03-21 22:13 UTC, Andrej
no flags Details
journalctl log (drm/kernel) (6.87 KB, text/plain)
2016-03-21 22:14 UTC, Andrej
no flags Details

Description Erich Schubert 2016-01-27 14:43:27 UTC
Created attachment 121325 [details]
/sys/class/drm/card0/error

dmesg:
[14047.920290] [drm] stuck on render ring
[14047.921017] [drm] GPU HANG: ecode 6:0:0x84fefffc, in chromium [5029], reason: Ring hung, action: reset
[14047.921018] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[14047.921019] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[14047.921020] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[14047.921021] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[14047.921022] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[14047.923116] drm/i915: Resetting chip after gpu hang

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller
	Flags: bus master, fast devsel, latency 0, IRQ 33
	Memory at c0000000 (64-bit, non-prefetchable) [size=4M]
	Memory at b0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 2000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

CPUinfo:
model name	: Intel(R) Core(TM) i7-2677M CPU @ 1.80GHz

Kernel version: 4.4.0-trunk from Debian

XOrg info:
[    20.798] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151010
[    20.798] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1 (Timo Aaltonen <tjaalton@debian.org>)
[    20.798] (II) intel(0): SNA compiled for use with valgrind
[    20.800] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000

[    20.826] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
[    20.826] (==) intel(0): Backing store enabled
[    20.826] (==) intel(0): Silken mouse enabled
[    20.827] (II) intel(0): HW Cursor enabled
[    20.827] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    20.828] (==) intel(0): DPMS enabled
[    20.828] (==) intel(0): Display hotplug detection enabled


I've been seeing graphics rendering issues for several weeks now (not so much in Chromium, but very frequently in xfce4-terminal); probably due to driver upgrades. Currently using "2:2.99.917+git20151217-1~exp1" from Debian experimental. I will try downgrading to unstable to see if the issue persists.

I've titled this as "probably userspace" because of the experimental userspace driver version.
Comment 1 Erich Schubert 2016-02-01 00:23:07 UTC
Created attachment 121429 [details]
Example of font corruption

Instead of missing text, I now have sometimes garbage fonts.

With new driver version:
xserver-xorg-video-intel (2:2.99.917+git20160127-1)
Comment 2 Andrej 2016-03-21 22:12:21 UTC
Seems the same bug on my laptop after resuming from suspend.

OS: Fedora 23 / KDE

Description of problem:
After resuming from suspend fonts are messed up. This bug started after a recent update (max. 2 weeks ago from now).

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-19.20151206.fc23.x86_64
xorg-x11-server-Xorg-1.18.1-3.fc23.x86_64
kernel-4.4.5-300.fc23.x86_64

How reproducible:
Suspend computer (by closing a laptop lid) and then resume from suspend.

Actual results:
Many letters are missing all over the place, most notably in Firefox (see screenshot).

Expected results:
Font rendering should be the same as before suspend.

Hardware:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev ff)
Laptop: Asus Zenbook UX32VD


Attachments:
1. example screenshot
2. journalctl log (grep drm|kernel)
Comment 3 Andrej 2016-03-21 22:13:47 UTC
Created attachment 122469 [details]
font corruption example
Comment 4 Andrej 2016-03-21 22:14:42 UTC
Created attachment 122470 [details]
journalctl log (drm/kernel)
Comment 5 Erich Schubert 2016-03-23 16:41:43 UTC
Right now, I have not experienced this issue anymore for at least two weeks.
I experimented with the modesetting driver, but brightness controls were broken after resume, that is not usable for me. The "intel" driver works better.

Kernel: 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1
Driver: intel, 2:2.99.917+git20160307-2

This combination currently works for me. YMMV. I guess the bug was fixed in the meantime.
Comment 6 yann 2016-09-13 15:06:08 UTC
(In reply to Erich Schubert from comment #5)
> Right now, I have not experienced this issue anymore for at least two weeks.
> I experimented with the modesetting driver, but brightness controls were
> broken after resume, that is not usable for me. The "intel" driver works
> better.
> 
> Kernel: 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1
> Driver: intel, 2:2.99.917+git20160307-2
> 
> This combination currently works for me. YMMV. I guess the bug was fixed in
> the meantime.

Closing this issue. If you are facing it again, please reopen the bug and attach new logs (kernel & gpu crash dump).


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.