public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>, linux-kernel@vger.kernel.org
Subject: Re: e1000/ICH8LAN weirdness - no ethtool link until initially forced up
Date: Tue, 07 Nov 2006 07:51:22 -0800	[thread overview]
Message-ID: <4550AB7A.10508@intel.com> (raw)
In-Reply-To: <20061107071449.GB21655@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
>> [Please CC me on responses].
>>
>> A spot of weirdness I ran into on my e1000 card.
>> It's the 82566DC model [8086:104b] (rev 02) x1 PCIe.
>>
>> After modprobe e1000, ethtool reports that there is no link, despite the
>> correct link lights on the port. This breaks booting during a boot process that
>> checks for actual link status before using a device.
> ...
>> This behavior differs from every other network card, and is also present in the
>> 7.3* version of the driver from sourceforge.
>>
>> I think the e1000 should try to raise the link during the probe, so that it
>> works properly, without having to set ifconfig ethX up first.
> 
> I think you should cc e1000 maintainers, and perhaps provide a patch....

I've read it and not come up with an answer due to some other issues at hand. E1000 
hardware works differently and this has been asked before, but the cards itself are in 
low power state when down. Changing this to bring up the link would make the card start 
to consume lots more power, which would automatically suck enormously for anyone using a 
laptop.

Unfortunately, we have no way to distinguish directly between mobile and non-mobile 
adapters, since they are usually the same.

Your application should really `ifconfig up` the device before checking for link.

Cheers,

Auke

  reply	other threads:[~2006-11-07 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  1:31 e1000/ICH8LAN weirdness - no ethtool link until initially forced up Robin H. Johnson
2006-11-07  7:14 ` Pavel Machek
2006-11-07 15:51   ` Auke Kok [this message]
2006-11-07 19:35     ` Theodore Tso
2006-11-08 15:59       ` Auke Kok
2006-11-07 21:31     ` Robin H. Johnson
2006-11-07 22:32       ` Auke Kok
2006-11-08  3:56         ` Robin H. Johnson
2006-11-08 12:04     ` Pavel Machek
2006-11-08 19:54       ` General network driver suspend/resume (was e1000 carrier related) Stephen Hemminger
2006-11-08 21:10         ` Auke Kok
2006-11-08 21:33           ` Stephen Hemminger

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=4550AB7A.10508@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robbat2@gentoo.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