dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 219895] amdgpu spamming log [drm] scheduler comp_1.0.1 is not ready, skipping and becoming slow
Date: Tue, 22 Jul 2025 22:58:00 +0000	[thread overview]
Message-ID: <bug-219895-2300-QsCw5qdQJA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219895-2300@https.bugzilla.kernel.org/>

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

kolAflash (kolAflash@kolahilft.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kolAflash@kolahilft.de

--- Comment #3 from kolAflash (kolAflash@kolahilft.de) ---
FTR, here's the follow up:

After waking from sleep, log spam of "[drm] scheduler comp_1.0.n is not ready,
skipping" after "WARNING: CPU: 12 PID: 11871 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:100
generic_reg_update_ex+0x1d2/0x290 [amdgpu]"
https://gitlab.freedesktop.org/drm/amd/-/issues/3911#note_2941418

-- 
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:[~2025-07-22 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19  0:38 [Bug 219895] New: amdgpu spamming log [drm] scheduler comp_1.0.1 is not ready, skipping and becoming slow bugzilla-daemon
2025-03-19  0:41 ` [Bug 219895] " bugzilla-daemon
2025-03-20  8:34 ` bugzilla-daemon
2025-07-22 22:58 ` 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-219895-2300-QsCw5qdQJA@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).