From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morgan <morgan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kevin Winchester <kjwinchester@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kamalesh@linux.vnet.ibm.com
Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures
Date: Sat, 17 Nov 2007 13:57:00 +0000 [thread overview]
Message-ID: <20071117135640.GA22058@shadowen.org> (raw)
In-Reply-To: <473E794A.4060107@kernel.org>
On Fri, Nov 16, 2007 at 09:16:58PM -0800, Andrew Morgan wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> This warning is just saying that you might want to reconsider
> recompiling your dhclient with a newer libcap - which has native support
> for 64-bit capabilities. This is supposed to be informative, and not be
> associated with any particular error.
>
> - From your comments, you believe that this patch causes something in your
> boot process to fail. Can you supply some detail about the version of
> dhclient you are using? I'd like to understand exactly what it is doing
> (via libcap).
>
> Thanks
The machine which show this problem for me are using static network
configurations, so I don't know if libcap is still in the mix there.
I've just compared the boot logs from a successful and unsuccessful boot
on this kernel, and I don't see that particular message, nor do I see
any significant differences overall.
Perlexed.
-apw
prev parent reply other threads:[~2007-11-17 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071113175906.497a1a6a.akpm@linux-foundation.org>
2007-11-15 10:02 ` 2.6.24-rc2-mm1 -- strange apparent network failures Andy Whitcroft
2007-11-16 0:28 ` Kevin Winchester
2007-11-16 0:44 ` Andrew Morton
2007-11-17 5:16 ` Andrew Morgan
2007-11-17 12:48 ` Kevin Winchester
2007-11-17 23:52 ` Andrew Morgan
2007-11-18 0:50 ` Kevin Winchester
2007-11-18 1:17 ` Kevin Winchester
2007-11-18 1:57 ` Andrew Morgan
2007-11-18 1:23 ` Kevin Winchester
2007-11-17 13:57 ` Andy Whitcroft [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=20071117135640.GA22058@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@linux-foundation.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@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;
as well as URLs for NNTP newsgroup(s).