*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Appears to be a red herring, VirtualBox apparently experiences random
guest crashes when split lock detection is enabled on the Host OS. ( I
am able to verify this )
Reference:
"Random crashes with Windows 10 guest operating system with Intel Tiger Lake
chipset"
CPU is :
https://ark.intel.com/content/www/us/en/ark/products/208664/intel-core-i71185g7-processor-12m-cache-up-to-4-80-ghz-with-ipu.html
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
(yes, it's Tiger Lake).
The reference in the VirtualBox ticketing system seems to have been
deleted, it appears that VirtualBox is using split locking.
Reference to the much longer discussion of what this is and how it's impacting
systems is here :
https://lwn.net/Articles/911219/
seems there's a penalty applied when the code is doing split locking.
This is a tunable.
Deeper discussion of how Intel and the Linux kernel team were involved is here:
https://www.virtualbox.org/ticket/20180?cversion=0&cnum_hist=4
Here are the errors again for the split lock, note the gnome-shell errors just
before :
2023-07-11T16:01:26.427798-07:00 semiauto gnome-character[5478]: JS LOG:
Characters Application exiting
2023-07-11T16:01:29.507946-07:00 semiauto gnome-shell[2700]: Can't update stage
views actor <unnamed>[<MetaWindowActorX11>:0x55c018ffa2a0] is on because it
needs an allocation.
2023-07-11T16:01:29.508086-07:00 semiauto gnome-shell[2700]: Can't update stage
views actor <unnamed>[<MetaSurfaceActorX11>:0x55c01daf3ce0] is on because it
needs an allocation.
2023-07-11T16:01:29.601935-07:00 semiauto gnome-shell[2700]: Can't update stage
views actor <unnamed>[<MetaWindowActorX11>:0x55c01ab19670] is on because it
needs an allocation.
2023-07-11T16:01:29.602058-07:00 semiauto gnome-shell[2700]: Can't update stage
views actor <unnamed>[<MetaSurfaceActorX11>:0x55c018212df0] is on because it
needs an allocation.
2023-07-11T16:01:37.587046-07:00 semiauto kernel: [ 2385.543465] x86/split lock
detection: #AC: EMT-0/5871 took a split_lock trap at address: 0x7fd78aa96453
2023-07-11T16:01:38.079070-07:00 semiauto kernel: [ 2386.033592] x86/split lock
detection: #AC: EMT-1/5872 took a split_lock trap at address: 0x7fd78aa96453
2023-07-11T16:01:39.723080-07:00 semiauto kernel: [ 2387.676986] x86/split lock
detection: #AC: EMT-2/5873 took a split_lock trap at address: 0x7fd78aa96453
2023-07-11T16:01:45.484475-07:00 semiauto systemd[1]:
systemd-timedated.service: Deactivated successfully.
2023-07-11T16:02:22.331078-07:00 semiauto kernel: [ 2430.285901] pcieport
0000:00:07.2: pciehp: Slot(0-1): Link Down
2023-07-11T16:02:22.331102-07:00 semiauto kernel: [ 2430.285908] pcieport
0000:00:07.2: pciehp: Slot(0-1): Card not present
The split lock penalty triggered by VirtualBox seems to trip some kind of timer
which causes the link to the eGPU to be reset. Which then of course causes all
kinds of havoc on the system.
Further logs ;
2023-07-11T16:07:55.895042-07:00 semiauto kernel: [ 2763.846900] thunderbolt
0000:00:0d.2: failed to send driver ready to ICM
So -- long way around , there are a lot of things interacting in here.
I am unsure how to get a pure Xorg work-around in place to use the extra
GPU. I am also a little concerned that any application doing split
locking and having the kernel penalty imposed will cause this setup to
crash because of link detection.
Unsure where to go next, I suppose I'll try split lock disabling ..
** Bug watch added: Virtualbox Trac #20180
http://www.virtualbox.org/ticket/20180
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
