Bug 110652 - [byt] GPU HANG: ecode 7:1:0xfffffffe, in gnome-shell
Summary: [byt] GPU HANG: ecode 7:1:0xfffffffe, in gnome-shell
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 08:14 UTC by mikhail.v.gavrilov
Modified: 2019-05-09 10:01 UTC (History)
1 user (show)

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


Attachments
dmesg (65.69 KB, text/plain)
2019-05-09 08:14 UTC, mikhail.v.gavrilov
Details
/sys/class/drm/card0/error (29.27 KB, text/plain)
2019-05-09 08:15 UTC, mikhail.v.gavrilov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mikhail.v.gavrilov 2019-05-09 08:14:14 UTC
Created attachment 144203 [details]
dmesg

[  512.296756] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in gnome-shell [1753], 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
Comment 1 mikhail.v.gavrilov 2019-05-09 08:15:49 UTC
Created attachment 144204 [details]
/sys/class/drm/card0/error
Comment 2 Chris Wilson 2019-05-09 08:30:21 UTC
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.)
Comment 3 mikhail.v.gavrilov 2019-05-09 09:58:22 UTC
(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.
Comment 4 Chris Wilson 2019-05-09 10:01:21 UTC
Let's optimistically pin this on mesa until proven otherwise.


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.