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: Tue, 06 Oct 2009 09:31:44 -0700	[thread overview]
Message-ID: <4ACB70F0.5020502@goop.org> (raw)
In-Reply-To: <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@mail.gmail.com>

On 10/06/09 08:13, Bryan D. Payne wrote:
> Ok, so I tried setting dom0_mem to a variety of values less than 32GB.
>  I'm still getting a crash, but now it is more random.  Basically, I'm
> watching the boot process via a serial line, and instead of seeing the
> dom0 crash output that I posted before, I'm simply seeing the output
> stop, and the boot process hanging, in a different spot with each
> boot.  Removing the dom0_mem value beings me back to the behavior I
> had before, where the dom0 crash output shows up reliably each time.
>   

That's mysterious.  My first thought is that this is a separate problem.

Is it ever stable?  What happens if you set dom0_mem to 4G or less?

Is the console responsive when the kernel hangs?  That is, can you type
"Ctrl-A Ctrl-A Ctrl-A" to get Xen, then enter debug keys?  '0' (zero)
should dump the context for dom0 and give some clue about where it is dying.

Thanks,
    J

  reply	other threads:[~2009-10-06 16:31 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
2009-10-06 15:13       ` Bryan D. Payne
2009-10-06 16:31         ` Jeremy Fitzhardinge [this message]
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=4ACB70F0.5020502@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.