All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: dom0 crash without any message
Date: Wed, 5 Jun 2013 10:56:25 -0400	[thread overview]
Message-ID: <20130605145625.GA28843@phenom.dumpdata.com> (raw)
In-Reply-To: <CAJ75kXbWVpi+=0=5hEoN6nYy=AtEReT-0M1iMUR5cp+vcGMTew@mail.gmail.com>

On Wed, Jun 05, 2013 at 02:52:49PM +0200, William Dauchy wrote:
> On Tue, Jun 4, 2013 at 6:26 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > I would think that the 64-bit kernel under Xen would work as well?
> 
> haven't tested but I guess so regarding the issue.
> 
> > There is also the Linux ones - nr_cpus= or some variant of it.
> 
> yup, it only worked through bios configuration.
> 
> > But instead of using work-arounds I would like to understand why you are
> > hitting this and fix it.
> > Hence the question about baremetal - and if you could kindly also attach
> > the serial log of that bootup - it could in figuring out what is going
> > on.
> 
> you mean an i386 baremetal log?

Yes.
> 
> --
> William

      reply	other threads:[~2013-06-05 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 16:14 dom0 crash without any message William Dauchy
2013-06-03 16:37 ` Ian Campbell
2013-06-03 17:38   ` William Dauchy
2013-06-03 17:45     ` Andrew Cooper
2013-06-03 21:13       ` William Dauchy
2013-06-04 14:05     ` Konrad Rzeszutek Wilk
2013-06-04 14:21       ` William Dauchy
2013-06-04 16:26         ` Konrad Rzeszutek Wilk
2013-06-05 12:52           ` William Dauchy
2013-06-05 14:56             ` Konrad Rzeszutek Wilk [this message]

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=20130605145625.GA28843@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=wdauchy@gmail.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.