FS#20543 - [kernel26] e1000e keeps changing MTU from 1500 to 1492
Attached to Project:
Arch Linux
Opened by jackoneill (jackoneill) - Friday, 20 August 2010, 20:59 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 18 June 2011, 15:22 GMT
Opened by jackoneill (jackoneill) - Friday, 20 August 2010, 20:59 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 18 June 2011, 15:22 GMT
|
Details
Description:
I plug in the ethernet cable, run '# ifconfig eth0 up' then '# dhcpcd eth0' then immediately 'ping google.com'. The first few pings go through, then the network connection dies. As soon as I run dhcpcd, dmesg shows: e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 1492 e1000e 0000:00:19.0: eth0: Reset adapter e1000e 0000:00:19.0: eth0: changing MTU from 1492 to 1500 e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO and so on... (full dmesg here: http://codepad.org/RlVUW9zl ) The 'Reset adapter' line is new, only appears with linux 2.6.35, but everything else happens exactly the same with every kernel since 2.6.30 (including 2.6.30). With every *-ARCH* kernel, that is, because neither ubuntu (9.10, linux 2.6.31) nor fedora (13, linux 2.6.33.3) are affected. I also tested a few older arch live cds: 2008.03 (linux 2.6.24) - unaffected 2008.06 (linux 2.6.25) - unaffected 2009.02 (linux 2.6.28) - unaffected 2009.08 (linux 2.6.30) IS affected, and 2010.05 (linux 2.6.33.4) also. I don't think the -ARCH patch could be responsible, because I experience this problem with kernel26-ice, which is (in my case anyway) basically vanilla with the tuxonice patch - it does not apply the -ARCH patch. A temporary fix is to set the mtu manually to the number from dmesg, in this case 1492: # ifconfig eth0 mtu 1492 This makes the connection usable, until the next reboot. There is at least one other arch user who can confirm this problem, and the fix as well. Oh yeah, almost forgot: 00:19.0 Ethernet controller: Intel Corporation 82562GT 10/100 Network Connection (rev 03) lspci -vvv here: http://codepad.org/ReBwG1JU |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Saturday, 18 June 2011, 15:22 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.39-1
Saturday, 18 June 2011, 15:22 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.39-1
Comment by Neferty (andor44) -
Friday, 20 August 2010, 21:09 GMT
Comment by jackoneill (jackoneill) -
Friday, 20 August 2010, 21:56 GMT
Comment by jackoneill (jackoneill) -
Sunday, 09 January 2011, 11:22 GMT
Comment by
Jelle van der Waa (jelly) - Sunday,
05 June 2011, 11:09 GMT
I can confirm this issue. It happens with my FS Amilo xi3650 as
well (Intel 82567LF Gigabit adapter). In my case, it likes to
stick to 576 MTU. 2.6.34-ARCH was affected, 2.6.35-ARCH is
affected too. dmesg has similar (if not the exact same, I cannot
confirm it for 100% as I'm writing from a different PC right now)
output.
Looks like this is in the wrong category, sorry about that...
I just tried exactly the same steps, except with dhclient instead
of dhcpcd. It works. No mtu-changing whatsoever and I have a
stable connection.
any update?