lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 15 Nov 2007 16:44:41 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Kevin Winchester <kjwinchester@...il.com> Cc: apw@...dowen.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, kamalesh@...ux.vnet.ibm.com, Andrew Morgan <morgan@...nel.org> Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures On Thu, 15 Nov 2007 20:28:29 -0400 Kevin Winchester <kjwinchester@...il.com> wrote: > 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 Yes, that's a good one to suspect. What a peculiar error message. > or so, and see if that's the problem. If anyone has any other ideas, let me > know. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists