Kernel Crash on PopOS Thinkpad x13 (AMD)

Level1 Store KVM Helpdesk
1

KVM Model:

  • HDMI 2.1 KVM w/EDID & Serial Control - Dual Monitor - Four Computer

USB Interface (5-gigabit or 10-gigbit):

10-gigbit

Problem:

I have connected the KVM to my Gaming-Rig running Windows, my Work-from-Home PC running Windows and my Lenovo Thunderbolt Dock with a Thinkpad x13 (AMD) running PopOS. Switching between the windows machines works like a breeze, but my Thinkpad keeps crashing when i switch away from it.

I get the following output in dmesg when this happens:

May 17 05:45:26 pop-os kernel: usb 5-1.3.4: USB disconnect, device number 29
May 17 05:45:26 pop-os kernel: usb 5-1.3.4.4: USB disconnect, device number 30
May 17 05:45:26 pop-os kernel: usb 5-1.3.4.4.1: USB disconnect, device number 31
May 17 05:45:26 pop-os acpid[922]: input device has been disconnected, fd 10
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) event14 - Logitech G Pro : device removed
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device Logitech G Pro
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "43"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: not releasing fd for 13:78, still in use
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device Logitech G Pro
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "43"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: releasing fd for 13:78
May 17 05:45:26 pop-os kernel: usb 5-1.3.4.4.2: USB disconnect, device number 32
May 17 05:45:26 pop-os kernel: usb 5-1.3.4.4.4: USB disconnect, device number 33
May 17 05:45:26 pop-os acpid[922]: input device has been disconnected, fd 11
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) event15 - ZSA Technology Labs Voyager: device removed
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device ZSA Technology Labs Voyager
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "73"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:26 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: releasing fd for 13:79
May 17 05:45:27 pop-os acpid[922]: input device has been disconnected, fd 12
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) event16 - ZSA Technology Labs Voyager System Control: device removed
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device ZSA Technology Labs Voyager System Control
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "65"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: releasing fd for 13:80
May 17 05:45:27 pop-os acpid[922]: input device has been disconnected, fd 13
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) event17 - ZSA Technology Labs Voyager Consumer Control: device removed
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device ZSA Technology Labs Voyager Consumer Control
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "67"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: not releasing fd for 13:81, still in use
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device ZSA Technology Labs Voyager Consumer Control
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "67"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: releasing fd for 13:81
May 17 05:45:27 pop-os acpid[922]: input device has been disconnected, fd 14
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) event18 - ZSA Technology Labs Voyager Keyboard: device removed
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) config/udev: removing device ZSA Technology Labs Voyager Keyboard
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (**) Option "fd" "68"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) UnloadModule: "libinput"
May 17 05:45:27 pop-os /usr/libexec/gdm-x-session[1609]: (II) systemd-logind: releasing fd for 13:82
May 17 05:45:43 pop-os kernel: [drm] DM_MST: stopping TM on aconnector: 000000007a3e9cf9 [id: 107]
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:43 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
May 17 05:45:44 pop-os kernel: [drm] Send DSC disable to synaptics
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (WW) AMDGPU(0): flip queue failed: Invalid argument
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (WW) AMDGPU(0): Page flip failed: Invalid argument
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Allocate new frame buffer 2560x1600
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0):  => pitch 10240 bytes
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:44 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:44 pop-os gnome-shell[1759]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
May 17 05:45:44 pop-os gnome-shell[1759]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
May 17 05:45:44 pop-os gnome-shell[1759]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
May 17 05:45:44 pop-os gnome-shell[1759]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os gnome-shell[1759]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
May 17 05:45:45 pop-os gnome-shell[1759]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
May 17 05:45:45 pop-os gnome-shell[1759]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
May 17 05:45:45 pop-os gnome-shell[1759]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
May 17 05:45:45 pop-os gnome-shell[1759]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
May 17 05:45:45 pop-os gnome-shell[1759]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5efce21182f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f15ae0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b860] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f156f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b4e0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5efce21182f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f15ae0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b860] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f156f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b4e0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f15300] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b160] is on because it needs an allocation.
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5efce21182f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f15ae0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b860] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5efce4f156f0] is on because it needs an allocation.
May 17 05:45:45 pop-os gnome-shell[1759]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5efce4f1b4e0] is on because it needs an allocation.
May 17 05:45:45 pop-os kernel: [drm] DM_MST: starting TM on aconnector: 000000007a3e9cf9 [id: 107]
May 17 05:45:45 pop-os kernel: [drm] DM_MST: DP14, 2-lane link detected
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:45 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:46 pop-os kernel: [drm] Downstream port present 1, type 2
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): EDID vendor "CSO", prod id 4869
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using hsync ranges from config file
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Using vrefresh ranges from config file
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Printing DDC gathered Modelines:
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Modeline "2560x1600"x0.0  268.63  2560 2608 2640 2720  1600 1603 1609 1646 -hsync -vsync (98.8 kHz eP)
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (WW) AMDGPU(0): flip queue failed: Invalid argument
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (WW) AMDGPU(0): Page flip failed: Invalid argument
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Allocate new frame buffer 5120x1600
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0):  => pitch 20480 bytes
May 17 05:45:46 pop-os kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
May 17 05:45:46 pop-os kernel: #PF: supervisor read access in kernel mode
May 17 05:45:46 pop-os kernel: #PF: error_code(0x0000) - not-present page
May 17 05:45:46 pop-os kernel: PGD 0 P4D 0 
May 17 05:45:46 pop-os kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
May 17 05:45:46 pop-os kernel: CPU: 7 PID: 1609 Comm: Xorg Tainted: G           OE      6.8.0-76060800daily20240311-generic #202403110203~1714077665~22.04~4c8e9a0
May 17 05:45:46 pop-os kernel: Hardware name: LENOVO 20XHCTO1WW/20XHCTO1WW, BIOS R1NET43W (1.13) 09/29/2021
May 17 05:45:46 pop-os kernel: RIP: 0010:drm_dp_add_payload_part2+0xbe/0xf0 [drm_display_helper]
May 17 05:45:46 pop-os kernel: Code: c8 8f c0 e8 d4 82 4d f7 44 89 f0 5b 41 5c 41 5d 41 5e 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 e9 b4 2b c3 f7 48 8b 80 78 05 00 00 <48> 8b 76 08 4c 8b 40 60 48 85 f6 74 04 48 8b 76 08 48 c7 c1 18 c8
May 17 05:45:46 pop-os kernel: RSP: 0018:ffff979f8f3c3460 EFLAGS: 00010297
May 17 05:45:46 pop-os kernel: RAX: ffff8c9ee9bf2000 RBX: ffff8c9ee9bf2000 RCX: 0000000000000000
May 17 05:45:46 pop-os kernel: RDX: ffff8c9ec1b91b80 RSI: 0000000000000000 RDI: ffff8c9ee7364800
May 17 05:45:46 pop-os kernel: RBP: ffff979f8f3c3480 R08: 0000000000000000 R09: 0000000000000000
May 17 05:45:46 pop-os kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8c9ee7364000
May 17 05:45:46 pop-os kernel: R13: ffff8c9eca546ae0 R14: ffff8ca089321000 R15: 0000000000000006
May 17 05:45:46 pop-os kernel: FS:  0000707bbb831a80(0000) GS:ffff8ca58ed80000(0000) knlGS:0000000000000000
May 17 05:45:46 pop-os kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 05:45:46 pop-os kernel: CR2: 0000000000000008 CR3: 0000000126002000 CR4: 0000000000f50ef0
May 17 05:45:46 pop-os kernel: PKRU: 55555554
May 17 05:45:46 pop-os kernel: Call Trace:
May 17 05:45:46 pop-os kernel:  <TASK>
May 17 05:45:46 pop-os kernel:  ? show_regs+0x6d/0x80
May 17 05:45:46 pop-os kernel:  ? __die+0x24/0x80
May 17 05:45:46 pop-os kernel:  ? page_fault_oops+0x99/0x1b0
May 17 05:45:46 pop-os kernel:  ? do_user_addr_fault+0x2f9/0x6c0
May 17 05:45:46 pop-os kernel:  ? exc_page_fault+0x83/0x1b0
May 17 05:45:46 pop-os kernel:  ? asm_exc_page_fault+0x27/0x30
May 17 05:45:46 pop-os kernel:  ? drm_dp_add_payload_part2+0xbe/0xf0 [drm_display_helper]
May 17 05:45:46 pop-os kernel:  dm_helpers_dp_mst_send_payload_allocation+0x51/0xa0 [amdgpu]
May 17 05:45:46 pop-os kernel:  allocate_mst_payload.isra.0+0x1d2/0x3b0 [amdgpu]
May 17 05:45:46 pop-os kernel:  link_set_dpms_on+0x699/0x6d0 [amdgpu]
May 17 05:45:46 pop-os kernel:  dce110_apply_single_controller_ctx_to_hw+0x38e/0x520 [amdgpu]
May 17 05:45:46 pop-os kernel:  dce110_apply_ctx_to_hw+0x20d/0x380 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? dcn10_wait_for_mpcc_disconnect+0x174/0x240 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  dc_commit_state_no_check+0x2ee/0xdc0 [amdgpu]
May 17 05:45:46 pop-os kernel:  dc_commit_streams+0x2e7/0x670 [amdgpu]
May 17 05:45:46 pop-os kernel:  amdgpu_dm_commit_streams+0x59a/0x730 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? drm_dp_mst_atomic_wait_for_dependencies+0x84/0x170 [drm_display_helper]
May 17 05:45:46 pop-os kernel:  amdgpu_dm_atomic_commit_tail+0xff/0x10a0 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? dma_resv_iter_first_unlocked+0x66/0x80
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? amdgpu_dm_plane_fill_plane_buffer_attributes+0x188/0x2d0 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? wait_for_completion_timeout+0x119/0x150
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? amdgpu_dm_plane_helper_prepare_fb+0x1a9/0x330 [amdgpu]
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  commit_tail+0xc2/0x190
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? drm_atomic_helper_swap_state+0x246/0x380
May 17 05:45:46 pop-os kernel:  drm_atomic_helper_commit+0x11d/0x150
May 17 05:45:46 pop-os kernel:  drm_atomic_commit+0x99/0xd0
May 17 05:45:46 pop-os kernel:  ? __pfx___drm_printfn_info+0x10/0x10
May 17 05:45:46 pop-os kernel:  drm_atomic_helper_set_config+0x82/0xd0
May 17 05:45:46 pop-os kernel:  drm_mode_setcrtc+0x4eb/0x830
May 17 05:45:46 pop-os kernel:  ? __pfx_drm_mode_setcrtc+0x10/0x10
May 17 05:45:46 pop-os kernel:  drm_ioctl_kernel+0xbc/0x120
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  drm_ioctl+0x2d0/0x550
May 17 05:45:46 pop-os kernel:  ? __pfx_drm_mode_setcrtc+0x10/0x10
May 17 05:45:46 pop-os kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
May 17 05:45:46 pop-os kernel:  __x64_sys_ioctl+0xa3/0xf0
May 17 05:45:46 pop-os kernel:  do_syscall_64+0x79/0x140
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? __x64_sys_epoll_wait+0x6f/0x110
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? syscall_exit_to_user_mode+0x8e/0x1e0
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? do_syscall_64+0x85/0x140
May 17 05:45:46 pop-os kernel:  ? syscall_exit_to_user_mode+0x8e/0x1e0
May 17 05:45:46 pop-os kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 17 05:45:46 pop-os kernel:  ? do_syscall_64+0x85/0x140
May 17 05:45:46 pop-os kernel:  ? do_syscall_64+0x85/0x140
May 17 05:45:46 pop-os kernel:  ? do_syscall_64+0x85/0x140
May 17 05:45:46 pop-os kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
May 17 05:45:46 pop-os kernel: RIP: 0033:0x707bbb71a94f
May 17 05:45:46 pop-os kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00
May 17 05:45:46 pop-os kernel: RSP: 002b:00007ffc8312bb30 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
May 17 05:45:46 pop-os kernel: RAX: ffffffffffffffda RBX: 00007ffc8312bbc0 RCX: 0000707bbb71a94f
May 17 05:45:46 pop-os kernel: RDX: 00007ffc8312bbc0 RSI: 00000000c06864a2 RDI: 000000000000000f
May 17 05:45:46 pop-os kernel: RBP: 00000000c06864a2 R08: 0000000000000000 R09: 000059fb30370450
May 17 05:45:46 pop-os kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
May 17 05:45:46 pop-os kernel: R13: 000000000000000f R14: 000059fb30370450 R15: 0000000000000000
May 17 05:45:46 pop-os kernel:  </TASK>
May 17 05:45:46 pop-os kernel: Modules linked in: ipmi_devintf ipmi_msghandler tls veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nf>
May 17 05:45:46 pop-os kernel:  edac_mce_amd bfq nls_iso8859_1 ecc snd_usbmidi_lib videobuf2_v4l2 snd_intel_sdw_acpi snd_ump snd_acp_pci videodev mac80211 snd_hda_codec snd_acp_legacy_common snd_seq_midi snd_seq_midi_event kvm_amd snd_hda_core videobu>
May 17 05:45:46 pop-os kernel:  crct10dif_pclmul r8169 hid_generic nvme_core cec video ucsi_acpi xhci_pci crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 psmouse typec_ucsi i2c_piix4 rc_core xhci_pci_renesas nv>
May 17 05:45:46 pop-os kernel: CR2: 0000000000000008
May 17 05:45:46 pop-os kernel: ---[ end trace 0000000000000000 ]---
May 17 05:45:46 pop-os kernel: RIP: 0010:drm_dp_add_payload_part2+0xbe/0xf0 [drm_display_helper]
May 17 05:45:46 pop-os kernel: Code: c8 8f c0 e8 d4 82 4d f7 44 89 f0 5b 41 5c 41 5d 41 5e 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 e9 b4 2b c3 f7 48 8b 80 78 05 00 00 <48> 8b 76 08 4c 8b 40 60 48 85 f6 74 04 48 8b 76 08 48 c7 c1 18 c8
May 17 05:45:46 pop-os kernel: RSP: 0018:ffff979f8f3c3460 EFLAGS: 00010297
May 17 05:45:46 pop-os kernel: RAX: ffff8c9ee9bf2000 RBX: ffff8c9ee9bf2000 RCX: 0000000000000000
May 17 05:45:46 pop-os kernel: RDX: ffff8c9ec1b91b80 RSI: 0000000000000000 RDI: ffff8c9ee7364800
May 17 05:45:46 pop-os kernel: RBP: ffff979f8f3c3480 R08: 0000000000000000 R09: 0000000000000000
May 17 05:45:46 pop-os kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8c9ee7364000
May 17 05:45:46 pop-os kernel: R13: ffff8c9eca546ae0 R14: ffff8ca089321000 R15: 0000000000000006
May 17 05:45:46 pop-os kernel: FS:  0000707bbb831a80(0000) GS:ffff8ca58ed80000(0000) knlGS:0000000000000000
May 17 05:45:46 pop-os kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 05:45:46 pop-os kernel: CR2: 0000000000000008 CR3: 0000000126002000 CR4: 0000000000f50ef0
May 17 05:45:46 pop-os kernel: PKRU: 55555554
May 17 05:45:46 pop-os kernel: note: Xorg[1609] exited with irqs disabled
May 17 05:45:52 pop-os touchegg[967]: libinput error: event22 - ELAN0678:00 04F3:3195 Touchpad: kernel bug: Touch jump detected and discarded.
May 17 05:45:52 pop-os touchegg[967]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
May 17 05:45:52 pop-os touchegg[967]: libinput error: event22 - ELAN0678:00 04F3:3195 Touchpad: kernel bug: Touch jump detected and discarded.
May 17 05:45:52 pop-os touchegg[967]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
May 17 05:45:59 pop-os kernel: usb 5-1.3.4: new high-speed USB device number 34 using xhci_hcd
May 17 05:45:59 pop-os kernel: usb 5-1.3.4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.07
May 17 05:45:59 pop-os kernel: usb 5-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:45:59 pop-os kernel: usb 5-1.3.4: Product: USB2.1 Hub
May 17 05:45:59 pop-os kernel: usb 5-1.3.4: Manufacturer: GenesysLogic
May 17 05:46:00 pop-os kernel: usb 5-1.3.4: can't set config #1, error -71
May 17 05:46:00 pop-os fwupd[1589]: 10:46:00.059 FuEngine             failed to probe device usb:05:00:01:03:04: USB error on device 05e3:0610 : Entity not found [-5]
May 17 05:46:00 pop-os kernel: usb 5-1.3.4: USB disconnect, device number 34
May 17 05:46:00 pop-os kernel: usb 5-1.3.4: new high-speed USB device number 35 using xhci_hcd
May 17 05:46:01 pop-os kernel: usb 5-1.3.4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.07
May 17 05:46:01 pop-os kernel: usb 5-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:46:01 pop-os kernel: usb 5-1.3.4: Product: USB2.1 Hub
May 17 05:46:01 pop-os kernel: usb 5-1.3.4: Manufacturer: GenesysLogic
May 17 05:46:01 pop-os kernel: hub 5-1.3.4:1.0: USB hub found
May 17 05:46:01 pop-os kernel: hub 5-1.3.4:1.0: 4 ports detected
May 17 05:46:01 pop-os kernel: usb 5-1.3.4.4: new high-speed USB device number 36 using xhci_hcd
May 17 05:46:01 pop-os kernel: usb 5-1.3.4.4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.07
May 17 05:46:01 pop-os kernel: usb 5-1.3.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:46:01 pop-os kernel: usb 5-1.3.4.4: Product: USB2.1 Hub
May 17 05:46:01 pop-os kernel: usb 5-1.3.4.4: Manufacturer: GenesysLogic
May 17 05:46:01 pop-os kernel: hub 5-1.3.4.4:1.0: USB hub found
May 17 05:46:01 pop-os kernel: hub 5-1.3.4.4:1.0: 4 ports detected
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.1: new full-speed USB device number 37 using xhci_hcd
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.1: New USB device found, idVendor=046d, idProduct=c539, bcdDevice=39.06
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.1: Product: USB Receiver
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.1: Manufacturer: Logitech
May 17 05:46:02 pop-os kernel: logitech-djreceiver 0003:046D:C539.0022: hidraw4: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:05:00.4-1.3.4.4.1/input0
May 17 05:46:02 pop-os kernel: logitech-djreceiver 0003:046D:C539.0023: hiddev0,hidraw5: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:05:00.4-1.3.4.4.1/input1
May 17 05:46:02 pop-os kernel: logitech-djreceiver 0003:046D:C539.0024: hiddev1,hidraw6: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:05:00.4-1.3.4.4.1/input2
May 17 05:46:02 pop-os kernel: logitech-djreceiver 0003:046D:C539.0024: device of type eQUAD Lightspeed 1 (0x0c) connected on slot 1
May 17 05:46:02 pop-os mtp-probe[16489]: checking bus 5, device 37: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.1"
May 17 05:46:02 pop-os mtp-probe[16489]: bus: 5, device: 37 was not an MTP device
May 17 05:46:02 pop-os kernel: input: Logitech G Pro  as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.1/5-1.3.4.4.1:1.2/0003:046D:C539.0024/0003:046D:4079.0025/input/input61
May 17 05:46:02 pop-os kernel: logitech-hidpp-device 0003:046D:4079.0025: input,hidraw7: USB HID v1.11 Keyboard [Logitech G Pro ] on usb-0000:05:00.4-1.3.4.4.1/input2:1
May 17 05:46:02 pop-os mtp-probe[16502]: checking bus 5, device 37: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.1"
May 17 05:46:02 pop-os mtp-probe[16502]: bus: 5, device: 37 was not an MTP device
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.2: new high-speed USB device number 38 using xhci_hcd
May 17 05:46:02 pop-os systemd-logind[957]: Watching system buttons on /dev/input/event14 (Logitech G Pro )
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.2: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.63
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.2: Product: USB2.1 Hub
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.2: Manufacturer: GenesysLogic
May 17 05:46:02 pop-os kernel: hub 5-1.3.4.4.2:1.0: USB hub found
May 17 05:46:02 pop-os kernel: hub 5-1.3.4.4.2:1.0: 4 ports detected
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.4: new full-speed USB device number 39 using xhci_hcd
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.4: New USB device found, idVendor=3297, idProduct=1977, bcdDevice= 0.01
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.4: Product: Voyager
May 17 05:46:02 pop-os kernel: usb 5-1.3.4.4.4: Manufacturer: ZSA Technology Labs
May 17 05:46:03 pop-os kernel: input: ZSA Technology Labs Voyager as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4/5-1.3.4.4.4:1.0/0003:3297:1977.0026/input/input62
May 17 05:46:03 pop-os kernel: hid-generic 0003:3297:1977.0026: input,hidraw8: USB HID v1.11 Keyboard [ZSA Technology Labs Voyager] on usb-0000:05:00.4-1.3.4.4.4/input0
May 17 05:46:03 pop-os kernel: hid-generic 0003:3297:1977.0027: hiddev2,hidraw9: USB HID v1.11 Device [ZSA Technology Labs Voyager] on usb-0000:05:00.4-1.3.4.4.4/input1
May 17 05:46:03 pop-os kernel: input: ZSA Technology Labs Voyager System Control as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4/5-1.3.4.4.4:1.2/0003:3297:1977.0028/input/input63
May 17 05:46:03 pop-os kernel: input: ZSA Technology Labs Voyager Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4/5-1.3.4.4.4:1.2/0003:3297:1977.0028/input/input64
May 17 05:46:03 pop-os kernel: input: ZSA Technology Labs Voyager Keyboard as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4/5-1.3.4.4.4:1.2/0003:3297:1977.0028/input/input65
May 17 05:46:03 pop-os kernel: hid-generic 0003:3297:1977.0028: input,hidraw10: USB HID v1.11 Keyboard [ZSA Technology Labs Voyager] on usb-0000:05:00.4-1.3.4.4.4/input2
May 17 05:46:03 pop-os mtp-probe[16510]: checking bus 5, device 39: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4"
May 17 05:46:03 pop-os mtp-probe[16510]: bus: 5, device: 39 was not an MTP device
May 17 05:46:03 pop-os systemd-logind[957]: Watching system buttons on /dev/input/event16 (ZSA Technology Labs Voyager System Control)
May 17 05:46:03 pop-os systemd-logind[957]: Watching system buttons on /dev/input/event17 (ZSA Technology Labs Voyager Consumer Control)
May 17 05:46:03 pop-os systemd-logind[957]: Watching system buttons on /dev/input/event18 (ZSA Technology Labs Voyager Keyboard)
May 17 05:46:03 pop-os systemd-logind[957]: Watching system buttons on /dev/input/event15 (ZSA Technology Labs Voyager)
May 17 05:46:03 pop-os mtp-probe[16532]: checking bus 5, device 39: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4.4/5-1.3.4.4.4"
May 17 05:46:03 pop-os mtp-probe[16532]: bus: 5, device: 39 was not an MTP device
May 17 05:46:09 pop-os com.brave.Browser.desktop[4117]: [0517/054609.659394:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
May 17 05:46:10 pop-os xdg-desktop-por[3330]: Failed to get current display state: Timeout was reached
May 17 05:46:10 pop-os gsd-xsettings[1941]: Failed to get current display configuration state: Timeout was reached

the system completely freezes after that.

Other Notes:

Edit: It might be worth noting that this does not happen 100% of the time, but rather randomly every couple of times i switch away from the laptop. However i can reliably trigger it if i just switch back and forth a couple times.

Any suggestions on how to solve this would be much appreciated! Thank you

2

Does this error occur as well if you disconnect and reconnect the displayport cable(s) going from the thunderbolt dock to the KVM?

This looks like it might be an error with AMDGPU.

I’m seeing gnome-shell errors trying to enumerate the displays, as well as warning logs from AMDGPU. The warnings may be okay actually, but the gnome-shell errors appear to be more likely to be a cause for concern.

3

unplugging directly from the dock doesn’t seem to be causing any issues, this is what i get when unplugging/plugging the HDMI cable from the dock 5 times:

[ 3105.162381] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3105.991021] [drm] Send DSC disable to synaptics
[ 3107.026850] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3107.040605] [drm] DM_MST: DP14, 2-lane link detected
[ 3107.341822] [drm] Downstream port present 1, type 2
[ 3114.470951] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3116.347312] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3116.361139] [drm] DM_MST: DP14, 2-lane link detected
[ 3116.846931] [drm] Downstream port present 1, type 2
[ 3117.072034] [drm] Downstream port present 1, type 2
[ 3118.313306] [drm] Send DSC enable to synaptics
[ 3118.569238] [drm] Send DSC enable to synaptics
[ 3134.976463] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3135.799088] [drm] Send DSC disable to synaptics
[ 3136.839389] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3136.853251] [drm] DM_MST: DP14, 2-lane link detected
[ 3137.154953] [drm] Downstream port present 1, type 2
[ 3153.341145] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3155.163937] workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10666us 4 times, consider switching to WQ_UNBOUND
[ 3155.219789] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3155.233656] [drm] DM_MST: DP14, 2-lane link detected
[ 3155.828768] [drm] Downstream port present 1, type 2
[ 3155.964929] [drm] Downstream port present 1, type 2
[ 3157.389305] [drm] Send DSC enable to synaptics
[ 3157.645282] [drm] Send DSC enable to synaptics
[ 3170.275890] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3171.087801] [drm] Send DSC disable to synaptics
[ 3172.131058] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3172.144743] [drm] DM_MST: DP14, 2-lane link detected
[ 3172.446449] [drm] Downstream port present 1, type 2
[ 3184.621860] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3186.499606] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3186.513432] [drm] DM_MST: DP14, 2-lane link detected
[ 3186.999171] [drm] Downstream port present 1, type 2
[ 3187.224721] [drm] Downstream port present 1, type 2
[ 3188.449324] [drm] Send DSC enable to synaptics
[ 3188.701322] [drm] Send DSC enable to synaptics
[ 3197.506902] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3198.327017] [drm] Send DSC disable to synaptics
[ 3199.371194] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3199.384991] [drm] DM_MST: DP14, 2-lane link detected
[ 3199.686718] [drm] Downstream port present 1, type 2
[ 3209.175113] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3211.012060] workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10666us 8 times, consider switching to WQ_UNBOUND
[ 3211.068013] [drm] DM_MST: starting TM on aconnector: 0000000046dc1633 [id: 107]
[ 3211.081801] [drm] DM_MST: DP14, 2-lane link detected
[ 3211.676237] [drm] Downstream port present 1, type 2
[ 3211.812407] [drm] Downstream port present 1, type 2
[ 3213.253498] [drm] Send DSC enable to synaptics
[ 3213.509389] [drm] Send DSC enable to synaptics
4

So that’s good, it means your software stack seems to be handling hotplugs properly. I wonder if something’s going on with the EDID feeder.

@Level1_Amber probably has more insight into this KVM than I do, as I’ve never touched this model. Let’s see if she has any information that can help.

5

i also just had it happen on a fresh boot with the KVM already active on the Thinkpad. Immediately after logging in everything froze up and i had to hard-reset again.

6

just updating to document what i have tried already.

  • ensure everything is running the very latest software/firmware including my monitor
  • power off, move hdcp switch to a different setting, learn edid by pressing button for 3 seconds, wait until light is blue, power on
  • repeated above with every possible setting on the hdcp switch

i also happen to have a thinkpad x1 with intel igpu for testing:
i installed popos on it and connected it to the same lenovo dock. While the system does not crash, it loses the monitor after switching and i have to reboot the OS in order for the display to be available again. Even disconnecting and reconnecting the thinkpad from the dock doesn’t change anything.

7

I would have to ask @wendell about all of this, not sure when it comes to Linux.

8

would appreciate it very much if he could take a look at this!

9

does the thinkpad have a bios update? The MST info in logs is curious. Sometimes I see that whenever MST isnt in play but if MST is enabled on your monitor (i.e. it is daisy-chainable, maybe try disabling that?) strictly speaking mst works fine with the kvms but dell’s version of MST on some of their monitors is sketch.

Could be borderline cables too, causing excessive DP handshakes, leading to undefined behavior.

1 Like
10

i just updated to the latest bios and got excited for a moment, but then it crashed again :slightly_frowning_face:

My Dell side-monitor does have MST and it was already disabled, also that monitor is not connected to the KVM.

just to clarify how my setup is connected right now:

  • peripherals are connected to the KVM and switched between all 3 devices
  • main monitor DP is connected directly to GamingPC and HDMI to the KVM, but only for Thinkpad and WorkPC
  • side-monitor is connected directly to GamingPC (DP) and directly to the Thinkpad (HDMI), not on KVM

here is a ugly drawing of it:

image
image2483Ă—1361 274 KB

I decided to keep the GamingPC directly connected with DP because i want to be able to use the full bandwidth for 240hz@4k and to my knowledge a KVM that supports that, does not yet exist.

another thing i noticed is that i can not get more than 60Hz @ 3840 x 2160 when the monitor is connected through the KVM, on both Windows and Linux.

For cables i am using identical “Cable Matters 48Gbps 8K HDMI Cable 6.6 ft / 2m with 8K@120Hz, 4K@240Hz” for all connections. I was hoping these are decent quality.

11

i can not get more than 60Hz @ 3840 x 2160 when the monitor is connected through the KVM, on both Windows and Linux.
HDMI on linux is, in general, gimped. Nothing to do with the kvm. Our DP kvms can do 4k/240 no problem. HDMI can at least do 144, maybe more with dsc.
Your work PC igpu is likely not capable of more than 4k/60 via hdmi; Does the thinkpad have an igpu or dgpu? does it have two native hdmi or is one of then via some sort of adapter?

For troubleshooting you may have to unplug the “direct” connections as the errors from that may disappear, which mean those errors don’t have anything to do with the kvm.

So all of this

[ 3157.645282] [drm] Send DSC enable to synaptics
[ 3170.275890] [drm] DM_MST: stopping TM on aconnector: 0000000046dc1633 [id: 107]
[ 3171.087801] [drm] Send DSC disable to synaptics

kind of stuff might be a red herring.

stuff like:

May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0): Allocate new frame buffer 5120x1600
May 17 05:45:46 pop-os /usr/libexec/gdm-x-session[1609]: (II) AMDGPU(0):  => pitch 20480 bytes

May 17 05:45:46 pop-os kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008

the kvm doesnt really have any control over… thats a kernel bug… but could be maybe caused by some weird edge case thing like… the monitor with two inputs, the input not via the kvm is “inactive” and the linux display driver has never seen that before because the kvm is trying to keep that input “hot” when it will never be hot as long as its inactive, triggers this bug.

I would power cycle the kvm for sure by just unplugging it from power and usb for a minute just to clear out any of this undefined behavior after it happens.

“native” HDMI on linux is just not a good experience because of the HDMI consortiium for beyond 4k/60 imho.

12

HDMI on linux is, in general, gimped. Nothing to do with the kvm. Our DP kvms can do 4k/240 no problem. HDMI can at least do 144, maybe more with dsc.
Your work PC igpu is likely not capable of more than 4k/60 via hdmi; Does the thinkpad have an igpu or dgpu? does it have two native hdmi or is one of then via some sort of adapter?

My work PC has a 1080Ti in it, so that should not be an issue. The Thinkpad has a igpu, the HDMI ports are on the “Lenovo Thunderbolt 3 Dock”, which i now realize, should have mentioned in the last post :facepalm:

I looked at the DP variants before i ordered the HDMI one, and all of the 4 PC DP1.4 KVMs on the store have the same “up to 4k/120” noted under “Features”.

  • Two DP 1.4 connection from each computer (up to 4k/120hz or 8k/30hz).
  • Lower resolutions + Higher framerates possible e.g. 144hz @ 1440p work just fine because of full DP 1.4 compatibility. (Overclocking not supported)

Am i misinterpreting this info from the product pages somehow?

For troubleshooting you may have to unplug the “direct” connections as the errors from that may disappear, which mean those errors don’t have anything to do with the kvm.

the kvm doesnt really have any control over… thats a kernel bug… but could be maybe caused by some weird edge case thing like… the monitor with two inputs, the input not via the kvm is “inactive” and the linux display driver has never seen that before because the kvm is trying to keep that input “hot” when it will never be hot as long as its inactive, triggers this bug.

Appreciate your input Wendell! I will do some “clean tests” tonight

13

Yeah, so DP 1.4 has an absolute maximum bandwidth of 32.7 gigabit. This is the raw data rate. The Math says that you can only get 4k/120. But display stream compression is a thing, so with compression you can go beyond 4k/120. You can’t fixate on res and refresh. KVM doesn’t care. It’s about protocol spec – DP 1.4

when you go beyond 4k/120 compression has to be used so the 4k/144 or 4k/240 signal fits below the 32.7 gigabit threshold. Turns out raw video bitmap is highly compressible.

Are there DP 2.0 and 2.1 monitors out there that are beyond DP1.4? Yes and also no… many of the “DP 2.0” monitors out there are mostly DP 1.4 with required display stream compression features. There are also levels of DSC, some lossier than others, but the kvm doesn’t care about any of this. Samsung is DSC DP1.4, so 32.7 gigabit datarate even when beyond 4k/120.

Also macs don’t do displaystream compression, mostly, except on specially-apple-blessed displays.

So 4k/240hz samsung monitors work fine via the DP1.4 kvm because its “full fat” DP1.4. But the most you will get uncompressed on DP1.4 is 4k/120. 4k/144 even 4k/240 can work with compression because with compression it fits under the 32.7 gigabit absolute max data rate…

the 1080ti also has a nasty bug in it, make sure you’ve got the optional DP1.4 firmware. just google 1080ti nvidia DP firmware update and make sure its installed.

1 Like
14

Thanks for the clarification Wendell! I never really thought about the actual bandwidth needed to push 4k@240 and also never wanted to read up on DP. I just treated it like the good old VGA/DVI stuff, just plug it in :smiley:

some weird edge case thing like… the monitor with two inputs, the input not via the kvm is “inactive” and the linux display driver has never seen that before because the kvm is trying to keep that input “hot” when it will never be hot as long as its inactive, triggers this bug.

i believe this is kind off what is happening here… the Samsung monitor has this thing where it will turn off, if the currently selected input goes inactive.

So with my weird setup where i use DP and HDMI for the same monitor there will be a 3 second countdown displayed through the monitors ui, warning that it will turn off because the input is inactive. When i switch from the laptop (HDMI) to my gaming pc (DP) and don’t switch the monitors input within the 3 second window, the monitor turns off, which reliably crashes the system.

This “pressing the monitor button” to switch inputs between HDMI and DP has become “muscle memory” for me because I’ve been using a usb switch for laptop and gaming pc for several years now and always switched the monitor myself. So sometimes i would switch it within the 3 second window and other times the monitor would already be off when i switch it. And this never mattered because both inputs will remain active with just the usb switch. I think this is the reason why i didn’t recognize it at first and was convinced that it just happens randomly when i switch away from the laptop:

Edit: It might be worth noting that this does not happen 100% of the time, but rather randomly every couple of times i switch away from the laptop. However i can reliably trigger it if i just switch back and forth a couple times.

So in conclusion, there is nothing wrong with the KVM and it is most likely a bug in the kernel.

Thank you all!