Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756596AbZJGPNj (ORCPT ); Wed, 7 Oct 2009 11:13:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753403AbZJGPNi (ORCPT ); Wed, 7 Oct 2009 11:13:38 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:63281 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752038AbZJGPNh (ORCPT ); Wed, 7 Oct 2009 11:13:37 -0400 Subject: Re: system gets stuck in a lock during boot From: Steven Rostedt Reply-To: rostedt@goodmis.org To: "Justin P. Mattock" Cc: Jason Baron , Ingo Molnar , Peter Zijlstra , Li Zefan , Frederic Weisbecker , Linux Kernel Mailing List In-Reply-To: <4ACCAB54.4010408@gmail.com> References: <1251096925.7538.121.camel@twins> <4A9251EB.8040805@gmail.com> <20090825085919.GB14003@elte.hu> <4A94803A.5060408@gmail.com> <20090826073351.GE23435@elte.hu> <4A9549E5.5020002@gmail.com> <20091002211211.GA2633@redhat.com> <1254792249.13160.213.camel@gandalf.stny.rr.com> <20091006203225.GC2631@redhat.com> <1254880921.1696.112.camel@gandalf.stny.rr.com> <4ACC001D.4050105@gmail.com> <1254920429.1696.127.camel@gandalf.stny.rr.com> <4ACCAB54.4010408@gmail.com> Content-Type: text/plain Organization: Kihon Technologies Inc. Date: Wed, 07 Oct 2009 11:11:38 -0400 Message-Id: <1254928298.1696.166.camel@gandalf.stny.rr.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1257 Lines: 42 On Wed, 2009-10-07 at 07:53 -0700, Justin P. Mattock wrote: > Steven Rostedt wrote: > > On Tue, 2009-10-06 at 19:42 -0700, Justin P. Mattock wrote: > > > > > >>> > >>> > >> o.k. applied your patch, but unfortunantly > >> I still am hitting this kernel panic. > >> > >> must admit I have no idea why this is doing this. > >> (but am willing to sit through this, because eventually > >> sooner or later will hit this if I update gcc). > >> > > > > But the panic you showed was that it could not find an init to execute. > > Which looks like a setup issue and not a kernel bug. > > > > -- Steve > > > > > > > > > That's whats getting me, i.g. if I compile > sysvinit normally without adding an SELinux patch > the system boots, as soon as I compile sysvinit with > SELinux support to load the policy, bam... I hit this. > > I can send a post to SELinux and see what they think, > and the go from there. Oh! It's an SELinux thing. It probably prevents you from executing init ;-) -- Steve -- 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/