All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Unzner <knusperbrot@gmx.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] XEN bug at traps.c:3271
Date: Mon, 20 Jan 2014 18:16:48 +0100	[thread overview]
Message-ID: <52DD5A00.8070502@gmx.de> (raw)
In-Reply-To: <52DD19B10200007800115046@nat28.tlf.novell.com>

OK, well, that is unfortunate.

I suppose you will announce new versions of Xen on the xen-users mailing 
list, or is there another channel where you would communicate a solution 
for this issue?

Thanks!

Am 20.01.2014 12:42, schrieb Jan Beulich:
>>>> On 20.01.14 at 11:15, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Sun, 2014-01-19 at 13:37 +0100, Martin Unzner wrote:
>>> Hi list,
>>>
>>> I just installed Xen 4.3.1 for EFI according to
>>> https://bbs.archlinux.org/viewtopic.php?pid=1359933 and tried to boot
>>> it. There was a crash at the very beginning, notifying me of a bug at
>>> traps.c:3271. I could not find any logs, so I just noted the stack trace
>>> on a sheet of paper:
>>>
>>> do_device_not_available
>>> handle_exception
>>> efi_get_time
>>> get_cmos_time
>>> init_xen_time
>>> __start_xen
>>>
>>> Does that mean my hardware is incompatible?
>> No, just that you've found a bug I think.
>>
>> I'm copying the devel list here to see if anyone has any clues.
> We've seen that before: You unfortunately have got one of those
> UEFI implementations that utilize XMM (or, unlikely, FPU) registers,
> and Xen doesn't allow this. Which is a consequence of the UEFI
> specification being imprecise here: Some firmware implementors
> read it to allow such, while my reading of it results in this not being
> allowed. This is currently being brought up with the USWG for a
> resolution. I'm afraid there's nothing you can do to work around
> this for the time being (short of not booting via xen.efi, which -
> depending on how you do it and depending on your firmware -
> may have other bad side effects).
>
> Jan
>

      reply	other threads:[~2014-01-20 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52DBC709.80707@gmx.de>
2014-01-20 10:15 ` [Xen-users] XEN bug at traps.c:3271 Ian Campbell
2014-01-20 11:42   ` Jan Beulich
2014-01-20 17:16     ` Martin Unzner [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=52DD5A00.8070502@gmx.de \
    --to=knusperbrot@gmx.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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.