All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John P. McDermott (USN Civilian)" <john.mcdermott@nrl.navy.mil>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM64 HiKey 960 Xen BUG at page_alloc.c:738
Date: Fri, 29 Sep 2017 11:57:05 -0400	[thread overview]
Message-ID: <FB4C66B7-CCF8-4651-A1E6-AA39FF316929@nrl.navy.mil> (raw)
In-Reply-To: <4B0E9805-0F28-493C-B853-439DFB85CB4D@nrl.navy.mil>


> On Sep 29, 2017, at 11:31 AM, John P. McDermott (USN Civilian) <john.mcdermott@nrl.navy.mil> wrote:
> 
> 
>> On Sep 29, 2017, at 11:25 AM, Roger Pau Monné <roger.pau@citrix.com> wrote:
>> 
>> On Fri, Sep 29, 2017 at 02:57:11PM +0000, John P. McDermott (USN Civilian) wrote:
>>> (XEN) Xen BUG at page_alloc.c:738
>> 
>> Do you have XSA-245 applied?
>> 
>> http://xenbits.xen.org/xsa/advisory-245.html
>> 
>> Roger.
> 
> No, just the vanilla change set as listed at the top of the trace.
> 

Now my development board is refusing to flash anything new, so I may have to go away for a while until I can get it to do that. I will follow up as soon as I get any new data.

John.


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

  reply	other threads:[~2017-09-29 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 14:57 ARM64 HiKey 960 Xen BUG at page_alloc.c:738 John P. McDermott (USN Civilian)
2017-09-29 15:17 ` (Offlist)Re: " Konrad Rzeszutek Wilk
2017-09-29 15:25 ` Roger Pau Monné
2017-09-29 15:31   ` John P. McDermott (USN Civilian)
2017-09-29 15:57     ` John P. McDermott (USN Civilian) [this message]
2017-09-29 16:20       ` John P. McDermott (USN Civilian)
2017-09-29 20:19         ` Goel, Sameer

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=FB4C66B7-CCF8-4651-A1E6-AA39FF316929@nrl.navy.mil \
    --to=john.mcdermott@nrl.navy.mil \
    --cc=roger.pau@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.