This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] PROBLEM: [BISECTED] xen domU panics just after

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] PROBLEM: [BISECTED] xen domU panics just after the boot
From: Paweł Zuzelski <pawelz@xxxxxxxxxxxxx>
Date: Fri, 24 Sep 2010 07:40:00 +0200
Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Paweł Zuzelski <pawelz@xxxxxxxxxxxxx>, James Dingwall <james.dingwall@xxxxxxxxxx>, lkml <linux-kernel@xxxxxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Sep 2010 22:43:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C9BEA8C.2030808@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100921190525.GD4573@xxxxxxxxxxxxxxx> <4C9BEA8C.2030808@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, 23 Sep 2010, Jeremy Fitzhardinge wrote:

>  On 09/21/2010 12:05 PM, Paweł Zuzelski wrote:
> > Hello,
> >
> > kernels and xen domU panics at the very begining of the
> > boot process.
> >
> > I have bisected it to a single commit, and the first bad commit is:
> > [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for 
> > IPIs and VIRQs
> >
> > kernel v2.6.35.5 with reverted this commit works for me.
> Thanks very much for doing that.  I'll have to work out what's going on
> (obviously it doesn't do it for me).

Have you seen the message from James Dingwall?

He had found the typo in fb412a178502dc498430723b082a932f797e4763
commit and sent the patch to lkml that fixes it.

Please, see https://patchwork.kernel.org/patch/202282/ if you have
not received James' mail. That patch resolves the problem for me and
for James.

Paweł Zuzelski

Xen-devel mailing list