Skip to contentSkip to conversation

e1000 problems in 2.6.x

DISCUSSION Paul Blazejowski 2 participants 2 messages Feb 16, 2004 – Feb 17, 2004

lore
Share & tools
lore
#0 lore raw

Hi Steve,

I am experiencing same problem with e1000 on 2.6.3-rc2-mm1 and all previous 2.6 kernels with getting the transmit timed out messages.I do not get the transmission errors though.The same setup works fine on 2.4 kernel just like yours.

This happens on Slackware 9.1 on NFORCE2 based Gigabyte 7NNXP board with OEM Intel 1000MT builtin chip.

Have you found any solutions yet?

Regards,

Paul B.

#1 lore raw

Hi,

Quoted 4 lines

I am experiencing same problem with e1000 on 2.6.3-rc2-mm1 and all previous 2.6 kernels with getting the transmit timed out messages.I do not get the transmission errors though.The same setup works fine on 2.4 kernel just like yours.

We beat a recent 2.6 up with specweb on ppc64 and got the transmit timeout errors within about 30 seconds. Disabling TSO made the problem go away. (I actually hacked the driver forgetting we can do it via ethtool these days).

Scott: it smells like the TSO early write back issue, perhaps the new version of the fix isnt working properly. I need to verify that turning TSO on/off via ethtool has the same effect.

Anton