netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Sven Anders <sven@anduras.de>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] e1000e: Fix usage under kexec
Date: Tue, 10 Nov 2009 10:35:37 +0100	[thread overview]
Message-ID: <87tyx2k9hy.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4AF87AB1.1070603@anduras.de> (Sven Anders's message of "Mon, 09 Nov 2009 21:25:21 +0100")

Sven Anders <sven@anduras.de> writes:
>
> We get the following error:
>   e1000e: probe of 0000:02:00.0 failed with error -2
>
> We cannot unload the driver of the first kernel, because it's
> compiled in statically.
>
> It's caused by the PHY, because it's already initialized by the
> first driver and therefore does not respond correctly. The driver
> assumes the PHY to be in 'reset' state, which is done by the BIOS.
>
> We fixed it by adding a
>
> +       /* Reset PHY before initializing it. Allows re-init after kexec. */
> +       if (!e1000_check_reset_block(hw))
> +         e1000_phy_hw_reset(hw);

The problem of resetting PHYs in the driver init path is that it tends
to lose link-state, and if the link takes some time to re-negotiate
you can significantly slow down the "total time to network access"
at boot.

Perhaps you could only reset when the message above would trigger
and try again?

-Andi

  reply	other threads:[~2009-11-10  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 20:25 [PATCH] e1000e: Fix usage under kexec Sven Anders
2009-11-10  9:35 ` Andi Kleen [this message]
2009-11-17  9:21 ` Stefan Assmann
2009-11-17 21:28   ` Tantilov, Emil S
2009-11-17 21:34   ` Tantilov, Emil S
2009-12-04  9:10     ` Sven Anders

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=87tyx2k9hy.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=netdev@vger.kernel.org \
    --cc=sven@anduras.de \
    /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).