From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205089] amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
Date: Fri, 09 May 2025 22:50:00 +0000 [thread overview]
Message-ID: <bug-205089-2300-sKeaztdJx9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205089
Nelson G (konoha02@yahoo.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |konoha02@yahoo.com
--- Comment #63 from Nelson G (konoha02@yahoo.com) ---
6.1.135 (debian 12), ryzen 3500u, xfce4 (xfwm4 with vblank=xpresent)
was using libreoffice and atril both tiled to each side of the screen, i was
scrolling through the pdf then this happened (first time ever it happens ime):
may 09 19:14:12 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=2363974, emitted seq=2363976
may 09 19:14:12 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process Xorg pid 1891 thread Xorg:cs0 pid 1936
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: free PSP TMR buffer
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded,
trying to resume
may 09 19:14:12 kernel: [drm] PCIE GART of 1024M enabled.
may 09 19:14:12 kernel: [drm] PTB located at 0x000000F400A00000
may 09 19:14:12 kernel: [drm] VRAM is lost due to GPU reset!
may 09 19:14:12 kernel: [drm] PSP is resuming...
may 09 19:14:12 kernel: [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode
is not available
may 09 19:14:12 kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode
is not available
may 09 19:14:13 kernel: [drm] kiq ring mec 2 pipe 1 q 0
may 09 19:14:13 kernel: [drm] VCN decode and encode initialized
successfully(under SPG Mode).
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0
on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM
inv eng 1 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM
inv eng 4 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM
inv eng 5 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM
inv eng 6 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM
inv eng 7 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM
inv eng 8 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM
inv eng 9 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM
inv eng 10 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv
eng 11 on hub 0
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng
0 on hub 1
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv
eng 1 on hub 1
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv
eng 4 on hub 1
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv
eng 5 on hub 1
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv
eng 6 on hub 1
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo from
shadow start
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: recover vram bo from
shadow done
may 09 19:14:13 kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset(2) succeeded!
may 09 19:14:13 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to
initialize parser -125!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-05-09 22:50 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 11:48 [Bug 205089] New: amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125 bugzilla-daemon
2019-10-07 3:16 ` [Bug 205089] " bugzilla-daemon
2019-10-08 17:50 ` bugzilla-daemon
2019-10-08 18:23 ` bugzilla-daemon
2019-10-08 20:15 ` bugzilla-daemon
2019-10-08 20:19 ` bugzilla-daemon
2019-10-12 19:05 ` bugzilla-daemon
2019-10-12 19:06 ` bugzilla-daemon
2019-10-14 17:20 ` bugzilla-daemon
2019-10-14 19:07 ` bugzilla-daemon
2020-04-27 16:58 ` bugzilla-daemon
2020-04-28 7:25 ` bugzilla-daemon
2020-04-28 8:01 ` bugzilla-daemon
2020-07-25 7:35 ` bugzilla-daemon
2021-07-26 20:35 ` bugzilla-daemon
2021-07-28 19:03 ` bugzilla-daemon
2021-08-01 19:43 ` bugzilla-daemon
2021-08-02 14:13 ` bugzilla-daemon
2021-08-02 14:24 ` bugzilla-daemon
2021-08-15 19:03 ` bugzilla-daemon
2021-08-25 16:03 ` bugzilla-daemon
2021-11-11 16:14 ` bugzilla-daemon
2021-11-11 16:15 ` bugzilla-daemon
2021-11-12 5:06 ` bugzilla-daemon
2021-11-12 19:29 ` bugzilla-daemon
2021-11-21 17:30 ` bugzilla-daemon
2021-11-22 14:50 ` bugzilla-daemon
2021-11-26 11:43 ` bugzilla-daemon
2021-11-27 2:51 ` bugzilla-daemon
2021-11-27 14:12 ` bugzilla-daemon
2021-11-28 14:32 ` bugzilla-daemon
2022-01-02 9:37 ` bugzilla-daemon
2022-03-06 12:34 ` bugzilla-daemon
2022-03-09 14:54 ` bugzilla-daemon
2022-03-13 17:46 ` bugzilla-daemon
2022-03-13 18:54 ` bugzilla-daemon
2022-03-21 17:07 ` bugzilla-daemon
2022-05-07 5:54 ` bugzilla-daemon
2022-05-07 6:28 ` bugzilla-daemon
2022-05-07 6:48 ` bugzilla-daemon
2022-05-08 19:23 ` bugzilla-daemon
2022-05-11 9:51 ` bugzilla-daemon
2022-05-27 11:22 ` bugzilla-daemon
2022-05-27 11:23 ` bugzilla-daemon
2022-05-30 12:39 ` bugzilla-daemon
2022-05-31 16:03 ` bugzilla-daemon
2022-05-31 18:34 ` bugzilla-daemon
2022-06-02 10:12 ` bugzilla-daemon
2022-09-09 4:08 ` bugzilla-daemon
2022-09-10 9:57 ` bugzilla-daemon
2022-10-07 21:41 ` bugzilla-daemon
2022-12-27 9:52 ` bugzilla-daemon
2022-12-27 9:53 ` bugzilla-daemon
2023-06-13 14:34 ` bugzilla-daemon
2023-07-01 5:10 ` bugzilla-daemon
2023-07-01 5:16 ` bugzilla-daemon
2023-07-11 13:14 ` bugzilla-daemon
2023-07-11 13:19 ` bugzilla-daemon
2023-09-07 17:31 ` bugzilla-daemon
2023-10-14 18:37 ` bugzilla-daemon
2023-10-15 12:09 ` bugzilla-daemon
2024-01-05 10:51 ` bugzilla-daemon
2024-12-13 1:06 ` bugzilla-daemon
2025-05-09 22:50 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-205089-2300-sKeaztdJx9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).