From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: 2.6.27-rc4 pvops domU on Xen 3.3 Kernel panic Date: Sat, 6 Sep 2008 20:14:06 +0200 Message-ID: <20080906181406.GA21872@elte.hu> References: <1e16a9ed0808272026me171d36g34efe97f51194cdc@mail.gmail.com> <48B6DF07.7040103@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <48B6DF07.7040103@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: deshantm@gmail.com, xen-devel mailing list List-Id: xen-devel@lists.xenproject.org * Jeremy Fitzhardinge wrote: > Todd Deshane wrote: > > I'm trying to build a kernel.org domU to run on Xen 3.3 > > > > My first attempt produced a kernel panic. > > > > Below is my setup and the panic that occurred during boot right after: > > > > [ 0.004000] Initializing cgroup subsys cpuacct > > [ 0.008000] > > [ 0.008000] CPU 0/0 -> Node 0 > > [ 0.008000] CPU: Physical Processor ID: 0 > > [ 0.008000] CPU: Processor Core ID: 0 > > [ 0.008000] SMP alternatives: switching to UP code > > [ 0.020001] Freeing SMP alternatives: 22k freed > > > > The same panic happens for both default vcpus, vcpus=1, and vcpus=2 > > > > Any ideas or hints? > > > > Ah, it's a bug which has been since fixed, but it looks like the fix > hasn't made it into mainline. Patch below. > > (Ingo, can you push this to Linus? It needs to be in mainline.) ok - cherry-picked it into tip/x86/urgent. Ingo