From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel" <e1000-devel@lists.sourceforge.net>
Subject: Re: 3.0.0rc6: ethtool not working without a cable
Date: Wed, 6 Jul 2011 18:57:21 +0200 [thread overview]
Message-ID: <201107061857.21206.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <1309971146.6217.0.camel@jbrandeb-mobl.amr.corp.intel.com>
On Wednesday 06 of July 2011, Brandeburg, Jesse wrote:
> On Wed, 2011-07-06 at 08:26 -0700, Ben Hutchings wrote:
> > On Wed, 2011-07-06 at 16:53 +0200, Arkadiusz Miskiewicz wrote:
> > > On Wednesday 06 of July 2011, Ben Hutchings wrote:
> > > > On Wed, 2011-07-06 at 13:38 +0200, Arkadiusz Miskiewicz wrote:
> > > > > 3.0.0rc6, thinkpad t400 notebook.
> > > > >
> > > > > If there is no cable then ethtool reports no device. It wasn't that
> > > > > before AFAIK.
> > > > >
> > > > > ethtool version 2.6.36
>
> snip
>
> > Then the only other explanation I can think of is that the driver has
> > 'detached' the device due to some kind of error. The ethtool core does
> > have a check for that.
>
> could it be that aspm is enabled
I have CONFIG_PCIEASPM=y
> or that you've enabled runtime power
> management?
In e1000e? no (unless it's default somehow).
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2011-07-06 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 11:38 3.0.0rc6: ethtool not working without a cable Arkadiusz Miskiewicz
2011-07-06 14:28 ` Ben Hutchings
2011-07-06 14:53 ` Arkadiusz Miskiewicz
2011-07-06 15:26 ` Ben Hutchings
2011-07-06 16:52 ` Brandeburg, Jesse
2011-07-06 16:57 ` Arkadiusz Miskiewicz [this message]
2011-07-07 16:47 ` Arkadiusz Miskiewicz
2011-07-07 17:03 ` Ben Hutchings
2011-07-20 17:53 ` Brandeburg, Jesse
2011-07-20 17:57 ` Arkadiusz Miskiewicz
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=201107061857.21206.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@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).