On Wed, Mar 4, 2026 at 4:44 AM Timur Kristóf <[email protected]> wrote: > > On Wednesday, March 4, 2026 11:06:53 AM Central European Standard Time > Christian König wrote: > > > > > > 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. The DC code path just works bettter. So what if suspend is broken. I would much rather a working system. Hyprsunset for example doesn't work without DC. No idea why.
Speaking of suspend, the fixes for it are fairly trivial to backport to 6.12 as well. > > > > > > After a user reported to me that this causes issues for him with DC on > > > 6.17 > > > and older kernels, That was me. > > > 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. > > > > Hi Christian, > > > In theory Harry an Leo should take care of stuff like this > > I don't blame them for this. It is my fault for breaking it in the first > place, > and I didn't think there was any interest in using DC on older kernels. > > > pretty much everybody is overworked. > > Yeah. We all are. > > > > > 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. > > Thanks! Probably I should have sent the patches myself, then they already > would have had all the necessary tags. Sorry for the confusion. > > Now that the situation is cleared up, is there anything else we need to do for > these two patches here? Speaking of which, it's probably best to take over here. It's not fun dealing with stable. I also didn't author these patches. > > Best regards, > Timur > > >
