that "tcp_v4_rechecksum" thing

[Phil Blundell <pb@nexus.co.uk>]

Did anybody ever really get to the bottom of that problem with TCP
checksums in 2.2?  I just noticed that elara and europa, running a
2.2.19 build from back in April, are both spewing out large numbers of
these debug messages, which might account for the poor network
performance that we're seeing on those machines.  (The amusing thing is
that most of the "old" checksum values look more like kernel pointers
than actual checksums.)

tcp_v4_rechecksum: c29a4510 => f5be936d
tcp_v4_rechecksum: c29a4110 => 9e64904b
tcp_v4_rechecksum: c29a4d10 => 9ec21e00
tcp_v4_rechecksum: a2967359 => 98647d8b
tcp_v4_rechecksum: c29a4710 => ba338715
tcp_v4_rechecksum: 6e86feae => 611d0c18
tcp_v4_rechecksum: c29a4510 => 73b5b42e
tcp_v4_rechecksum: c29a4b10 => c2af117d

FWIW, medusa is back on 2.2.13 or something; it shows some of these
messages too, but apparently less often.  And this time, most of the
numbers are identical in the "before" and "after" case:

tcp_v4_rechecksum: 0 => 0
tcp_v4_rechecksum: 0 => 0
tcp_v4_rechecksum: 0 => 0
tcp_v4_rechecksum: 0 => 0
tcp_v4_rechecksum: 0 => 0
tcp_v4_rechecksum: 3aa8dc8e => 3aa8dc8e
tcp_v4_rechecksum: ab340fb3 => ab340fb3
tcp_v4_rechecksum: 90dd61d7 => 90dd61d7
tcp_v4_rechecksum: 90dd61d7 => 90dd61d7
tcp_v4_rechecksum: 90dd61d7 => 90dd61d7
tcp_v4_rechecksum: cc9d6d4d => cc9d6d4d
tcp_v4_rechecksum: cc9d6d4d => cc9d6d4d

So, what's to be done - any suggestions?  I'd rather not upgrade to a
2.4 kernel at the moment.

Anyone else on debian-arm seeing this kind of effect?

p.