From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0
Date: Fri, 2 Sep 2011 09:37:03 -0400 [thread overview]
Message-ID: <20110902133703.GB5968@dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1109020042460.7892@vega3.dur.ac.uk>
On Fri, Sep 02, 2011 at 12:44:31AM +0100, M A Young wrote:
>
>
> On Thu, 1 Sep 2011, Jeremy Fitzhardinge wrote:
>
> >On 09/01/2011 02:29 PM, M A Young wrote:
> >>On Wed, 31 Aug 2011, M A Young wrote:
> >>
> >>>On Fri, 19 Aug 2011, Andreas Olsowski wrote:
> >>>
> >>>>Source:
> >>>>git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> >>>>
> >>>>Tested branches:
> >>>>xen/stable-2.6.32.x
> >>>>xen/next-2.6.32.x
> >>>>
> >>>>When trying to boot the current kernel bare-metal it will not load
> >>>>properly, instead i am prompted with:
> >>>>
> >>>>panic early exception 0e rip 10:0 error 10 cr2 0
> >>>
> >>>I am seeing this as well. I have been trying to narrow it down a bit,
> >>>and it seems to me that the bug was introduced somewhere between
> >>>xen-2.6.32.39 and xen-2.6.32.42.
> >>
> >>xen-2.6.32.40 also crashes. I think that means that it is either
> >>commits c3dd7941354fa96a71f2613e2c7a1b215fa175dc or
> >>280802657fb95c52bb5a35d43fea60351883b2af (or something in the stable
> >>kernel or else compile differences though both are unlikely). I am
> >>still working on this to confirm which patch it is.
> >
> >280802657fb95c5 is unlikely - that's just a blkback change.
> >
> >c3dd7941354fa96 looks plausible.
>
> Yes, xen-2.6.32.40 with c3dd7941354fa96a71f2613e2c7a1b215fa175dc
> reverted will boot on bare metal.
<smacks his head> bare metal. Yes, it won't work under that - at least
not in that state.
Jeremy, can you revert that patch please - it was fixing one instance
of machines - and it looks to be breaking many more.
Grrrrrr
next prev parent reply other threads:[~2011-09-02 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 23:04 [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0 Andreas Olsowski
2011-08-18 23:35 ` Eric Camachat
2011-08-19 21:14 ` Jeremy Fitzhardinge
2011-08-24 17:59 ` Konrad Rzeszutek Wilk
2011-08-31 22:22 ` M A Young
2011-09-01 9:46 ` Andreas Olsowski
2011-09-01 21:29 ` M A Young
2011-09-01 22:42 ` Jeremy Fitzhardinge
2011-09-01 23:44 ` M A Young
2011-09-02 13:37 ` Konrad Rzeszutek Wilk [this message]
2011-09-02 19:26 ` Jeremy Fitzhardinge
2011-09-02 13:35 ` Konrad Rzeszutek Wilk
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=20110902133703.GB5968@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).