gnome session freeze when open settings

[Xavier Hsinyuan]

gnome session freeze when open settings and do some operation e.g scroll down by mouse wheel to the bottom of the pannel

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Nov 4 16:01:04 2022
SourcePackage: gnome-session
UpgradeStatus: Upgraded to kinetic on 2022-09-07 (58 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Next time the problem happens please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[Xavier Hsinyuan (thelastlinex)]

Thanks your reply, and it seems to be a duplicate of LP#1998950?

[Daniel van Vugt (vanvugt)]

I see...

12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in gnome-control-c [5686]
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] gnome-shell[4227] context reset due to GPU hang
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] gnome-control-c[5686] context reset due to GPU hang
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] HuC authenticated
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] GuC submission enabled
12月 15 16:08:08 y9000x-nul kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled

[Zac Mussatt (zmussatt)]

Bug seems to remain in 5.19.0-40-generic and is specific to happening when settings panel is up. For me, I've only noticed this happen when manipulating the printers in the settings panel. This is on 22.10.

Apr 17 16:35:20 TEAL-IT-02 kernel: [28001.136992] Asynchronous wait on fence 0000:00:02.0:gnome-shell[3806]:d9730 timed out (hint:intel_atomic_commit_ready [i915])
Apr 17 16:35:20 TEAL-IT-02 kernel: [28001.136990] Asynchronous wait on fence 0000:00:02.0:gnome-shell[3806]:d972e timed out (hint:intel_atomic_commit_ready [i915])
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.010046] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in gnome-control-c [53467]
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.010278] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.112427] i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.113147] i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.113245] i915 0000:00:02.0: [drm] gnome-control-c[53467] context reset due to GPU hang
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.113328] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.113334] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.132148] i915 0000:00:02.0: [drm] HuC authenticated
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.132472] i915 0000:00:02.0: [drm] GuC submission enabled
Apr 17 16:35:24 TEAL-IT-02 kernel: [28005.132472] i915 0000:00:02.0: [drm] GuC SLPC enabled
Apr 17 16:39:33 TEAL-IT-02 kernel: [ 5.224216] i915 0000:00:02.0: [drm] VT-d active for gfx access

[Daniel van Vugt (vanvugt)]

Zac, please open a new bug because this is just a duplicate of a closed bug (other people don't experience the issue anymore).

[Daniel van Vugt (vanvugt)]

You might also want to try the workaround in bug 2007668