archive mirror
 help / color / mirror / Atom feed
From: Matthew Dharm <>
To: Kernel Developer List <>
Subject: e1000 with 82546EB parts on 2.4?
Date: Tue, 15 Jul 2003 00:16:55 -0700	[thread overview]
Message-ID: <> (raw)

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

I'm working with some hardware that may or may not be completely reliable,
and trying to figure out if something I'm seeing is a 'known issue' or
something strange about my setup (which is entirely possible).

I'm using 2.4.20 with some custom hardware.

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.

Has anyone seen anything like this before?


Matthew Dharm                              Home: 
Maintainer, Linux USB Mass Storage Driver

A:  The most ironic oxymoron wins ...
DP: "Microsoft Works"
A:  Uh, okay, you win.
					-- A.J. & Dust Puppy
User Friendly, 1/18/1998

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

             reply	other threads:[~2003-07-15  7:02 UTC|newest]

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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).