From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: crash while booting latest hackery kernel
Date: Sun, 29 Mar 2009 13:54:06 -0700 [thread overview]
Message-ID: <49CFDFEE.2080009@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0903291903420.23469@vega4.dur.ac.uk>
M A Young wrote:
> I get the following crash while booting a kernel built with the latest
> version of xen/dom0/hackery (booting without xen, but booting with xen
> also crashes in a similar way but I haven't managed to capture the
> crash from that) Reverting bd4a7874716d1b1f69cacfef4adf9f94050ecd82
> and cfb667260eb7f6dd26ceb6d49da818978396757d allows it to boot.
Yes, those changes are troublesome; I shouldn't have pushed them out
yet. But at the moment push2/xen/dom0/master is probably a more stable
base for experimenting, since its close to what I'm proposing for the
current merge window (though it includes backend support which I have
not yet pushed). One the merge window has finished, I'll probably
restructure the xen.git branches a fair amount anyway.
J
prev parent reply other threads:[~2009-03-29 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 18:09 crash while booting latest hackery kernel M A Young
2009-03-29 20:54 ` Jeremy Fitzhardinge [this message]
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=49CFDFEE.2080009@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--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.