On Mon, 17 Apr 2006, David S. Miller wrote: > > From: Herbert Xu <[EMAIL PROTECTED]> > Date: Mon, 17 Apr 2006 16:17:00 +1000 > > > On Sun, Apr 16, 2006 at 10:32:03PM -0700, David S. Miller wrote: > > > So it nearly has to be a send side issue that can only trigger with > > > TSO enabled, and my next planned chore is to audit the TSO splitting > > > during ACK processing. We may be doing something stupid there. > > > > BTW, do we have a dmesg log from the machine that did this with tg3? > > I don't know, Jesse do you have it? > > Jesse, my previously lead was a dead end, we're looking into other > possibilities, so if you have the kernel log from reproducing this > BUG(!sk_forward_alloc) problem with tg3 it would be very valuable at > this point.
we explicitly enabled TSO before performing the test. attached bz2 due to size: Let me know if there is anything else I can do, Jesse
sk_alloc_forward_tg3_dmesg.bz2
Description: Binary data
