From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: tg3 and machine lockup?
Date: Tue, 15 Jul 2003 22:07:40 -0700 [thread overview]
Message-ID: <3F14DD9C.9090807@candelatech.com> (raw)
I was running 2500 pps tx+rx on a 100bt port, with a tg3 in
the same machine. 1000 tcp connections, memory pressure, and
cpu was max'ed out.
I plugged in the tg3 to a e1000 (via cross-over cable), and then, or
very soon after that, the machine hung solid (or, maybe it tried
to spew to console..was on kvm and not selected..)
Last thing I see in the /var/log/messages is tg3 saying flow control
is on for tx and rx.
Now, it could be one of a million things...but just curious if anyone
else has seen anything like this. Kernel is 2.4.20 + my hacks.
Take it easy,
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 reply other threads:[~2003-07-16 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 5:07 Ben Greear [this message]
2003-07-16 5:08 ` tg3 and machine lockup? David S. Miller
2003-07-16 7:04 ` 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=3F14DD9C.9090807@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
/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).