Bug 99605 - [BDW] GPU HANG: ecode 8:0:0x13e3226f, in plasmashell [1093], reason: Hang on render ring, action: reset
Summary: [BDW] GPU HANG: ecode 8:0:0x13e3226f, in plasmashell [1093], reason: Hang on ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-30 21:01 UTC by Marcel Dischinger
Modified: 2017-02-02 07:56 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error after hibernate (717.53 KB, text/plain)
2017-01-30 21:01 UTC, Marcel Dischinger
no flags Details

Description Marcel Dischinger 2017-01-30 21:01:08 UTC
Created attachment 129238 [details]
/sys/class/drm/card0/error after hibernate

On returning from hibernation (suspend-to-disk) with kernel 4.9.x I get this problem. X is unusable after GPU reset, but at least I am able to switch to a console and can reboot from there (X/KDE is not usable after resume, my guess is that plasma crashes). 
Suspend-to-ram works without problems. I had no problems with hibernation in 4.8.x and before.

I am running Debian Testing with the 4.9.x kernels from Unstable (linux-image-4.9.0-1-amd64-unsigned 4.9.6-3) on amd64.
uname -a: Linux  4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux
I am using the modesetting X driver instead of the intel one, but I also tried with intel with the same problem.
Plasma is configured to use OpenGL 2.0

Hardware: Asus Zenbook UX303L

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. HD Graphics 5500
        Flags: bus master, fast devsel, latency 0, IRQ 46
        Memory at f6000000 (64-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
        Kernel modules: i915

client glx vendor string: Mesa Project and SGI
    Device: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)  (0x1616)
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 13.0.3
OpenGL version string: 3.0 Mesa 13.0.3
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.3
Comment 1 yann 2017-01-31 09:34:53 UTC
Marcel Dischinger, can you try with latest drm-tip kernel (https://cgit.freedesktop.org/drm/drm-tip/)?

From gpu crash dump, we can see that we have 2 waiters in render ring
 seqno 0x00001a42 for plasmashell [1093]
 seqno 0x00001a44 for Xorg [691]

and the sequence (I guess 0x00001a41)
has
0x00966204:      0x05e96da8: MI_SUSPEND_FLUSH
Bad length 57346 in 3DSTATE_LINE_STIPPLE, expected 3-3
0x00966208:      0x7908e000: 3DSTATE_LINE_STIPPLE

that ends finally with:
ERROR: Decode attempted to continue beyond end of batchbuffer

Chris, do you think that could be linked to a Mesa issue?
Comment 2 Marcel Dischinger 2017-02-01 18:58:00 UTC
I tried drm-tip a0695bf4e1c12de4863e775747fe850b92661dc6 (Jan 31st). The problem is gone with this version.

I would love to see thefix in 4.9 as well as it is a LTS release...

Thanks for your support and keep up the great work.
Comment 3 yann 2017-02-02 07:56:51 UTC
(In reply to Marcel Dischinger from comment #2)
> I tried drm-tip a0695bf4e1c12de4863e775747fe850b92661dc6 (Jan 31st). The
> problem is gone with this version.
> 
> I would love to see thefix in 4.9 as well as it is a LTS release...
> 
> Thanks for your support and keep up the great work.

thanks for your confirmation and feedback


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.