轻薄本KDE玩游戏死机

plasma70 · 2023-05-20 11:55:11

华为Matebook2020Ryzen(AMD R54500U，核显)
在玩Minecraft时能跑到200fps，但玩一会儿之后就会死机，画面不动，Ctrl+Alt+F4不会进入TTY,但有声音，屏幕时不时黑一下。
任何游戏都是一样的
电脑没有过热，CPU没有瓶颈，显卡没有瓶颈，内存没有瓶颈。
xf-video-*** 全部删除仍然没有解决
驱动是公版

如果各位有遇到类似问题，欢迎讨论

依云 · 2023-05-20 18:25:59

看看出问题时的系统日志。也可考虑开个 sshd 在出问题时手机连上去看看情况。

plasma70 · 2023-05-20 20:01:56

发现：OpenGL的问题，Vulkan似乎不受影响
日志没有任何反常

Retiould · 2024-02-01 01:47:12

plasma70 说：

华为Matebook2020Ryzen(AMD R54500U，核显)
在玩Minecraft时能跑到200fps，但玩一会儿之后就会死机，画面不动，Ctrl+Alt+F4不会进入TTY,但有声音，屏幕时不时黑一下。
任何游戏都是一样的
事实上，只有 CS2 可以正常工作，当我坐在平台上时 CS2 新闻，其他时候它会过热。
电脑没有过热，CPU没有瓶颈，显卡没有瓶颈，内存没有瓶颈。
xf-video-*** 全部删除仍然没有解决
驱动是公版
如果各位有遇到类似问题，欢迎讨论

看起来你的华为Matebook2020在玩Minecraft时表现出了一些奇怪的问题。尽管你的硬件配置足够强大，但仍然遇到了死机和画面黑屏的情况，这确实令人困扰。

首先，我建议检查系统和游戏的更新。确保你的操作系统和Minecraft游戏都是最新版本，以确保没有已知的兼容性问题。

其次，考虑清理和优化你的系统。有时候，系统中的垃圾文件或过多的后台进程可能会导致游戏运行不稳定。尝试清理临时文件并关闭不必要的后台进程，以释放系统资源。

另外，尝试降低游戏的图形设置。尽管你的硬件能够支持高帧率，但降低一些图形设置可能有助于减轻系统负担，从而提高稳定性。

最后，如果问题仍然存在，可能需要考虑联系华为客服或寻求专业的技术支持。他们可能能够提供更具体的解决方案，帮助你解决这个问题。

希望这些建议能够帮助你找到解决问题的方法。如果其他人有类似的经历或解决方案，欢迎分享讨论！

依云 · 2024-02-01 09:45:43

@Retiould 请不要贴 GPT 生成的回复。考虑到你的账号状况，再有下次，你将被视为无用的机器人账号而被封禁。

lspl5 · 2024-08-29 14:20:33

我今天也遇到了这个问题，是在使用vulkan模式下的cs2发生的，在死机前一般还会发生游戏内无声，游戏延迟突然升高的情况，同时无法切换tty
并且即便没有死机也经常出现cs2自行崩溃，之后steam也直接崩溃的情况，无法阻止
但没有在kde里直接弹出崩溃报告
---
当天的情况：
安装了steam
安装了vulakn的相关驱动
在steam里安装了CS2
曾使用过pacman -Syu来排除依赖问题（在游戏前）
---
之后找到了下面的指令查看了相关的日志

journalctl：

8月 29 08:57:00 lenovoxiaoxinair14 kernel: Linux version 6.10.6-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240805, GNU ld>
8月 29 08:57:00 lenovoxiaoxinair14 kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=73f865d3-7d28-403d-b065-0b82e72>
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-provided physical RAM map:
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000099fffff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000009a00000-0x0000000009dfffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000009e00000-0x0000000009efffff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f0efff] ACPI NVS
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000009f0f000-0x00000000b9968fff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000b9969000-0x00000000bab68fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000bab69000-0x00000000c8d7efff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000c8d7f000-0x00000000cbd7efff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000cbd7f000-0x00000000cdf7efff] ACPI NVS
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000cdf7f000-0x00000000cdffefff] ACPI data
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000cdfff000-0x00000000cdffffff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000ce000000-0x00000000cfffffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fde00000-0x00000000fdefffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe0fffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec01fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed81fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000020e2fffff] usable
8月 29 08:57:00 lenovoxiaoxinair14 kernel: BIOS-e820: [mem 0x000000020e300000-0x000000022fffffff] reserved
8月 29 08:57:00 lenovoxiaoxinair14 kernel: NX (Execute Disable) protection: active
8月 29 08:57:00 lenovoxiaoxinair14 kernel: APIC: Static calls initialized

dmesg：

[    6.473498] systemd[1]: Starting Load/Save OS Random Seed...
[    6.473513] systemd[1]: TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
[    6.484808] systemd[1]: Started Journal Service.
[    6.501337] systemd-journald[379]: Received client request to flush runtime journal.
[    6.656763] mousedev: PS/2 mouse device common for all mice
[    6.685523] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[    6.685531] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
[    6.690970] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[    6.693578] ccp 0000:04:00.2: enabling device (0000 -> 0002)
[    6.697022] ccp 0000:04:00.2: ccp: unable to access the device: you might be running a broken BIOS.
[    6.698981] ccp 0000:04:00.2: tee enabled
[    6.699051] ccp 0000:04:00.2: psp enabled
[    6.721163] Adding 4194300k swap on /dev/nvme0n1p2.  Priority:-2 extents:1 across:4194300k SS
[    6.735048] input: MSFT0002:00 04F3:317F Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0002:00/0018:04F3:317F.0003/input/input9
[    6.735186] input: MSFT0002:00 04F3:317F Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0002:00/0018:04F3:317F.0003/input/input11
[    6.735325] hid-generic 0018:04F3:317F.0003: input,hidraw2: I2C HID v1.00 Mouse [MSFT0002:00 04F3:317F] on i2c-MSFT0002:00
[    6.742695] input: PC Speaker as /devices/platform/pcspkr/input/input12
[    6.750464] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer
[    6.750467] RAPL PMU: hw unit of domain package 2^-16 Joules
[    6.769456] mc: Linux media interface: v0.10
[    6.770938] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.771137] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.771316] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    6.772920] cryptd: max_cpu_qlen set to 1000
[    6.777329] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    6.777335] cfg80211: failed to load regulatory.db
[    6.797666] Bluetooth: Core ver 2.22
[    6.797741] NET: Registered PF_BLUETOOTH protocol family
[    6.797743] Bluetooth: HCI device and connection manager initialized
[    6.797747] Bluetooth: HCI socket layer initialized
[    6.797749] Bluetooth: L2CAP socket layer initialized
[    6.797753] Bluetooth: SCO socket layer initialized

最近编辑记录 lspl5 (2024-08-29 14:27:10)

matrikslee · 2024-08-29 17:01:26

死机一般考虑内核问题，你目前用的啥内核，试试换个内核会不会改善

lspl5 · 2024-08-30 09:26:41

matrikslee 说：

死机一般考虑内核问题，你目前用的啥内核，试试换个内核会不会改善

---
linux的stable,因为是第一次使用linux,所以没有在一开始装其他内核，现在可以额外安装例如zen之类的内核并使用吗？

matrikslee · 2024-08-30 14:49:45

可以的，用pacman安装一下其它的内核软件包，然后重启开机的时候选择即可

lspl5 · 2024-09-05 20:02:28

在更换了内核之后，我发现依旧没有效果
于是我又重新尝试了包括top在内的命令来查找CS2线程的问题
最后在CS2崩溃后马上用dmesg命令才找到了问题所在：
----

$ sudo dmesg
>[ 2487.211778] Out of memory: Killed process 29510 (cs2) total-vm:12843352kB, anon-rss:2054580kB, file-rss:13736kB, shmem-rss:4248kB, UID:1000 pgtables:14688kB oom_score_adj:200

----
也就是说物理内存（RES）与虚拟内存（VIRT）的不足导致CS2崩溃
如果要解决可能只能加装物理内存或扩大虚拟内存，甚至可能是在bios里调核显共用显存的大小（我的只有512mb共用）
----
但我仍有以下疑问：
为什么steam也会紧跟着与CS2一起崩溃呢？
在dmesg命令输出里没有提到kill steam
steam与CS2在命令top的输出里也是两个单独的线程
望各位能够帮助我解答一下，谢谢

最近编辑记录 lspl5 (2024-09-05 20:04:45)

依云 · 2024-09-05 20:08:50

没听说过虚拟内存不足的，这东西有些程序跑起来就是2T来着。
OOM 时被连带杀死的话，大概是 systemd 干的。你去看系统日志。

lspl5 · 2024-09-05 22:11:55

依云说：

没听说过虚拟内存不足的，这东西有些程序跑起来就是2T来着。
OOM 时被连带杀死的话，大概是 systemd 干的。你去看系统日志。

不好意思，上面那个帖子我自己不懂装懂，麻烦依云大大了QAQ
---
同一台电脑（lenovo xiaoxin_air_14_2021）话说为什么CS2在linux下会直接触发OOM,而在windows下不会呢？
是不是因为后者会自动把CS2的进程靠前，还是说windows压根就没有oom,只会放慢自己的运行速度或者原地死机？

最近编辑记录 lspl5 (2024-09-05 22:15:39)

依云 · 2024-09-05 23:45:34

没听说过 Windows 有 OOM Killer。

matrikslee · 2024-09-09 09:11:11

哪里有内存泄漏了吧，

话说你不如先报告一下你机器的内存配置，以及打开游戏后top/htop显示的游戏进程使用的内存情况

lspl5 · 2024-09-09 12:28:21

matrikslee 说：

哪里有内存泄漏了吧，
话说你不如先报告一下你机器的内存配置，以及打开游戏后top/htop显示的游戏进程使用的内存情况

--------------
好的，下面是今天刚更新完后的系统：
OS: Arch Linux x86_64
Host: 82LM Lenovo XiaoXinAir 14ALC 2021
Kernel: 6.10.8-zen1-1-zen
Uptime: 13 mins
Packages: 1075 (pacman)
Shell: bash 5.2.32
Resolution: 1920x1080
DE: Plasma 6.1.4
WM: kwin
Theme: Breeze [GTK2/3]
Icons: breeze [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 5 5500U with Radeon Graphics (12) @ 4.056GHz
GPU: AMD ATI 04:00.0 Lucienne
Memory: 4147MiB / 7268MiB
---------------------
下面是top指令的内容（top -b -n 1 > top_output.txt）：
进程号 USER PR NI VIRT RES SHR %CPU %MEM TIME+ COMMAND
31862 lspl5 20 0 9527700 818004 73720 S 18.2 11.0 1:04.71 cs2
1703 lspl5 20 0 897236 31972 24084 S 9.1 0.4 0:54.56 steam
32314 lspl5 20 0 12824 9128 6952 R 9.1 0.1 0:00.01 top
1 root 20 0 21124 10116 7380 S 0.0 0.1 0:01.21 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
---------------------
用ksystemlog获取的信息：(有截图，已发送至依云与matrikslee两位的邮箱里了，抱歉，看了帮助后还是没理解如何在帖子上发图片QAQ)
1journald:

2024/9/9 12:00 kernel oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@autostart.service,task=cs2,pid=31862,uid=1000
2024/9/9 12:00 kernel Out of memory: Killed process 31862 (cs2) total-vm:11470656kB, anon-rss:1041176kB, file-rss:8044kB, shmem-rss:4300kB, UID:1000 pgtables:12456kB oom_score_adj:200
2024/9/9 12:00 systemd user@1000.service: A process of this unit has been killed by the OOM killer.
2024/9/9 12:00 systemd app-steam@autostart.service: A process of this unit has been killed by the OOM killer.
2024/9/9 12:00 pipewire pw.node: (alsa_output.pci-0000_04_00.6.HiFi__Speaker__sink-49) graph xrun not-triggered (1 suppressed)
2024/9/9 12:00 pipewire pw.node: (alsa_output.pci-0000_04_00.6.HiFi__Speaker__sink-49) xrun state:0x72bec9c96008 pending:1/2 s:1531991499820 a:1531991545636 f:1531991561490 waiting:45816 process:15854 status:triggered
2024/9/9 12:00 pipewire pw.node: (Audio Stream-121) xrun state:0x72bec9bf5008 pending:0/1 s:1532012836540 a:1531991524963 f:1531991538023 waiting:18446744073688240039 process:13060 status:triggered
2024/9/9 12:00 systemd-coredump Process 2218 (steamwebhelper) of user 1000 terminated abnormally with signal 5/TRAP, processing...
2024/9/9 12:00 systemd Created slice Slice /system/drkonqi-coredump-processor.
2024/9/9 12:00 systemd Created slice Slice /system/systemd-coredump.
2024/9/9 12:00 systemd Started Process Core Dump (PID 32468/UID 0).
2024/9/9 12:00 systemd Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024/9/9 12:00 systemd-coredump Process 2218 (steamwebhelper) of user 1000 dumped core.

Stack trace of thread 2218:
#0 0x0000791a32c2c338 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c2c338)
#1 0x0000791a31728837 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x4728837)
#2 0x0000791a31725ac6 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x4725ac6)
#3 0x0000791a31724943 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x4724943)
#4 0x0000791a3172fcb4 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x472fcb4)
#5 0x0000791a31731044 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x4731044)
#6 0x0000791a3159203f n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x459203f)
#7 0x0000791a315f13a4 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x45f13a4)
#8 0x0000791a315f15c9 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x45f15c9)
#9 0x0000791a32c78126 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c78126)
#10 0x0000791a32c91c9b n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c91c9b)
#11 0x0000791a32c924ea n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c924ea)
#12 0x0000791a32c333a4 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c333a4)
#13 0x0000791a32c92bfc n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c92bfc)
#14 0x0000791a32c59f58 n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x5c59f58)
#15 0x0000791a2f56889a n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/libcef.so + 0x256889a)
#16 0x000062b1bb3a3faa n/a (/home/lspl5/.local/share/Steam/ubuntu12_64/steamwebhelper + 0x2c2faa)
ELF object binary architecture: AMD x86-64

2024/9/9 12:00 systemd systemd-coredump@0-32468-0.service: Deactivated successfully.
2024/9/9 12:00 systemd systemd-coredump@0-32468-0.service: Consumed 1.447s CPU time, 741.3M memory peak.
2024/9/9 12:00 plasmashell The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.
2024/9/9 12:00 drkonqi-coredump-processor "/home/lspl5/.local/share/Steam/ubuntu12_64/steamwebhelper" 2218 "/var/lib/systemd/coredump/core.steamwebhelper.1000.d92439f25feb4537b6f33a8f12a92f6f.2218.1725854434000000.zst"
2024/9/9 12:00 systemd Started Launch DrKonqi for a systemd-coredump crash (PID 32471/UID 0).
2024/9/9 12:00 drkonqi-coredump-launcher Unable to find file for pid 2218 expected at "kcrash-metadata/steamwebhelper.d92439f25feb4537b6f33a8f12a92f6f.2218.ini"
2024/9/9 12:00 drkonqi-coredump-launcher Nothing handled the dump
2024/9/9 12:00 systemd drkonqi-coredump-processor@0-32468-0.service: Deactivated successfully.
2024/9/9 12:00 systemd app-steam@autostart.service: State 'stop-sigterm' timed out. Killing.
2024/9/9 12:00 systemd app-steam@autostart.service: Killing process 1703 (steam) with signal SIGKILL.
2024/9/9 12:00 systemd app-steam@autostart.service: Killing process 32477 (steam-runtime-l) with signal SIGKILL.
2024/9/9 12:00 systemd app-steam@autostart.service: Killing process 12114 (steam) with signal SIGKILL.
2024/9/9 12:00 kded6 Service ":1.75" unregistered
2024/9/9 12:00 systemd app-steam@autostart.service: Failed with result 'oom-kill'.
2024/9/9 12:00 systemd app-steam@autostart.service: Consumed 6min 12.615s CPU time, 3.8G memory peak, 2.7G memory swap peak.

2、内核日志:
2024/9/9 12:00
oom-kill
onstraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@autostart.service,task=cs2,pid=31862,uid=1000
2024/9/9 12:00
Out of memory
Killed process 31862 (cs2) total-vm:11470656kB, anon-rss:1041176kB, file-rss:8044kB, shmem-rss:4300kB, UID:1000 pgtables:12456kB oom_score_adj:200
-------------
dmesg：
[ 1532.004407] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@autostart.service,task=cs2,pid=31862,uid=1000
[ 1532.004520] Out of memory: Killed process 31862 (cs2) total-vm:11470656kB, anon-rss:1041176kB, file-rss:8044kB, shmem-rss:4300kB, UID:1000 pgtables:12456kB oom_score_adj:200
----------
这就是目前已有的信息
希望对这个问题有所帮助
：）

Arch Linux

#1 2023-05-20 11:55:11

轻薄本KDE玩游戏死机

#2 2023-05-20 18:25:59

Re: 轻薄本KDE玩游戏死机

#3 2023-05-20 20:01:56

Re: 轻薄本KDE玩游戏死机

#4 2024-02-01 01:47:12

Re: 轻薄本KDE玩游戏死机

#5 2024-02-01 09:45:43

Re: 轻薄本KDE玩游戏死机

#6 2024-08-29 14:20:33

Re: 轻薄本KDE玩游戏死机

#7 2024-08-29 17:01:26

Re: 轻薄本KDE玩游戏死机

#8 2024-08-30 09:26:41

Re: 轻薄本KDE玩游戏死机

#9 2024-08-30 14:49:45

Re: 轻薄本KDE玩游戏死机

#10 2024-09-05 20:02:28

Re: 轻薄本KDE玩游戏死机

#11 2024-09-05 20:08:50

Re: 轻薄本KDE玩游戏死机

#12 2024-09-05 22:11:55

Re: 轻薄本KDE玩游戏死机

#13 2024-09-05 23:45:34

Re: 轻薄本KDE玩游戏死机

#14 2024-09-09 09:11:11

Re: 轻薄本KDE玩游戏死机

#15 2024-09-09 12:28:21

Re: 轻薄本KDE玩游戏死机

页脚