i915 GPU hang on chromebook peppy (Acer c720p)

I can confirm this on the same machine. I had this with Kubuntu 20.04 while trying the 20.04 5.8 kernel. No problems with the 5.6 kernel. Tried with X11/Wayland and both default and "AccelMethod" "sna".

Now after upgrading to Kubuntu 20.10 with 5.8 kernel same problem, while falling back to old 5.6 kernel no problem happens.

From journal:

chromium:~$ journalctl -b -1 | grep i915
kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
kernel: i915 0000:00:02.0: [drm] applying backlight present quirk
kernel: [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
kernel: fbcon: i915drmfb (fb0) is primary device
kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1087]
kernel: Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] Xorg[1087] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in ksplashqml [1284]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [1284]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] ksplashqml[1284] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1087]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] Xorg[1087] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in kwin_x11 [1422]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in QSGRenderThread [1416]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] QSGRenderThread[1416] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1087]
kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
kernel: i915 0000:00:02.0: [drm] Xorg[1087] context reset due to GPU hang

I just tried 5.9.1 kernel, which hangs even worse (with 5.8 the mouse is visible and moving during kde startup screen, with 5.9 just completely black)

Hi Reporter, can you try to reproduce this issue on latest drm-tip.

https://cgit.freedesktop.org/drm-tip

Please post your observations on it and any steps followed to reproduce the issue.

Issue persists on drm-tip 495b9f6832fabdc47ac38a5392c7b96749d5d274 and linux-firmware 7455a36066741a6e52fba65e04f6451b4cdfd9c4. Reproduction steps are in the first message.

This issue is still a problem for me, currently using the Acer C720P Chromebook with Arch Linux using linux 5.9.14.arch1-1. This has caused problems on various apps like Chromium, Discord, nextcloud-client and kdeconnect.

This is the relevant part when I used sudo journalctl -b. When trying to launch Chromium.

Dec 23 21:54:15 acer audit[990]: USER_AUTH pid=990 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="patrick" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Dec 23 21:54:15 acer xfce4-screensaver-dialog[971]: gkr-pam: unlocked login keyring
Dec 23 21:54:15 acer kernel: audit: type=1100 audit(1608785655.255:103): pid=990 uid=1000 auid=1000 ses=3 msg='op=PAM:unix_chkpwd acct="patrick" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Dec 23 21:54:15 acer xfce4-screensaver-dialog[971]: pam_warn(xfce4-screensaver:account): function=[pam_sm_acct_mgmt] flags=0 service=[xfce4-screensaver] terminal=[:0] user=[patrick] ruser=[<unknown>] rhost=[<unknown>]
Dec 23 21:54:41 acer kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in Xorg [417]
Dec 23 21:54:41 acer kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Dec 23 21:54:41 acer kernel: Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/intel/issues/new.
Dec 23 21:54:41 acer kernel: Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
Dec 23 21:54:41 acer kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Dec 23 21:54:41 acer kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.
Dec 23 21:54:41 acer kernel: GPU crash dump saved to /sys/class/drm/card0/error
Dec 23 21:54:41 acer kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Dec 23 21:54:41 acer kernel: i915 0000:00:02.0: [drm] Xorg[417] context reset due to GPU hang
Dec 23 21:54:44 acer kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in Xorg [417]
Dec 23 21:54:44 acer kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Dec 23 21:54:44 acer kernel: i915 0000:00:02.0: [drm] Xorg[417] context reset due to GPU hang

Probably a duplicate of #2024 (closed). The proposed patch fixes this issue for me.

closed

Good news, I am running 5.11.0-5c5 from ubuntu kernel ppa and the problem seems to be resolved .

i915 GPU hang on chromebook peppy (Acer c720p)

Child items ...

Activity

Admin message

Admin message

i915 GPU hang on chromebook peppy (Acer c720p)

Activity