This is a resend of an old bug report. This problem has never been fixed, and my message about it a year ago was just ignored. I noticed some recent activity with the TG3 driver in the 2.4.27 changelog and hoped that the problem was fixed. Nope - 2.4.27-pre2 is still broken in exactly the same way. Is anyone interested in fixing this problem, or will I have to keep reverting the tg3 driver back to the 2.4.21-pre4 version to use newer kernels? Incidently, there is also a compile error with tg3.c in 2.4.27-pre2 about the use of WARN_ON(). The original message that describes the problem is below. ---------------------------- The tg3.c driver in 2.4.21-pre5 through 2.4.21-rc6 has a problem with setting the MTU. After initially bringing the interface up with a MTU of 9000, or after changing the MTU setting, there is no RX activity until "ifconfig eth0 down; ifconfig eth0 up" is done. 2.4.21-pre4 and before do not have this problem. See the commands below for an illustration of the problem: modprobe tg3 ifconfig eth0 192.168.1.2 netmask 255.255.255.0 mtu 1500 up ping 192.168.1.1 (ok) ifconfig eth0 mtu 9000 ping 192.168.1.1 (no response) ifconfig eth0 down ifconfig eth0 up ping 192.168.1.1 (ok) ifconfig eth0 down modprobe -r tg3 modprobe tg3 ifconfig eth0 192.168.1.2 netmask 255.255.255.0 mtu 9000 up ping 192.168.1.1 (no response) ifconfig eth0 down ifconfig eth0 up ping 192.168.1.1 (ok) ifconfig eth0 mtu 1500 ping 192.168.1.1 (no response) ifconfig eth0 down ifconfig eth0 up ping 192.168.1.1 (ok) ---------------- 2.4.21-pre4 and before are ok. This is how they behave: modprobe tg3 ifconfig eth0 192.168.1.2 netmask 255.255.255.0 mtu 1500 up ping 192.168.1.1 (ok) ifconfig eth0 mtu 9000 ping 192.168.1.1 (ok) ifconfig eth0 down modprobe -r tg3 modprobe tg3 ifconfig eth0 192.168.1.2 netmask 255.255.255.0 mtu 9000 up ping 192.168.1.1 (ok) ifconfig eth0 mtu 1500 ping 192.168.1.1 (ok) The NIC I am using is a 3Com 3C996BT. Anthony J. Battersby Cybernetics - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
