From: "memristor2 via groups.io" <memristor2=proton.me@groups.io>
To: devel@edk2.groups.io
Subject: Re: [edk2-devel] Linux kernel Hangs after exit_boot_services using UEFIPayload
Date: Mon, 10 Mar 2025 13:53:01 +0000 [thread overview]
Message-ID: <WvQHpHCuj-ogjacxSQcQBoTQaEUdfjhGlUgWbvqQw8t36YOPYqbZ_cs_MeVKAZ1WJjG71EXyLQBX1hDlM77aqCAZ0uS8oSe18uj3ixDX-kM=@proton.me> (raw)
In-Reply-To: <9243.1741613931031243279@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Ok I'll look into this thanks for the help again. this seems that this new panic is a rather complicated challenge to overcome. I hope you wouldn't mind asking more questions about this matter on the mailling list.
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
On Monday, March 10th, 2025 at 5:08 PM, Ajan <ajan.zhong@newfw.com> wrote:
> On Mon, Mar 10, 2025 at 09:30 PM, memristor2 wrote:
>
>> BUG: unable to handle page fault for address: 0000000063441850
>
> To "nokaslr", maybe MemMap or E820 table passed to Linux kernel is incorrect. Then you need to check MemMap or E820 table entries.
>
> To kernel panic, page fault triggered at 0x63441850 with log "BUG: unable to handle page fault for address: 0000000063441850 ". This issue might be caused by invalid page table access. And also it seems you are using FPU "kernel_fpu_begin_mask+0x2b/0xc0 ", maybe you need to check whether FPU has been initialized correctly.
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121174): https://edk2.groups.io/g/devel/message/121174
Mute This Topic: https://groups.io/mt/111617309/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: 3570 bytes --]
next prev parent reply other threads:[~2025-03-10 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 12:10 [edk2-devel] Linux kernel Hangs after exit_boot_services using UEFIPayload memristor2 via groups.io
2025-03-10 12:39 ` Ajan
2025-03-10 12:57 ` memristor2 via groups.io
2025-03-10 13:11 ` Ajan
2025-03-10 13:29 ` memristor2 via groups.io
2025-03-10 13:30 ` memristor2 via groups.io
2025-03-10 13:38 ` Ajan
2025-03-10 13:53 ` memristor2 via groups.io [this message]
[not found] ` <182B756C71707289.31525@groups.io>
2025-03-12 10:05 ` memristor2 via groups.io
2025-03-12 13:44 ` Ajan
2025-03-12 13:46 ` memristor2 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='WvQHpHCuj-ogjacxSQcQBoTQaEUdfjhGlUgWbvqQw8t36YOPYqbZ_cs_MeVKAZ1WJjG71EXyLQBX1hDlM77aqCAZ0uS8oSe18uj3ixDX-kM=@proton.me' \
--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