[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1254928298.1696.166.camel@gandalf.stny.rr.com>
Date: Wed, 07 Oct 2009 11:11:38 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Justin P. Mattock" <justinmattock@...il.com>
Cc: Jason Baron <jbaron@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Li Zefan <lizf@...fujitsu.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: system gets stuck in a lock during boot
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists