[wayland] Xorg进程CPU占用率超高,达100%
Tofloor
poster avatar
lovelock2017
deepin
2024-10-18 09:01
Author

为啥使用一段时间后,XOrg进程CPU占用率接近100%,界面也就开始卡顿,不流畅.

PS:请问如何排查这个问题?

image.png

Reply Favorite View the author
All Replies
neko
deepin
Ecological co-builder
2024-10-18 09:03
#1

啥显卡,显存多大。可能显存不够了。

感觉是AMD核显,可以到BIOS把显存调大。

Reply View the author
lovelock2017
deepin
2024-10-18 09:27
#2

那应该是内核针对这款CPU的支持还有些问题,未正常分配显存。下面这个是设备的配置。无独显。

image.png

Reply View the author
owen_337
deepin testing team
2024-10-18 09:28
#3

楼主你好,出现此情况时,可以查看下cat Xorg.0.log |grep -i EE 是否存在报错信息

Reply View the author
qmicrosoftcom
deepin
2024-10-18 11:16
#4
neko

啥显卡,显存多大。可能显存不够了。

感觉是AMD核显,可以到BIOS把显存调大。

非也,我也是这个问题,调大显存没用,占用率连一半都没有的情况下电脑就开始卡了。

Reply View the author
qmicrosoftcom
deepin
2024-10-18 11:18
#5
owen_337

楼主你好,出现此情况时,可以查看下cat Xorg.0.log |grep -i EE 是否存在报错信息

具体路径是啥,我也是这个问题,并且此刻仍然复现。

@Qiang-PC:/media/Qiang/08F666E5F666D28C/Logs/1017# cat Xorg.0.log |grep -i EE
cat: Xorg.0.log: 没有那个文件或目录

Reply View the author
qmicrosoftcom
deepin
2024-10-18 11:20
#6

跟你完全相同的问题,到现在也没解决,此刻哪怕就这点VRAM占用率,电脑照样慢动作。

image.png

见https://bbs.deepin.org/zh/post/278647

Reply View the author
lovelock2017
deepin
2024-10-18 15:06
#7
owen_337

楼主你好,出现此情况时,可以查看下cat Xorg.0.log |grep -i EE 是否存在报错信息

日志见下:

image.png

Reply View the author
hinata
deepin
2024-10-19 01:39
#8

confused

Reply View the author
Oli
deepin
2024-10-19 02:17
#9

不懂

Reply View the author
owen_337
deepin testing team
2024-10-21 11:27
#10
lovelock2017

日志见下:

image.png

请问触摸板能正常使用吗?

Reply View the author
owen_337
deepin testing team
2024-10-21 11:29
#11
qmicrosoftcom

具体路径是啥,我也是这个问题,并且此刻仍然复现。

@Qiang-PC:/media/Qiang/08F666E5F666D28C/Logs/1017# cat Xorg.0.log |grep -i EE
cat: Xorg.0.log: 没有那个文件或目录

路径是/var/log/Xorg.0.log

Reply View the author
qmicrosoftcom
deepin
2024-10-21 14:00
#12

Qiang@Qiang-PC:/media/Qiang/08F666E5F666D28C/Logs/1018$ cat /var/log/Xorg.0.log | grep -i EE
[ 8.997] Current Operating System: Linux Qiang-PC 6.6.47-amd64-desktop-hwe #23.01.00.37 SMP PREEMPT_DYNAMIC Tue Aug 20 17:33:52 CST 2024 x86_64
[ 8.997] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6.47-amd64-desktop-hwe root=UUID=1e7ad7cc-0f01-4a22-825e-4b2317613745 ro splash quiet DEEPIN_GFXMODE=
[ 8.997] xorg-server 2:21.1.10-1deepin1 (https://www.debian.org/support)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8.999] (==) No Layout section. Using the first Screen section.
[ 8.999] (==) No screen section available. Using defaults.
[ 8.999] (**) |-->Screen "Default Screen Section" (0)
[ 8.999] (==) No monitor specified for screen "Default Screen Section".
[ 9.003] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 9.004] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 9.021] (II) AMDGPU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 9.201] (==) AMDGPU(0): TearFree property default: auto
[ 9.237] (II) AMDGPU(0): Year: 2018 Week: 17
[ 9.237] (II) AMDGPU(0): redX: 0.632 redY: 0.340 greenX: 0.333 greenY: 0.626
[ 9.239] (II) AMDGPU(0): Year: 2018 Week: 32
[ 9.239] (II) AMDGPU(0): redX: 0.632 redY: 0.340 greenX: 0.333 greenY: 0.626
[ 9.320] (II) Initializing extension MIT-SCREEN-SAVER
[ 9.324] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 9.324] (II) Initializing extension XFree86-VidModeExtension
[ 9.324] (II) Initializing extension XFree86-DGA
[ 9.324] (II) Initializing extension XFree86-DRI
[ 9.325] (II) AMDGPU(0): Setting screen physical size to 1016 x 285
[ 9.571] (II) This device may have been added with another device file.
[ 9.727] (II) This device may have been added with another device file.
[ 9.728] (II) This device may have been added with another device file.
[ 9.728] (II) This device may have been added with another device file.
[ 9.729] (II) This device may have been added with another device file.
[ 9.730] (II) This device may have been added with another device file.
[ 15096.299] (II) This device may have been added with another device file.
[107796.709] (EE) event3 - USB OPTICAL MOUSE: client bug: event processing lagging behind by 22ms, your system is too slow
[362781.223] (II) This device may have been added with another device file.

Reply View the author
lovelock2017
deepin
21 hours ago
#13
owen_337

请问触摸板能正常使用吗?

触摸板 正常

Reply View the author
lovelock2017
deepin
21 hours ago
#14
lovelock2017

触摸板 正常

现在只有 MIC 不正常。

以前是 输出设备(喇叭)和MIC 都不正常,按贴子上面的方法处理后,可以识别 输出设备,但MIC 还是无法识别

Reply View the author
owen_337
deepin testing team
20 hours ago
#15
lovelock2017

触摸板 正常

请提供下xorg的版本哈

apt policy xserver-xorg-core

Reply View the author