From: "André Detsch" <adetsch@br.ibm.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH] Fix link test for e1000 and e1000e when iface is down
Date: Fri, 13 Feb 2009 10:08:38 -0200 [thread overview]
Message-ID: <499562C6.3060001@br.ibm.com> (raw)
In-Reply-To: <9929d2390902121710q681f7143i16b5c98001279cc1@mail.gmail.com>
Jeff Kirsher wrote:
> I guess this comes down to what the definition of a Link test should
> be doing. My $0.02 is that it should be testing if the interface has
> a link, in which case if you ifdown the interface before running the
> Link test, I would expect it to fail.
>
> With this patch, if you bring down the device and run the ethtool diag
> tests, the Link test would come back as passing which is something I
> would not expect.
With the current code, e1000_reset is called during the test anyway, so
ethtool -t fails only the first time it is run (after ifconfig down). Is that
the expected behavior for the test?
# ifconfig eth0 up; ifconfig eth0 down; ethtool -t eth0
The test result is FAIL
The test extra info:
Register test (offline) 0
Eeprom test (offline) 0
Interrupt test (offline) 0
Loopback test (offline) 0
Link test (on/offline) 1
# ethtool -t eth0
The test result is PASS
The test extra info:
Register test (offline) 0
Eeprom test (offline) 0
Interrupt test (offline) 0
Loopback test (offline) 0
Link test (on/offline) 0
Thanks for the feedback.
--
André Detsch
Kernel Software Engineer
Linux Technology Center Brazil
next prev parent reply other threads:[~2009-02-13 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 16:35 [PATCH] Fix link test for e1000 and e1000e when iface is down Andre Detsch
2009-02-13 0:29 ` David Miller
2009-02-13 1:10 ` Jeff Kirsher
2009-02-13 1:17 ` David Miller
2009-02-13 12:08 ` André Detsch [this message]
2009-02-13 12:52 ` Jeff Kirsher
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=499562C6.3060001@br.ibm.com \
--to=adetsch@br.ibm.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).