Bug 97785 - WebKitGtk+ 2.13.91 hangs my Intel GPU
Summary: WebKitGtk+ 2.13.91 hangs my Intel GPU
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
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-09-13 12:23 UTC by Andrés Gómez García
Modified: 2017-02-22 07:36 UTC (History)
2 users (show)

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


Attachments
GPU dump error at /sys/class/drm/card0/error (1.98 MB, text/plain)
2016-09-13 12:23 UTC, Andrés Gómez García
no flags Details

Description Andrés Gómez García 2016-09-13 12:23:36 UTC
Created attachment 126482 [details]
GPU dump error at /sys/class/drm/card0/error

I'm using WebKitGtk+ with my own JHBuild setting:
https://github.com/tanty/jhbuild-epiphany/tree/master

Epiphany 3.20.3 and WebKit 2.13.91.

I'm running Epiphany with the dconf key:

"process-model" = "shared-secondary-process"

The compilation was done with CMake args:

'-DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS"'

Just by opening the last closed session, the desktop gets stall, even when there is, apparently, no high CPU usage.

I can see this in the logs:

$ less /var/log/kern.log

[snip]

Sep 12 18:02:33 pomeron kernel: [  142.207298] [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle
Sep 12 18:03:33 pomeron kernel: [  202.140067] [drm] no progress on render ring
Sep 12 18:03:33 pomeron kernel: [  202.141208] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Ring hung, action: reset
Sep 12 18:03:33 pomeron kernel: [  202.141212] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Sep 12 18:03:33 pomeron kernel: [  202.141214] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Sep 12 18:03:33 pomeron kernel: [  202.141217] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Sep 12 18:03:33 pomeron kernel: [  202.141219] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Sep 12 18:03:33 pomeron kernel: [  202.141222] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Sep 12 18:03:33 pomeron kernel: [  202.141409] [drm:i915_switch_context [i915]] *ERROR* ring init context: -11
Sep 12 18:03:33 pomeron kernel: [  202.143473] drm/i915: Resetting chip after gpu hang
Sep 12 18:03:33 pomeron kernel: [  202.396871] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Sep 12 18:03:33 pomeron kernel: [  202.399002] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Sep 12 18:03:33 pomeron kernel: [  202.399026] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Sep 12 18:03:33 pomeron kernel: [  202.408353] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Sep 12 18:03:33 pomeron kernel: [  202.432732] [drm:intel_check_pch_fifo_underruns [i915]] *ERROR* pch fifo underrun on pch transcoder B
Sep 12 18:03:41 pomeron kernel: [  210.163587] [drm] stuck on render ring
Sep 12 18:03:41 pomeron kernel: [  210.163990] [drm] GPU HANG: ecode 6:0:0x0009090b, in WebKitWebProces [4143], reason: Ring hung, action: reset
Sep 12 18:03:41 pomeron kernel: [  210.166054] drm/i915: Resetting chip after gpu hang


$ lspci -v

[snip]

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller
        Flags: bus master, fast devsel, latency 0, IRQ 34
        Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 5000 [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

$ glxinfo | grep string
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.2
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 11.2.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

$ uname -a
Linux pomeron 4.6.0-1-amd64 #1 SMP Debian 4.6.1-1 (2016-06-06) x86_64 GNU/Linux
Comment 1 yann 2016-09-13 12:44:53 UTC
Looks like this is not occurring in any batch. Can you attach kernel log (keep it untouched from boot time) and add "drm.debug=0xe log_buf_len=1M" as command line boot parameters
Comment 2 Chris Wilson 2016-09-13 12:56:46 UTC
It's still a userspace GPU hang. Just it resulted in the command parser no longer functioning, the HEAD was advancing but it was no longer executing commands.
Comment 3 Ricardo 2017-02-21 17:01:26 UTC
@Andres can you please provide futher information requested, if there is no update in 30 days the bug will be closed due to lack of activity.
Comment 4 Andrés Gómez García 2017-02-22 07:32:59 UTC
(In reply to Ricardo from comment #3)
> @Andres can you please provide futher information requested, if there is no
> update in 30 days the bug will be closed due to lack of activity.

I cannot reproduce this any longer so I cannot provide further information.
Comment 5 yann 2017-02-22 07:36:05 UTC
(In reply to Andrés Gómez García from comment #4)
> (In reply to Ricardo from comment #3)
> > @Andres can you please provide futher information requested, if there is no
> > update in 30 days the bug will be closed due to lack of activity.
> 
> I cannot reproduce this any longer so I cannot provide further information.

thanks Andrés Gómez García. So I am closing this ticket. Please reopen new one if it happens again.


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.