Bug ID 1161720
Summary i915 hang continues in 5.4.12-1-default
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter cwdillon@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 828183 [details]
contents of /sys/class/drm/card0/error

I dropped down to 5.4.12-default today when the latest Tumbleweed release came
out and have already experienced graphical environment freeze with this error. 

Perhaps I misunderstood that Tumbleweed release managers applied the
drm/i915/gt patch to 5.4.12 default kernel? I understand that this patch is not
planned to be applied to 5.4 branch kernels by i915 drm managers.
(https://www.spinics.net/lists/stable/msg351278.html)

I hadn't experienced any freezes under 5.4.13 pre-release from Kernel:next (but
I also don't any support for Bumblebee/NVIDIA in that kernel).

Also attaching the contents of dmesg | grep i915:

```
[    3.845376] i915 0000:00:02.0: vgaarb: deactivate vga console
[    3.847415] i915 0000:00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    3.848292] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin
(v1.4)
[    4.529697] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor
0
[    4.681033] fbcon: i915drmfb (fb0) is primary device
[    4.725228] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
[    9.671989] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops
i915_audio_component_bind_ops [i915])
[    9.721605] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04:
bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ 3021.917516] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
[ 3021.917518] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
[ 3021.918523] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 3021.919248] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed
out: {request: 00000001, RESET_CTL: 00000001}
[ 3021.919351] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 3021.921095] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed
out: {request: 00000001, RESET_CTL: 00000001}
[ 3021.921814] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed
out: {request: 00000001, RESET_CTL: 00000001}

```


You are receiving this mail because: