From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: 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: Thu, 01 Sep 2011 11:46:51 +0200 [thread overview]
Message-ID: <4E5F548B.1010602@leuphana.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1108312318380.32350@vega4.dur.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]
> 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.
Sounds realistic, i did test 42-45.
I will try to find the time to narrow it down to one exact version this
weekend.
--
Andreas Olsowski
Leuphana Universität Lüneburg
Rechen- und Medienzentrum
Scharnhorststraße 1, C7.015
21335 Lüneburg
Tel: ++49 4131 677 1309
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-09-01 9:46 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 [this message]
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
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=4E5F548B.1010602@leuphana.de \
--to=andreas.olsowski@leuphana.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.