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 23:28:57 +0200 [thread overview]
Message-ID: <87aancqf3a.fsf@small.ssi.corp> (raw)
In-Reply-To: <20100920.131839.173838219.davem@davemloft.net> (David Miller's message of "Mon, 20 Sep 2010 13:18:39 -0700 (PDT)")
Hi,
David Miller <davem@davemloft•net> writes:
> From: arno@natisbad•org (Arnaud Ebalard)
> Date: Mon, 20 Sep 2010 22:09:16 +0200
>
>> The packets sent are an IPv6 Router Solicitation (to get IPv6 subnet
>> prefixes from the router) and a DHCP Request (to get an IPv4 address
>> from the DHCP server).
>>
>> The former is sent from the unspecified address (::) and the latter from
>> 0.0.0.0. The former is sent by UMIP Mobile IPv6 daemon. The second by my
>> DHCP client. They both use netlink to do that as soon as the link is up.
>> Both are for address configuration ...
>
> So do both DHCP request and the IPV6 RS get dropped, or just the IPV6 RS?
I added printk() to see where/if those first packets get dropped in
e1000e code. I followed those first packets to e1000_xmit_frame() and
don't see anything obvious happening there, i.e. they are passed to the
device as expected.
If I find some time tomorrow, I will try and take a look at
e1000_watchdog_task() and other functions that may perform asynchronous
tasks.
Cheers,
a+
next prev parent reply other threads:[~2010-09-20 21:28 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
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 [this message]
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=87aancqf3a.fsf@small.ssi.corp \
--to=arno@natisbad$(echo .)org \
--cc=brian.haley@hp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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