All of lore.kernel.org
 help / color / mirror / Atom feed
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 01:07:14 +0000	[thread overview]
Message-ID: <1015981634.2652.82.camel@monkey> (raw)
In-Reply-To: <20020312.165609.18574402.davem@redhat.com>
In-Reply-To: <1015978127.2653.49.camel@monkey> <20020312.161057.18308390.davem@redhat.com> <1015979767.2652.77.camel@monkey>  <20020312.165609.18574402.davem@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Hi David,

On Wed, 2002-03-13 at 00:56, David S. Miller wrote:
> No problem.  If you add this patch below does it make Pause get
> negotiated on?  Please print everything the driver says from module
> load to the time the link comes up.

It doesn't appear to :(

sungem.c:v0.96 11/17/01 David S. Miller (davem@redhat.com)
PCI: Found IRQ 5 for device 00:0a.0
PCI: Sharing IRQ 5 with 00:0b.1
eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:00:00:00:00:00 
eth0: Link is up at 1000 Mbps, full-duplex.
eth0: Pause is disabled
eth0: PCS AutoNEG complete.
eth0: PCS link is now up.
eth0: Link is up at 1000 Mbps, full-duplex.
eth0: Pause is disabled
eth0: Link is up at 1000 Mbps, full-duplex.
eth0: Pause is disabled
eth0: Link is up at 1000 Mbps, full-duplex.
eth0: Pause is disabled

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-03-13  1:07 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
2002-03-13  0:56             ` David S. Miller
2002-03-13  1:07               ` Beezly [this message]
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=1015981634.2652.82.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 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.