From: Petr Vorel <pvorel@suse.cz>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Uma Shankar <uma.shankar@intel.com>,
Jani Nikula <jani.nikula@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/i915/dmc: Use drm_WARN_ONCE()
Date: Thu, 16 Oct 2025 14:55:32 +0200 [thread overview]
Message-ID: <20251016125532.GA280868@pevik> (raw)
In-Reply-To: <aO_goOiwQwo41tQW@intel.com>
> On Wed, Oct 15, 2025 at 03:50:42PM +0200, Petr Vorel wrote:
> > assert_dmc_loaded() removed in 43175c92d4038 used drm_WARN_ONCE(),
> > but new assert_dmc_loaded() use drm_WARN().
> > Log is already noise quite a lot due loop over dmc->dmc_info[dmc_id]
> > array (76 logs on my machine), therefore use drm_WARN_ONCE().
> > Fixes: 43175c92d4038 ("drm/i915/dmc: Assert DMC is loaded harder")
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > Ville, am I wrong and it's really needed to see all the oops for the
> > threads?
> Kinda irrelevant because this should never happen. So the real
> question we need to ask is why are you seeing this at all?
+1
> Please file a bug at
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues
> and attch the full dmesg with drm.debug=0xe passed to the kernel
> cmdline.
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15153
Kind regards,
Petr
prev parent reply other threads:[~2025-10-16 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 13:50 [PATCH 1/1] drm/i915/dmc: Use drm_WARN_ONCE() Petr Vorel
2025-10-15 17:18 ` ✗ LGCI.VerificationFailed: failure for series starting with [1/1] " Patchwork
2025-10-15 17:57 ` [PATCH 1/1] " Ville Syrjälä
2025-10-16 12:55 ` Petr Vorel [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=20251016125532.GA280868@pevik \
--to=pvorel@suse.cz \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=simona@ffwll.ch \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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