From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: xen-devel@lists.xensource.com
Subject: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0
Date: Fri, 19 Aug 2011 01:04:48 +0200 [thread overview]
Message-ID: <4E4D9A90.30800@leuphana.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]
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
at the bottom line of the screen.
Here is a screenshot:
http://imageshack.us/photo/my-images/10/crashtm.png/
System is:
Dell PE2950 (Xeon L5335, Intel 5000 chipset)
Debian 6.0.2 squeeze(stable)
grub 1.98+20100804-14
Kernel .config:
http://pastebin.com/bQAyC30i
It has been derived from the example configurations on
"http://wiki.xensource.com/xenwiki/XenParavirtOps".
The kernel boots loads fine as dom0 under Xen 4.1.1
Though i know this kernel tree is intended to be a dom0 kernel, it
should still be bootable bare-metal or am i mistaken?
It worked previously, allthough i am unable to tell what the latest
working version was.
with best regards
--
Andreas Olsowski
[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 5144 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 reply other threads:[~2011-08-18 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 23:04 Andreas Olsowski [this message]
2011-08-18 23:35 ` [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0 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
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=4E4D9A90.30800@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 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).