All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Chenxiao Zhao <chenxiao.zhao@gmail.com>,
	Xen Devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [Xen-users] Hypervisor trap when dumping register
Date: Wed, 25 May 2016 12:24:48 +0100	[thread overview]
Message-ID: <57458B80.8090700@arm.com> (raw)
In-Reply-To: <4d4e3960-a393-696a-4684-be2bb2a53197@gmail.com>

(Move the thread to Xen-devel)

On 26/05/16 02:47, Chenxiao Zhao wrote:
> On 5/25/2016 2:37 AM, Julien Grall wrote:

[...]

> root@linaro-alip:~# (XEN) *** Serial input -> Xen (type 'CTRL-x' three
> times to
> switch input to DOM0)
> (XEN) 'd' pressed -> dumping registers
> (XEN)
> (XEN) *** Dumping CPU0 host state: ***
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000245f10Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8Hypervisor Trap. HSR=0x96000007 EC=0x25
> IL=1 Syndrome=0x7
> (XEN) CPU0: Unexpected Trap: Hypervisor
> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) PC:     0000000000231dc8

I was able to reproduce it with the latest RC on Juno r2. I will 
investigate it.


-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

       reply	other threads:[~2016-05-25 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+e=sbLjGHLxKW2OA9+U8y3LzBTOjD7bwXwa_rkyO8958mmM9Q@mail.gmail.com>
     [not found] ` <203f955a-04d8-2f18-0fdd-a9c5cb6bc091@arm.com>
     [not found]   ` <CA+e=sbKRP07GqnyJtFyire1jpr9f-RcVroOKtyvJYveT=vJSDQ@mail.gmail.com>
     [not found]     ` <5745724B.8050109@arm.com>
     [not found]       ` <4d4e3960-a393-696a-4684-be2bb2a53197@gmail.com>
2016-05-25 11:24         ` Julien Grall [this message]
2016-05-25 12:24           ` [Xen-users] Hypervisor trap when dumping register Julien Grall

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=57458B80.8090700@arm.com \
    --to=julien.grall@arm.com \
    --cc=chenxiao.zhao@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.