You are not logged in.
I don't know what causes it, when it happens, I can't even switch to TTY, then I do REISUB to reboot.
What log file can I offer to figure out what has happened to my PC?
DE: Plasma 6.5
GPU: AMD RX9070XT
MESA: 25.2.5-arch1.2
Last edited by laichiaheng (2025-11-06 12:05:07)
Offline
I suspect that it is caused by gpu-screen-recorder, I think that I need to watch for a while.
Offline
gpu-screen-recorder
how about use obs instead?
are people really still use stuff like bansycam/hyprcam or sich crap instead of just obs?
Offline
Check with
journalctl -b -1 -p err..alertafter a reboot
Check for any amdgpu errors, if your suspicion of gpu-screen-recorder being the culprit is true.
laichiaheng wrote:gpu-screen-recorder
how about use obs instead?
are people really still use stuff like bansycam/hyprcam or sich crap instead of just obs?
What an ignorant comment. gpu-screen-recorder is probably the most performant hardware accelerated screen recorder across any OS available right now. I could in turn ask you why you're still on OBS.
Offline
Check with
journalctl -b -1 -p err..alertafter a reboot
Check for any amdgpu errors, if your suspicion of gpu-screen-recorder being the culprit is true.
[laichiaheng@laichiaheng ~]$ journalctl -b -1 -p err..alert|grep amdgpu
Journal file /var/log/journal/262b10715d8143e0af71df2c57de45df/system@000642093a435739-f791076df19414cc.journal~ is truncated, ignoring file.
10月 29 17:26:13 laichiaheng kernel: amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
10月 29 17:26:40 laichiaheng kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
10月 29 17:26:47 laichiaheng kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
It hasn't happend since I exit gpu-screen-recorder 5 hours ago.
Offline
I could in turn ask you why you're still on OBS.
several reasons - but to stay at your level: just because its objectively better in multiple ways
(yes, this useless reply is intentional to fullfill your "i'm ignorant" view of mine)
Offline
Hey, only arch gets to draw that card!![]()
Leaving aside who has the bigger penis (me) the bug seems in the kernel module anyway and there's little reason to assume that OBS would not run into the same problems using the same HW acceleration.
@laichiaheng,
Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
=> Have you done that and does the problem remain?
Wrt you grep, when you trigger the proble, DO NOT REBOOT WITH THE POWER BUTTON!
Use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (+REISUB)
Do the timestamps match an incident?
Please post a complete journal covering the problem - not filtered for err..alert
Offline
It's not about having a bigger penis, but comparing gpu-screen-recorder to something like hyprcam just shows this person has absolutely no clue about the software they're shitting on beyond "it's not OBS". ![]()
I mentioned specifiying error priority because that's usually what I do after a perceived GPU driver crash to filter out the noise, but it doesn't seem like it provided much context in this case. My bad.
Offline
Hey, only arch gets to draw that card!
Leaving aside who has the bigger penis (me) the bug seems in the kernel module anyway and there's little reason to assume that OBS would not run into the same problems using the same HW acceleration.
@laichiaheng,
amdgpu wrote:Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
=> Have you done that and does the problem remain?
I haven't disabled the overdrive yet, but it has never happened since I disable gpu-screen-recorder yesterday.
Wrt you grep, when you trigger the proble, DO NOT REBOOT WITH THE POWER BUTTON!
Use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (+REISUB)
Do the timestamps match an incident?
Please post a complete journal covering the problem - not filtered for err..alert
I do reboot with REISUB, isn't the full journal too long to be here?
Offline
the comparison is actually justified - because gsr does exactly and not more than fraps/bandycam/hyprcam did: just record
even worse: for full screen capture it requires root - why?
it's cli - ok, but rely on SIGINT and SIGUSR2? that's just poor design choice and is quite error prone
it's also limited in not able to make use of a 2nd gpu as encoder accelerator so the main gpu isn't affected at all
the tests its site claim and the used system - c'mon - someone failed something quite hard - i used obs back in late 2010s with gtav in triple-screen setup and it didn't affected the framerate - and that was on a amd fx - a chip design about as bad as pentium
so "obs is better" is not just an uneducated guess but objective based on knowledge and years of experience
I come from a time back in the late 2000s when fraps was pretty much the only option and hence used by everybody - obs was a huge step in content creation - why should i tbrow away all its benefits for some one-person hobby project which is merely any better than the mentioned grabbers were 10-20 years ago?
but i'm the ignorant one having no clue i'm talkin about?
yea - maybe you should go ouside and touch grass for start instead of bitchin around with people you don't know
Offline
I do reboot with REISUB, isn't the full journal too long to be here?
Depends on how long it actually is, but you can upload it eg to
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stI believe you that gpu-screen-recorder is the trigger, but the question is whether it triggers a failure caused by the overdrive mode.
@b1scotti, that's not what she said ![]()
Offline
I do reboot with REISUB, isn't the full journal too long to be here?
Depends on how long it actually is, but you can upload it eg to
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stI believe you that gpu-screen-recorder is the trigger, but the question is whether it triggers a failure caused by the overdrive mode.
@b1scotti, that's not what she said
I have disabled the overdrive, I'll watch if it still happens.
Offline
I do reboot with REISUB, isn't the full journal too long to be here?
Depends on how long it actually is, but you can upload it eg to
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stI believe you that gpu-screen-recorder is the trigger, but the question is whether it triggers a failure caused by the overdrive mode.
@b1scotti, that's not what she said
It keeps happening without gpu-screen-recorder and overdrive.
Last edited by laichiaheng (2025-11-01 17:18:16)
Offline
The boot is only two minutes but the amd errors are still 80s before
11月 02 01:14:09 laichiaheng drkonqi-coredump-launcher[7388]: Unable to find file for pid 66100 expected at "kcrash-metadata/ksecretd.c8c9ae79ac3a4179975b1671d3795c18.66100.ini"
11月 02 01:14:09 laichiaheng drkonqi-coredump-processor[1488]: "/usr/bin/mpv" 9065 "/var/lib/systemd/coredump/core.mpv.1000.a9fe779d006349d3a0f0d9b9ce97101f.9065.1761670247000000.zst"
11月 02 01:14:09 laichiaheng systemd[966]: Started Launch DrKonqi for a systemd-coredump crash (PID 1488/UID 1000).
11月 02 01:14:09 laichiaheng drkonqi-coredump-processor[1488]: "/usr/bin/gsr-notify" 961 "/var/lib/systemd/coredump/core.gsr-notify.1000.879ccb24a9e741a7867954fb3af65c66.961.1761722511000000.zst"
11月 02 01:14:09 laichiaheng drkonqi-coredump-launcher[7393]: Unable to find file for pid 9065 expected at "kcrash-metadata/mpv.a9fe779d006349d3a0f0d9b9ce97101f.9065.ini"
11月 02 01:14:09 laichiaheng systemd[966]: Started Launch DrKonqi for a systemd-coredump crash (PID 1488/UID 1000).
11月 02 01:14:09 laichiaheng drkonqi-coredump-launcher[7394]: Unable to find file for pid 961 expected at "kcrash-metadata/gsr-notify.879ccb24a9e741a7867954fb3af65c66.961.ini"
11月 02 01:14:12 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:30:4f:75:62:22:47:08:00 SRC=202.39.67.204 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=121 ID=53080 PROTO=TCP SPT=443 DPT=40114 WINDOW=1045 RES=0x00 ACK URGP=0
11月 02 01:14:15 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:30:4f:75:62:22:47:08:00 SRC=202.39.67.204 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=121 ID=59676 PROTO=TCP SPT=443 DPT=40102 WINDOW=1045 RES=0x00 ACK URGP=0
11月 02 01:14:18 laichiaheng konsole[7266]: QObject::disconnect: Unexpected nullptr parameter
11月 02 01:14:42 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:30:4f:75:62:22:47:08:00 SRC=202.39.67.204 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=121 ID=53081 PROTO=TCP SPT=443 DPT=40114 WINDOW=1045 RES=0x00 ACK URGP=0
11月 02 01:14:45 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:30:4f:75:62:22:47:08:00 SRC=202.39.67.204 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=121 ID=59677 PROTO=TCP SPT=443 DPT=40102 WINDOW=1045 RES=0x00 ACK URGP=0
11月 02 01:14:58 laichiaheng kernel: sysrq: Keyboard mode set to system defaultwhen it happens, I can't even switch to TTY
Can you still ssh into the system and restart sddm/isolate the multi-user.target?
Offline
Can you still ssh into the system and restart sddm/isolate the multi-user.target?
I will try it if it happens.
Offline
The boot is only two minutes but the amd errors are still 80s before
when it happens, I can't even switch to TTY
Can you still ssh into the system and restart sddm/isolate the multi-user.target?
Nope, I can't connect to my PC via SSH when it happens.
By the way, why does this appear when I try to upload my logfile?
Journal file /var/log/journal/262b10715d8143e0af71df2c57de45df/system@000642093a435739-f791076df19414cc.journal~ is truncated, ignoring file.I'm disabling the experimental HDR on Firefox to see if it still happens, most of the time seem to happen when I play HDR video, but I'm not so sure.
Last edited by laichiaheng (2025-11-03 04:01:09)
Offline
11月 03 10:03:12 laichiaheng kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
11月 03 10:03:19 laichiaheng kernel: amdgpu: Freeing queue vital buffer 0x7ff3cd600000, queue evicted
11月 03 10:03:19 laichiaheng kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:06:49 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 03 10:06:49 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 012a6ae38579c502aa837bf701f2d523843df443]
11月 03 10:19:50 laichiaheng kernel: sysrq: Keyboard mode set to system defaultThere're 13 minutes between the last amdgpu errors and the sysrq
The tail
11月 03 10:18:39 laichiaheng systemd[950]: Started app-org.kde.konsole-10196.scope.
11月 03 10:18:42 laichiaheng rtkit-daemon[1210]: Successfully made thread 10277 of process 10221 owned by '1000' RT at priority 20.
11月 03 10:18:42 laichiaheng rtkit-daemon[1210]: Supervising 11 threads of 8 processes of 1 users.
11月 03 10:18:43 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:fb:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
11月 03 10:18:46 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:9c:65:ee:ac:4d:57:08:00 SRC=1.1.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=15707 DF PROTO=2
11月 03 10:18:53 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:40:55:39:5b:40:06:08:00 SRC=172.26.187.4 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=72 PROTO=2
11月 03 10:18:54 laichiaheng kernel: HDR SB:01 1a 02 00 2f 88 9a 39 4b 27 c3 8c 2f 1d 04 0c
11月 03 10:18:54 laichiaheng kernel: HDR SB:3a 3d 47 40 b7 03 00 00 b7 03 b7 03 00 00 00 00
11月 03 10:18:56 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:fb:c2:24:db:26:30:b6:08:00 SRC=192.168.1.105 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=35887 PROTO=2
11月 03 10:19:03 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=1433 DF PROTO=TCP SPT=1716 DPT=51974 WINDOW=87 RES=0x00 ACK FIN URGP=0
11月 03 10:19:04 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=15321 DF PROTO=TCP SPT=1716 DPT=59806 WINDOW=84 RES=0x00 ACK FIN URGP=0
11月 03 10:19:09 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=1434 DF PROTO=TCP SPT=1716 DPT=51974 WINDOW=87 RES=0x00 ACK FIN URGP=0
11月 03 10:19:09 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=15322 DF PROTO=TCP SPT=1716 DPT=59806 WINDOW=84 RES=0x00 ACK FIN URGP=0
11月 03 10:19:17 laichiaheng sshd-session[10314]: Accepted publickey for laichiaheng from 192.168.1.111 port 49030 ssh2: ED25519 SHA256:VeL9yCVpXUADRHHqguKUcZ4Z+KN+LSrbzlhHYWGLh2o
11月 03 10:19:17 laichiaheng sshd-session[10314]: pam_unix(sshd:session): session opened for user laichiaheng(uid=1000) by laichiaheng(uid=0)
11月 03 10:19:21 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=15323 DF PROTO=TCP SPT=1716 DPT=59806 WINDOW=84 RES=0x00 ACK FIN URGP=0
11月 03 10:19:43 laichiaheng kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=04:d4:c4:48:24:f3:9e:9d:f0:f2:38:d8:08:00 SRC=192.168.1.111 DST=192.168.1.102 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=15324 DF PROTO=TCP SPT=1716 DPT=59806 WINDOW=84 RES=0x00 ACK FIN URGP=0
11月 03 10:19:50 laichiaheng kernel: sysrq: Keyboard mode set to system default10:18:39 - starting konsole
10:18:54 - HDR messages
10:19:17 - you /do/ ssh into the system
10:19:50 - sysrq
By the way, why does this appear when I try to upload my logfile?
There's a bogus-ish journal archived.
ls -l /var/log/journal/262b10715d8143e0af71df2c57de45dfOffline
10:18:39 - starting konsole
10:18:54 - HDR messages
10:19:17 - you /do/ ssh into the system
10:19:50 - sysrqBy the way, why does this appear when I try to upload my logfile?
There's a bogus-ish journal archived.
ls -l /var/log/journal/262b10715d8143e0af71df2c57de45df
So...is it caused by the HDR on Firefox? So far, I haven't had the freezing issue since I disabled it.
I tried to connect to the PC via SSH, but there was no response. Once I rebooted, I could connect my PC.
Last edited by laichiaheng (2025-11-03 10:13:27)
Offline
Seems so, yes.
On a formal note, please avoid bloating the thread with completely pointless full quotes of the immediately previous post.
Offline
I do seem to experience similar issue recently:
Nov 03 16:02:40 maya kernel: INFO: task kworker/1:0:27 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/1:0 state:D stack:0 pid:27 tgid:27 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:0:81 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:0 state:D stack:0 pid:81 tgid:81 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/1:1:109 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/1:1 state:D stack:0 pid:109 tgid:109 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:1:158 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:1 state:D stack:0 pid:158 tgid:158 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:2:501 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:2 state:D stack:0 pid:501 tgid:501 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/1:2:756 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/1:2 state:D stack:0 pid:756 tgid:756 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/1:3:784 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/1:3 state:D stack:0 pid:784 tgid:784 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:3:1092 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:3 state:D stack:0 pid:1092 tgid:1092 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:4:6623 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:4 state:D stack:0 pid:6623 tgid:6623 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:5:6624 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:5 state:D stack:0 pid:6624 tgid:6624 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/1:3:784 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/1:3 state:D stack:0 pid:784 tgid:784 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:3:1092 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:3 state:D stack:0 pid:1092 tgid:1092 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:4:6623 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:4 state:D stack:0 pid:6623 tgid:6623 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: INFO: task kworker/10:5:6624 blocked for more than 122 seconds.
Nov 03 16:02:40 maya kernel: Tainted: G OE 6.17.6-arch1-1 #1
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: task:kworker/10:5 state:D stack:0 pid:6624 tgid:6624 ppid:2 task_flags:0x4208060 flags:0x00004000
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: Call Trace:
Nov 03 16:02:40 maya kernel: <TASK>
Nov 03 16:02:40 maya kernel: __schedule+0x418/0x1330
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: ? place_entity+0x1b/0x150
Nov 03 16:02:40 maya kernel: ? srso_return_thunk+0x5/0x5f
Nov 03 16:02:40 maya kernel: schedule+0x27/0xd0
Nov 03 16:02:40 maya kernel: schedule_timeout+0xbd/0x100
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: ? lock_timer_base+0x70/0x90
Nov 03 16:02:40 maya kernel: process_one_work+0x193/0x350
Nov 03 16:02:40 maya kernel: worker_thread+0x2d7/0x410
Nov 03 16:02:40 maya kernel: ? __pfx_worker_thread+0x10/0x10
Nov 03 16:02:40 maya kernel: kthread+0xfc/0x240
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork+0x1c4/0x1f0
Nov 03 16:02:40 maya kernel: ? __pfx_kthread+0x10/0x10
Nov 03 16:02:40 maya kernel: ret_from_fork_asm+0x1a/0x30
Nov 03 16:02:40 maya kernel: </TASK>
Nov 03 16:02:40 maya kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warningsThe system froze around 16:18 without any error messages other than network related at a time.
I'm on Gnome with AMD Radeon 7800XT. I do have Firefox HDR disabled, but I have Gnome with 2 x 4K monitors, both HDR enabled.
Last edited by suhy (2025-11-03 15:42:36)
Offline
The journal segment is from 16:02, not 16:18
See whether you've stuff like
11月 03 10:18:54 laichiaheng kernel: HDR SB:01 1a 02 00 2f 88 9a 39 4b 27 c3 8c 2f 1d 04 0c
11月 03 10:18:54 laichiaheng kernel: HDR SB:3a 3d 47 40 b7 03 00 00 b7 03 b7 03 00 00 00 00Offline
$ journalctl -b -1 -k | grep -i "GPU\|fence\|hung\|HDR"
grep: warning: GREP_COLOR='1;33' is deprecated; use GREP_COLORS='mt=1;33'
Nov 03 15:58:59 maya kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
Nov 03 15:58:59 maya kernel: [drm] amdgpu kernel modesetting enabled.
Nov 03 15:58:59 maya kernel: amdgpu: Virtual CRAT table created for CPU
Nov 03 15:58:59 maya kernel: amdgpu: Topology: Add CPU node
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: initializing kernel modesetting (IP DISCOVERY 0x1002:0x747E 0x1002:0x0E37 0xC8).
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: register mmio base: 0xFC800000
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: register mmio size: 1048576
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 0 <soc21_common>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 1 <gmc_v11_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 2 <ih_v6_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 3 <psp>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 4 <smu>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 5 <dm>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 6 <gfx_v11_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 7 <sdma_v6_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 8 <vcn_v4_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 9 <jpeg_v4_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: detected ip block number 10 <mes_v11_0>
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: No more image in the PCI ROM
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Fetched VBIOS from ROM BAR
Nov 03 15:58:59 maya kernel: amdgpu: ATOM BIOS: 113-D7120200-100
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: CP RS64 enable
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: vgaarb: deactivate vga console
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: MEM ECC is not presented.
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: SRAM ECC is not presented.
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: DF poison setting is inconsistent(1:0:0:0)!
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Poison setting is inconsistent in DF/UMC(0:1)!
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: amdgpu: 16368M of VRAM memory ready
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: amdgpu: 16019M of GTT memory ready.
Nov 03 15:58:59 maya kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x07002F00
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 22
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 22
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: reserve 0xa700000 from 0x83e0000000 for PSP TMR
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: RAP: optional rap ta ucode is not available
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00505500 (80.85.0)
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: SMU driver if version not matched
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: SMU is initialized successfully!
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] Display Core v3.2.340 initialized on DCN 3.2
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] DP-HDMI FRL PCON supported
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
Nov 03 15:58:59 maya kernel: amdgpu: HMM registered 16368MB device memory
Nov 03 15:58:59 maya kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Nov 03 15:58:59 maya kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Nov 03 15:58:59 maya kernel: amdgpu: Virtual CRAT table created for GPU
Nov 03 15:58:59 maya kernel: amdgpu: Topology: Add dGPU node [0x747e:0x1002]
Nov 03 15:58:59 maya kernel: kfd kfd: amdgpu: added device 1002:747e
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: SE 3, SH per SE 2, CU per SH 10, active_cu_number 60
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: amdgpu: Using BAMACO for runtime pm
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: [drm] Registered 4 planes with drm panic
Nov 03 15:58:59 maya kernel: [drm] Initialized amdgpu 3.64.0 for 0000:1f:00.0 on minor 1
Nov 03 15:58:59 maya kernel: fbcon: amdgpudrmfb (fb0) is primary device
Nov 03 15:58:59 maya kernel: amdgpu 0000:1f:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Nov 03 15:59:00 maya kernel: snd_hda_intel 0000:1f:00.1: bound 0000:1f:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Nov 03 15:59:11 maya kernel: HDR SB:01 1a 02 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:01 1a 02 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:01 1a 02 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:01 1a 02 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:11 maya kernel: HDR SB:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Nov 03 15:59:19 maya kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
Nov 03 15:59:27 maya kernel: amdgpu: Freeing queue vital buffer 0x7f5a6e400000, queue evicted
Nov 03 15:59:27 maya kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 03 16:02:40 maya kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
Nov 03 16:02:40 maya kernel: dma_fence_default_wait+0x199/0x280
Nov 03 16:02:40 maya kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Nov 03 16:02:40 maya kernel: dma_fence_wait_timeout+0x129/0x150
Nov 03 16:02:40 maya kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5faa1405a9473f94b2740a5b7ab0b7bf19eca396]
Nov 03 16:02:40 maya kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warningsThere are HDR messages, but even earlier than the amdgpu errors.
The journal segment is from 16:02, not 16:18
Indeed, there is nothing relevant in journalctl I can find from around 16:18. When I'll get another issue like this I'll try to ssh into from another machine to see whether there is anything else that I can find.
EDIT: Just had a freeze probably triggered by a video which played on a website. Couldn't find anything more useful in logs over SSH - checked both dmesg and journalctl
Last edited by suhy (2025-11-03 16:51:49)
Offline
there is nothing relevant in journalctl I can find from around 16:18.
What /is/ there around 16:18?
In case the journal stops early, don't reboot w/ the power button but in doubt use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB
Offline
I successfully connected to my PC via SSH this time, I tried to restart sddm, no responsed, I tried to reboot, no responsed either.
The experimental HDR on Firefox was disabled.
Last edited by laichiaheng (2025-11-04 12:40:16)
Offline
This is two minutes before you ssh into the system
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/8:0:69 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/8:0 state:D stack:0 pid:69 tgid:69 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x88/0x990
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? psi_group_change+0x160/0x310
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:0:75 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:0 state:D stack:0 pid:75 tgid:75 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x334/0x990
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/8:1:135 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/8:1 state:D stack:0 pid:135 tgid:135 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x334/0x990
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:1:159 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:1 state:D stack:0 pid:159 tgid:159 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x88/0x990
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? psi_group_change+0x160/0x310
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:2:339 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:2 state:D stack:0 pid:339 tgid:339 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x334/0x990
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/8:2:414 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/8:2 state:D stack:0 pid:414 tgid:414 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/8:3:415 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/8:3 state:D stack:0 pid:415 tgid:415 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x334/0x990
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:3:694 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:3 state:D stack:0 pid:694 tgid:694 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x334/0x990
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:4:5177 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:4 state:D stack:0 pid:5177 tgid:5177 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x88/0x990
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? psi_group_change+0x160/0x310
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: INFO: task kworker/9:5:5178 blocked for more than 122 seconds.
11月 04 20:21:07 laichiaheng kernel: Not tainted 6.17.7-zen1-1-zen #1
11月 04 20:21:07 laichiaheng kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
11月 04 20:21:07 laichiaheng kernel: task:kworker/9:5 state:D stack:0 pid:5178 tgid:5178 ppid:2 task_flags:0x4208060 flags:0x00004000
11月 04 20:21:07 laichiaheng kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
11月 04 20:21:07 laichiaheng kernel: Call Trace:
11月 04 20:21:07 laichiaheng kernel: <TASK>
11月 04 20:21:07 laichiaheng kernel: __schedule+0x456/0x23a0
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? try_to_wake_up+0x88/0x990
11月 04 20:21:07 laichiaheng kernel: ? srso_return_thunk+0x5/0x5f
11月 04 20:21:07 laichiaheng kernel: ? psi_group_change+0x160/0x310
11月 04 20:21:07 laichiaheng kernel: schedule+0x27/0xd0
11月 04 20:21:07 laichiaheng kernel: schedule_timeout+0xbd/0x100
11月 04 20:21:07 laichiaheng kernel: dma_fence_default_wait+0x137/0x280
11月 04 20:21:07 laichiaheng kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: dma_fence_wait_timeout+0x191/0x210
11月 04 20:21:07 laichiaheng kernel: amdgpu_tlb_fence_work+0x2c/0xe0 [amdgpu 5da64d241a288b5d268c3450bcf5865582f32cd7]
11月 04 20:21:07 laichiaheng kernel: process_one_work+0x193/0x350
11月 04 20:21:07 laichiaheng kernel: worker_thread+0x254/0x3a0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_worker_thread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: kthread+0xfc/0x240
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork+0x1c4/0x1f0
11月 04 20:21:07 laichiaheng kernel: ? __pfx_kthread+0x10/0x10
11月 04 20:21:07 laichiaheng kernel: ret_from_fork_asm+0x1a/0x30
11月 04 20:21:07 laichiaheng kernel: </TASK>
11月 04 20:21:07 laichiaheng kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings and also fits suhy (despite the time gap, maybe broken watch
)
Offline