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.
About the error info "BIOS Release Date string is unexpected length: 7. This string must be in MM/DD/YYYY format. No other format is allowed and no additional information may be included. See field description in the SMBIOS specification."
I talked with xuwei, and run a edk2-ovmf-20220826gitba0e0e4c6a-2.el9.noarch pkg, that error was disappeared. but case still got failed. just update latest debug progress here. and thanks to xueqiang. debugging in progress as well.
Boot a Win2022 guest with the attached build in Comment 6 (edk2-ovmf-20221207gitfff6d81270b5-5.el9.bz2168046.20230208.1117.noarch.rpm)
Check the BIOS string, the release date format is correct.
PS C:\Users\Administrator> systeminfo | findstr BIOS
BIOS Version: EDK II edk2-20221207gitfff6d81270b5-5.el9.bz2168046.20230208.1117, 12/7/2022
(In reply to Qianqian Zhu from comment #8)
> Hi Dehan,
>
> Please help check if the build in comment 6 could pass SVVP job.
After updating rpm to edk2-ovmf-20221207gitfff6d81270b5-5.el9.bz2168046.20230208.1117.noarch, svvp failed case still be there. please
contact me if you need to check the whole log. @kraxel @xuwei .
Tested with edk2-ovmf-20221207gitfff6d81270b5-6.el9.noarch, it works as expected. So set status to VERIFIED.
1. boot a rhel9.2 guest, check the release date
# dmidecode -t 0
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: EDK II
Version: edk2-20221207gitfff6d81270b5-6.el9
Release Date: 12/07/2022
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
BIOS characteristics not supported
Targeted content distribution is supported
UEFI is supported
System is a virtual machine
BIOS Revision: 0.0
2. boot a win2022 guest, check the release date
PS C:\Users\Administrator> systeminfo | findstr BIOS
BIOS Version: EDK II edk2-20221207gitfff6d81270b5-6.el9, 12/7/2022
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