public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Min Xu via groups.io" <min.m.xu=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"crystallee@ami.com" <crystallee@ami.com>
Cc: "POLUDOV, FELIX" <felixp@ami.com>,
	"davidhsieh@ami.com" <davidhsieh@ami.com>,
	"jameswang@ami.com" <jameswang@ami.com>,
	"Ni, Ray" <ray.ni@intel.com>, "Xu, Min M" <min.m.xu@intel.com>,
	"Sun, CepingX" <cepingx.sun@intel.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: [edk2-devel] PR#5939 broke the legacy VM bootup
Date: Tue, 14 Jan 2025 02:54:23 +0000	[thread overview]
Message-ID: <PH0PR11MB5064CB6166EAEBC7B98C7F79C5182@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]

Hi, Crystal
PR#5939 (https://github.com/tianocore/edk2/pull/5939) was merged yesterday but it seems it broke the legacy VM bootup.

Below is the crash log of the failure.

Booting `CentOS Stream (6.2.0-6.2.19.2.52.x86_64) 9'

ConvertPages: range 1000000 - 5A27FFF covers multiple entries
!!!! X64 Exception Type - 0E(#PF - Page-Fault)  CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000003  I:0 R:0 U:0 W:1 P:1 PK:0 SS:0 SGX:0
RIP  - 0000000074BAA1EE, CS  - 0000000000000038, RFLAGS - 0000000000210002
RAX  - 00000000739B4000, RCX - 000000007F9EC018, RDX - 000000007E0BE000
RBX  - 000000007E0BE000, RSP - 000000007FE6D0B0, RBP - 000000007FE6D200
RSI  - 000000007F9EC018, RDI - 000000007EC7D618
R8   - 00000000739B4390, R9  - 000000007BCEB6FD, R10 - 000000007DA55DB9
R11  - 0000000000000077, R12 - 000000007E0C3318, R13 - 000000000026A628
R14  - 000000007EC7D618, R15 - 000000007DFC3518
DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
GS   - 0000000000000030, SS  - 0000000000000030
CR0  - 0000000080010033, CR2 - 0000000074BB1BE8, CR3 - 000000007FC01000
CR4  - 0000000000000668, CR8 - 0000000000000000
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 000000007F9DC000 0000000000000047, LDTR - 0000000000000000
IDTR - 000000007F515018 0000000000000FFF,   TR - 0000000000000000
FXSAVE_STATE - 000000007FE6CD10
!!!! Find image based on IP(0x74BAA1EE)  Build/OvmfX64/DEBUG_GCC5/X64/OvmfPkg/VirtioRngDxe/VirtioRng/DEBUG/VirtioRngDxe.dll (ImageBase=0000000000D8EF34, EntryPoint=0000000000D90DF5) !

Thanks
Min


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120986): https://edk2.groups.io/g/devel/message/120986
Mute This Topic: https://groups.io/mt/110601533/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 4741 bytes --]

             reply	other threads:[~2025-01-14  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  2:54 Min Xu via groups.io [this message]
2025-01-14  8:21 ` [edk2-devel] PR#5939 broke the legacy VM bootup Ard Biesheuvel via groups.io
2025-01-14  8:30   ` Min Xu via groups.io
2025-01-14  8:35     ` Ard Biesheuvel via groups.io
2025-01-14 13:02       ` Gerd Hoffmann via groups.io
2025-01-15  3:04       ` Crystal Lee via groups.io

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR11MB5064CB6166EAEBC7B98C7F79C5182@PH0PR11MB5064.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox