Hi Matthias,

On Sun, Feb 23, 2025 at 04:59:34AM +0100, Matthias Babisch wrote:
> Moin Salvatore.
> 
> Am 21.02.25 um 08:11 schrieb Salvatore Bonaccorso:
> > Hi Matthias,
> > 
> > On Wed, Feb 19, 2025 at 01:40:35PM +0100, Matthias Babisch wrote:
> > > Package: src:linux
> > > Version: 6.1.124-1
> > > Severity: important
> > > File: linux-image-6.1.0
> > > X-Debbugs-Cc:m...@gosmooth.de
> > > 
> > > lspci on system affected
> > > root@takashi:~# lspci
> > > 0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote 
> > > Signal Processor (rev 01)
> > > 0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
> > > 2.5GbE Controller (rev 05)
> > > 0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote 
> > > Signal Processor (rev 01)
> > > 
> > > lspci on system not affected
> > > root@kiyoko:~# lspci
> > > 0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote 
> > > Signal Processor (rev 01)
> > > 0000:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
> > > 2.5GbE Controller (rev 05)
> > > 0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote 
> > > Signal Processor (rev 01)
> > > 0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
> > > 2.5GbE Controller (rev 05)
> > > 0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote 
> > > Signal Processor (rev 01)
> > > 
> > > System is unaffected if running older kernel. I have two systems. They 
> > > both
> > > work if running the older kernel, both don't when running the newer 
> > > kernel.
> > I think this is the same as 1098250 and 1095745.
> > 
> > See:https://lore.kernel.org/lkml/20250106100001.1344418-2-amad...@jmu.edu.cn/
> > 
> I see a strong similarity to 1098250. Lesser so to 1095745 and the patch.
> But it could very well be.
> 
> Its just way beyond my level of expertise ;o) Any idea when the patch is
> entering the debian kernel? I would gladly test a preliminary package if
> that helps. Thank you very much. Matthias Babisch

It needs first to land in mainline, from there it needs to be picked
for the supported stable series, at which point we can either
cherry-pick it it advance or flows in when we rebase it the respective
stable version.

So the first step is, having in mainline and the the Linux stable
maintainers queueing it for the stable series.

Regards,
Salvatore

Reply via email to