e1000 driver hang

Code: 
  GNU nano 7.2                                                                                  interfaces                                                                                           
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp0s25 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.***.***.***/24
        gateway 192.***.***.*
        bridge-ports enp0s25
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

So in my case it is enp0s25 or vmbr0? And where to place the line?

Thank you for the help - I hope the best to have proxmox high available again.
 
  • Like
Reactions: golfreeze
Gorki said:
Code: 
  GNU nano 7.2                                                                                  interfaces                                                                                         
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp0s25 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.***.***.***/24
        gateway 192.***.***.*
        bridge-ports enp0s25
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

So in my case it is enp0s25 or vmbr0? And where to place the line?

Thank you for the help - I hope the best to have proxmox high available again.
Click to expand...
Correct your iface is: enp0s25

here is what my interfaces file looks like:
----------------------------------------------------------------------------------------------------------------------------



auto lo
iface lo inet loopback

iface eno1 inet manual
post-up ethtool -K eno1 gso off tso off rxvlan off txvlan off gro off tx off rx off sg off

auto vmbr0
iface vmbr0 inet static
address 192.168.0.2/24
gateway 192.168.0.1
bridge-ports eno1
bridge-stp off
bridge-fd 0


source /etc/network/interfaces.d/*

----------------------------------------------------------------------------------------------------------------------------

Hope this helps you.
I am new to Proxmox also only been running it for a few months.
But I have been using VMware ESXi since it was called GSX in the early 2000's

Have a great day!
 
  • Like
Reactions: golfreeze and Gorki
"Same" Problem using kernel Proxmox VE GNU/Linux, with Linux 6.8.12-9-pve after monthly update, network unavailable and syslog loop of :
Code: 
2025-04-01T04:19:44.099279+02:00 kernel: [ 7197.924206] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
2025-04-01T04:19:44.099300+02:00 kernel: [ 7197.924206]   TDH                  <ce>
2025-04-01T04:19:44.099303+02:00 kernel: [ 7197.924206]   TDT                  <e2>
2025-04-01T04:19:44.099304+02:00 kernel: [ 7197.924206]   next_to_use          <e2>
2025-04-01T04:19:44.099304+02:00 kernel: [ 7197.924206]   next_to_clean        <cd>
2025-04-01T04:19:44.099306+02:00 kernel: [ 7197.924206] buffer_info[next_to_clean]:
2025-04-01T04:19:44.099308+02:00 kernel: [ 7197.924206]   time_stamp           <1006936fb>
2025-04-01T04:19:44.099309+02:00 kernel: [ 7197.924206]   next_to_watch        <ce>
2025-04-01T04:19:44.099310+02:00 kernel: [ 7197.924206]   jiffies              <100694041>
2025-04-01T04:19:44.099311+02:00 kernel: [ 7197.924206]   next_to_watch.status <0>
2025-04-01T04:19:44.099312+02:00 kernel: [ 7197.924206] MAC Status             <40080083>
2025-04-01T04:19:44.099313+02:00 kernel: [ 7197.924206] PHY Status             <796d>
2025-04-01T04:19:44.099315+02:00 kernel: [ 7197.924206] PHY 1000BASE-T Status  <3800>
2025-04-01T04:19:44.099316+02:00 kernel: [ 7197.924206] PHY Extended Status    <3000>
2025-04-01T04:19:44.099317+02:00 kernel: [ 7197.924206] PCI Status             <10>

Back to kernel Proxmox VE GNU/Linux, with Linux 6.8.12-8-pve (before the next crash) using:
Code: 
# Set in /etc/default/grub
GRUB_DEFAULT="Advanced options for Proxmox VE GNU/Linux>Proxmox VE GNU/Linux, with Linux 6.8.12-8-pve"

# Update  grub
PATH=$PATH:/usr/sbin
update-grub

# Reboot to apply
systemctl reboot
 
  • Like
Reactions: leandrosgf and OrionNE
manusfreedom said:
"Same" Problem using kernel Proxmox VE GNU/Linux, with Linux 6.8.12-9-pve after monthly update, network unavailable and syslog loop of :
Code: 
2025-04-01T04:19:44.099279+02:00 kernel: [ 7197.924206] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
2025-04-01T04:19:44.099300+02:00 kernel: [ 7197.924206]   TDH                  <ce>
2025-04-01T04:19:44.099303+02:00 kernel: [ 7197.924206]   TDT                  <e2>
2025-04-01T04:19:44.099304+02:00 kernel: [ 7197.924206]   next_to_use          <e2>
2025-04-01T04:19:44.099304+02:00 kernel: [ 7197.924206]   next_to_clean        <cd>
2025-04-01T04:19:44.099306+02:00 kernel: [ 7197.924206] buffer_info[next_to_clean]:
2025-04-01T04:19:44.099308+02:00 kernel: [ 7197.924206]   time_stamp           <1006936fb>
2025-04-01T04:19:44.099309+02:00 kernel: [ 7197.924206]   next_to_watch        <ce>
2025-04-01T04:19:44.099310+02:00 kernel: [ 7197.924206]   jiffies              <100694041>
2025-04-01T04:19:44.099311+02:00 kernel: [ 7197.924206]   next_to_watch.status <0>
2025-04-01T04:19:44.099312+02:00 kernel: [ 7197.924206] MAC Status             <40080083>
2025-04-01T04:19:44.099313+02:00 kernel: [ 7197.924206] PHY Status             <796d>
2025-04-01T04:19:44.099315+02:00 kernel: [ 7197.924206] PHY 1000BASE-T Status  <3800>
2025-04-01T04:19:44.099316+02:00 kernel: [ 7197.924206] PHY Extended Status    <3000>
2025-04-01T04:19:44.099317+02:00 kernel: [ 7197.924206] PCI Status             <10>

Back to kernel Proxmox VE GNU/Linux, with Linux 6.8.12-8-pve (before the next crash) using:
Code: 
# Set in /etc/default/grub
GRUB_DEFAULT="Advanced options for Proxmox VE GNU/Linux>Proxmox VE GNU/Linux, with Linux 6.8.12-8-pve"

# Update  grub
PATH=$PATH:/usr/sbin
update-grub

# Reboot to apply
systemctl reboot
Click to expand...
That is a good quick fix. Hopefully next kernel update will fix issue. I am on the fence on setting the nic setting back as it has not caused any issues for me with new settings. We shall see. Thanks for posting and confirming that rolling back a kernel resolved your issue.

-thx
 
Last edited:
You must log in or register to reply here.
Top Bottom