Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934114AbXKPA2o (ORCPT ); Thu, 15 Nov 2007 19:28:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757460AbXKPA2g (ORCPT ); Thu, 15 Nov 2007 19:28:36 -0500 Received: from simmts5-srv.bellnexxia.net ([206.47.199.163]:57105 "EHLO simmts5-srv.bellnexxia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757186AbXKPA2f (ORCPT ); Thu, 15 Nov 2007 19:28:35 -0500 From: Kevin Winchester To: Andy Whitcroft Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures Date: Thu, 15 Nov 2007 20:28:29 -0400 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Kamalesh Babulal References: <20071113175906.497a1a6a.akpm@linux-foundation.org> <20071115100209.GB2513@shadowen.org> In-Reply-To: <20071115100209.GB2513@shadowen.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711152028.29734.kjwinchester@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1506 Lines: 36 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/