All of lore.kernel.org
 help / color / mirror / Atom feed
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, 13 Mar 2022 17:46:15 +0000	[thread overview]
Message-ID: <bug-205089-2300-wO1uKnuZ0D@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205089-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205089

Christine Lemmer-Webber (cwebber@dustycloud.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cwebber@dustycloud.org

--- Comment #34 from Christine Lemmer-Webber (cwebber@dustycloud.org) ---
Hello,

I'm running a mostly stock upstream Linux kernel, 5.16.11 on Guix (using the
nonguix channel to get the upstream kernel).

  05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Device 164c (rev c1)
model name      : AMD Ryzen 7 5700U with Radeon Graphics

I've been hitting the same error ("[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
Failed to initialize parser -125!" as posted in the top of this thread) and it
can take out my whole desktop if using an accelerated compositor like Gnome
Shell.  Here's how to reproduce:

 - Open Blender 3.0
 - click the "New File -> 2D Animation" option from the splash screen
 - if it doesn't crash the first time, try it a few more times

Sometimes the desktop recovers, but often not.  If press ctrl-alt-f1 I see that
error being spit out repeatedly at the STTY.

If I'm running XFCE, it seems like similar issues happen in Blender in that it
stutters, etc, but it seems to make the screen go black for a second, then it's
able to recover.

Here's another way to trigger it: try opening a fresh scene and going to view
-> viewpoint -> camera.  Similarly, you might have to try this a few times. 
Strangely, the issue may be even worse: even on XFCE, Blender can't generally
recover in a usable way, I have to restart it.

Would love to see this fixed!  If I should open a new bug instead, let me know.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-03-13 17:46 UTC|newest]

Thread overview: 62+ 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 [this message]
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

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-wO1uKnuZ0D@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.