From: PGNet Dev <pgnet.dev@gmail.com>
To: konrad.wilk@oracle.com
Cc: xen-devel@lists.xen.org
Subject: Re: fyi, Xen's EFI workarounds (/mapbs & efi=no-rs) on SuperMicro hardware; fixes solve 1/2 problems & SM responds that can't/won't fix their firmware
Date: Mon, 7 Dec 2015 06:48:27 -0800 [thread overview]
Message-ID: <56659C3B.7090107@gmail.com> (raw)
In-Reply-To: <20151207142012.GB22814@char.us.oracle.com>
On 12/07/2015 06:20 AM, Konrad Rzeszutek Wilk wrote:
> However I am wondering - why are you using '/mapbs' ? What did it
> help? (The combination of 'efi=no-rs' means you are in effect not
> using _any_ EFI operations - so doing /mapbs is not needed).
I used /mapbs because it was suggested in #irc by a dev (IIUC) @citrix
to do exactly that in response to the crash.
What it helped is that it cured the crash.
I switched to using efi=no-rs _instead_ of /mapbs because it was
recommended by a Xen dev that I do so, having called into question the
robustness of /mapbs as a fix, calling it 'quite ugly'.
Using just efi=no-rs also cures the crash, with the additional removal
of a non-fatal acpi error.
I'm now using more than just /mapbs -- specifically, adding efi=no-rs
and reboot=acpi -- for, admittedly, no good reason other than you'd
suggested I do so, above.
I'll see what I can manage with the patch you've provided. First, tho,
I need to reread all the various commentary, as I've completely lost
track of what the functions and benefits of any one option, or combo
thereof, are ...
prev parent reply other threads:[~2015-12-07 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 23:16 fyi, Xen's EFI workarounds (/mapbs & efi=no-rs) on SuperMicro hardware; fixes solve 1/2 problems & SM responds that can't/won't fix their firmware PGNet Dev
2015-12-05 2:49 ` Zir Blazer
2015-12-05 18:05 ` Konrad Rzeszutek Wilk
2015-12-05 18:32 ` PGNet Dev
2015-12-05 19:44 ` Konrad Rzeszutek Wilk
2015-12-05 20:54 ` PGNet Dev
2015-12-07 14:20 ` Konrad Rzeszutek Wilk
2015-12-07 14:20 ` Konrad Rzeszutek Wilk
2015-12-07 17:15 ` Doug Goldstein
2015-12-07 18:09 ` Konrad Rzeszutek Wilk
2015-12-07 14:48 ` PGNet Dev [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=56659C3B.7090107@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=konrad.wilk@oracle.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.