It seems that you are experiencing
network disconnection issues with your Proxmox 8.4.1 server running on a Dell PowerEdge T310, using a
NetXtreme NIC. This is a common issue, especially with older Broadcom NICs (like the NetXtreme), and can often be traced to driver or power management problems.
Here are
troubleshooting steps and solutions you can try:
1.
Run the following command after a disconnection or after reboot:
journalctl -xe
Or check kernel logs:
dmesg | grep -i eth
Look for lines that mention:
- eth0: Link is Down
- bnx2, tg3, or bnx2x errors (Broadcom driver names)
- IRQ or DMA issues
2.
Run:
lspci -nnk | grep -A3 -i net
This shows:
- The exact model of the NIC
- The driver in use (tg3, bnx2, etc.)
3.
Sometimes the NIC goes to sleep and fails to wake.
Add this to your boot kernel parameters:
pcie_aspm=off
Edit /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"
Then update GRUB and reboot:
update-grub
reboot
4.
Sometimes the NIC driver needs proprietary firmware to function correctly.
Run:
apt install firmware-bnx2 firmware-linux-nonfree
Then reboot.
5.
The NIC might be losing link due to negotiation failure.
Try forcing speed/duplex:
ethtool -s eth0 speed 1000 duplex full autoneg off
(Replace eth0 with your actual interface name, e.g., enp3s0)
To make permanent, create a systemd .link or use ifupdown configs.
6.
Broadcom NetXtreme cards are known for these issues. Consider:
- Adding a cheap Intel PRO/1000 PCIe NIC
- Disabling onboard Broadcom in BIOS
7.
Boot Ubuntu live or Debian live ISO.
- If the same NIC loses connection, it’s likely hardware or firmware.
- If stable, it may be a Proxmox driver or config issue.
8.
Enable persistent journaling to catch logs even after reboot:
mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal
systemctl restart systemd-journald
Would you like to share:
- The output of lspci -nnk | grep -A3 -i net?
- The output of dmesg | grep -i bnx or tg3?
That will help identify if it's driver-related.
