Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionEduardo Habkost
2021-07-16 13:30:53 UTC
Cloning RHEL-8 BZ to RHEL-9.
+++ This bug was initially created as a clone of Bug #1982176 +++
Issue detected while testing bug 1904267:
(In reply to Laszlo Ersek from bug 1904267 comment #57)
> (In reply to Eduardo Habkost from bug 1904267 comment #54)
> > (In reply to Brian Payton from bug 1904267 comment #30)
> > > Simple failure with 1024 vcpus and 8TB
> >
> > For reference, this is the failure on debugcon:
> >
> > [...]
> > GetMicrocodePatchInfoFromHob: Microcode patch cache HOB is not found.
> > CpuMpPei: 5-Level Paging = 0
> > Register PPI Notify: 8F9D4825-797D-48FC-8471-845025792EF6
> >
> > ASSERT_EFI_ERROR (Status = Out of Resources)
> > ASSERT
> > /builddir/build/BUILD/edk2-ca407c7246bf/UefiCpuPkg/CpuMpPei/CpuBist.c(186):
> > !EFI_ERROR (Status)
> >
> >
> >
> > And this is the failing code:
> >
> > BistInformationSize = sizeof (EFI_SEC_PLATFORM_INFORMATION_RECORD2) +
> > sizeof (EFI_SEC_PLATFORM_INFORMATION_CPU) *
> > NumberOfProcessors;
> > Status = PeiServicesAllocatePool (
> > (UINTN) BistInformationSize,
> > (VOID **) &PlatformInformationRecord2
> > );
> > ASSERT_EFI_ERROR (Status);
> >
> > Maybe we're hitting some limit on allocation sizes? I don't know what's the
> > size of EFI_SEC_PLATFORM_INFORMATION_RECORD2 and
> > EFI_SEC_PLATFORM_INFORMATION_CPU.
>
> This is an edk2 design limitation.
>
> Please file an edk2 bug for RHEL-8, and clone it for RHEL-9.
>
> Meanwhile I've sent an upstream problem report:
>
> * [edk2-devel] CPU count limitation in CpuMpPei BIST processing
>
>
> https://listman.redhat.com/archives/edk2-devel-archive/2021-June/msg01493.
> html
> http://mid.mail-archive.com/ffa9d7db-b670-8b88-758f-4785c8d05d40@redhat.com
> https://edk2.groups.io/g/devel/message/77376
Comment 11Nitesh Narayan Lal
2022-06-15 15:48:13 UTC
Pawel, Gerd,
Is the fix required to resolve this issue already upstream?
Thanks
(In reply to Nitesh Narayan Lal from comment #11)
> Pawel, Gerd,
> Is the fix required to resolve this issue already upstream?
No. Possible solutions have been discussed (see linked mails in the original description of this bug), nothing merged so far, Pawel is busy creating a patch.
Comment 13Nitesh Narayan Lal
2022-06-16 12:46:13 UTC
(In reply to Gerd Hoffmann from comment #12)
> (In reply to Nitesh Narayan Lal from comment #11)
> > Pawel, Gerd,
> > Is the fix required to resolve this issue already upstream?
>
> No. Possible solutions have been discussed (see linked mails in the
> original description of this bug), nothing merged so far, Pawel is busy
> creating a patch.
Understood, thank you for the update.
I am clearing the needinfo for Pawel.
Comment 22Klaus Heinrich Kiwi
2022-10-26 12:29:16 UTC
Adding Vivek.
Vivek,this BZ has been state for a while.. Can we get an update of where it stands?
(In reply to Klaus Heinrich Kiwi from comment #22)
> Adding Vivek.
>
> Vivek,this BZ has been state for a while.. Can we get an update of where it
> stands?
We discussed status of this bug this Tuesday. Following were latest updates on this.
- Pawel continues to work on this.
- This needs changes in qemu as well. Gerd has provided a patch to Pawel for qemu so that he can test firmware changes.
- Pawel and Gerd to discuss if changing data structure size is going to break something else in the system. Gerd is on sick leave, so I guess this part can make progress once Gerd is back.
Pawel, do you have changes ready and tested so that Gerd (and others) can review it?
Hi All, sorry I make you waiting.
I do not have code ready for this, just some raw draft. Will discuss this with Gerd
on Wednesday if possible (Tuesday is public holiday in Poland).
For last 2 weeks both me and Gerd were on PTO which delayed our sync also.
Miroslav, is it some script which sets the status automatically from Assigned to POST. What we have currently there is just some Draft and its not about to be merged.
Comment 39Miroslav Rezanina
2022-12-08 13:12:46 UTC
(In reply to Vivek Goyal from comment #38)
> Miroslav, is it some script which sets the status automatically from
> Assigned to POST. What we have currently there is just some Draft and its
> not about to be merged.
Yes, it's done by our gitlab checker. However, it is expect name in form "DRAFT: ...." to identify MR as draft. As the MR uses format "[draft] ..." it is not properly identified as draft MR. I updated MR to be in form we expect.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: edk2 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:2165