All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: 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 11:15:54 -0600	[thread overview]
Message-ID: <5665BECA.6030605@cardoe.com> (raw)
In-Reply-To: <20151207142050.GA24671@char.us.oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 2625 bytes --]

On 12/7/15 8:20 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 07, 2015 at 09:20:12AM -0500, Konrad Rzeszutek Wilk wrote:
>> On Sat, Dec 05, 2015 at 12:54:56PM -0800, PGNet Dev wrote:
>>> On 12/05/2015 11:44 AM, Konrad Rzeszutek Wilk wrote:
>>>>> Two issues exist with the SuperMicro EFI
>>>>>
>>>>> 	(1) firmware EFI mis-mapping causing Xen PANIC on restart
>>>>
>>>> Can you try 'reboot=acpi' ?
>>>>
>>> ...
>>>>> I.e., what combination of
>>>>>
>>>>> /mapbs
>>>>> efi=no-rs
>>>>> reboot=acpi
>>>>>
>>>> All? It should be on the Xen command line.
>>>
>>> with /mapbs on the EFI exec line,
>>>
>>> 	grep mapbs /boot/grub2/grub.cfg
>>> 		chainloader $cmdpath/xen-4.6.0_04-398.efi xen-4.6.0_04-398.efi config.1
>>> /mapbs
>>>
>>> and on the Xen Cmd Line,
>>>
>>> 	grep efi= /boot/efi/EFI/opensuse/xen-4.6.0_04-398.cfg
>>> 		options= dom0_mem=3072M,max:3072M ... loglvl=all guest_loglvl=all
>>> efi=no-rs reboot=acpi
>>
>>>
>>> not clear to me what effect, if any, the addition of 'reboot=acpi' and
>>> '/mapbs' has, relative to just 'efi=no-rs' has.
>>
>>
>> Are you by chance an lawyer? :-)
>>
>> Try without /mapbs, efi=nr-rs and with reboot=acpi. That should use EFI routines
>> for everything (including reboot). Doing the 'reboot=acpi' will override
>> the reboot routine to only use the ACPI method.
>>
>> Granted if you did 'efi=nr-rs' we bypass EFI altogether and use 'acpi' method.
>>
>> My theory was that if use some EFI routines it inits the firmware enough
>> that ACPI reboot should work. But it may be that it is just not happy.
>>
>> There is an extra patch you can try to determine if the failure is
>> due to us doing ExitBootServices and not using virtual addresses (which
>> for example is the reason that under Lenovo it goes haywire).
>>
>> See attached patch (against staging). With that you would do:
> 
> Now attached.
>>
>> xen.efi /noexitboot /mapbs
>>
>> And you can try without 'efi=no-rs'.
>>
>> 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).
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel

Konrad,

Can we land the /noexitboot (probably better to call it /noexitbs to
match rs) into the tree?

I have to have a very similar patch locally to bring up my machine and
it would make sense that if you and I are seeing this problem then
others are.

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-07 17:15 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 [this message]
2015-12-07 18:09               ` Konrad Rzeszutek Wilk
2015-12-07 14:48           ` PGNet Dev

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=5665BECA.6030605@cardoe.com \
    --to=cardoe@cardoe.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.