Bug 2168046

Summary: [edk2] BIOS Release Date string is unexpected length
Product: Red Hat Enterprise Linux 9 Reporter: dehanmeng <demeng>
Component: edk2Assignee: Gerd Hoffmann <kraxel>
Status: CLOSED ERRATA QA Contact: Xueqiang Wei <xuwei>
Severity: medium Docs Contact:
Priority: high    
Version: 9.2CC: berrange, coli, jinzhao, juzhang, kraxel, leidwang, mkedzier, pbonzini, qizhu, virt-maint, xuwei
Target Milestone: rcKeywords: Regression, TestBlocker, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: edk2-20221207gitfff6d81270b5-6.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:25:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2144442, 2169904    

Comment 1 dehanmeng 2023-02-08 07:57:16 UTC
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.

Comment 7 Xueqiang Wei 2023-02-08 17:09:59 UTC
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

Comment 8 Qianqian Zhu 2023-02-10 10:12:23 UTC
Hi Dehan,

Please help check if the build in comment 6 could pass SVVP job.

Comment 9 dehanmeng 2023-02-13 02:05:20 UTC
(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 .

Comment 11 Qianqian Zhu 2023-02-13 10:19:39 UTC
Please be aware that the test case still failed with the provided build.
Hi Dehan,

Would you please paste the latest fail log here?

Comment 13 Yanan Fu 2023-02-14 10:15:45 UTC
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 16 Qianqian Zhu 2023-02-15 06:28:35 UTC
Move this back to MODIFIED as we open another bz 2169904 against qemu-kvm.

Comment 20 Xueqiang Wei 2023-02-15 08:39:08 UTC
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

Comment 22 errata-xmlrpc 2023-05-09 07:25:12 UTC
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