Example error, ¿may happen on weird and complex routing schemes(citation needed for cause):
e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang
Possible solution, tested by Nazara:
Disable C-states:
for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 > $i; done
Example error, ¿may happen on weird and complex routing schemes(citation needed for cause):
e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang
Possible solution, tested by Nazara:
Disable C-states:
for i in /sys/devices/system/cpu/cpu*/cpuidle/state*/disable; do echo 1 > $i; done
Example error, ¿may happen on weird and complex routing schemes(citation needed for cause):
e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang
Possible solution, tested by Nazara:
Disable C-states:
for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 > $i; done
Most easily reproduced by sending a large amount of any traffic cross subnets on the same interface
(e.g. 10.1.1.2 > (eth0) x200 router (eth0) > 10.1.2.2)
The relevant part of the logs:
swiftgeek, can you submit a patch adding thisn to the docs