I use the e1000e kernel module with Linux 3.7.0: 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05) Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at f7400000 (32-bit, non-prefetchable) [size=128K] Memory at f7429000 (32-bit, non-prefetchable) [size=4K] I/O ports at f080 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e *** The problem is: everytime I turn off the router or change the ISP device (I recently changed the ISP from a cable modem to a ONT -- fiber) this link goes up and down many times: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO e1000e: eth0 NIC Link is Down e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO e1000e: eth0 NIC Link is Down And it stays doing that even if I turn everything off including the router. The strange is that I JUST changed my ISP. The router is exactly the same (TP-Link WDR4300). Before that everything was completely normal and I could connect to router using 100Mbps or even 1000Mbps full duplex without problem. What's my workaround? I did a: ethtool -t eth0 offline and the tests PASSED. After that I can connect just at 10 Mbps speed :( So, something is very wrong with this driver since I saw on Google LOTS and LOTS of users complaining. I can do any tests you want, compile things, apply patches, so just ask and I'll do my best to help. Any hints? Thanks!
I forgot to mention I had to disable autonegotiation so it can stay stable at 10 Mbps. Output from ethtool: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 2 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes
Forget it. I separate the cable from the others and now it's ok. Probably cable interference. thanks.
I reopened this because I was wrong and the problem remains. Anyone wants to comment or give a hint? Thanks.
Well, my workaround is to turn off (unplug from AC power) the TP-Link WDR4300, wait a few minutes and turn it on. Then e1000e will autonegotiate 1000 Mbps correctly. The question is: the problem is with the router or with the e1000e driver? Since many users are having the same problem, couldn't e1000e deal with it ia a better way?
Nobody?
This is a bug tracking system not a support forum. I would ask netdev@vger.kernel.org or the drvier maintainers at Intel.
(In reply to Alan from comment #6) > This is a bug tracking system not a support forum. I would ask > netdev@vger.kernel.org or the drvier maintainers at Intel. I am not asking for support. I thought it could be a bug. I asked in the e1000e list and the developer said Intel complies with the standard so it's a problem with the router. Anyway, it doesn't happen with Realtek, so better to buy motherboard with realtek chip instead of intel if someone wish to use with a TP-Link router. Anyway I'll mark it as INVALID. Thanks.
Ok cool - I wasn't sure if it had just been sitting there - and the "Nobody ?" question made me concerned. Alan
(In reply to Alan from comment #8) > Ok cool - I wasn't sure if it had just been sitting there - and the "Nobody > ?" question made me concerned. > > Alan No problem. Thanks for the feedback.