All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: andi@firstfloor.org
Cc: romieu@fr.zoreil.com, netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Current git r8169 driver often misses link at boot
Date: Tue, 21 Oct 2008 16:45:36 -0700 (PDT)	[thread overview]
Message-ID: <20081021.164536.219372605.davem@davemloft.net> (raw)
In-Reply-To: <20081021235011.GL12825@one.firstfloor.org>

From: Andi Kleen <andi@firstfloor.org>
Date: Wed, 22 Oct 2008 01:50:11 +0200

> On Tue, Oct 21, 2008 at 10:26:01PM +0200, Francois Romieu wrote:
> > Andi Kleen <andi@firstfloor.org> :
> > [...]
> > > I have a nfsroot test system with a r8169 NIC. Since I updated
> > > from 2.6.27 to 2.6.27-git10 it doesn't find its root fs in 2 out of
> > > 3 boots. The r8169 gets detected, but there is never
> > > a message that it finds the link in the failed cases:
> > > 
> > > r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> > > r8169 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> > > r8169 0000:02:00.0: setting latency timer to 64
> > > r8169 0000:02:00.0: irq 45 for MSI/MSI-X
> > > eth0: RTL8168b/8111b at 0xffffc2000035a000, 00:00:00:00:00:00, XID 38000000 IRQ 45
> > 
> > The workarounds are in Jeff's tree as :
> > 9b1abbccf53ef1a1213b159d56257b535c599f07
> > d7d25be4418b609e54b407458003a4b6bff1c63b
> 
> Confirmed.
> 
> With upstream-fixes it survived three boots now. Can this fix please
> be submitted ASAP, not having it impacts testing here.

I can't, as Jeff's pull request breaks the build.

He'll hopefully fix that up and resubmit to me soon, sit tight.


      reply	other threads:[~2008-10-21 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 19:11 Current git r8169 driver often misses link at boot Andi Kleen
2008-10-21 20:26 ` Francois Romieu
2008-10-21 23:50   ` Andi Kleen
2008-10-21 23:45     ` David Miller [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=20081021.164536.219372605.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andi@firstfloor.org \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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.