Latest working kernel version: ?? Earliest failing kernel version: ?? Distribution: ubuntu 8.04 Hardware Environment: many built-in sis 191 Software Environment: linux Problem Description: incorrect MTU size. Command 'ifconfig eth0' show MTU:1500, but network failed with packet large more than 1024. Modifying the mtu of the ethernet interface to 1024 with command 'ifconfig eth0 mtu 1024' make it to work. Steps to reproduce:
Hmm here I have the bug but it works fine up to 1496
Same for me, 1496 is the highest value. Tested on 2.6.31.6, fedora-based
Are you using vlans ?
No
During the attemptions to ping or other actions, which mean the adoption of the package with the MTU size of interface (1500), the frame isn't accepted and there is an increasing of value error and frame by one in ifconfig output. By practical consideration was cleared up, that 4 last bytes aren't able to get throught, as the maximum size of delivered ip package can't be more than 1496 bytes (from 1500 supposed to be), and accordingly to it, the size of the ethernet frame can't be more than 1510 (from 1514 supposed to be) bytes.The tests of this hardware in the alternative operating system (windows 7) have shown us the positive result and pointed on the correct work of hardware and the communication medium. System: Ubuntu Karmic 9.10 amd64 Kernel: 2.6.31-20-generic Hardware: Laptop Asus F5SL Network Adapter: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02): 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02) Subsystem: ASUSTeK Computer Inc. Device 1815 Flags: bus master, medium devsel, latency 0, IRQ 19 Memory at fddfcc00 (32-bit, non-prefetchable) [size=128] I/O ports at cc00 [size=128] Capabilities: <access denied> Kernel driver in use: sis190 Kernel modules: sis190 ps. On 32-bit kernel everything works fine. pps. May be related: http://bugzilla.kernel.org/show_bug.cgi?id=11509
This seems the same as Bug 10694
*** Bug 13862 has been marked as a duplicate of this bug. ***
*** Bug 43731 has been marked as a duplicate of this bug. ***
Shame, that we could not find the problem.But I am sure that bug still there