xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: List etiquette [Was: Re: EFI GetNextVariableName hang/crash]
Date: Fri, 25 Sep 2015 09:02:45 +0100	[thread overview]
Message-ID: <5604FFA5.3020004@citrix.com> (raw)
In-Reply-To: <1443111887.3276.38.camel@citrix.com>

On 09/24/2015 05:24 PM, Dario Faggioli wrote:
> [Unrelated to anything technical, dropping some Cc-s]
>
> On Thu, 2015-09-24 at 16:26 +0100, Ross Lagerwall wrote:
>> On 09/24/2015 03:53 PM, Marek Marczykowski-Górecki wrote:
>
>>> (XEN) Xen call trace:
>>> (XEN)    [<00000000ca9e6f98>] 00000000ca9e6f98
>>> (XEN)    [<ffff82d08011f7a7>] csched_vcpu_wake+0x1b7/0x4b0
>>> (XEN)    [<ffff82d08022a66f>] efi_runtime_call+0x76f/0x870
>>> (XEN)    [<ffff82d08022a5ed>] efi_runtime_call+0x6ed/0x870
>>> (XEN)    [<ffff82d080166ef4>] do_platform_op+0x504/0x1300
>>> (XEN)    [<ffff82d080225e29>] syscall_enter+0xa9/0xae
>>> (XEN)
>>> (XEN) Pagetable walk from 00000000ca9e6f98:
>>> (XEN)  L4[0x000] = 00000000c6a9f063 ffffffffffffffff
>>> (XEN)  L3[0x003] = 0000000093e74063 ffffffffffffffff
>>> (XEN)  L2[0x054] = 00000000c6c0b063 ffffffffffffffff
>>> (XEN)  L1[0x1e6] = 0000000000000000 ffffffffffffffff
>>> [   32.312081] a(XEN)
>>> (XEN) ****************************************
>>> (XEN) Panic on CPU 3:
>>> (XEN) FATAL PAGE FAULT
>>> (XEN) [error_code=0010]
>>> (XEN) Faulting linear address: 00000000ca9e6f98
>>> (XEN) ****************************************
>>> (XEN)
>>> (XEN) Reboot in five seconds...
>>>
>
>> XenServer has a patch specifically for this issue (which seems to
>> happen
>> on Dell machines):
>> https://github.com/xenserver/xen-4.6.pg/blob/master/master/0002-efi-E
>> nsure-incorrectly-typed-runtime-services-get-ma.patch
>>
> Can you trim when quoting? It's certainly not ideal to have to scroll
> down so much to get to the real content, especially in cases like this,
> when it's really not necessary.
>

OK. I usually do, but forgot for this email.

-- 
Ross Lagerwall

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

  reply	other threads:[~2015-09-25  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 14:53 EFI GetNextVariableName hang/crash Marek Marczykowski-Górecki
2015-09-24 15:26 ` Ross Lagerwall
2015-09-24 16:24   ` List etiquette [Was: Re: EFI GetNextVariableName hang/crash] Dario Faggioli
2015-09-25  8:02     ` Ross Lagerwall [this message]
2015-09-24 23:44   ` EFI GetNextVariableName hang/crash Marek Marczykowski-Górecki

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=5604FFA5.3020004@citrix.com \
    --to=ross.lagerwall@citrix.com \
    --cc=dario.faggioli@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 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).