From: stephen mulcahy <smulcahy@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Ayaz Abdulla <aabdulla@nvidia.com>,
572201@bugs.debian.org
Subject: Re: forcedeth driver hangs under heavy load
Date: Mon, 12 Apr 2010 14:05:36 +0100 [thread overview]
Message-ID: <4BC31AA0.5070006@gmail.com> (raw)
In-Reply-To: <1271076426.16881.21.camel@edumazet-laptop>
Eric Dumazet wrote:
> Le lundi 12 avril 2010 à 13:39 +0100, stephen mulcahy a écrit :
> I am not sure I understand. Are you saying that using 2.6.30-2-amd64
> kernel also makes your forcedeth adapter being not functional ?
Hi Eric,
If I run my tests with the 2.6.30-2-amd64 kernel the network doesn't
malfunction.
If I run my tests with the 2.6.32-3-amd64 kernel the network does
malfunction.
If I take the forcedeth.ko module from the 2.6.30-2-amd64 kernel and
drop that into /lib/modules/2.6.32-3-amd64/kernel/drivers/net/ and then
reboot to 2.6.32-3-amd64 and rerun my tests - the network does malfunction.
> Are both way non functional (RX and TX), or only one side ?
Whats the best way of testing this? (tcpdump listening on both hosts and
then running pings between the systems?)
-stephen
next prev parent reply other threads:[~2010-04-12 13:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B9E6C60.7030300@atlanticlinux.ie>
[not found] ` <20100315182220.GQ2763@decadent.org.uk>
[not found] ` <4B9F5E5E.2060209@atlanticlinux.ie>
[not found] ` <1270393967.8341.11.camel@localhost>
[not found] ` <4BBCA19C.5080204@atlanticlinux.ie>
2010-04-10 23:36 ` forcedeth driver hangs under heavy load Ben Hutchings
2010-04-12 10:01 ` Bug#572201: " stephen mulcahy
2010-04-12 12:39 ` stephen mulcahy
2010-04-12 12:47 ` Eric Dumazet
2010-04-12 13:05 ` stephen mulcahy [this message]
2010-04-12 13:19 ` stephen mulcahy
2010-04-12 15:24 ` Eric Dumazet
2010-04-12 16:11 ` stephen mulcahy
2010-04-12 16:59 ` Eric Dumazet
2010-04-13 10:03 ` stephen mulcahy
2010-04-13 10:49 ` Eric Dumazet
2010-04-13 11:00 ` stephen mulcahy
2010-04-13 12:04 ` Ben Hutchings
2010-04-13 14:27 ` stephen mulcahy
2010-04-13 14:42 ` Eric Dumazet
2010-04-13 14:49 ` stephen mulcahy
2010-04-13 15:00 ` stephen mulcahy
2010-04-13 15:05 ` Eric Dumazet
2010-04-13 15:08 ` stephen mulcahy
2010-04-13 15:22 ` Eric Dumazet
2010-04-13 15:25 ` stephen mulcahy
2010-04-13 20:01 ` Eric Dumazet
2010-04-13 21:43 ` David Miller
2010-04-13 21:46 ` Eric Dumazet
2010-04-14 5:33 ` Bug#572201: " Ayaz Abdulla
2010-04-14 1:41 ` David Miller
2010-04-14 14:30 ` stephen mulcahy
2010-04-14 5:31 ` Bug#572201: [PATCH] forcedeth: fix tx limit2 flag check Ayaz Abdulla
2010-04-14 10:14 ` stephen mulcahy
2010-04-13 17:22 forcedeth driver hangs under heavy load Xose Vazquez Perez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC31AA0.5070006@gmail.com \
--to=smulcahy@gmail.com \
--cc=572201@bugs.debian.org \
--cc=aabdulla@nvidia.com \
--cc=ben@decadent.org.uk \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).