All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Major Hayden <major@mhtx.net>, xen-devel@lists.xen.org
Subject: Re: Xen BUG at page_alloc.c:1738 (Xen 4.5)
Date: Tue, 19 May 2015 19:16:36 +0100	[thread overview]
Message-ID: <555B7E04.5060300@citrix.com> (raw)
In-Reply-To: <555B7BB8.90909@mhtx.net>

On 19/05/15 19:06, Major Hayden wrote:
> Hello there,
>
> I've been doing some testing of Xen 4.5 on Fedora 22 (due out within a week) and I have an error that prevents the server from booting in the very early boot process:
>
>> (XEN) Xen call trace:
>> (XEN)    [<ffff82d08011d160>] free_domheap_pages+0x240/0x430
>> (XEN)    [<ffff82d08018c944>] mmio_ro_do_page_fault+0x114/0x160
>> (XEN)    [<ffff82d0801a4c10>] do_page_fault+0x1a0/0x4f0
>> (XEN)    [<ffff82d080239768>] handle_exception_saved+0x2e/0x6c
>> (XEN) 
>> (XEN) 
>> (XEN) ****************************************
>> (XEN) Panic on CPU 0:
>> (XEN) Xen BUG at page_alloc.c:1738
>> (XEN) ****************************************
> The full output is over in a Github Gist[1].
>
> I've tested this on some physical machines (Dell, HP, and SuperMicro servers) as well as within a KVM virtual machine but I get the same boot error each time.  It occurs with Xen 4.5 and Linux 3.17-4.0.x.  Xen 4.5.1-rc1 fails in the same way.  I've opened a Red Hat Bug[2] as well as a Xen bug[3] on it.
>
> The code within free_domheap_pages() hasn't changed much since late 2014 so I'm not sure if that's the culprit.  Does anyone have any suggestions on how to debug it further?
>
> Thanks in advance!
>
> [1] https://gist.github.com/major/baa0e2eee7de51a2bcd1
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1219197
> [3] http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1908

Can you try a debug hypervisor and rerun, to confirm the stack trace and
see whether any assertions fire.

Can you identify exactly which line xen/common/page_alloc.c:1738 is in
your source?

~Andrew

  reply	other threads:[~2015-05-19 18:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 18:06 Xen BUG at page_alloc.c:1738 (Xen 4.5) Major Hayden
2015-05-19 18:16 ` Andrew Cooper [this message]
2015-05-20  2:11   ` Major Hayden
2015-05-20 10:41 ` Jan Beulich
2015-05-20 16:52   ` Major Hayden
2015-05-20 19:51     ` M A Young
  -- strict thread matches above, loose matches on Subject: below --
2015-05-29  6:24 Jason Fritcher
2015-05-29 10:09 ` Andrew Cooper
2015-05-29 10:50   ` M A Young
2015-05-29 10:57     ` Andrew Cooper
2015-05-29 11:17       ` M A Young
2015-05-29 18:12         ` Andrew Cooper
2015-05-30 22:07           ` M A Young
2015-05-30 22:43             ` Andrew Cooper
2015-06-01  7:40               ` Jan Beulich
2015-06-01  7:47                 ` M A Young
2015-06-06 21:00                   ` M A Young

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=555B7E04.5060300@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=major@mhtx.net \
    --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.