From: Graeme Gregory <graeme.gregory@linaro.org>
To: James Morse <james.morse@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-efi <linux-efi@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Geoff Levand <geoff@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Riku Voipio <riku.voipio@linaro.org>,
Mark Salter <msalter@redhat.com>,
Will Deacon <will.deacon@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Ian Campbell <ijc@debian.org>
Subject: Re: [RFC PATCH 0/2] efi: add contents of LinuxExtraArgs EFI var to command line
Date: Thu, 2 Aug 2018 16:47:54 +0100 [thread overview]
Message-ID: <20180802154754.GC2372@xora-sinquacker> (raw)
In-Reply-To: <cf544006-79c6-89ba-458d-57c1718c9fa7@arm.com>
On Wed, Aug 01, 2018 at 11:07:17AM +0100, James Morse wrote:
> Hi Geoff,
>
> On 31/07/18 16:54, Geoff Levand wrote:
> > This m400 HEST problem is blocking me from enabling APEI support in
> > Debian [1], so I'd like to come to a conclusion on it.
> >
> > In summary from [2], Riku and Graeme mention they still have some m400
> > systems in use. Mark did some investigation and found the cause to be
> > generated by the m400's firmware, appearing after the EFI stub's call
> > to ExitBootServices.
>
> I did manage to borrow of one of these boxes to discover one additional piece of
> information: this firmware bug doesn't exist in the latest released firmware.
>
> The box was running the most recent firmware, and quotes its System ROM version as:
> | U02 v1.01 (10/02/2015)
>
> This thing doesn't have a HEST at all.
>
>
> Why is the the latest? A current Moonshot component pack[0]'s release notes
> quote m400 as removed, and say 'MCP 2017.06.0' was the latest with support. I
> can't find the Release Notes for '2017.07.0', but '2017.04.0' is here[1], and it
> contains:
> | ProLiant_m400_Server_ROM_U02_2015_10_02.HPb
>
>
> It looks like we've been talking about a bug in firmware that was never
> released. Can anyone shed any light on where "U02 v1.10 (08/19/2016)" comes from?
>
>
> > Do we want to have an arm64 specific in-kernel fix for this, or should
> > it be left to the distro maintainers and end users to decide if and
> > how they want to handle it?
>
> Leave it to the distro maintainers to decide. Any user capable of installing
> unofficial firmware should be able to add a string to the kernel command line.
>
>
I think most people are running the firmware provided from HPe support
but was never put on release site. NDA prevents us talking about it
though!
Graeme
> Thanks,
>
> James
>
> [0]
> https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=5409784&swItemId=MTX_7ad3cb148b4a444f96470839d8&swEnvOid=4184#tab4
> [1] https://support.hpe.com/hpsc/doc/public/display?docId=c05335771
next prev parent reply other threads:[~2018-08-02 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 15:49 [RFC PATCH 0/2] efi: add contents of LinuxExtraArgs EFI var to command line Ard Biesheuvel
2018-07-04 15:49 ` [RFC PATCH 1/2] efi/libstub: refactor load option command line processing for reuse Ard Biesheuvel
2018-07-04 15:49 ` [RFC PATCH 2/2] efi/libstub: taken contents of LinuxExtraArgs UEFI variable into account Ard Biesheuvel
2018-07-12 17:01 ` [RFC PATCH 0/2] efi: add contents of LinuxExtraArgs EFI var to command line Will Deacon
2018-07-12 17:39 ` Ard Biesheuvel
2018-07-12 19:24 ` Ian Campbell
2018-07-12 22:22 ` Geoff Levand
2018-07-13 6:15 ` Ard Biesheuvel
2018-07-13 9:56 ` Will Deacon
2018-07-13 15:59 ` Geoff Levand
2018-07-31 15:54 ` Geoff Levand
2018-08-01 10:07 ` James Morse
2018-08-02 15:47 ` Graeme Gregory [this message]
2018-08-06 21:23 ` Geoff Levand
2018-07-13 10:02 ` Ian Campbell
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=20180802154754.GC2372@xora-sinquacker \
--to=graeme.gregory@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=geoff@infradead.org \
--cc=hanjun.guo@linaro.org \
--cc=ijc@debian.org \
--cc=james.morse@arm.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=msalter@redhat.com \
--cc=riku.voipio@linaro.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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).