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: Sun, 08 May 2022 19:23:34 +0000 [thread overview]
Message-ID: <bug-205089-2300-UFlBPnsu4J@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205089
Manuel Jesús de la Fuente (m@nueljl.in) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m@nueljl.in
--- Comment #40 from Manuel Jesús de la Fuente (m@nueljl.in) ---
Can still reproduce using the following:
- Ryzen 9 5900XT
- Radeon RX 6700XT
- Linux 5.17.4-1-default (openSUSE Tumbleweed with KDE Plasma)
- Mesa 22.0.2-308.2
May 08 20:18:32 localhost.localdomain kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2371535, emitted
seq=2371537
May 08 20:18:32 localhost.localdomain kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process kwin_x11 pid 1795 thread
kwin_x11:cs0 pid 1801
May 08 20:18:32 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: GPU
reset begin!
May 08 20:18:33 localhost.localdomain kernel: amdgpu 0000:2d:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
May 08 20:18:33 localhost.localdomain kernel: [drm:gfx_v10_0_hw_fini [amdgpu]]
*ERROR* KGQ disable failed
May 08 20:18:33 localhost.localdomain kernel: amdgpu 0000:2d:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed
(-110)
May 08 20:18:33 localhost.localdomain kernel: [drm:gfx_v10_0_hw_fini [amdgpu]]
*ERROR* KCQ disable failed
May 08 20:18:33 localhost.localdomain kernel: [drm:gfx_v10_0_hw_fini [amdgpu]]
*ERROR* failed to halt cp gfx
May 08 20:18:33 localhost.localdomain kernel: [drm] free PSP TMR buffer
May 08 20:18:33 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu:
MODE1 reset
May 08 20:18:33 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: GPU
mode1 reset
May 08 20:18:33 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: GPU
smu mode1 reset
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: GPU
reset succeeded, trying to resume
May 08 20:18:34 localhost.localdomain kernel: [drm] PCIE GART of 512M enabled
(table at 0x0000008000300000).
May 08 20:18:34 localhost.localdomain kernel: [drm] VRAM is lost due to GPU
reset!
May 08 20:18:34 localhost.localdomain kernel: [drm] PSP is resuming...
May 08 20:18:34 localhost.localdomain kernel: [drm] reserve 0xa00000 from
0x82fe000000 for PSP TMR
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: RAS:
optional ras ta ucode is not available
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu:
SECUREDISPLAY: securedisplay ta ucode is not available
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: SMU
is resuming...
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: smu
driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw version
= 0x00413500 (65.53.0)
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: SMU
driver if version not matched
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: SMU
is resumed successfully!
May 08 20:18:34 localhost.localdomain kernel: [drm] DMUB hardware initialized:
version=0x0202000C
May 08 20:18:34 localhost.localdomain kernel: [drm] kiq ring mec 2 pipe 1 q 0
May 08 20:18:34 localhost.localdomain kernel: [drm] VCN decode and encode
initialized successfully(under DPG Mode).
May 08 20:18:34 localhost.localdomain kernel: [drm] JPEG decode initialized
successfully.
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
gfx_0.0.0 uses VM inv eng 0 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.0.0 uses VM inv eng 1 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.1.0 uses VM inv eng 4 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.2.0 uses VM inv eng 5 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.3.0 uses VM inv eng 6 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.0.1 uses VM inv eng 7 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.1.1 uses VM inv eng 8 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.2.1 uses VM inv eng 9 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
comp_1.3.1 uses VM inv eng 10 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
kiq_2.1.0 uses VM inv eng 11 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
sdma0 uses VM inv eng 12 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
sdma1 uses VM inv eng 13 on hub 0
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
vcn_dec_0 uses VM inv eng 0 on hub 1
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
vcn_enc_0.0 uses VM inv eng 1 on hub 1
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
vcn_enc_0.1 uses VM inv eng 4 on hub 1
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: ring
jpeg_dec uses VM inv eng 5 on hub 1
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu:
recover vram bo from shadow start
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu:
recover vram bo from shadow done
May 08 20:18:34 localhost.localdomain kernel: [drm] Skip scheduling IBs!
May 08 20:18:34 localhost.localdomain kernel: [drm] Skip scheduling IBs!
May 08 20:18:34 localhost.localdomain kernel: amdgpu 0000:2d:00.0: amdgpu: GPU
reset(2) succeeded!
May 08 20:18:34 localhost.localdomain kernel: [drm] Skip scheduling IBs!
[ ... the previous line, but loads of times ]
May 08 20:18:34 localhost.localdomain kernel: [drm] Skip scheduling IBs!
May 08 20:18:34 localhost.localdomain kernel: amdgpu_cs_ioctl: 46 callbacks
suppressed
May 08 20:18:34 localhost.localdomain kernel: [drm:amdgpu_cs_ioctl [amdgpu]]
*ERROR* Failed to initialize parser -125!
[ ... the previous line, but loads of times. These are the '-125!' ones ]
May 08 20:18:44 localhost.localdomain kernel: [drm:amdgpu_cs_ioctl [amdgpu]]
*ERROR* Failed to initialize parser -125!
May 08 20:18:44 localhost.localdomain xembedsniproxy[1862]: Container window
visible, stack below
May 08 20:18:44 localhost.localdomain kernel: [drm:amdgpu_cs_ioctl [amdgpu]]
*ERROR* Failed to initialize parser -125!
One interesting detail/partial workaround is that underclocking the RAM speed
helps reduce it. Setting it to 2400 especifically (native speed of the 32GB of
ram is 3600) makes it happen much less often (still does happen though).
Another thing is that it might be somehow related to the GPU's built in audio
conflicting with intel's snd_hda_intel, which is part of a few other's logs
(sometimes appearing for me too). Audio is also choppy until a Pulse restart
with pulseaudio -k, which might be the cause for this first freeze with RAM at
2400. This may be unrelated though, and is just conjecture from my part.
Happy to help debug the issue if anyone can guide me through the process a bit.
Will also take a look at reporting this to the Mesa side too.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-08 19:23 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 [this message]
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
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-UFlBPnsu4J@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