Bug 103574 - [ivb] GPU hang in gnome-shell
Summary: [ivb] GPU hang in gnome-shell
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-05 00:36 UTC by Taifu
Modified: 2018-03-20 18:03 UTC (History)
2 users (show)

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


Attachments
Crash dump (17.87 KB, text/plain)
2017-11-05 00:36 UTC, Taifu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Taifu 2017-11-05 00:36:36 UTC
Created attachment 135240 [details]
Crash dump

Upgraded from 16:04 to 17:10.
Never do that again... Unable to startx automatically now (only from terminal and with sudo).

Dmesg error:

[   34.814222] [drm] GPU HANG: ecode 7:0:0x85fffdfc, in gnome-shell [1342], reason: Hang on rcs0, action: reset
[   34.814224] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   34.814224] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   34.814225] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   34.814225] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   34.814226] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 Elizabeth 2017-11-07 17:41:42 UTC
From error state:
...
ERROR: 0x00000101
    TLB page fault error (GTT entry not valid)
    Cacheline containing a PD was marked as invalid
...
  FAULT_REG: 0x000000c5
    Valid
    Unloaded PD Fault (PPGTT)
    Address 0x00000000
    Source ID 24
...
  Active context: gnome-shell[1342] user_handle 1 hw_id 3, ban score 0 guilty 0 active 0
...
Active (rcs0) [16]:
...
    00000000_03201000     4096 7e 00 [ 16 00 00 00 00 ] 00 Y dirty purgeable LLC (fence: 2)
...

Last after IPEHR: 0x7a000003:
...
0x04ededc0:      0x7a000003: PIPE_CONTROL
0x04ededc4:      0x00106000:    qword write, cs stall, depth stall, 
0x04ededc8:      0x00858000:    destination address
0x04ededcc:      0x00000000:    immediate dword low
0x04ededd0:      0x00000000:    immediate dword high
0x04ededd4:      0x78150005: 3DSTATE_CONSTANT_VS
0x04ededd8:      0x00000004:    len 0 = 4, len 1 = 0
0x04ededdc:      0x00000000:    len 2 = 0, len 3 = 0
0x04edede0:      0x00007541:    pointer to constbuf 0
0x04edede4:      0x00000000:    pointer to constbuf 1
0x04edede8:      0x00000000:    pointer to constbuf 2
0x04ededec:      0x00000000:    pointer to constbuf 3
0x04ededf0:      0x78170005: 3DSTATE_CONSTANT_PS
0x04ededf4:      0x00000001:    len 0 = 1, len 1 = 0
0x04ededf8:      0x00000000:    len 2 = 0, len 3 = 0
0x04ededfc:      0x00007521:    pointer to constbuf 0
0x04edee00:      0x00000000:    pointer to constbuf 1
0x04edee04:      0x00000000:    pointer to constbuf 2
0x04edee08:      0x00000000:    pointer to constbuf 3
0x04edee0c:      0x782a0000: 3DSTATE_BINDING_TABLE_POINTERS_PS
0x04edee10:      0x000074e0:    dword 1
0x04edee14:      0x782f0000: 3DSTATE_SAMPLER_STATE_POINTERS_PS
0x04edee18:      0x000074c0:    dword 1
0x04edee1c:      0x78080003: 3DSTATE_VERTEX_BUFFERS
0x04edee20:      0x00014020:    buffer 0: sequential, pitch 32b
0x04edee24:      0x03247200:    buffer address
0x04edee28:      0x03247481:    max index
0x04edee2c:      0x00000000:    mbz
0x04edee30:      0x78090003: 3DSTATE_VERTEX_ELEMENTS
0x04edee34:      0x02400000:    buffer 0: valid, type 0x0040, src offset 0x0000 bytes
0x04edee38:      0x11130000:    (X, Y, Z, 1.0), dst offset 0x00 bytes
0x04edee3c:      0x02850010:    buffer 0: valid, type 0x0085, src offset 0x0010 bytes
0x04edee40:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0x04edee44:      0x7b000005: 3DPRIMITIVE: 
0x04edee48:      0x00000006:    tri fan sequential
0x04edee4c:      0x00000004:    vertex count
0x04edee50:      0x00000010:    start vertex
0x04edee54:      0x00000001:    instance count
0x04edee58:      0x00000000:    start instance
0x04edee5c:      0x00000000:    index bias
0x04edee60:      0x05000000: MI_BATCH_BUFFER_END
Comment 2 Elizabeth 2017-12-27 18:04:15 UTC
Could you try kernel 4.9 and share your mesa version?
Thank you.
Comment 3 Vladimir Los 2018-03-20 18:03:17 UTC
No any crushes were reproduced.

By default Ubuntu 17.10 was updated without installing XOrg. Due to this second and third option in LogIn window (“Ubuntu on xorg” and “Unity”) couldn’t find X files. 
After X had been installed the ability to select remained two options has been allowed. 


Updated from 16.04.4 to 17.10 through:
SystemSettings->Software&Updates->Updates->Notify me of a new Ubuntu version: "For any new version"
Software Updater->Upgrade...


Tested with all kernel below:
*:$ ~ukuu --list-installed
ukuu v18.1
Distribution: Ubuntu 17.10
Architecture: amd64
...
----------------------------------------------------------------------
Found installed: 4.13.0-37.42
Found installed: 4.13.0-36.40
Found installed: 4.15.11-041511.201803190530
Found installed: 4.13.0.37.40
Found installed: 4.9.88-040988.201803181131
----------------------------------------------------------------------

System:
*:~$ inxi -CGS
System:    Host: *** Kernel: 4.******-generic x86_64 bits: 64 Desktop: Gnome 3.26.2
           Distro: Ubuntu 17.10
CPU:       Quad core Intel Core i5-3470 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 1764 MHz 2: 1602 MHz 3: 1747 MHz 4: 1600 MHz
Graphics:  Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
           Display Server: wayland (X.Org 1.19.5 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@59.96hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Desktop version: 4.2 Mesa 17.2.8


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.