From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
Date: Thu, 15 Feb 2024 06:59:46 +0100 [thread overview]
Message-ID: <e65c6dc4-9b43-4c97-bb4c-d9c14655835d@leemhuis.info> (raw)
In-Reply-To: <ZbUB0YWxEET3Y0xA@eldamar.lan>
On 27.01.24 14:14, Salvatore Bonaccorso wrote:
>
> In Debian (https://bugs.debian.org/1061449) we got the following
> quotred report:
>
> On Wed, Jan 24, 2024 at 07:38:16PM +0100, Patrice Duroux wrote:
>> Package: src:linux
>> Version: 6.7.1-1~exp1
>> Severity: normal
>>
>> Giving a try to 6.7, here is a message extracted from dmesg:
>>
>> [ 4.177226] ------------[ cut here ]------------
>> [ 4.177227] WARNING: CPU: 6 PID: 248 at
>> drivers/gpu/drm/amd/amdgpu/../display/dc/link/link_factory.c:387
>> construct_phy+0xb26/0xd60 [amdgpu]
>
> Analysis showed that this appears to be a regression from b17ef04bf3a4
> ("drm/amd/display: Pass pwrseq inst for backlight and ABM"). Does that
> ring some bells?
>
> See: https://bugs.debian.org/1061449#27
>
> #regzbot introduced: b17ef04bf3a4
> #regzbot link: https://bugs.debian.org/1061449
> #regzbot title: Regression by b17ef04bf3a4 ("drm/amd/display: Pass pwrseq inst for backlight and ABM")
#regzbot monitor:
https://lore.kernel.org/amd-gfx/20240214184006.1356137-8-Rodrigo.Siqueira@amd.com/
#regzbot fix: drm/amd/display: Only allow dig mapping to pwrseq in new asic
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2024-02-15 5:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170612149675.7169.757906919183146487.reportbug@kos-moceratops.home>
2024-01-27 13:14 ` Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu Salvatore Bonaccorso
2024-01-27 13:14 ` Salvatore Bonaccorso
2024-01-28 10:44 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-28 10:44 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-28 11:09 ` Bug#1061449: Info received (Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu) Debian Bug Tracking System
2024-01-30 7:03 ` Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu Salvatore Bonaccorso
2024-01-30 7:03 ` Salvatore Bonaccorso
2024-02-15 5:59 ` Linux regression tracking #update (Thorsten Leemhuis) [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=e65c6dc4-9b43-4c97-bb4c-d9c14655835d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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.