On 3/4/26 10:09, Timur Kristóf wrote: > 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 <[email protected]> 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.
Yeah that indeed helped me to understand the situation, thanks. In theory Harry an Leo should take care of stuff like this, but pretty much everybody is overworked. In that case guys feel free to go ahead and ping the stable maintainers that something is missing. Just make sure that when a patch passes through your hands that you add a Signed-off-by tag. Regards, Christian. > > Thanks & best regards, > Timur > > >
