[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Xine.LNX.4.64.0807200553380.22632@us.intercode.com.au>
Date: Sun, 20 Jul 2008 05:54:52 +1000 (EST)
From: James Morris <jmorris@...ei.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Al Viro <viro@...iv.linux.org.uk>,
Alexander Beregalov <a.beregalov@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Stephen Smalley <sds@...ho.nsa.gov>,
Eric Paris <eparis@...isplace.org>
Subject: Re: linux-next: Tree for July 17: early crash on x86-64
On Sat, 19 Jul 2008, Rafael J. Wysocki wrote:
> > vfs-next/net-next conflict; apply the patch below on top of the merge.
>
> That helped, thanks.
>
> But next it ran into the BUG_ON() in line 883 of security/selinux/avc.c .
> Disabling selinux made the kernel boot, finally.
Ugh, that's not supposed to happen. Where was this in the boot? Do you
have a console log?
- James
--
James Morris
<jmorris@...ei.org>
--
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