*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
I was unable to select the "Ubuntu on Xorg" as a configuration option,
so I did it manually.
I modified /etc/gdm3/custom.conf
current configuration:
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
# Enabling timed login
# TimedLoginEnable = true
# TimedLogin = user1
# TimedLoginDelay = 10
[security]
DisallowTCP=false
[xdmcp]
ServerArguments=-listen tcp
[chooser]
[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
Enable=true
This does not appear to work-around the problem. I am getting drm errors :
[Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma Keyboard as
/devices/pci0000:00/0000:00:07.2/0000:50:00.0/0000:51:04.0/0000:53:00.0/0000:54:02.0/0000:57:00.0/usb9/9-2/9-2:1.1/0003:1532:0F1A.000C/input/input39
[Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000006
[Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
[Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000007
[Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
[Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000008
[Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
[Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000009
[Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
[Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma as
/devices/pci0000:00/0000:00:07.2/0000:50:00.0/0000:51:04.0/0000:53:00.0/0000:54:02.0/0000:57:00.0/usb9/9-2/9-2:1.1/0003:1532:0F1A.000C/input/input40
[Tue Jul 11 13:24:20 2023] hid-generic 0003:1532:0F1A.000C: input,hidraw8: USB
HID v1.11 Keyboard [Razer Razer Core X Chroma] on usb-0000:57:00.0-2/input1
[Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma as
/devices/pci0000:00/0000:00:07.2/0000:50:00.0/0000:51:04.0/0000:53:00.0/0000:54:02.0/0000:57:00.0/usb9/9-2/9-2:1.2/0003:1532:0F1A.000D/input/input41
[Tue Jul 11 13:24:20 2023] hid-generic 0003:1532:0F1A.000D: input,hidraw9: USB
HID v1.11 Mouse [Razer Razer Core X Chroma] on usb-0000:57:00.0-2/input2
[Tue Jul 11 13:24:21 2023] ax88179_178a 10-1:1.0 eth0: register 'ax88179_178a'
at usb-0000:57:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 98:bb:1e:1e:f9:7c
[Tue Jul 11 13:24:21 2023] usbcore: registered new interface driver ax88179_178a
[Tue Jul 11 13:24:21 2023] ax88179_178a 10-1:1.0 enx98bb1e1ef97c: renamed from
eth0
[Tue Jul 11 13:24:24 2023] ax88179_178a 10-1:1.0 enx98bb1e1ef97c: ax88179 -
Link status is: 1
[Tue Jul 11 13:24:24 2023] IPv6: ADDRCONF(NETDEV_CHANGE): enx98bb1e1ef97c: link
becomes ready
[Tue Jul 11 13:24:26 2023] thunderbolt 1-1: new device found, vendor=0x127
device=0x2
[Tue Jul 11 13:24:26 2023] thunderbolt 1-1: Razer Core X Chroma
[Tue Jul 11 13:24:33 2023] thunderbolt 1-101: new device found, vendor=0x127
device=0x3
[Tue Jul 11 13:24:33 2023] thunderbolt 1-101: Razer Core X Chroma
[Tue Jul 11 13:24:53 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000006
[Tue Jul 11 13:24:53 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
[Tue Jul 11 13:24:53 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x00005200] Failed to lookup gem object for mapping:
0x00000007
[Tue Jul 11 13:24:53 2023] [drm] [nvidia-drm] [GPU ID 0x00005200] Framebuffer
memory not appropriate for scanout
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 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/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
