xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>,
	xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen-unstable panic: FATAL PAGE FAULT
Date: Mon, 30 Aug 2010 10:02:05 +0100	[thread overview]
Message-ID: <C8A1321D.21554%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <BAY121-W47C2F18C8C8A31F98554B0DA890@phx.gbl>

On 30/08/2010 09:47, "MaoXiaoyun" <tinnycloud@hotmail.com> wrote:

>        3) Every panic pointer to the same address:  ffff8315ffffffe4, which is
> not a valid page address.
> I printted pages of the domain in assign_pages, which all looks like
> ffff82f60bd64000,  at least
> ffff82f60 is the same.

Yes, well you may not be crashing on a supposed page address. Certainly the
page pointer that relinquish_memory() is working on, and passed to
put_page->free_domheap_pages is valid enough to not cause any of those
functions to crash when dereferencing it. At the moment you really have no
idea what is causing free_heap_pages() to crash.

>        A bit of lost direction to go further.  Thanks.

You need to find out which line of code in free_heap_pages() is crashing,
and what variable it is trying to dereference when it crashes. You have a
nice backtrace with an EIP value, so you can 'objdump -d xen-syms' and
search for the EIP in the disassembly. If you have a debug build of Xen you
can even do 'objdump -S xen-syms' and have the disassembly annotated with
corresponding source lines.

Have you seen this on more than one physical machine? If not, have you run
memtest on the offending machine?

 -- Keir

  reply	other threads:[~2010-08-30  9:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SNT0-MC2-F12iKC1rdi000797d9@snt0-mc2-f12.Snt0.hotmail.com>
2010-08-26  4:49 ` Re:Re: Xen-unstable panic: FATAL PAGE FAULT MaoXiaoyun
2010-08-26  7:39   ` Keir Fraser
2010-08-26  8:59     ` MaoXiaoyun
2010-08-26  9:11       ` Keir Fraser
2010-08-30  8:47         ` MaoXiaoyun
2010-08-30  9:02           ` Keir Fraser [this message]
2010-08-30 13:03             ` MaoXiaoyun
2010-08-30 13:16               ` Keir Fraser
2010-08-31 13:49                 ` MaoXiaoyun
2010-08-31 14:49                   ` Keir Fraser
2010-08-31 15:00                     ` Keir Fraser
2010-08-31 15:07                     ` Jan Beulich
2010-08-31 16:01                       ` Keir Fraser
2010-08-31 16:22                         ` Jan Beulich
2010-08-31 16:35                           ` Keir Fraser
2010-08-31 17:03                             ` Keir Fraser
2010-09-01  7:17                               ` MaoXiaoyun
2010-09-01  7:40                                 ` Keir Fraser
2010-09-01  8:05                                 ` Jan Beulich
2010-09-01  8:32                                   ` MaoXiaoyun
2010-09-01  8:02                               ` Jan Beulich
2010-09-01  8:49                                 ` Keir Fraser
2010-09-01  9:01                                   ` Jan Beulich
2010-09-01  9:28                                     ` Keir Fraser
2010-09-01  9:48                                     ` MaoXiaoyun
2010-09-01 10:09                                       ` Jan Beulich
2010-09-01  9:06                                   ` MaoXiaoyun
2010-09-01  9:23                                   ` MaoXiaoyun
2010-09-01  9:58                                     ` Keir Fraser
2010-09-01 10:21                                       ` MaoXiaoyun
2010-09-01 10:25                                         ` Keir Fraser
2010-09-01 10:28                                           ` Keir Fraser
2010-09-01 10:34                                         ` Jan Beulich
2010-09-01 11:32                                       ` MaoXiaoyun
2010-09-01  7:54                             ` Jan Beulich
2010-09-01  3:17                     ` MaoXiaoyun
2010-02-06 22:56 Mark Hurenkamp
2010-02-07 11:56 ` Keir Fraser
2010-04-30 20:52   ` Bastian Blank

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=C8A1321D.21554%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=tinnycloud@hotmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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).