All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Bryan D. Payne" <bryan@thepaynes.cc>
Cc: xen-devel@lists.xensource.com
Subject: Re: dom0 crash with unstable
Date: Thu, 01 Oct 2009 14:01:21 -0700	[thread overview]
Message-ID: <4AC518A1.8080905@goop.org> (raw)
In-Reply-To: <64bddf0e0910010635wc085961tf55000d4305da2bf@mail.gmail.com>

On 10/01/09 06:35, Bryan D. Payne wrote:
> (gdb) x/i 0xffffffff819067de
> 0xffffffff819067de <xen_fix_mfn_list+38>:	ud2a
> (gdb) x/i 0xffffffff81906d64
> 0xffffffff81906d64 <xen_ident_map_ISA+128>:	leaveq
> (gdb) x/i 0xffffffff81906166
> 0xffffffff81906166 <xen_start_kernel+1343>:	
>     mov    0xa028b(%rip),%rax        # 0xffffffff819a63f8 <xen_start_info>
>   

It looks like its encountering a pfn (page number) that's greater than
the total number of pages given to the domain. 

Aaah, 36GB memory.  What happens if you configure
CONFIG_XEN_MAX_DOMAIN_MEMORY larger to match, or set dom0_mem to less
than 32GB?

(It shouldn't crash regardless, but it will confirm the diagnosis.)

    J

  reply	other threads:[~2009-10-01 21:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 18:05 dom0 crash with unstable Bryan D. Payne
2009-09-30 23:47 ` Jeremy Fitzhardinge
2009-10-01 13:35   ` Bryan D. Payne
2009-10-01 21:01     ` Jeremy Fitzhardinge [this message]
2009-10-06 15:13       ` Bryan D. Payne
2009-10-06 16:31         ` Jeremy Fitzhardinge
2009-10-06 17:23           ` Bryan D. Payne
2009-10-06 17:54             ` Jeremy Fitzhardinge
2009-10-06 18:25               ` Bryan D. Payne
2009-10-06 18:56                 ` Jeremy Fitzhardinge
2009-10-06 19:02                   ` Bryan D. Payne
2009-10-06 19:37                     ` Jeremy Fitzhardinge
2009-10-07 11:47                       ` Jan Beulich
2009-10-07 19:09                         ` Jeremy Fitzhardinge

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=4AC518A1.8080905@goop.org \
    --to=jeremy@goop.org \
    --cc=bryan@thepaynes.cc \
    --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 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.