[i915] [drm] GPU HANG: ecode 12:0:00000000

Bug #2001914 reported by Tsvetomir
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
linux-oem-5.17 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is:

Jan 05 12:10:40 Linux kernel: i915 0000:00:02.0: [drm]i915 0000:00:02.0: [drm] GPU HANG: ecode 12:0:00000000
Jan 05 12:10:40 Linux kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Jan 05 12:10:40 Linux kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled
Jan 05 12:10:40 Linux kernel: i915 0000:00:02.0: [drm] GuC SLPC: enabled
Jan 05 12:10:40 Linux kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes
Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 5 12:25:49 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-02 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tsvetomir (tsvetovasilev) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Does the bug still happen with the latest kernel update 5.15.0-58.64 ?

Try updating:

  sudo apt update
  sudo apt full-upgrade

and then reboot.

affects: gnome-shell (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Tsvetomir (tsvetovasilev) wrote :

Yes, it does! Sometimes I have to restart the laptop, cause I don't have other terminal to restart the GPU. And the kernel is the same 5.15.0-58.64.
Sorry, but for now and for me the problem isn't "Closed".

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brian Knutsson (maps-t) wrote :

I have the same issue. I got this output from dmesg:

[14591.143452] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:0:00000000
[14591.143865] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[14591.147696] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled
[14591.147702] i915 0000:00:02.0: [drm] GuC SLPC: enabled
[14591.147705] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes

Seems like this is a common issue: https://gitlab.freedesktop.org/drm/intel/-/issues/6916

Revision history for this message
Brian Knutsson (maps-t) wrote :

user@host:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
user@host:~$ uname -a
Linux host 5.17.0-1028-oem #29-Ubuntu SMP PREEMPT Fri Feb 10 10:28:20 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

summary: - The gpu hangs and is not possible to work with GPU-envioronment
+ [i915] [drm] GPU HANG: ecode 12:0:00000000
Changed in linux-oem-5.17 (Ubuntu):
status: New → Confirmed
Revision history for this message
Tuukka Hastrup (tuukkah2) wrote :

On my machine (Framework 13, 12th Gen Intel), this started when I upgraded 22.10 from 5.19.0-38-generic to 5.19.0-40-generic. After downgrade, it hasn't returned for now. I wonder if others also have this line about "fence" before each hang like I do:

  Apr 18 18:22:20 kernel: Asynchronous wait on fence 0000:00:02.0:gnome-shell[2578]:47f4 timed out (hint:intel_atomic_commit_ready [i915])
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:0:00000000
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] HuC authenticated
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] GuC submission enabled
  Apr 18 18:22:22 kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled

The only other difference I notice compared to -38 is a new error/warning at each boot on -40:

  Apr 19 00:35:20 kernel: i915 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A

Do we have this patch applied (as mentioned on the freedesktop.org issue? https://patchwork.freedesktop.org/series/114080/

Revision history for this message
Arsen Kitov (akitov) wrote :

I had this exact error. I downgraded from 5.19.0-41 to 5.19.0-38 and that did NOT fix the issue.

What I think helped is following this reddit thread (link below), i.e., setting i915.enable_dc=0 kernel parameter. So far two days and no freezes, before it used to freeze for 5-10 seconds every couple of hours.

For reference, my laptop is Dell Latitude 7430, with i7-1265u with integrated graphics.

https://www.reddit.com/r/linuxquestions/comments/yiiua7/does_anyone_know_what_the_status_is_on_the_i915/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.