XPost: linux.debian.bugs.dist   
   From: ukleinek@debian.org   
      
   Control: tag -1 + moreinfo   
      
   On Tue, Jan 20, 2026 at 11:30:59PM +0200, Radostin Dimitrov wrote:   
   > Starting a "fresh" / cleaner mail loop, since it gets far longer and harder   
   > for everyone to track, hope you don't mind. Dunno what happened - but I did   
   > send requested logs, on the very same day they were requested. Attaching   
   > these once again.   
      
   The dmesg still has   
      
   	[    7.412563] nvidia: loading out-of-tree module taints kernel.   
      
   . Can you please blacklist this driver for further tests?   
      
   Looking at the code, there is:   
      
           /* read fwsm.ext_err_ind register and log errors */   
           fwsm = IXGBE_READ_REG(hw, IXGBE_FWSM(hw));   
      
           /* skip if E610's FW is reloading, warning in that case may be   
   misleading */   
           if (fwsm & IXGBE_FWSM_EXT_ERR_IND_MASK ||   
               (!(fwsm & IXGBE_FWSM_FW_VAL_BIT) && !(hw->mac.type ==   
   ixgbe_mac_e610)))   
                   e_dev_warn("Warning firmware error detected FWSM: 0x%08X\n",   
                              fwsm);   
      
   I think the diagnosis is wrong, the value read is 0xffffffff which in   
   other code locations is interpreted as IXGBE_FAILED_READ_REG.   
      
   Can you please:    
      
    a) check the issue also occurs without the nvidia (and other tainting   
       modules) loaded. Try adding `module_blacklist=nvidia` to the kernel   
       commandline. (If the problem doesn't reproduce without the nvidia   
       module, stop here. Then it seems the nvidia code is the culprit and   
       we cannot do anything for you.)   
      
    b) You wrote Debian 13 wasn't affected. Can you please install kernels   
       from https://snapshot.debian.org/ between 6.12 and 6.17 and check   
       which is the newest kernel still working and the oldest being   
       broken? Do the working kernels also report things like:   
      
   	[    0.265544] pci 0000:01:00.0: VF BAR 2 [mem size 0x10000000 64bit pref]:   
   can't assign; no space   
      
       ?   
      
   Best regards   
   Uwe   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmlw884ACgkQj4D7WH0S   
   /k5SUAgAmPp4mUiOrNytCq9lNXrIPv6ScLRO2maH4OGmnGyJZl3AsC5xvS78FBtO   
   qJYgVQdAzvxRVvBXO68ILe1Jm/UjEXhk7fOnJLAcm7nfdGwI3lDfO18jsK+w/s+B   
   hOIBUl2Nx40fvte5DVNbKBKugitWGS9ehTJrOLWFprQ532VFFonlZ3Ql/U+WByW2   
   vqsf7aTzzB4Pv36zHsK1bRezXBq/O169t3cB+iNbdg1TgYMpMb4joGLbvbZcgcGT   
   jrpXXI+oXAOu/Sr8n4/JpayjC7yqQBioNWjwd6GdLvl/qgPlgZEbaKEyqTDBOepz   
   inhyO9+Q3Ebakn/BZaIFsGJVlHrDRQ==   
   =EH+k   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)