From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux.nics@intel.com
Cc: marcelo.tosatti@cyclades.com, jgarzik@pobox.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Problem with e1000 driver from kernel 2.4.23-pre6
Date: Thu, 9 Oct 2003 16:22:41 +0200 [thread overview]
Message-ID: <20031009162241.00e93abb.skraw@ithnet.com> (raw)
Hello,
I just found out that the e1000-driver included in the latest kernel
2.4.23-pre6 has a problem cooperating with keepalived. Keepalived uses netlink
to find out about interfaces being up or down. This works well with eepro100
driver from Don Becker (or tulip), but does not work at all with e1000.
Probably for the same reason mii-tool does not show anything useful either.
Is this fixable inside the e1000-driver? Should keepalived be fixed in any way?
Regards,
Stephan
next reply other threads:[~2003-10-09 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 14:22 Stephan von Krawczynski [this message]
2003-10-09 17:09 ` Problem with e1000 driver from kernel 2.4.23-pre6 Stephan von Krawczynski
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=20031009162241.00e93abb.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=marcelo.tosatti@cyclades.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