Comment 8 for bug 2001914

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/