All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Rosen Penev" <rosenp@gmail.com>,
	"Christian König" <christian.koenig@amd.com>
Cc: Harry Wentland <harry.wentland@amd.com>,
	Leo Li <sunpeng.li@amd.com>,
	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Xinhui Pan <Xinhui.Pan@amd.com>, David Airlie <airlied@gmail.com>,
	Simona Vetter <simona@ffwll.ch>,
	Kenneth Feng <kenneth.feng@amd.com>,
	Alex Hung <alex.hung@amd.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lijo Lazar <lijo.lazar@amd.com>, "chr[]" <chris@rudorff.com>,
	Sasha Levin <sashal@kernel.org>, Wentao Liang <vulab@iscas.ac.cn>,
	"open list:AMD DISPLAY CORE" <amd-gfx@lists.freedesktop.org>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
	open list <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs
Date: Wed, 04 Mar 2026 10:09:19 +0100	[thread overview]
Message-ID: <2596902.XAFRqVoOGU@timur-hyperion> (raw)
In-Reply-To: <7d3a4090-06bf-40b0-8c80-ca08625608d7@amd.com>

On Wednesday, March 4, 2026 9:10:02 AM Central European Standard Time 
Christian König wrote:
> -stable +Greg
> 
> On 3/4/26 05:03, Rosen Penev wrote:
> > On Fri, Feb 27, 2026 at 8:54 PM Rosen Penev <rosenp@gmail.com> wrote:
> >> Because of incomplete backports to stable kernels, DC ended up breaking
> >> on older GCN 1 GPUs. This patchset adds the missing upstream commits to
> >> at least fix the panic/black screen on boot.
> >> 
> >> They are applicable to 6.12, 6.6, and 6.1 as those are the currently
> >> supported kernels that 7009e3af0474aca5f64262b3c72fb6e23b232f9b got
> >> backported to.
> >> 
> >> 6.1 needs two extra backports for these two commits to be cherry-picked
> >> cleanly. Those are
> >> 
> >> 96ce96f8773da4814622fd97e5226915a2c30706
> >> d09ef243035b75a6d403ebfeb7e87fa20d7e25c6
> >> 
> >> v2: Add Signed-off-by.
> > 
> > Do I need to resend?
> 
> Well first of all please stop sending those patches at all.
> 
> When you want something backported then add the CC: stable tag to the
> original patch.
> 
> If you find that some patch is already upstream which isn't correctly tagged
> then ping the relevant maintainers if that patch can be backported.
> 
> But don't send stuff to the stable list all by yourself.
> 
> Regards,
> Christian.

Hi Everyone,

The patches actually come from a branch of mine:
https://gitlab.freedesktop.org/Venemo/linux/-/commits/v6.12.74_si_dc_fixes

For context:

The crash comes from a patch that I wrote for 6.18 that fixes some issues on 
the default, non-DC code path, that was backported to stable kernels. DC was 
not the default code path before Linux 6.19, so I didn't mark the patches that 
also fix DC for backporting, because I had assumed nobody uses the DC code path 
on these kernel versions.

After a user reported to me that this causes issues for him with DC on 6.17 
and older kernels, I sent a backported series to Greg and Sasha, in an email 
thread with the subject line "Fixing an amdgpu crash caused by a backported 
patch". The fixes were backported to 6.17 then.

I assumed that the stable maintainers would backport the fixes to all older 
kernels that were also affected, but Rosen brought it to my attention that it 
didn't happen. So I made the backports in the above branch. Rosen then decided 
to send them to the mailing list.

Hope that helps clear up the situation.

Thanks & best regards,
Timur




  reply	other threads:[~2026-03-04  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28  4:53 [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs Rosen Penev
2026-02-28  4:53 ` [PATCHv2 for 6.112 and 6.6 1/2] drm/amd/display: Add pixel_clock to amd_pp_display_configuration Rosen Penev
2026-02-28  4:53 ` [PATCHv2 for 6.112 and 6.6 2/2] drm/amd/pm: Use pm_display_cfg in legacy DPM (v2) Rosen Penev
2026-03-04  4:03 ` [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs Rosen Penev
2026-03-04  8:10   ` Christian König
2026-03-04  9:09     ` Timur Kristóf [this message]
2026-03-04 10:06       ` Christian König
2026-03-04 12:44         ` Timur Kristóf
2026-03-04 22:23           ` Rosen Penev
2026-03-08 13:15             ` Timur Kristóf
2026-03-19 11:53               ` Greg Kroah-Hartman

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=2596902.XAFRqVoOGU@timur-hyperion \
    --to=timur.kristof@gmail.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=chris@rudorff.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harry.wentland@amd.com \
    --cc=kenneth.feng@amd.com \
    --cc=lijo.lazar@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --cc=sashal@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sunpeng.li@amd.com \
    --cc=vulab@iscas.ac.cn \
    /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.