linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Kernel Developer List <linux-kernel@vger.kernel.org>
Subject: Re: e1000 with 82546EB parts on 2.4?
Date: Wed, 16 Jul 2003 09:26:43 -0700	[thread overview]
Message-ID: <20030716092643.B17580@one-eyed-alien.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0307150312250.32541@montezuma.mastecende.com>; from zwane@arm.linux.org.uk on Tue, Jul 15, 2003 at 03:13:31AM -0400

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

On Tue, Jul 15, 2003 at 03:13:31AM -0400, Zwane Mwaikambo wrote:
> On Tue, 15 Jul 2003, Matthew Dharm wrote:
> 
> > What I've got is your basic x86 machine with an Intel 82546EB dual-GigE
> > controller on a PCI bus.  I load e1000.o, ifconfig, and I'm running.  The
> > interface is solid as a rock, AFAICT.  I've left it running for days
> > without any problems.
> > 
> > However, if I ifdown and then ifup the interface, I'm borked.  Based on
> > tcpdump from another machine, the interface is definately transmitting
> > packets just fine.  But, it never seems to notice any packets on the
> > receive side.
> 
> Does unloading and reloading the module 'fix' things?

Only sometimes.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

I'm just trying to think of a way to say "up yours" without getting fired.
					-- Stef
User Friendly, 10/8/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2003-07-16 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  7:16 e1000 with 82546EB parts on 2.4? Matthew Dharm
2003-07-15  7:13 ` Zwane Mwaikambo
2003-07-16 16:26   ` Matthew Dharm [this message]

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=20030716092643.B17580@one-eyed-alien.net \
    --to=mdharm-kernel@one-eyed-alien.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@arm.linux.org.uk \
    /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).