From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: Re: xen kernel crash at boot since 23598:b24018319772 Date: Thu, 30 Jun 2011 15:29:16 +0200 Message-ID: <4E0C7A2C.5040102@amd.com> References: <4E0C66C2.7000300@amd.com> <19980.30920.752737.641653@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19980.30920.752737.641653@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/30/11 15:23, Ian Jackson wrote: > Christoph Egger writes ("xen kernel crash at boot since 23598:b24018319772"): >> Changeset 23598:b24018319772 causes the xen kernel crash at boot: > > 23598:b24018319772 is a merge. This occurs if two tree maintainers > with push access "race" and commit changes locally. > > In this case the two sub-branches are: > > 1. Olaf's xenpaging series ending with 23591:3dcb553f3ba9, > applied by me, affecting only tools/ > 2. A series of hypervisor patches ending with 23597:e2235fe267eb, > applied by Keir. > > You should be able to see this information in "hg log" (the commit > message "Merge" is a giveaway) but it's easier if you use "hg view". > > It seems likely that something in 2. is responsible. As Jan already pointed out it is changeset 23573:584c2e5e03d9. When I remove the assertion as Jan pointed out Xen boots again. Christoph -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632