https://bugzilla.suse.com/show_bug.cgi?id=1197556
Bug ID: 1197556 Summary: gnome42 completely unusable on Lenovo P15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: donald.vosburg@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
Logging into GNOME on Lenovo P15 with DockStation results in hung system unable to launch applications.
Keyboard and mouse become unresponsive, networking on dock gets disabled, and the only alternative is hard power-off.
Using plasma on the same OS on the same hardware works perfectly.
https://bugzilla.suse.com/show_bug.cgi?id=1197556
Don Vosburg donald.vosburg@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|gnome42 completely unusable |gnome42 completely unusable |on Lenovo P15 |on Lenovo P15 dockstation
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c1
--- Comment #1 from Don Vosburg donald.vosburg@suse.com --- Using the laptop without the dockstation works well, with multiple monitors and peripherals.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c2
--- Comment #2 from Don Vosburg donald.vosburg@suse.com --- Created attachment 857398 --> https://bugzilla.suse.com/attachment.cgi?id=857398&action=edit supportconfig
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c3
Yifan Jiang yfjiang@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gnome-bugs@suse.de, | |yfjiang@suse.com Assignee|gnome-bugs@suse.de |qkzhu@suse.com
--- Comment #3 from Yifan Jiang yfjiang@suse.com --- This looks in need of further review. Qingkai, could you please take a look please?
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c4
--- Comment #4 from QK ZHU qkzhu@suse.com --- (In reply to Yifan Jiang from comment #3)
This looks in need of further review. Qingkai, could you please take a look please?
I will look into it
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c5
--- Comment #5 from Don Vosburg donald.vosburg@suse.com --- If I remove the DockStation, the system behaves normally.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c6
Frederic Crozat fcrozat@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com
--- Comment #6 from Frederic Crozat fcrozat@suse.com --- Whick docking station is used ?
(For the record, I have a P15Gen2 + TB4 Workstation docking station)
I would suggest to open a bug for each different issue, since they touched various parts of the OS (or systems).
Networking not working might be a bug in Lenovo firmware, see https://github.com/fwupd/firmware-lenovo/issues/191#issuecomment-1094253562
For GNOME, it is used under Wayland or Xorg ?
There is still issue when using Wayland and nvidia driver, in hybrid display mode: https://gitlab.gnome.org/GNOME/mutter/-/issues/2166
Try to turn off hybrid display in Firmware setting. For me, it fixes most of the issues (still some issues with suspend.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c7
--- Comment #7 from Don Vosburg donald.vosburg@suse.com --- Created attachment 858144 --> https://bugzilla.suse.com/attachment.cgi?id=858144&action=edit Lenovo System update screenshot
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c8
--- Comment #8 from Don Vosburg donald.vosburg@suse.com --- Created attachment 858145 --> https://bugzilla.suse.com/attachment.cgi?id=858145&action=edit Firmware updating screenshot
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c9
--- Comment #9 from Don Vosburg donald.vosburg@suse.com --- (In reply to Frederic Crozat from comment #6)
Whick docking station is used ?
(For the record, I have a P15Gen2 + TB4 Workstation docking station)
This is exactly my setup
I would suggest to open a bug for each different issue, since they touched various parts of the OS (or systems).
Networking not working might be a bug in Lenovo firmware, see https://github.com/fwupd/firmware-lenovo/issues/191#issuecomment-1094253562
Firmware updated tonight using Windows - screenshots attached.
For GNOME, it is used under Wayland or Xorg ?
Xorg - Wayland is a failed experiment for me with more drawbacks than value.
There is still issue when using Wayland and nvidia driver, in hybrid display mode: https://gitlab.gnome.org/GNOME/mutter/-/issues/2166
Try to turn off hybrid display in Firmware setting. For me, it fixes most of the issues (still some issues with suspend.
System Settings have been only discrete graphics from day one.
It looks like it is recognized by the OS:
dpv-p15-tumble:~ # boltctl list ��� Lenovo ThinkPad Thunderbolt 4 Dock ������ type: peripheral ������ name: ThinkPad Thunderbolt 4 Dock ������ vendor: Lenovo ������ uuid: 0054e144-89a6-8780-ffff-ffffffffffff ������ generation: USB4 ������ status: authorized ��� ������ domain: 609f57dd-817b-8780-ffff-ffffffffffff ��� ������ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s ��� ������ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s ��� ������ authflags: none ������ authorized: Thu Apr 14 04:09:43 2022 ������ connected: Thu Apr 14 04:09:43 2022 ������ stored: Sat Mar 26 21:07:51 2022 ������ policy: iommu ������ key: no
As soon as I plug in the network cable, it kernel panics.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c10
--- Comment #10 from Don Vosburg donald.vosburg@suse.com --- Removing the dock completely brings rock-solid stability to this system - regardless of UI.
Plug the dock in and applications fail to load (firefox, gnome terminal), leading to eventual complete lockup.
This tool goes back on the shelf until it becomes supportable.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c11
--- Comment #11 from QK ZHU qkzhu@suse.com --- The supportconfig contains logs from Mar 3 to Mar 6, could you try to: - reboot your system - reproduce the issue - provide `sudo journalctl -b > journal.txt`
It seems the UI unresponsive
Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: Assuming 131072kB available aperture size. Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: May lead to reduced performance or incorrect rendering. Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: get chip id failed: -1 [22] Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: param: 4, val: 0 Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: libva error: /usr/lib64/dri/iHD_drv_video.so init failed
was caused by those nvidia_drm error:
13835:Mar 04 01:21:49 dpv-p15-tumble.site.com kernel: [drm:nv_drm_gem_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fence attach: 0x0000000a
And the network issue was cause by:
25705:Mar 04 12:49:45 dpv-p15-tumble kernel: iwlwifi 0000:09:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1 25711:Mar 04 12:49:45 dpv-p15-tumble kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: init of i915 and HDMI codec failed
Furthermore, the supportconfig indicates Don has bumblebee installed on the system, this might be something different with Frederic's configuration.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c12
--- Comment #12 from QK ZHU qkzhu@suse.com --- (In reply to QK ZHU from comment #11)
The supportconfig contains logs from Mar 3 to Mar 6, could you try to:
typo fix: ...from Mar 3 to Mar 26...
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c13
--- Comment #13 from Don Vosburg donald.vosburg@suse.com --- Created attachment 858172 --> https://bugzilla.suse.com/attachment.cgi?id=858172&action=edit journalctl -b log file after error appears
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c14
--- Comment #14 from Don Vosburg donald.vosburg@suse.com --- (In reply to QK ZHU from comment #11)
The supportconfig contains logs from Mar 3 to Mar 6, could you try to:
- reboot your system
- reproduce the issue
- provide `sudo journalctl -b > journal.txt`
It seems the UI unresponsive
Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: Assuming 131072kB available aperture size. Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: May lead to reduced performance or incorrect rendering. Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: get chip id failed: -1 [22] Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: param: 4, val: 0 Mar 04 01:21:49 dpv-p15-tumble.site.com gnome-shell[30106]: libva error: /usr/lib64/dri/iHD_drv_video.so init failed
was caused by those nvidia_drm error:
13835:Mar 04 01:21:49 dpv-p15-tumble.site.com kernel: [drm:nv_drm_gem_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fence attach: 0x0000000a
Video continues to be displayed through the dock, even when system is unresponsive
And the network issue was cause by:
25705:Mar 04 12:49:45 dpv-p15-tumble kernel: iwlwifi 0000:09:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
Not currently using wifi
25711:Mar 04 12:49:45 dpv-p15-tumble kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: init of i915 and HDMI codec failed
Furthermore, the supportconfig indicates Don has bumblebee installed on the system, this might be something different with Frederic's configuration.
bumblebee removed, yet the issue persists
New journal.txt attached after error, then a reboot without doc so I could have a system that allowed me to create it.
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c15
--- Comment #15 from Don Vosburg donald.vosburg@suse.com --- Created attachment 858174 --> https://bugzilla.suse.com/attachment.cgi?id=858174&action=edit New supportconfig 20220414
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c16
--- Comment #16 from Don Vosburg donald.vosburg@suse.com --- (In reply to Don Vosburg from comment #15)
Created attachment 858174 [details] New supportconfig 20220414
Looks like errors start to appear at 14:43:11
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c17
--- Comment #17 from QK ZHU qkzhu@suse.com --- Hi Don,
Just noticed that (In reply to Don Vosburg from comment #16)
(In reply to Don Vosburg from comment #15)
Created attachment 858174 [details] New supportconfig 20220414
Looks like errors start to appear at 14:43:11
Some kernel error and Nvidia warning/error occurred before this, and I just noticed that you are using GNOME+sddm. I am afraid GNOME with sddm is not a supported combination (you will lose the screensaver functionality at least). Could you switch to gdm and have another try?
Meanwhile, I think you can post this issue to the forums of Nvidia.
https://bugzilla.suse.com/show_bug.cgi?id=1197556
QK ZHU qkzhu@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|qkzhu@suse.com |yfjiang@suse.com
https://bugzilla.suse.com/show_bug.cgi?id=1197556 https://bugzilla.suse.com/show_bug.cgi?id=1197556#c18
Don Vosburg donald.vosburg@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME
--- Comment #18 from Don Vosburg donald.vosburg@suse.com --- Fixed now with updates to Tumbleweed, and avoiding the wired network adapter on the dock.
-
bugzilla_noreply＠suse.com