From: Kevin Winchester <kjwinchester@gmail•com>
To: Andy Whitcroft <apw@shadowen•org>
Cc: Andrew Morton <akpm@linux-foundation•org>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>
Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures
Date: Thu, 15 Nov 2007 20:28:29 -0400 [thread overview]
Message-ID: <200711152028.29734.kjwinchester@gmail.com> (raw)
In-Reply-To: <20071115100209.GB2513@shadowen.org>
On November 15, 2007 06:02:09 am Andy Whitcroft wrote:
> When testing some of the later 2.6.24-rc2-mm1+hotfix combinations on three
> of our test systems one job from each batch (1/4) failed. In each case the
> machine appears to have booted normally all the way to a login: prompt.
> However in the failed boots the networking though apparently initialised
> completely and correctly (as far as I can tell from the console output), is
> reported as not responding to ssh connections. The network interface seems
> to have been initialised on the right port, and the ssh daemons started.
>
> Two of the machines are powerpc boxes, the other an older x86_64.
> One machine is 4/4 in testing, just one. Most of the other machines are
> still not able to compile this stack so do not contribute to our knowledge.
>
> Any ideas?
>
I see this as well - the computer boots fine but no network. The only clues
in the dmesg are:
[ 294.097876] warning: process `dhclient' gets w/ old libcap
[ 294.097893] warning: process `dhclient' sets w/ old libcap
So I'll try backing up the patch series to before:
add-64-bit-capability-support-to-the-kernel.patch
or so, and see if that's the problem. If anyone has any other ideas, let me
know.
--
Kevin Winchester
next prev parent reply other threads:[~2007-11-16 0:28 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 [this message]
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
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=200711152028.29734.kjwinchester@gmail.com \
--to=kjwinchester@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=apw@shadowen$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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