Re: linux-3.0.18+r8169+ipv4/tcp forwarding = tso/gso weirdness and performance degration
From: Timo Teras <hidden>
Date: 2012-03-18 07:01:32
On Sat, 17 Mar 2012 23:20:04 +0100 Francois Romieu [off-list ref] wrote:
Francois Romieu [off-list ref] : [...]quoted
quoted
Or as easy alternative, enabling the VPD bit in Config1 should allow me to read the EEPROM contents using the PCI /sys/.../vpd interface, right?In theory, yes. I have not tested it. Imho both access methods will be useful.I tried vpd and got the eeprom content, duplicated 256 times. The eeprom content is fairly boring: # ethtool -e 8169sc-1 Offset Values ------ ------ 0x0000 29 81 ec 10 67 81 ec 10 67 81 20 40 01 a1 00 e0 0x0010 4c 67 00 01 15 cd c2 f7 ff 80 ff ff ff ff ff 13 0x0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0030 ff ff fa d6 ff ff ff ff ff ff ff ff ff ff ff 20 0x0040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Ok. Thanks. I should be able to swap my broken box tomorrow or the day after, and then start doing expirements and compare the eeprom. I also found one more weirdly broken box. One of my similar boxes fails to LACP bonding with a HP ProCurve switches. The switch just says LACP failed, but linux thinks it's ok and starts aggregation, and this results in broken traffic for all flows using the link that was not accepted as part of the aggregation by the switch. To only explanation I've found so far is: the switch reports other link as MDI and the other as MDI-X. And this is enough to fail the aggregation (links are not identical), but the linux bonding does not notice this. I have no idea why the other link is MDI-X - it's a straight cable. I wonder if it could be eeprom related too... or maybe it's just another broken NIC. Oh well - I'll get back to this after few days when I have the broken box on my table for playing.