On Thu, Oct 05, 2023 at 10:23:25AM +0200, Laszlo Ersek wrote:
> On 10/5/23 08:31, Nhi Pham via groups.io wrote:
> > Hi Ard, Oliver,
> >
> > I'm investigating the crash on grub2/shim loader due to the added
> > EFI_MEMORY_ATTRIBUTE_PROTOCOL when rebasing. I found this interesting
> > patch and went
On 10/5/23 08:31, Nhi Pham via groups.io wrote:
> Hi Ard, Oliver,
>
> I'm investigating the crash on grub2/shim loader due to the added
> EFI_MEMORY_ATTRIBUTE_PROTOCOL when rebasing. I found this interesting
> patch and went through on the discussion, I am still not sure the
> conclusion on this p
Hi Ard, Oliver,
I'm investigating the crash on grub2/shim loader due to the added
EFI_MEMORY_ATTRIBUTE_PROTOCOL when rebasing. I found this interesting
patch and went through on the discussion, I am still not sure the
conclusion on this patch.
This issue impacts many platforms, and any downs
I think that is an interesting idea but I would expect some push back
from OS loader maintainers. I would expect they don't want to be
constrained by the lowest common capabilities of the platforms they
still support/run on in the ecosystem. Not to mention the challenges
around servicing and/
On Tue, 20 Jun 2023 at 19:07, Sean Brogan wrote:
>
> I don't think a MemoryAttributes2Protocol with a single API would have
> avoided the errors.
>
> The programming pattern that triggered this would still need multiple calls
> to any API and in the future where all memory is allocated as NX thi
I don't think a MemoryAttributes2Protocol with a single API would have
avoided the errors.
The programming pattern that triggered this would still need multiple
calls to any API and in the future where all memory is allocated as NX
this possibility would still exist.
A short term effort to m
On Tue, Jun 20, 2023 at 04:16:40PM +0300, Ard Biesheuvel wrote:
> On Tue, Jun 20, 2023, 12:33 Gerd Hoffmann wrote:
>
> > On Mon, Jun 19, 2023 at 10:32:25PM +0200, Oliver Steffen wrote:
> > > Recent versions of shim (15.6 and 15.7) crash when the newly added
> > > EFI_MEMORY_ATTRIBUTE_PROTOCOL is
We recently encountered this issue as well.
For reference, some details are in this issue:
https://github.com/microsoft/mu_silicon_arm_tiano/issues/124
Specifically, this comment:
https://github.com/microsoft/mu_silicon_arm_tiano/issues/124#issuecomment-1593550704
On 6/20/2023 9:16 AM, Ard Bies
On Tue, Jun 20, 2023, 12:33 Gerd Hoffmann wrote:
> On Mon, Jun 19, 2023 at 10:32:25PM +0200, Oliver Steffen wrote:
> > Recent versions of shim (15.6 and 15.7) crash when the newly added
> > EFI_MEMORY_ATTRIBUTE_PROTOCOL is provided by the firmware. To allow
> > existing installations to boot, pr
On Mon, Jun 19, 2023 at 10:32:25PM +0200, Oliver Steffen wrote:
> Recent versions of shim (15.6 and 15.7) crash when the newly added
> EFI_MEMORY_ATTRIBUTE_PROTOCOL is provided by the firmware. To allow
> existing installations to boot, provide a workaround in form of a Pcd
> that allows tuning it
Recent versions of shim (15.6 and 15.7) crash when the newly added
EFI_MEMORY_ATTRIBUTE_PROTOCOL is provided by the firmware. To allow
existing installations to boot, provide a workaround in form of a Pcd
that allows tuning it off at build time (defaults to 'enabled').
Additionally, check the ret
11 matches
Mail list logo
