--NzB8fVQJ5HfG6fxh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 28, 2007 at 06:50:43PM +0100, Manuel Bouyer wrote:
> On Wed, Jan 24, 2007 at 09:28:14AM +1100, Daniel Carosone wrote:
> > On Mon, Jan 22, 2007 at 11:17:55AM +0100, Manuel Bouyer wrote:
> > > > Just one:
> > > >=20
> > > >   _xen_alloc_contig low 0 high fffff000 address_bits 32
> > >=20
> > > That's surprising, I would have expected high to be 0x3fffffff or 0x4=
0000000
> >=20
> >=20
> > However, if I use larger dom0_mem, I do get output with high at
> > 0x40000000 as you predicted --- and immediately after that, a panic
> > "HYPERVISOR_mmu_update failed".
> >=20
> sorry for the delay replying to this
> Did you have time to get a stack trace ? Also, is your kernel configured
> with options DEBUG ?

I have a backtrace. Sorry, the most useful form I could capture it in
was as pictures of the screen, dust and reflections and all.  No
serial ports on this laptop for console, and a very glossy reflective
screen..

  ftp.n.o:~dan/imgp3*.jpg

No DEBUG in this kernel at the moment, I can add it.

--
Dan.

--NzB8fVQJ5HfG6fxh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)

iD8DBQFFwAQIEAVxvV4N66cRAsqBAJkBxXaE9rg6qfRVo3J1EdOgxiNhGACgz8vO
HqYWmvidbIpZcBOspVjRyok=
=ZTGr
-----END PGP SIGNATURE-----

--NzB8fVQJ5HfG6fxh--