From: Beezly <beezly@beezly.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dropped packets on SUN GEM
Date: 13 Mar 2002 00:36:07 +0000 [thread overview]
Message-ID: <1015979767.2652.77.camel@monkey> (raw)
In-Reply-To: <20020312.161057.18308390.davem@redhat.com>
In-Reply-To: <1015976181.2652.30.camel@monkey> <20020312.155238.21594857.davem@redhat.com> <1015978127.2653.49.camel@monkey> <20020312.161057.18308390.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Hi David,
I *did* see the Pause is enabled message the other day, but I have only
seen it once. It hasn't been seen at all during tests today.
On Wed, 2002-03-13 at 00:10, David S. Miller wrote:
> You told me ealier that "sometimes pause is on, sometimes
> not". Today you told me "pause is not going on". Please,
> which is it? :)
>
> Do you have any manuals on the switch so we can check this
> out?
I've just checked the manual;
"Flow control is supported only on Gigabit Ethernet ports. It is enabled
or disabled as part of autonegotiation. If autonegotiation is set to
off, flow control is disabled. When autonegotiation is turned on, flow
control is enabled".
According to the switch, it's set up for autonegotiation and flow
control is set to "SYM";
Port Configuration Monitor Tue Mar 12 22:14:18
2002
Port Port Link Auto Speed Duplex Flow Ld Share
State Status Neg Cfg Actual Cfg Actual Ctrl Master
Pri Red
======================================================================== 50 ENABLED ACTIVE ON 1000 1000 AUTO FULL SYM
Sorry to be vague,
Cheers,
Beezly
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-03-13 0:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 23:11 Dropped packets on SUN GEM Beezly
2002-03-12 23:14 ` David S. Miller
2002-03-12 23:36 ` Beezly
2002-03-12 23:52 ` David S. Miller
2002-03-13 0:08 ` Beezly
2002-03-13 0:10 ` David S. Miller
2002-03-13 0:36 ` Beezly [this message]
2002-03-13 0:56 ` David S. Miller
2002-03-13 1:07 ` Beezly
2002-03-13 1:15 ` David S. Miller
2002-03-13 1:24 ` Beezly
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=1015979767.2652.77.camel@monkey \
--to=beezly@beezly.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox