[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81bfc67a0911250606k1ec76354n217da9ca20b3517c@mail.gmail.com>
Date: Wed, 25 Nov 2009 09:06:30 -0500
From: Caleb Cushing <xenoterracide@...il.com>
To: Jarek Poplawski <jarkao2@...il.com>
Cc: Frans Pop <elendil@...net.nl>, Andi Kleen <andi@...stfloor.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
e1000-devel@...ts.sourceforge.net
Subject: Re: large packet loss take2 2.6.31.x
> Alas it's not all information I asked. E.g. "netstat -s before faulty
> kernel" and "netstat -s after faulty kernel" seem to be the same file:
> netstat_after.slave4.log.gz.
sorry I guess I misunderstood what you wanted? (or maybe I just dorked
it when I created all the files) I upped a netstat -s from a good
kernel shortly after reboot.
> Anyway, since there are problems with
> getting stats from the router we still can't compare them, or check
> for the dropped stats. (Btw, could you check for /proc/net/softnet_stat
> yet?)
router? good kernel? bad kernel?
> So, it might be the kernel problem you reported, but there is not
> enough data to prove it. Then my proposal is to try to repeat this
> problem in more "testing friendly" conditions - preferably against
> some other, more up-to-date linux box, if possible?
yeah 2.6.31.6 works on my laptop fine I'll just have to see about
getting a direct connection to it. probably do that after I bring the
other NIC back from home, on thanksgiving.
--
Caleb Cushing
http://xenoterracide.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists