Recent content by Stoiko Ivanov

This is most likely a different issue - discussed in: https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/post-871933 the post links to a test-kernel that should contain a fix for the issue (at least other users...

I've now added the SOLVED prefix as requested. If I'm not mistaken - this is the result of new(er) users having a shorter timeframe, where they can edit their own posts and threads - and this has simply expired for @toumz in this case. I hope this helps!

A test-kernel for another regression (in bnxt_en) just got uploaded to: http://download.proxmox.com/temp/kernel-7.0.14-22_bnxt-test1/ this should contain the current fix mentioned above - if you can - please test booting that kerne (without pcie_aspm=off) - and let us know if it works see...

Thanks for the tests! much appreciated! We had a report about kernel 7.0.14-20-pve and realtek nics in our bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=8110 @t.lamprecht reverted a few patches that seem relevant in...

sorry should have written explicit versions here - the version after 7.0.14-21-pve (as this was packaged before the reports) did anything from that boot make it to the journal, that might point to where the error is? else - upgrading pve-firmware and testing with the next kernel seems like a...

This should be fixed in the next version of proxmox-kernel - with: https://git.proxmox.com/?p=pve-kernel.git;a=commitdiff;h=9bf87de266b6edfc42703a9da80692188f6e2d46

Thanks for the test! so it seems reverting the 2 patches does not resolve the issue (and it's not related to our diff to mainline) :/ does the system have an Intel or AMD CPU (most reporters seem to have AMD)?

No - we don't sign such test-kernels - the kernel package is http://download.proxmox.com/temp/kernel-7.0.14-22~test-bnxt-revert1/proxmox-kernel-7.0.14-22-pve_7.0.14-22~test-bnxt-revert1_amd64.deb which contains everything, but is not signed and will not work if you have secure-boot enabled (but...

We built a test-kernel with bnxt_en changes reverted - see: https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/post-871722 for more details We'd appreciate feedback if it resolves the issue Thanks!

Your NIC does not use the bnxt_en driver (I overlooked that (as the second post mentioned bnxt) - so I think the issue is probaly unrelated. https://bugzilla.proxmox.com/show_bug.cgi?id=8110 - this issue was opened recently for realtek nic issues with 7.0.14-20 it would be great if you could...

we uploaded a kernel with the changes for bnxt between 7.0.14-19-pve and 7.0.14-20-pve reverted: http://download.proxmox.com/temp/kernel-7.0.14-22~test-bnxt-revert1/ It would be great if people experiencing the issues with bnxt_en nics could test this kernel - as it would help us in narrowing...

see https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/ for an issue that might be related. if possible try booting with `pci=notph` (see the linked thread for other tests) - thanks!

Thanks for the logs! could you try booting with `pci=notph` added to the command-line (might have a detrimental effect on performance) also - as most logs here (for the broadcom nics) look like the NICs are in a bond - which bond-mode is used? (the stanza from /etc/network/interfaces would help)

could you (and others affected): * share the journal from booting up the machine until the issue occurred * try disabling some offloading functionality: `ethtool -K <nic> rx-gro-hw off lro off`

Wurde seinerzeit nicht implementiert - koennte aber hinzugefuegt werden - bitte einen enhancement-request (auf Englisch) unter https://bugzilla.proxmox.com dafuer erstellen Danke!