All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Ren <bin.ren@gmail.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: BUG at domain.c:144
Date: Fri, 8 Apr 2005 01:37:08 +0100	[thread overview]
Message-ID: <8ae7802505040717375271da6c@mail.gmail.com> (raw)
In-Reply-To: <001b01c53bc8$480bfb90$0201a8c0@hawk>

try 'objdump -D xen-syms | less' and navigate to the addresses printed
out by the Xen stack trace. Make sure that the 'xen-syms' is sync'ed
with 'xen.gz'.

- Bin

On Apr 8, 2005 12:19 AM, Christopher S. Aker <caker@theshore.net> wrote:
> Under the -testing tree:
> 
> (retrieved with bk clone -r<cset> bk://xen.bkbits.net/xen-2.0-testing.bk)
> 
> 1.1774 - boots correctly (creates a 2.6.10-xen0)
> 1.1784 - refuses to boot (creates a 2.6.11-xen0)
> 
> Anything past 1.1784 that I've tried also BUGs.  It seems like any 2.6.11-dom0 kernel
> fails on this machine. Incidentally, I am able to run 2.6.11-domUs using the -stable
> 2.6.10-dom0.
> 
> All of the changesets between 1.1774 and 1.1784 are the 2.6.11 merge.  I haven't
> bother to try changesets in between those, since they look to me like they all need
> each other.  If anyone wants me to try those changesets, let me know.
> 
> How can I get more information from the stack trace that Xen puts out to further
> narrow this down?
> 
> Thanks,
> -Chris
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2005-04-08  0:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  6:38 BUG at domain.c:144 Ian Pratt
2005-04-06  7:59 ` Christopher S. Aker
2005-04-06  8:08   ` Keir Fraser
2005-04-07 18:53     ` Christopher S. Aker
2005-04-07 19:34       ` Bin Ren
2005-04-07 20:34         ` Christopher S. Aker
2005-04-07 19:35       ` Keir Fraser
2005-04-07 19:39         ` Christopher S. Aker
2005-04-07 20:06       ` BK question " Adam Heath
2005-04-07 22:48       ` Chris Wright
2005-04-07 23:19       ` Christopher S. Aker
2005-04-08  0:37         ` Bin Ren [this message]
2005-04-08  7:42           ` M.A. Williamson
2005-04-08  5:12         ` Christopher S. Aker
2005-04-08  9:49           ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14  3:53 Keir Fraser
2005-04-14 20:59 ` Keir Fraser
2005-04-14 23:03   ` Christopher S. Aker
2005-04-13 21:21 Ian Pratt
2005-04-13 23:12 ` Christopher S. Aker
2005-04-10 14:38 Ian Pratt
2005-04-08  8:00 Ian Pratt
2005-04-08 10:05 ` Christopher S. Aker
2005-04-08 10:05 ` Keir Fraser
2005-04-08 10:19   ` Christopher S. Aker
2005-04-08 12:14     ` Keir Fraser
2005-04-08 19:54       ` Christopher S. Aker
2005-04-10 23:20         ` Keir Fraser
2005-04-12  4:02           ` Christopher S. Aker
2005-04-13 18:16             ` Christopher S. Aker
2005-04-13 19:33               ` Keir Fraser
2005-04-13 20:11                 ` Christopher S. Aker
2005-04-14  1:39                   ` Keir Fraser
2005-04-14  2:13                     ` Christopher S. Aker
2005-04-06  0:03 Ian Pratt
2005-04-06  0:35 ` Christopher S. Aker
2005-04-05 23:27 Christopher S. Aker

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=8ae7802505040717375271da6c@mail.gmail.com \
    --to=bin.ren@gmail.com \
    --cc=bin.ren@cl.cam.ac.uk \
    --cc=caker@theshore.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.