From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tg3 and Netgear GA302T x 2 locks machine
Date: Sat, 05 Oct 2002 13:08:02 -0700 [thread overview]
Message-ID: <3D9F46A2.6050004@candelatech.com> (raw)
In-Reply-To: 20021004.181537.104336257.davem@redhat.com
David S. Miller wrote:
> Yes but are you running parallel pktgen streams on two
> tg3's? :-)
>
> Ben, by chance, does reverting the patch below cure your problems?
No, didn't fix it, maybe made it worse.
With pktgen: Locked up as soon as I started it (or less than .5 seconds afterwards).
With raw ethernet packets, sent from user-space, at around 40Mbps bi-directional,
I see loads of these messages:
tg3: eth3: Error, poll already scheduled
tg3: eth2: Error, poll already scheduled
tg3: eth2: Error, poll already scheduled
tg3: eth3: Error, poll already scheduled
tg3: eth3: Error, poll already scheduled
tg3: eth3: Error, poll already scheduled
tg3: eth3: Error, poll already scheduled
tg3: eth3: Error, poll already scheduled
...
After about 1 minute, the whole machine locked.
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-05 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 4:19 tg3 and Netgear GA302T x 2 locks machine Ben Greear
2002-10-04 5:06 ` Ben Greear
2002-10-04 15:52 ` James Morris
2002-10-05 5:50 ` Ben Greear
2002-10-04 21:24 ` David S. Miller
2002-10-05 1:20 ` James Morris
2002-10-05 1:15 ` David S. Miller
2002-10-05 6:03 ` Ben Greear
2002-10-05 20:08 ` Ben Greear [this message]
2002-10-06 4:23 ` David S. Miller
2002-10-06 4:58 ` Ben Greear
2002-10-05 2:01 ` Matthew N. Andrews
2002-10-05 5:47 ` Ben Greear
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=3D9F46A2.6050004@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.