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, 27 May 2022 11:22:24 +0000 [thread overview]
Message-ID: <bug-205089-2300-Fgg68R5KIX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205089
Luke A. Guest (laguest@archeia.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |laguest@archeia.com
--- Comment #42 from Luke A. Guest (laguest@archeia.com) ---
(In reply to MasterCATZ from comment #38)
> amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125
I'm getting the same with VLC hanging my machine, R9 390.
# uname -a
Linux rogue 5.18.0-gentoo-x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 26 15:51:54 BST
2022 x86_64 AMD FX(tm)-8350 Eight-Core Processor AuthenticAMD GNU/Linux
I updated my firmware and there are no binary differences between the old and
the new, they weren't updated others were; taken from git HEAD.
sys-kernel/linux-firmware
Available versions: 20210518^bstd 20210629^bstd 20210716^bstd
20210818^bstd 20210919^bstd 20211027^bstd 20211216^bstd 20220209^bstd
20220310^bstd 20220411^bstd 20220509^bstd (**)99999999*l^bstd {initramfs
+redistributable savedconfig unknown-license}
Installed versions: 99999999*l^bst(12:08:44 27/05/22)(redistributable
-initramfs -savedconfig -unknown-license)
Homepage:
https://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git
Description: Linux firmware files
I get this on using vlc:
[ 229.233581] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring uvd timeout,
signaled seq=3, emitted seq=5
[ 229.233720] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process pid 0 thread pid 0
[ 229.233825] amdgpu 0000:01:00.0: amdgpu: GPU reset begin!
[ 233.233843] amdgpu 0000:01:00.0: amdgpu: failed to suspend display audio
[ 234.612017] amdgpu: VI should always have 2 performance levels
[ 234.719098] amdgpu 0000:01:00.0: amdgpu: BACO reset
[ 235.160372] amdgpu 0000:01:00.0: amdgpu: GPU reset succeeded, trying to
resume
[ 235.160416] [drm] PCIE gen 2 link speeds already enabled
[ 235.161162] [drm] PCIE GART of 1024M enabled (table at 0x000000F4007E9000).
[ 235.161207] [drm] VRAM is lost due to GPU reset!
[ 235.163312] amdgpu 0000:01:00.0: amdgpu: SRBM_SOFT_RESET=0x00100040
[ 235.338304] [drm] UVD initialized successfully.
[ 235.459249] [drm] VCE initialized successfully.
[ 235.461738] amdgpu 0000:01:00.0: amdgpu: recover vram bo from shadow start
[ 235.461827] amdgpu 0000:01:00.0: amdgpu: recover vram bo from shadow done
[ 235.461867] [drm] Skip scheduling IBs!
[ 235.461869] [drm] Skip scheduling IBs!
[ 235.461890] amdgpu 0000:01:00.0: amdgpu: GPU reset(1) succeeded!
[ 235.461926] [drm] Skip scheduling IBs!
[ 235.461930] [drm] Skip scheduling IBs!
[ 235.461934] [drm] Skip scheduling IBs!
[ 235.461937] [drm] Skip scheduling IBs!
[ 235.461941] [drm] Skip scheduling IBs!
[ 235.461954] [drm] Skip scheduling IBs!
[ 235.461958] [drm] Skip scheduling IBs!
[ 235.461962] [drm] Skip scheduling IBs!
[ 235.461963] [drm] Skip scheduling IBs!
[ 235.461965] [drm] Skip scheduling IBs!
[ 235.461968] [drm] Skip scheduling IBs!
[ 235.461973] [drm] Skip scheduling IBs!
[ 235.461975] [drm] Skip scheduling IBs!
[ 235.461979] [drm] Skip scheduling IBs!
[ 235.461981] [drm] Skip scheduling IBs!
[ 235.461983] [drm] Skip scheduling IBs!
[ 235.461989] [drm] Skip scheduling IBs!
[ 235.461992] [drm] Skip scheduling IBs!
[ 235.461994] [drm] Skip scheduling IBs!
[ 235.461998] [drm] Skip scheduling IBs!
[ 235.462003] [drm] Skip scheduling IBs!
[ 235.461983] [drm:amdgpu_uvd_cs_pass2 [amdgpu]] *ERROR* Invalid UVD handle
0xdca40001!
[ 235.462198] amdgpu_cs_ioctl: 131 callbacks suppressed
[ 235.462201] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.462236] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.462260] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.462545] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.462569] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.462608] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.464578] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.464793] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.466719] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 235.466957] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
( REPEATS )
--
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-27 11:22 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 [this message]
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-Fgg68R5KIX@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).