Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bernhard.kaindl@gmx.net
Cc: bruce.w.allan@intel.com, jeffrey.t.kirsher@intel.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH] Regression: e100_phy_init() isolates even selected PHY, causes 10 seconds boot delay
Date: Thu, 29 Oct 2009 06:02:39 -0700 (PDT)	[thread overview]
Message-ID: <20091029.060239.202729106.davem@davemloft.net> (raw)
In-Reply-To: <4AC3C09B.3040203@gmx.net>

From: Bernhard Kaindl <bernhard.kaindl@gmx.net>
Date: Wed, 30 Sep 2009 22:33:31 +0200

> The current e100.c:e100_phy_init() electrically isolates all
> the PHYs (even the selected PHY -- for a short time!) from the MII.
> 
> This happens only for a short duration before the isolation
> of the selected PHY is reverted, but it's enough to cause a
> major disturbance in the startup of our e100-based cards:
> 
> On a number of Embedded/Industry Pentium boards which are in use,
> the result is that the initial DHCP negotiation takes more
> than 10 seconds to complete with 2.6.30 and .31, while it's
> done in a fraction of a second with 2.6.29 and earlier
> (kernels tested with no delay range from 2.6.23 to 2.6.29)
> 
> That regression was introduced on March 31 in the by a patch
> from Bruce which first appeared in 2.6.30-rc3:

Bruce, can you give some feedback on this?  I'd like to see this issue
move forward.

The only reason I haven't applied Bernhard's patch is because I
haven't seen any feedback from Intel.  But I will apply it anyways if
I don't see reasonable feedback soon.

Thanks.

  reply	other threads:[~2009-10-29 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 20:33 [PATCH] Regression: e100_phy_init() isolates even selected PHY, causes 10 seconds boot delay Bernhard Kaindl
2009-10-29 13:02 ` David Miller [this message]
2009-10-29 13:19   ` Jeff Kirsher

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=20091029.060239.202729106.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bernhard.kaindl@gmx.net \
    --cc=bruce.w.allan@intel.com \
    --cc=jeffrey.t.kirsher@intel.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