Re: E1000E/82567LM-3: link reported up too soon

Refresh

This website lore-kernel.gnuweeb.org/all/878w2wnsyd.fsf@small.ssi.corp/ is currently offline. Cloudflare\'s Always Online™ shows a snapshot of this web page from the Internet Archive\'s Wayback Machine. To check for the live version, click Refresh.

From: arno@natisbad.org (Arnaud Ebalard) To: David Miller <davem@davemloft.net> Cc: brian.haley@hp.com, netdev@vger.kernel.org Subject: Re: E1000E/82567LM-3: link reported up too soon Date: Mon, 20 Sep 2010 20:57:46 +0200 [thread overview] Message-ID: <878w2wnsyd.fsf@small.ssi.corp> (raw) In-Reply-To: <20100920.112213.42810338.davem@davemloft.net> (David Miller's message of "Mon, 20 Sep 2010 11:22:13 -0700 (PDT)") Hi, David Miller <davem@davemloft.net> writes: > 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? On some ethernet devices (at least), link may be reported up (NEWLINK received by userspace with flags indicating UP and RUNNING) before the interface is really usable. When sending packets as soon as the link is available, the first one may be dropped. That's what you see on the capture above. I think all the details are in the first message of the thread: http://www.spinics.net/lists/netdev/msg140916.html I started adding printk in net/core/dev.c and net/sched/sch_generic.c and I am now in e1000e code ... I will report what I found if it's interesting. Cheers, a+

next prev parent replyother threads:[~2010-09-20 18:57 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 2010-09-20 18:57 ` Arnaud Ebalard [this message] 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=878w2wnsyd.fsf@small.ssi.corp \ --to=arno@natisbad.org \ --cc=brian.haley@hp.com \ --cc=davem@davemloft.net \ --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