All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Pitcock <nenolod@dereferenced.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Crash with paravirt-ops 2.6.31.6 kernel
Date: Thu, 19 Nov 2009 11:21:44 +0300 (MSK)	[thread overview]
Message-ID: <9082131.751258618904958.JavaMail.root@ifrit.dereferenced.org> (raw)
In-Reply-To: <20091118144518.GD15585@phenom.dumpdata.com>

Hi Konrad,

----- "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:

> > [    1.254927] init[1] general protection ip:f779042f sp:ff9b0340
> error:0
> 

This is a domU kernel only.  And I am aware that init crashing is the
reason why.  My paravirt-ops dom0 kernels boot fine, but they are 64bit
userland.

The reason why I ask is because this only happens with the paravirt-ops
tree, e.g. not with the XenLinux 2.6.18 tree or the forward ports.

I think it might be related to the stackprotector option?

William

  reply	other threads:[~2009-11-19  8:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 19:04 Crash with paravirt-ops 2.6.31.6 kernel William Pitcock
2009-11-18 14:45 ` Konrad Rzeszutek Wilk
2009-11-19  8:21   ` William Pitcock [this message]
2009-11-19 17:31     ` Konrad Rzeszutek Wilk
2009-11-20  4:12 ` Jeremy Fitzhardinge
2009-11-22  9:54 ` Bastian Blank
2009-11-23 15:25   ` Ian Campbell
2009-11-23 16:31     ` Bug#544145: [Xen-devel] " Bastian Blank
2009-11-23 16:42       ` Bug#544145: " Ian Campbell
2009-11-23 17:23         ` Bug#544145: [Xen-devel] " Bastian Blank
2009-11-24  0:52           ` Bug#544145: " Jeremy Fitzhardinge
2009-11-23 16:31     ` Jan Beulich
2009-11-23 16:44       ` Ian Campbell
2009-11-23 17:13         ` Keir Fraser
2009-11-23 17:17           ` Ian Campbell
2009-11-25 10:22         ` Jan Beulich
2009-11-25 21:24           ` Jeremy Fitzhardinge
2009-11-26  7:35             ` Jan Beulich
2009-11-26  9:57             ` Ian Campbell
2009-11-24  0:39     ` Jeremy Fitzhardinge
2009-11-24  9:48       ` Ian Campbell

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=9082131.751258618904958.JavaMail.root@ifrit.dereferenced.org \
    --to=nenolod@dereferenced.org \
    --cc=konrad.wilk@oracle.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 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.