Hi, On Mon, Feb 24, 2025 at 01:18:50PM +0100, Richard wrote: > Package: linux-image-amd64 > Version: 6.12.16-1 > Severity: normal > > Dear Maintainer, > > I'm not 100 % sure this is caused by the Kernel, but I'm convinced like 99 %. > For about two weeks I have issues with the networking on several of my > servers, mainly with mounting NFS shares. Mounting them works only on the > servers that are on Debian Stable, but the ones on Testing, and thus running > 6.12.x, have issues. I've now tried out to switch every server running > Testing and failing to mount their NFS share to the 6.13.4 Kernel found in > experimental, and for now it looks like this has fixed the issue. Though I > couldn't update it on one server running as a VM on a Xen hypervisor. When > trying to boot 6.13.4 on it, I can see in "xl console" this message: > > > Loading Linux 6.13-amd64 ... > error: not xen image. > Loading initial ramdisk ... > error: you need to load the kernel first. > > > so I need to select one of the installed 6.12.x Kernels. After successfull > boot, the first two messages that come up in the journal with priority > warning or higher are > > > Feb 24 13:01:18 kernel: Cannot find an available gap in the 32-bit address > range > Feb 24 13:01:18 kernel: PCI devices with unassigned 32-bit BARs may not work! > > > I'm not sure what these two lines refer to, so no idea if that's in > any way related or completely separate. But beyond that, I don't see > any anything on any of the servers that I was able to update, that > was in the logs before the update, but not afterwards. So sadly, > right now I can't really help with what has changed in one of the > 6.12.x versions that seems to have been fixed in 6.13. But it would > be great if whatever the fix is could be backported to 6.12.
Can you please test the most recent 6.12.y kernel available in Debian? (6.12.21-1), is the issue resolved there? If not, can you bisect the changes in upstream to see which commit fixes the issue? Regards, Salvatore
