From: Andrew Morton <akpm@linux-foundation.org>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: forcedeth, 2.6.29.1: no link during initialization
Date: Sun, 26 Apr 2009 18:16:04 -0700 [thread overview]
Message-ID: <20090426181604.7b38cab0.akpm@linux-foundation.org> (raw)
In-Reply-To: <49F066D8.5060802@t-online.de>
(cc's added)
On Thu, 23 Apr 2009 15:02:16 +0200 Harald Dunkel <harald.dunkel@t-online.de> wrote:
> Hi folks,
>
> I get these messages on every boot
>
> [ 37.413903] eth0: no link during initialization.
> [ 39.789316] eth0: link up.
> [ 39.794965] eth0: link down.
> [ 46.438599] eth0: link up.
> [ 48.407885] eth0: link down.
> [ 52.981754] eth0: link up.
> [ 52.986966] eth0: link down.
>
> After that dhcpclient or network manager give up to try
> again, i.e. the network is not set up.
>
>
> I saw this mentioned several times on Google, but without
> a solution. Maybe I could help to track this down?
prev parent reply other threads:[~2009-04-27 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 13:02 forcedeth, 2.6.29.1: no link during initialization Harald Dunkel
2009-04-27 1:16 ` Andrew Morton [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=20090426181604.7b38cab0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aabdulla@nvidia.com \
--cc=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--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