From: Peter Colberg <pcolberg@redhat.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Ivan Lipski" <ivan.lipski@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
"Mario Limonciello (AMD)" <superm1@kernel.org>
Subject: Re: [REGRESSION] drm/amd/display: Add an hdmi_hpd_debounce_delay_ms module
Date: Wed, 28 Jan 2026 15:48:21 -0500 [thread overview]
Message-ID: <aXp2FRLJh-7Q6TxS@earendel> (raw)
In-Reply-To: <CADnq5_OqFEi_ML9zR-i_WFtFmBBQQcbQNRAiP8pVdD+prvEoiQ@mail.gmail.com>
On Wed, Jan 28, 2026 at 03:17:18PM -0500, Alex Deucher wrote:
> On Wed, Jan 28, 2026 at 3:09 PM Peter Colberg <pcolberg@redhat.com> wrote:
> >
> > Hi,
> >
> > I hit a regression introduced as part of v6.19-rc6 (and still present
> > in v6.19-rc7), where, upon unloading the amdgpu module, __flush_work()
> > is passed a work struct with the work function set to NULL. The issue
> > is seen with an AMD Radeon Pro W7900, but not an AMD Instinct MI210.
>
> I think this should be fixed in:
> https://gitlab.freedesktop.org/agd5f/linux/-/commit/17b2c526fd8026d8e0f4c0e7f94fc517e3901589
That fix applied to v6.19-rc7 does indeed resolve the issue.
Thank you for the pointer and apologies for the noise.
Peter
prev parent reply other threads:[~2026-01-28 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:09 [REGRESSION] drm/amd/display: Add an hdmi_hpd_debounce_delay_ms module Peter Colberg
2026-01-28 20:17 ` Alex Deucher
2026-01-28 20:48 ` Peter Colberg [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=aXp2FRLJh-7Q6TxS@earendel \
--to=pcolberg@redhat.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=ivan.lipski@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=superm1@kernel.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.