From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christophe Saout <christophe@saout.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: NX related build failure in latest pv_ops dom0 hackery tree
Date: Thu, 16 Apr 2009 17:49:43 -0700 [thread overview]
Message-ID: <49E7D227.3070001@goop.org> (raw)
In-Reply-To: <1239928496.9443.24.camel@leto.intern.saout.de>
Christophe Saout wrote:
> Ok, that seems to help. Also, there was an unfortunate mixup of the
> kernels. The xen-tip/next kernel actually works fine as well (it's just
> my merged one that didn't). Sorry about that.
>
!? When I diffed them, there were hardly any differences, and nothing
which seemed relevant...
> With vdso32=0 I could now get the hackery kernel to boot up completely.
> For some reason the xen-tip/next also gets past the initramfs stage and
> I can see it mount the root filesystem, but doesn't come up further than
> that (the network never comes up and the last thing I see is netconsole
> telling me the rootfs got mounted)
>
> Maybe I mixed something up again. Possible, it's quite late, I'll
> follow up on this another time.
>
OK, thanks for looking at this.
J
next prev parent reply other threads:[~2009-04-17 0:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 19:23 NX related build failure in latest pv_ops dom0 hackery tree Pasi Kärkkäinen
2009-04-05 5:25 ` Jeremy Fitzhardinge
2009-04-12 16:55 ` Christophe Saout
2009-04-12 18:57 ` Boris Derzhavets
2009-04-12 20:06 ` Boris Derzhavets
2009-04-12 20:14 ` Christophe Saout
2009-04-13 10:18 ` Pasi Kärkkäinen
2009-04-13 12:08 ` Boris Derzhavets
2009-04-13 13:28 ` Andrew Lyon
2009-04-13 15:34 ` Boris Derzhavets
2009-04-13 18:20 ` Jeremy Fitzhardinge
2009-04-14 16:53 ` Jeremy Fitzhardinge
2009-04-14 17:11 ` Thomas DuBuisson
2009-04-14 19:58 ` Jeremy Fitzhardinge
2009-04-14 20:30 ` Thomas DuBuisson
2009-04-14 21:03 ` Jeremy Fitzhardinge
2009-04-15 7:01 ` Pasi Kärkkäinen
2009-04-15 16:08 ` Jeremy Fitzhardinge
2009-04-15 16:55 ` Thomas DuBuisson
2009-04-15 18:36 ` Thomas DuBuisson
2009-04-14 17:31 ` Boris Derzhavets
2009-04-14 18:00 ` Boris Derzhavets
2009-04-14 21:43 ` Christophe Saout
2009-04-16 13:16 ` Christophe Saout
2009-04-16 16:13 ` Jeremy Fitzhardinge
2009-04-16 16:24 ` Christophe Saout
2009-04-16 16:34 ` Jeremy Fitzhardinge
2009-04-16 16:49 ` Christophe Saout
2009-04-23 12:01 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-04-23 17:06 ` Jeremy Fitzhardinge
2009-04-16 16:34 ` Jeremy Fitzhardinge
2009-04-16 22:05 ` Christophe Saout
2009-04-16 22:27 ` Jeremy Fitzhardinge
2009-04-16 23:45 ` Christophe Saout
2009-04-16 23:54 ` Jeremy Fitzhardinge
2009-04-16 23:54 ` Christophe Saout
2009-04-17 0:03 ` Jeremy Fitzhardinge
2009-04-17 0:34 ` Christophe Saout
2009-04-17 0:49 ` Jeremy Fitzhardinge [this message]
2009-04-17 12:17 ` Christophe Saout
2009-04-17 12:41 ` Christophe Saout
2009-04-17 13:58 ` Jeremy Fitzhardinge
2009-04-17 0:03 ` Mainline kernel dom0 support Valtteri Kiviniemi
2009-04-18 16:44 ` Thiago Camargo Martins Cordeiro
2009-04-18 17:26 ` Thiago Camargo Martins Cordeiro
2009-04-18 20:39 ` Boris Derzhavets
2009-04-19 19:25 ` M A Young
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=49E7D227.3070001@goop.org \
--to=jeremy@goop.org \
--cc=christophe@saout.de \
--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.