From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: Re: [PATCH] xen: fix hypervisor crash with
	 xentrace
Date: Wed, 06 Apr 2011 16:03:51 +0100
Message-ID: <4D9C9CF7020000780003A32C@vpn.id2.novell.com>
References: <201104061632.02099.Christoph.Egger@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <201104061632.02099.Christoph.Egger@amd.com>
Content-Disposition: inline
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: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 06.04.11 at 16:32, Christoph Egger <Christoph.Egger@amd.com> wrote:
> Attached patch fixes hypervisor crashes when xentrace buffer gets=20
> initialized.

Just saw that Keir already fixed this the proper way as c/s
23173:94cef9aaf0cd. Thanks, Keir!

Jan

> The xen backtraces I have seen are:
>=20
> (XEN) Xen call trace:
> (XEN)    [<ffff82c48025cf70>] early_stack+0x0/0x48
> (XEN)    [<ffff82c4801278d0>] tb_control+0x182/0x278
> (XEN)    [<ffff82c480124aac>] do_sysctl+0x1fc/0xa40
> (XEN)    [<ffff82c480213248>] syscall_enter+0xc8/0x122
> (XEN)
> (XEN) Pagetable walk from ffff82c48025cf70:
> (XEN)  L4[0x105] =3D 00000000cfcaa027 5555555555555555
> (XEN)  L3[0x112] =3D 00000000cfcab027 5555555555555555
> (XEN)  L2[0x001] =3D 000000022f27b063 5555555555555555
> (XEN)  L1[0x05c] =3D 00000000cfc5c262 5555555555555555
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=3D0010]
> (XEN) Faulting linear address: ffff82c48025cf70
> (XEN) ****************************************
>=20
>=20
> (XEN) Xen call trace:
> (XEN)    [<ffff82c48025d852>] notifier_chain_register+0x0/0x35
> (XEN)    [<ffff82c4801275b2>] alloc_trace_bufs+0x5cd/0x7a9
> (XEN)    [<ffff82c480127910>] tb_control+0x182/0x278
> (XEN)    [<ffff82c480124aec>] do_sysctl+0x1fc/0xa40
> (XEN)    [<ffff82c480213288>] syscall_enter+0xc8/0x122
> (XEN)
> (XEN) Pagetable walk from ffff82c48025d852:
> (XEN)  L4[0x105] =3D 00000000cfcaa027 5555555555555555
> (XEN)  L3[0x112] =3D 00000000cfcab027 5555555555555555
> (XEN)  L2[0x001] =3D 000000022f27b063 5555555555555555
> (XEN)  L1[0x05d] =3D 00000000cfc5d262 5555555555555555
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=3D0010]
> (XEN) Faulting linear address: ffff82c48025d852
> (XEN) ****************************************
>=20
>=20
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>=20