Re: [Xen-devel] BUG at domain.c:144

[Bin Ren <bin.ren@xxxxxxxxx>]

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@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel