*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
This may be unrelated -- but I am also seeing "x86/split lock detection"
errors. Is this just a red herring ? Only seeing these when using the
VirtualBox to drive the GPU.
[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM TTY layer initialized
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM socket layer initialized
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM ver 1.11
[Tue Jul 11 14:50:47 2023] thunderbolt 1-1: new device found, vendor=0x127
device=0x2
[Tue Jul 11 14:50:47 2023] thunderbolt 1-1: Razer Core X Chroma
[Tue Jul 11 14:50:48 2023] rfkill: input handler disabled
[Tue Jul 11 14:50:53 2023] thunderbolt 1-101: new device found, vendor=0x127
device=0x3
[Tue Jul 11 14:50:53 2023] thunderbolt 1-101: Razer Core X Chroma
[Tue Jul 11 14:50:54 2023] rfkill: input handler enabled
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the
runtime rate 48000
[Tue Jul 11 14:50:59 2023] rfkill: input handler disabled
[Tue Jul 11 14:56:33 2023] SUPR0GipMap: fGetGipCpu=0x1b
[Tue Jul 11 14:56:33 2023] vboxdrv: 0000000000000000 VMMR0.r0
[Tue Jul 11 14:56:33 2023] vboxdrv: 0000000000000000 VBoxDDR0.r0
[Tue Jul 11 14:56:41 2023] x86/split lock detection: #AC: EMT-1/4206 took a
split_lock trap at address: 0x7f698f296453
[Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-2/4207 took a
split_lock trap at address: 0x7f698f296453
[Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-0/4205 took a
split_lock trap at address: 0x7f698f296453
Unsure why there is a magic address space number there: 0x7f698f296453
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2026790
Title:
Slow refresh rate (5-6hz) on Display managed by gnome-shell
Status in gnome-shell package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Bug description:
NVIDIA GPU sending out frames to an LG Electronics 27" display.
At the moment, just a single display.
The NVIDIA GPU is available across a Thunderbolt 3 link.
Here is what the Nvidia Drivers are reporting:
beadon@semiauto:~$ nvidia-smi
Mon Jul 10 20:35:25 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.54.03 Driver Version: 535.54.03 CUDA
Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile
Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util
Compute M. |
| | |
MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce GTX 1650 Off | 00000000:52:00.0 On |
N/A |
| 0% 33C P8 N/A / 85W | 99MiB / 4096MiB | 0%
Default |
| | |
N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes:
|
| GPU GI CI PID Type Process name
GPU Memory |
| ID ID
Usage |
|=======================================================================================|
| 0 N/A N/A 2341 G /usr/bin/gnome-shell
1MiB |
+---------------------------------------------------------------------------------------+
Performing an strace I am seeing that the gnome-shell is **very** frequently
hitting :
EAGAIN (Resource temporarily unavailable)
It's not clear to me what is causing this. strace on the 33 threads
included for reference. To show different behaviors, clicks, movement
of windows, typing in a terminal, as running glxgears to show(get) the
refresh rate of 5 frames per second.
Is there some kind of heavy CPU-based communication happening for
gnome-shell ? I am seeing the CPU usage spike to 90+% when simple
movements are done on screen. However, the nvidia-smi tools reports
that it truly is attached to the right GPU, the PID is correct.
Please see the strace for further information.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 10 20:40:20 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-09 (182 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 44.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
