netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: arno@natisbad.org
Cc: brian.haley@hp.com, netdev@vger.kernel.org
Subject: Re: E1000E/82567LM-3: link reported up too soon
Date: Mon, 20 Sep 2010 11:22:13 -0700 (PDT)	[thread overview]
Message-ID: <20100920.112213.42810338.davem@davemloft.net> (raw)
In-Reply-To: <87bp7vnnpj.fsf@small.ssi.corp>

From: arno@natisbad.org (Arnaud Ebalard)
Date: Sat, 18 Sep 2010 16:14:16 +0200

> Below, UMIP is configured w/o any additional delay before RS emission on
> that interface. No DHCP running either:
> 
> 15:40:22.984311 ethertype IPv6 (0x86dd), length 62: :: > ff02::2: ICMP6, router solicitation, length 8
> 15:40:26.984845 ethertype IPv6 (0x86dd), length 62: :: > ff02::2: ICMP6, router solicitation, length 8
> 15:40:26.989264 ethertype IPv6 (0x86dd), length 158: fe80::224:d5ff:fed4:476c > ff02::1: ICMP6, router advertisement
> 
> David, any idea on where this may come from and how to track the cause?

I have no context, what's the exact problem?

  reply	other threads:[~2010-09-20 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 13:48 E1000E/82567LM-3: link reported up too soon Arnaud Ebalard
2010-09-15 15:07 ` Brian Haley
2010-09-15 15:34   ` Arnaud Ebalard
2010-09-15 16:01     ` Brian Haley
2010-09-18 14:14       ` Arnaud Ebalard
2010-09-20 18:22         ` David Miller [this message]
2010-09-20 18:57           ` Arnaud Ebalard
2010-09-20 19:54             ` David Miller
2010-09-20 20:09               ` Arnaud Ebalard
2010-09-20 20:18                 ` David Miller
2010-09-20 20:22                   ` Arnaud Ebalard
2010-09-20 21:28                   ` Arnaud Ebalard
2010-09-20 22:23                     ` David Miller
2010-09-21 11:03                       ` Arnaud Ebalard

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=20100920.112213.42810338.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arno@natisbad.org \
    --cc=brian.haley@hp.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).