All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Bader <stefan.bader@canonical.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel@lists.xen.org
Subject: Re: (XEN) traps.c:3071: GPF (0000): ffff82d0801d76b2 -> ffff82d080222806
Date: Mon, 03 Nov 2014 11:00:50 +0100	[thread overview]
Message-ID: <54575252.4060408@canonical.com> (raw)
In-Reply-To: <54575E890200007800044446@mail.emea.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]

On 03.11.2014 10:52, Jan Beulich wrote:
>>>> On 03.11.14 at 10:45, <stefan.bader@canonical.com> wrote:
>> I see the message from the subject on my Intel box whenever a guest (iirc 
>> even
>> dom0) starts up. It is not fatal and everything seems ok. I am just curious
>> about what might trigger this. The addresses look to be inside the 
>> hypervisor
>> code. I was wondering whether there is a simple way to figure out what this
>> relates to (likely need to look at the objdump of the unstripped hv module).
>>
>> Or has someone already looked into this and knows what likely is the cause?
> 
> Often guest MSR accesses cause this. addr2line on the corresponding
> xen-syms should tell you.
> 
> Jan
> 
Ah, yes. There are usually messages about MSR access as well. Thanks for the
pointer about addr2line. I'll try that.

-Stefan


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2014-11-03 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  9:45 (XEN) traps.c:3071: GPF (0000): ffff82d0801d76b2 -> ffff82d080222806 Stefan Bader
2014-11-03  9:52 ` Jan Beulich
2014-11-03 10:00   ` Stefan Bader [this message]
2014-11-03 10:51 ` Andrew Cooper
2014-11-03 11:19   ` Stefan Bader
2014-11-03 11:37     ` Stefan Bader
2014-11-03 11:38     ` Andrew Cooper
2014-11-03 12:50       ` Stefan Bader

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=54575252.4060408@canonical.com \
    --to=stefan.bader@canonical.com \
    --cc=JBeulich@suse.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.