* Herbert Xu (herbert@gondor.apana.org.au) wrote:
quoted text
> On Tue, Feb 03, 2009 at 04:23:45PM -0800, Chris Wright wrote:
> > I'm able to trigger the GSO checksum warning, and after 67fd1a73 "net: Add
> > debug info to track down GSO checksum bug" here's the more verbose output:
> > 
> > e1000e: caps=(0x1119a9, 0x0) len=2960 data_len=0 ip_summed=0
> > 
> > What info would be helpful for you (couple full backtraces below)?
> 
> Interesting.  Is this a Linux guest or a Window guest?

Windows guest.

quoted text
> If it's a Linux guest, it means that somewhere along the line
> the partial checksum got lost.  But I can't see anything obvious.
> Since you can reproduce this, could you add some printks along
> the path shown in the back trace to see where ip_summed gets
> zapped? So that would be tun and bridge basically.

Sure.

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html