Document
e1000: eth0 NIC Link is Down

e1000: eth0 NIC Link is Down

In the log vmware.log , nothing special or at least nothing more than the previous log write in that ticket .I have compared le log from that machine

Related articles

Why FortiClient VPN is Not Connecting: Troubleshooting Guide 5 Best Cheap VPNs in India: Affordable Choices in 2024 Reliance Jio Cloud Gaming To Release Soon: Now Enjoy GTA 5 Without PC Diagrams Best VPNs for Roblox in 2024

In the log vmware.log , nothing special or at least nothing more than the previous log write in that ticket .

I have compared le log from that machine and another one ( his twin, machines are in cluster ) to see if there is something different. But the logs are identical ( I’m talking about log made during snapshot ).

On the machine itsef , I is see see log ” Kernel : e1000 : eth0 NIC Link is Down ” and then the machine trigger a Call trace regarding driver e1000 :

Apr 19 03:04:33 machine_name kernel: [24352097.784609] kworker/0:0     D ffff88013fc127c0     0  4695      2 0x00000000

Apr 19 03:04:33 machine_name kernel: [24352097.784617]  ffff880137ac3180 0000000000000046 ffff880100000000 ffffffff8160d020

Apr 19 03:04:33 machine_name kernel: [24352097.784624]  00000000000127c0 ffff880136c4dfd8 ffff880136c4dfd8 ffff880137ac3180

Apr 19 03:04:33 machine_name kernel: [24352097.784629]  ffff880139540c08 000000018110a61a 000000c0af981fcd 7fffffffffffffff

Apr 19 03:04:33 machine_name kernel: [24352097.784635] Call Trace:

Apr 19 03:04:33 machine_name kernel: [24352097.784683]  [<ffffffff813534e3>] ? schedule_timeout+0x2c/0xdb

Apr 19 03:04:33 machine_name kernel: [24352097.784709]  [<ffffffff8103817f>] ? set_next_entity+0x32/0x55

Apr 19 03:04:33 machine_name kernel: [24352097.784729]  [<ffffffff8100d02f>] ? load_TLS+0x7/0xa

Apr 19 03:04:33 machine_name kernel: [24352097.784743]  [<ffffffff8100d66d>] ? __switch_to+0x101/0x283

Apr 19 03:04:33 machine_name kernel: [24352097.784748]  [<ffffffff81353129>] ? wait_for_common+0xa0/0x119

Apr 19 03:04:33 machine_name kernel: [24352097.784757]  [<ffffffff8103f81d>] ? try_to_wake_up+0x197/0x197

Apr 19 03:04:33 machine_name kernel: [24352097.784775]  [<ffffffff8105b196>] ? wait_on_work+0xe6/0x11c

Apr 19 03:04:33 machine_name kernel: [24352097.784780]  [<ffffffff8105a7b8>] ? worker_set_flags+0x8f/0x8f

Apr 19 03:04:33 machine_name kernel: [24352097.784785]  [<ffffffff8105be3e>] ? __cancel_work_timer+0xb2/0xf4

Apr 19 03:04:33 machine_name kernel: [24352097.784804]  [<ffffffffa005c88a>] ? e1000_down_and_stop+0x2f/0x48 [e1000]

Apr 19 03:04:33 machine_name kernel: [24352097.784813]  [<ffffffffa005f1db>] ? e1000_down+0x108/0x15e [e1000]

Apr 19 03:04:33 machine_name kernel: [24352097.784822]  [<ffffffffa006137f>] ? e1000_reset_task+0x53/0x6c [e1000]

Apr 19 03:04:33 machine_name kernel: [24352097.784827]  [<ffffffff8105bac7>] ? process_one_work+0x179/0x299

Apr 19 03:04:33 machine_name kernel: [24352097.784832]  [<ffffffff8105caa8>] ? worker_thread+0xc2/0x145

Apr 19 03:04:33 machine_name kernel: [24352097.784836]  [<ffffffff8105c9e6>] ? manage_workers.isra.25+0x15b/0x15b

Apr 19 03:04:33 machine_name kernel: [24352097.784846]  [<ffffffff8105fbf1>] ? kthread+0x76/0x7e

Apr 19 03:04:33 machine_name kernel: [24352097.784862]  [<ffffffff8135b634>] ? kernel_thread_helper+0x4/0x10

Apr 19 03:04:33 machine_name kernel: [24352097.784868]  [<ffffffff8105fb7b>] ? kthread_worker_fn+0x139/0x139

Apr 19 03:04:33 machine_name kernel: [24352097.784874]  [<ffffffff8135b630>] ? gs_change+0x13/0x13

Apr 19 03:04:33 machine_name kernel: [24352097.785073] kworker/0:1     D ffff88013fc127c0     0 16493      2 0x00000000

Apr 19 03:04:33 machine_name kernel : [ 24352097.785078 ]   ffff880137de7100 0000000000000046 0000000000000000 ffffffff8160d020

Apr 19 03:04:33 machine_name kernel: [24352097.785084]  00000000000127c0 ffff88013af03fd8 ffff88013af03fd8 ffff880137de7100

Apr 19 03:04:33 machine_name kernel: [24352097.785089]  ffff88013fc0d500 00000001810419ed 0000000000000002 ffff88013763d000