From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Current xen-unstable xen crashing in boot
Date: Fri, 14 Aug 2009 14:02:49 -0700
Message-ID: <4A85D0F9.1080802@goop.org>
References: <4A85B8D0.7090206@goop.org> <4A85CDA0.2010905@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4A85CDA0.2010905@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, Wei Gang <gang.wei@intel.com>
List-Id: xen-devel@lists.xenproject.org

On 08/14/09 13:48, Jeremy Fitzhardinge wrote:
>> (XEN) Early fatal page fault at e008:ffff828c8015415c (cr2=3Dffff83007=
fc75008, ec=3D0000)
>> (XEN) Stack dump: 000000000007fc76 000000000000000c ffff83007fc77ff0 f=
fff83007fc76000 ffff828c8026fe58 0000000000000262 0000000000000020 018000=
0000000000 000000000000010c ffff828c802a6380 ffff83007fc75008 00000000000=
00001 ffff830000000000 ffff828c80219b0c ffff83007fc76000 0000000000000000=
 ffff828c8015415c 000000000000e008 0000000000010082 ffff828c8026fdd8 0000=
000000000000 ffff828c80154158 ffff828c8026fde8 0000000000000262 000000000=
00002e2 0000000000000086 0000000000000262 0000000000000000 000000008026fe=
18 ffff83007fc75008 ffff828c00000027 ffff83007fc76000 ffff828c8021dd60 00=
00000000000002 000000007fc42000 ffff83000008bfc0 ffff83000008bf40 0000000=
000002000 ffff828c8026fe68 ffff828c80154f85 ffff828c8026fe78 ffff828c8015=
4fa5 ffff828c8026ff18 ffff828c802343ef 0000000000000000 0000000000000000 =
0000000000a1e000 0000000000aca3e0 ffff83000008bf40 0000000000000000 00000=
000ffffffff ffff83000000000c 0000000800000000 000000010000006e 0000000000=
000003 00000000000002f8 0000000000000000 0000000000000000 000000000000000=
0 0000000000000000 0000000000000000 0000000000000000 0000000000067e8c fff=
f828c801000b5 0000000000000000 0000000000000000 0000000000000000 00000000=
00000000 0000000000000000 0000000000000000 0000000000000000 0000000000000=
000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0=
000000000000000 0000000000000000 0000000000000000 0000000000000000 000000=
0000000000 0000000000000000 0000000000000000 0000000000000000 00000000000=
00000 0000000000000000 0000000000000000 0000000000000000 0000000000000000=
 0000000000000000 00000000fffff000=20
>>
>> This appears to be:
>> (gdb) x/i 0xffff828c8015415c=20
>> 0xffff828c8015415c <map_pages_to_xen+112>:	mov    (%rax),%rax
>> (gdb) x/i 0xffff828c80154f85=20
>> 0xffff828c80154f85 <__memguard_change_range+237>:	leaveq=20
>>
>> but I can't find a good enclosing frame from there (is there a tool to=
 pretty-print these stack traces?).
>>  =20
>>    =20
>
> I bisected it down to:
>
> The first bad revision is:
> changeset:   20038:1197585e32b7
> user:        Keir Fraser <keir.fraser@citrix.com>
> date:        Fri Aug 07 17:29:50 2009 +0100
> summary:     x86: Increase default max CPUs to 64.
>  =20

Reverting this change on current tip works fine for me.

    J