Exception in Intel GCC platform with OpensslFullAccel library (Bugzilla Bug 4846)

[tianocore-issues]

This issue was created automatically with bugzilla2github

Bugzilla Bug 4846

Date: 2024-09-10T08:43:28+00:00
From: prarthanasv
To: unassigned <>
CC: kanagavels, sountharyan, srinivasanm, yi1.li

Last updated: 2024-10-25T02:35:31+00:00

[tianocore-issues]

Comment 23391

Date: 2024-09-10 08:43:28 +0000
From: prarthanasv

• Industry Specification: ---
• Release Observed: EDK II Master
• Releases to Fix: EDK II Master
• Target OS: ---
• Bugzilla Assignee(s): unassigned <>

Facing exception with OpensslLibFullAccel library during normal boot in Intel GCC platforms. Below exception occurs in SHA256_Update().

FmpDxe.Entry(691203DC)
!!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000000 I:0 R:0 U:0 W:0 P:0 PK:0 SS:0 SGX:0
RIP - 00000000691C09B1, CS - 0000000000000038, RFLAGS - 0000000000210206
RAX - 000000006F584898, RCX - 00000000693B6098, RDX - 0000001A47A44CDE
RBX - 00000000693B6098, RSP - 000000006F584800, RBP - 00000000000003DE
RSI - 00000000000003DE, RDI - 0000000000000000
R8 - 000000000000000F, R9 - 0000000040000000, R10 - 0000000040000200
R11 - 0000000000000000, R12 - 00000000691E9124, R13 - 00000000691E9502
R14 - 00000000691E9124, R15 - 00000000691E9504
DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030
GS - 0000000000000030, SS - 0000000000000030
CR0 - 0000000080010013, CR2 - 0000000000000000, CR3 - 000000006F001000
CR4 - 0000000000000668, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 0000000069BC8020 0000000000000057, LDTR - 0000000000000000
IDTR - 0000000069BF4018 0000000000000FFF, TR - 0000000000000048
FXSAVE_STATE - 0000000069BC7470
!!!! Find image based on IP(0x691C09B1) /builds/adl/Build/AlderLake/DEBUG_GCC/X64/FmpDevicePkg/FmpDxe/2fe2cbfc-b9aa-4a93-ab5b-40173b581c42/DEBUG/FmpDxe.dll (ImageBase=000000006911B000, EntryPoint=00000000691203DC) !!!!

[tianocore-issues]

Comment 23410

Date: 2024-09-24 05:09:27 +0000
From: sountharyan

Hi @[email protected],
@[email protected],
@[email protected],
@[email protected],
@[email protected],
@[email protected],
@[email protected]

Kindly provide your comments ASAP.

Thanks,
Sountharya

[tianocore-issues]

Comment 23451

Date: 2024-10-15 01:07:16 +0000
From: sountharyan

[email protected]

[tianocore-issues]

Comment 23452

Date: 2024-10-15 01:58:14 +0000
From: @liyi77

Hi, could you enabled AVX2 and try again?

[tianocore-issues]

Comment 23453

Date: 2024-10-15 02:29:59 +0000
From: sountharyan

(In reply to [email protected] from comment #3)
> Hi, could you enabled AVX2 and try again?

Do we need to enable OPENSSL_NO_EC_NISTP_64_GCC_128 or DEFINE OPENSSL_FLAGS_X64 = -mavx2 to enable AVX2?

[tianocore-issues]

Comment 23454

Date: 2024-10-15 02:35:14 +0000
From: @liyi77

(In reply to sountharyan from comment #4)
> (In reply to [email protected] from comment #3)
> > Hi, could you enabled AVX2 and try again?
>
> Do we need to enable OPENSSL_NO_EC_NISTP_64_GCC_128 or DEFINE
> OPENSSL_FLAGS_X64 = -mavx2 to enable AVX2?

I mean enable avx2 in BIOS, there should be a AVX2 Knob in CPU Configuration of BIOS SETUP.

[tianocore-issues]

Comment 23462

Date: 2024-10-18 04:52:56 +0000
From: sountharyan

Created attachment 1549
Attached the Bios setup image.

Attachment: BZ-1549-image.png

[tianocore-issues]

Comment 23463

Date: 2024-10-18 04:54:01 +0000
From: sountharyan

Hi @[email protected],

AVX is enabled by default. still, we are facing exception.
Attached the image for reference.

Thanks,
Sountharya

[tianocore-issues]

Comment 23468

Date: 2024-10-22 02:20:35 +0000
From: sountharyan

Hi @[email protected],

AVX is enabled by default in BIOS SETUP. But still exception occurred.

Attached the Bios setup image for reference. Kindly provide your comments.

Thanks,
Sountharya

[tianocore-issues]

Comment 23499

Date: 2024-10-25 02:35:31 +0000
From: @liyi77

I can not reproduce it on my board.
Please provide more debugging information, such as

1. Is it reproduced under VS build
2. Add more debug logs, track which line has the problem, and what is the input.