All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 21 Sep 2010 13:03:10 +0200	[thread overview]
Message-ID: <87iq1z8ikx.fsf@small.ssi.corp> (raw)
In-Reply-To: <20100920.152352.193726412.davem@davemloft.net> (David Miller's message of "Mon, 20 Sep 2010 15:23:52 -0700 (PDT)")

Hi,

David Miller <davem@davemloft.net> writes:

> From: arno@natisbad.org (Arnaud Ebalard)
> Date: Mon, 20 Sep 2010 23:28:57 +0200
>
>> 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.
>
> I suspect the packet is sucessfully given to the chip and the PHY simply
> doesn't put it onto the wire for whatever reason.

I spent additional time on it, putting printk() at various locations in
e1000e driver code and also using driver's debug functions to see what
could be different in the internal state when the first packet is
delivered and when it is not. I just found nothing, so AFAICT your guess
above is backed up by those tests. 

I will try and summarize that for Intel ethernet drivers maintainers.

Cheers,

a+

      reply	other threads:[~2010-09-21 11:02 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
2010-09-20 22:23                     ` David Miller
2010-09-21 11:03                       ` Arnaud Ebalard [this message]

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=87iq1z8ikx.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.