Bug#990279: Status?
----- Original Message -----
> From: "Salvatore Bonaccorso" <carnil@debian.org>
> To: "Timothy Pearson" <tpearson@raptorengineering.com>, "990279" <990279@bugs.debian.org>
> Cc: "Christian König" <christian.koenig@amd.com>, "Xi Ruoyao" <xry111@mengyan1223.wang>, "Alex Deucher"
> <alexander.deucher@amd.com>
> Sent: Tuesday, February 8, 2022 3:16:32 PM
> Subject: Re: Bug#990279: Status?
> Hi Timothy,
>
> On Tue, Feb 08, 2022 at 01:23:10PM -0600, Timothy Pearson wrote:
>> I can confirm Bullseye is still affected by this bug.
>>
>> Is there any chance of this fix being applied to the Bullseye stable
>> kernels? We're having to maintain kernel builds in our own
>> repositories to fix this regression, and that introduces some lag
>> when e.g. security updates are pushed to Debian.
>
> This needs someone to submit a (tested) backport patch to
> stable maintainers, so it can be applied in the 5.10.y stable series.
I can confirm the patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279#47 is what we're using and that it does work as intended.
If you need me to generate / submit a patch just let me know.
> Christian, would it be possible to do that? Cf.
> https://bugs.debian.org/990279#42 and
> https://bugs.debian.org/990279#52
>
> Regards,
> Salvatore
Reply to: