All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@eventdriven.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Never mind Re: Re: Xen reboots when trying to start new domain
Date: Thu, 9 Sep 2004 22:34:39 -0700 (PDT)	[thread overview]
Message-ID: <20040909215823.Q98582@demos.bsdclusters.com> (raw)
In-Reply-To: <E1C5dE0-0003cO-00@mta1.cl.cam.ac.uk>

Zeroing the page in between improves the situation substantially.
Although I'm not sure if it is fixed.


pdb seems broken, to use pdb the symbols for the pdb_ctx variable must
be present, but they aren't:


my options:

verbose     ?= y
debug       ?= y
debugger    ?= y
perfc       ?= n
trace       ?= n

(gdb) ptype pdb_ctx
type = <data variable, no debug info>

gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -O3
-iwithprefix include -Wall -Werror -fomit-frame-pointer -pipe
-I/t/niners/users/xen/xeno-unstable.bk.work.1.1303/xen/include
-Wno-pointer-arith -Wredundant-decls -msoft-float -m32 -march=i686
-DVERBOSE -DXEN_DEBUGGER -c pdb-stub.c -o pdb-stub.o

-- If you stick a -g in there it works a little better:
(gdb) p pdb_ctx
$1 = {
  valid = 0x0,
  domain = 0x0,
  process = 0xfc53bd1a,
  system_call = 0x0,
  ptbr = 0x0
}
(gdb)
but it still won't give me a backtrace like it used to:
(XEN) pdb: [m12,8]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [m12,8]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [m12,1]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [m12,1]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [m12,1]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [m12,1]
(XEN) pdb: L2 error (0x12)
(XEN) pdb: [mc01ab330,1]
(XEN) pdb: L2 error (0xc01ab330)
(XEN) pdb: [mc01ab330,1]
(XEN) pdb: L2 error (0xc01ab330)



On Fri, 10 Sep 2004, Keir Fraser wrote:

> > >
> > > Note that we don't support direct writing to pde's (yet), only to leaf
> > > entries in the multi-level page table.
> >
> > Ahh - then it wouldn't help with this particular problem. I'm getting
> > an error when I unpin a page as an L2 table and then immediately re-pin
> > it as an L1.
>
> Please post us the debug output from Xen when this occurs. Might you
> still be running on the L2? Whatever -- we can probably narrow it down
> with the debug tracing.
>
>  -- Keir
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

  reply	other threads:[~2004-09-10  5:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  2:50 Question about starting a domain Kathy Chen
2004-09-01  7:20 ` Steven Hand
2004-09-01 19:15   ` Kathy Chen
2004-09-01 19:51     ` Ian Pratt
2004-09-01 20:22       ` Kathy Chen
2004-09-08 23:43       ` Xen reboots when trying to start new domain Kip Macy
2004-09-09  0:10         ` Keir Fraser
2004-09-09  0:14           ` Kip Macy
2004-09-09  0:27             ` Keir Fraser
2004-09-09 23:52               ` Kip Macy
2004-09-10  0:28                 ` Keir Fraser
2004-09-10 13:51                 ` Ronald G. Minnich
2004-09-10 16:31                   ` Kip Macy
2004-09-09  0:18           ` world doesn't compile with debug enabled Kip Macy
2004-09-09  0:25             ` Keir Fraser
2004-09-09  0:18           ` Re: Xen reboots when trying to start new domain Kip Macy
2004-09-09  0:19           ` Keir Fraser
2004-09-09  0:25             ` Kip Macy
2004-09-09  0:28               ` Keir Fraser
2004-09-09  0:36               ` Keir Fraser
2004-09-09  1:02                 ` Keir Fraser
2004-09-09  1:52                   ` Ian Pratt
2004-09-09  5:21                     ` Kip Macy
2004-09-10  0:11                     ` Never mind " Kip Macy
2004-09-10  0:29                       ` Keir Fraser
2004-09-10  0:41                         ` Kip Macy
2004-09-10  0:50                         ` Kip Macy
2004-09-10  2:53                           ` Keir Fraser
2004-09-10  3:09                             ` Kip Macy
2004-09-10  4:41                               ` Keir Fraser
2004-09-10  5:34                                 ` Kip Macy [this message]
     [not found] <41419F96.3090106@melon.dk>
2004-09-10 14:19 ` Keir Fraser

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=20040909215823.Q98582@demos.bsdclusters.com \
    --to=kmacy@eventdriven.org \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.