All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Nathan March <nathan@gt.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: 4.1.0rc3 page fault on boot prior to kernel loading
Date: Thu, 3 Feb 2011 07:35:32 +0000	[thread overview]
Message-ID: <1296718532.20804.251.camel@localhost.localdomain> (raw)
In-Reply-To: <4D49F5E5.4040708@gt.net>

On Thu, 2011-02-03 at 00:25 +0000, Nathan March wrote: 
> On 2/1/2011 4:05 PM, Nathan March wrote:
> > I ran into this on 4.0.2 as well, posted it to xen-users a couple 
> > weeks ago but didn't get any useful responses.
> 
> Just an update here, switching from the 2.6.32 head to next/2.6.37 has 
> solved this. Would be good to include a note about in the docs or 
> release notices since the wiki XenParavirtOps page still says 2.6.32.x 
> is the recommended branch.

2.6.32.x is still the recommended branch since it is the stable
maintained branch. 2.6.37+ are currently development branches. So we
really ought to try and get to the bottom of your issue.

Which exact kernel version (git sha1) are you using?

http://wiki.xen.org/xenwiki/XenParavirtOps contains (under "Are there
more debugging options I could enable to troubleshoot problems with Xen
and/or dom0 kernel?") further details of useful debugging options to
use.

Please can you try converting the various addresses from your stack
trace into functions / line numbers. I usually use "$ gdb vmlinux" and
then "(gdb) list *0xaddress", other people use addr2line, both options
require that you have a kernel built with debug symbols
(CONFIG_DEBUG_INFO IIRC).

Ian.

      reply	other threads:[~2011-02-03  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  0:05 4.1.0rc3 page fault on boot prior to kernel loading Nathan March
2011-02-03  0:25 ` Nathan March
2011-02-03  7:35   ` Ian Campbell [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=1296718532.20804.251.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=nathan@gt.net \
    --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.