Display freeze when using gnome settings " display" to enable/disable displays on eGPU

[beadon]

When using the Ubuntu settings app to change displays I was enabling and disabling displays to see if I could replicate a problem. It appears that the drivers / setup are OK with 2x displays, but things start to fall apart when there are 3x displays. 2x displys managed by NVIDIA displayport connection, and 1x display managed by the Intel Iris GPU.

I have noticed that windows appear to move between displays, so I think there is a problem with how the displays and the windows are arranged.

Attached are as many logs as I can find for this problem.

Notably, I am receiving errors in my local terminal when reporting this bug:

 [15578:15578:0710/200056.340294:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[15578:15578:0710/200056.356275:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[15578:15578:0710/200056.357312:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[15529:15529:0710/200138.416553:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented

This appears to be related to DRM ??

Tehese messages occured as I enabled / disabled the displays on displayport:
[Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer memory not appropriate for scanout
[Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer memory not appropriate for scanout
[Mon Jul 10 19:53:41 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x00000000fc099386
[Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x00000000cd359766
[Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x0000000040936ab7

These messages appeard when I started the gnome display manager :

Mon Jul 10 19:46:16 2023] rfkill: input handler enabled
[Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x00000000f989da34
[Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x0000000032149488
[Mon Jul 10 19:46:18 2023] rfkill: input handler disabled
[Mon Jul 10 19:46:25 2023] bijiben-shell-s[3102]: segfault at 7f9c05be1b13 ip 00007f9c1bb4e5a1 sp 00007fff6f49e438 error 4 in libgobject-2.0.so.0.7600.1[7f9c1bb24000+34000] likely on CPU 6 (core 2, socket 0)
[Mon Jul 10 19:46:25 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:26 2023] bijiben-shell-s[3224]: segfault at 7fcb58c86283 ip 00007fccc790c5a1 sp 00007ffd276291d8 error 4 in libgobject-2.0.so.0.7600.1[7fccc78e2000+34000] likely on CPU 2 (core 2, socket 0)
[Mon Jul 10 19:46:26 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:27 2023] bijiben-shell-s[3278]: segfault at 7f33cc004 ip 00007f33f16425a1 sp 00007ffd563f0fb8 error 4 in libgobject-2.0.so.0.7600.1[7f33f1618000+34000] likely on CPU 0 (core 0, socket 0)
[Mon Jul 10 19:46:27 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:28 2023] bijiben-shell-s[3333]: segfault at 7f5bedc1f1b1 ip 00007f5c3a6025a1 sp 00007ffdba3e2308 error 4 in libgobject-2.0.so.0.7600.1[7f5c3a5d8000+34000] likely on CPU 0 (core 0, socket 0)
[Mon Jul 10 19:46:28 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:29 2023] bijiben-shell-s[3384]: segfault at 7f58ddf0b019 ip 00007f5f493745a1 sp 00007ffc9b25f038 error 4 in libgobject-2.0.so.0.7600.1[7f5f4934a000+34000] likely on CPU 6 (core 2, socket 0)
[Mon Jul 10 19:46:29 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:30 2023] bijiben-shell-s[3488]: segfault at 7f6fd2827793 ip 00007f6843a2d5a1 sp 00007ffdcc7353c8 error 4 in libgobject-2.0.so.0.7600.1[7f6843a03000+34000] likely on CPU 6 (core 2, socket 0)
[Mon Jul 10 19:46:30 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:30 2023] bijiben-shell-s[3559]: segfault at 7f1dec023 ip 00007f1e0fbf05a1 sp 00007ffc2a8a15c8 error 4 in libgobject-2.0.so.0.7600.1[7f1e0fbc6000+34000] likely on CPU 5 (core 1, socket 0)
[Mon Jul 10 19:46:30 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:30 2023] bijiben-shell-s[3604]: segfault at 7f24b2348c43 ip 00007f2362ab55a1 sp 00007ffe1d253728 error 4 in libgobject-2.0.so.0.7600.1[7f2362a8b000+34000] likely on CPU 0 (core 0, socket 0)
[Mon Jul 10 19:46:30 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74
[Mon Jul 10 19:46:31 2023] bijiben-shell-s[3651]: segfault at 7f3b8bc7c553 ip 00007f3c997ce5a1 sp 00007ffce62df018 error 4 in libgobject-2.0.so.0.7600.1[7f3c997a4000+34000] likely on CPU 5 (core 1, socket 0)
[Mon Jul 10 19:46:31 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74

Any assistance appreciated !

I believe this is preventing operation in some way ...

__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00005200] Failed to map NvKmsKapiMemory 0x0000000032149488

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.52.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023
 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 10 20:03:08 2023
DistUpgraded: 2023-04-26 15:38:23,675 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 8812au/5.6.4.2_35491.20191025, 6.2.0-23-generic, x86_64: installed
 8812au/5.6.4.2_35491.20191025, 6.2.0-24-generic, x86_64: installed
 nvidia/535.54.03, 6.2.0-24-generic, x86_64: installed
 virtualbox/7.0.6, 6.2.0-23-generic, x86_64: installed
 virtualbox/7.0.6, 6.2.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257]
InstallationDate: Installed on 2023-01-09 (182 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: LENOVO 20XY0027US
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago)
dmi.bios.date: 06/12/2023
dmi.bios.release: 1.61
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET85W (1.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XY0027US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.34
dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
dmi.product.family: ThinkPad X1 Yoga Gen 6
dmi.product.name: 20XY0027US
dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
dmi.product.version: ThinkPad X1 Yoga Gen 6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Were you using Wayland when the freeze happened? Next time it happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Daniel van Vugt (vanvugt)]

I'm now thinking the screen freeze was:

[ 198.184944] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
[ 198.209428] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
...
[ 199.493073] semiauto gnome-shell[2341]: meta_frame_native_release: assertion '!frame_native->kms_update' failed
[ 199.494175] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached
[ 199.494260] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached
[ 199.527787] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached

from bug 2026790. Because I can reproduce that perfectly by modifying code.

[beadon (bryant-eadon)]

added prevboot.txt here -- I switched to Xorg and am running into a similar problem, I will track my progress on the Xorg transition in the parallel bug report.

[beadon (bryant-eadon)]

Note that when I say "freeze" I am referring to SOME displays freezing, not all displays freeze. Others remain black (no signal), while at least 1 is "frozen" even though I can move my cursor from one screen to this "frozen" screen and also get it back.

[Daniel van Vugt (vanvugt)]

Thanks, I can see you switched to Xorg so the log in comment #5 is no longer relevant to this bug. Not all freezes have the same cause. What I can see in that log is the Nvidia driver refusing to support eGPUs at boot time:

Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): This device is an external GPU, but external GPUs have not
Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): been enabled with AllowExternalGpus. Disabling this device
Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW) NVIDIA(GPU-0): to prevent crashes from accidental removal.

To fix that you need to add a custom Xorg configuration line as documented in:

http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/egpu.html

But that's not actually related to this bug anymore since this original bug was almost certainly about a Wayland session. For this bug we are still waiting on an original log from the Wayland session (unless it's the log already posted in bug 2026790?).