Description of problem: VMware ESXI 6 with Intel I350 adapter fails to work after loading newer version of kernel. Log displays error message: NetworkManager[697]: <info> (eth2): link disconnected (deferring action for 4 seconds) kernel: igb 0000:13:00.0 eth2: Reset adapter NetworkManager[697]: <info> (eth2): link disconnected (calling deferred action) NetworkManager[697]: <info> (eth2): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] kernel: igb 0000:13:00.0 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Version-Release number of selected component (if applicable): Affected kernels: Kernel 4.2.3-300.fc23.x86_64 Kernel 4.2.3-200.fc22.x86_64 Last good kernel: Kernel 4.1.10-200.fc22.x86_64 How reproducible: Steps to Reproduce: 1. Boot to affected kernel. 2. 3. Actual results: Non working NIC Expected results: Working NIC Additional info:
Please attach the full output of dmesg from both a working and non-working boot.
Created attachment 1089827 [details] Working dmesg | more
I will add non-working when I can.
Created attachment 1090401 [details] NOT working dmesg - adapter keeps resetting.
Kernel 4.2.5-300.fc23.x86_64 not working.
Created attachment 1090973 [details] NOT working dmesg - adapter keeps resetting.
Kernel 4.2.6-300.fc23.x86_64 not working as well.
Kernel 4.2.7-300.fc23.x86_64 not working as well.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days