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] unstable tip not booting on x86-64 with 'domain_crash_sy

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] unstable tip not booting on x86-64 with 'domain_crash_sync'
From: "Travis Betak" <travis.betak@xxxxxxx>
Date: Thu, 7 Sep 2006 13:02:59 -0500 (CDT)
Cc: Muli Ben-Yehuda <muli@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 07 Sep 2006 11:03:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C126103B.104A%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C126103B.104A%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Thu, 7 Sep 2006, Keir Fraser wrote:

On 7/9/06 15:32, "Muli Ben-Yehuda" <muli@xxxxxxxxxx> wrote:

Have you tried disassembling the kernel image to look at the address
in the backtrace to see where the kernel is crashing?

Working on it now.

FWIW, it's an 8G Intel based machine, but playing with the ammount of
memory dedicated to Xen/dom0 doesn't make a different. Also, it
doesn't happen on a dual Opteron x86-64 machine.

Binary chop on changeset revisions isn't a bad idea. I would think
that such a blatant failure mode couldn't have crept in all that long

For what it's worth, a couple of us here got bitten by this every now
and then a couple of weeks back and it was on Opterons.  From what we
saw, it might have been dependent on the toolchain or something of the
like (although I hope it isn't).  I was building using Debian AMD64
stable and it would crash.  I upgraded to Debian testing and it went
away.  It started happening after c/s 11131 within about 100 changesets
or so.  It seemed really obscure and not widespread so we just moved on.

I hope this information helps a little.


Xen-devel mailing list