All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Renan W. P." <renanwilliamprado@gmail.com>,
	rodrigo.vivi@intel.com, intel-gfx@lists.freedesktop.org, "Deak,
	Imre" <imre.deak@intel.com>
Subject: Re: A huge warning in dmesg pointing to drivers/gpu/drm/i915/display/intel_tc.c
Date: Thu, 15 Aug 2024 11:44:28 +0300	[thread overview]
Message-ID: <87wmkixjir.fsf@intel.com> (raw)
In-Reply-To: <2810b938-7df7-408e-9775-6f20d1694176@gmail.com>


[dropped a bunch of mailing lists and maintainers, added Imre]

On Thu, 15 Aug 2024, "Renan W. P." <renanwilliamprado@gmail.com> wrote:
> [2.] Full description of the problem/report:
>
> I can't identify any factual problems beyond a warning in dmesg triggered at every boot, i.e., I have seen no features affected. The dmesg output is located in the log files in the attachment.
> I am facing this warning in LENOVO 82MG/LNVNB161216, BIOS H4CN35WW(V2.04) 04/12/2024 (Lenovo Ganing 3i). I have tried two new kernel versions fromwww.kernel.org  site, the Kernel 6.10.5 and 6.1.105.
> Additionally, I have used Debian at least since kernel version 6.1.22. All kernels present warnings in the same file with slightly different outputs in dmesg. I am compiling the kernel with the config-6.1.105 file in the attachment.

Unless Imre has some obvious ideas what the problem is, please file the
bug report at freedesktop.org gitlab as described in [1]. While the
detail in your report here is great, I'm afraid it's just going to be
completely forgotten on the mailing list.

Thanks,
Jani.


[1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html



-- 
Jani Nikula, Intel

  reply	other threads:[~2024-08-15  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  5:45 A huge warning in dmesg pointing to drivers/gpu/drm/i915/display/intel_tc.c Renan W. P.
2024-08-15  8:44 ` Jani Nikula [this message]
2024-08-15 11:33 ` Imre Deak
2024-08-15 15:52   ` Renan W. P.

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=87wmkixjir.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=renanwilliamprado@gmail.com \
    --cc=rodrigo.vivi@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 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.