Created attachment 144203 [details]
[ 512.296756] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in gnome-shell , hang on rcs0
[ 512.296761] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 512.296762] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 512.296763] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 512.296764] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 512.296766] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 512.296875] i915 0000:00:02.0: Resetting chip for hang on rcs0
$ inxi -bM
System: Host: localhost Kernel: 5.1.0-1.fc31.x86_64 x86_64 bits: 64 Desktop: Gnome 3.32.1
Distro: Fedora release 31 (Rawhide)
Machine: Type: Laptop System: ASUSTeK product: T100TA v: 1.0 serial: <root required>
Mobo: ASUSTeK model: T100TA v: 1.0 serial: <root required> UEFI: American Megatrends v: T100TA.314 date: 08/13/2015
Battery: ID-1: BATC charge: 23.9 Wh condition: 28.4/30.6 Wh (93%)
CPU: Quad Core: Intel Atom Z3740 type: MCP speed: 533 MHz min/max: 533/1866 MHz
Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 v: kernel
Display: wayland server: Fedora Project X.org 1.20.4 driver: i915 resolution: 1368x768~60Hz
OpenGL: renderer: Mesa DRI Intel Bay Trail v: 4.2 Mesa 19.1.0-rc1
Network: Message: No Device data found.
Drives: Local Storage: total: 87.69 GiB used: 11.85 GiB (13.5%)
Info: Processes: 243 Uptime: 47m Memory: 1.83 GiB used: 784.6 MiB (41.8%) Shell: bash inxi: 3.0.34
Created attachment 144204 [details]
Any clue as to whether it was introduced with the kernel or mesa update? Any clue if was introduced recently at all? (My expectation is that it will be timing dependent and not easy to reproduce at will.)
(In reply to Chris Wilson from comment #2)
> Any clue as to whether it was introduced with the kernel or mesa update? Any
> clue if was introduced recently at all? (My expectation is that it will be
> timing dependent and not easy to reproduce at will.)
Can not answer because this netbook lay idle for three years. Today I decided to wipe the dust in it and check how things are with the touch screen in Linux in 2019.
Let's optimistically pin this on mesa until proven otherwise.
Please test with
Author: Chris Wilson <email@example.com>
Date: Fri Apr 19 12:17:47 2019 +0100
drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context
heading to v5.1 via stable in the next few weeks.
*** This bug has been marked as a duplicate of bug 111014 ***