From: "Jan Beulich" <JBeulich@novell.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] xen: fix hypervisor crash with xentrace
Date: Wed, 06 Apr 2011 16:03:51 +0100 [thread overview]
Message-ID: <4D9C9CF7020000780003A32C@vpn.id2.novell.com> (raw)
In-Reply-To: <201104061632.02099.Christoph.Egger@amd.com>
>>> On 06.04.11 at 16:32, Christoph Egger <Christoph.Egger@amd.com> wrote:
> Attached patch fixes hypervisor crashes when xentrace buffer gets
> 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:
>
> (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] = 00000000cfcaa027 5555555555555555
> (XEN) L3[0x112] = 00000000cfcab027 5555555555555555
> (XEN) L2[0x001] = 000000022f27b063 5555555555555555
> (XEN) L1[0x05c] = 00000000cfc5c262 5555555555555555
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0010]
> (XEN) Faulting linear address: ffff82c48025cf70
> (XEN) ****************************************
>
>
> (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] = 00000000cfcaa027 5555555555555555
> (XEN) L3[0x112] = 00000000cfcab027 5555555555555555
> (XEN) L2[0x001] = 000000022f27b063 5555555555555555
> (XEN) L1[0x05d] = 00000000cfc5d262 5555555555555555
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0010]
> (XEN) Faulting linear address: ffff82c48025d852
> (XEN) ****************************************
>
>
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
prev parent reply other threads:[~2011-04-06 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 14:32 [PATCH] xen: fix hypervisor crash with xentrace Christoph Egger
2011-04-06 14:36 ` Christoph Egger
2011-04-06 15:01 ` Jan Beulich
2011-04-06 14:54 ` Keir Fraser
2011-04-06 15:03 ` Jan Beulich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D9C9CF7020000780003A32C@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Christoph.Egger@amd.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).