public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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: Wed, 12 Mar 2025 10:05:44 +0000	[thread overview]
Message-ID: <enoaafJ8awLkRakT9GrBO4CFKm7gNkfAGZs5vwJD9PmDO-HFP4o0vgeq03sB-prfLS3AUB7jCnKOg8DyzaggX2mmwHe3VPDpURbjHBtNxOM=@proton.me> (raw)
In-Reply-To: <182B756C71707289.31525@groups.io>

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

So i resolved the previous mentioned issue by turning off all of the debug logs which I had manually added.
But now I have a bigger issue.
So Ubuntu started crating processes but eventually has to kill a lot of them due to lack of memory. the log is as below:

[ 0.000000] signal:maxsigframesize:11952
[ 0.000000] BIOS-providedphysicalRAMmap:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000062e57fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000062e58000-0x0000000062e5bfff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000062e5c000-0x0000000063241fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000063242000-0x0000000063449fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000006344a000-0x0000000063454fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000063455000-0x0000000063466fff] ACPIdata
[ 0.000000] BIOS-e820: [mem 0x0000000063467000-0x0000000063467fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000063468000-0x000000008fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff020000-0x00000000ff05ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000107f000000-0x000000107fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0004380004000000-0x00043c0803ffffff] usable
[ 0.000000] NX(ExecuteDisable)protection:active
[ 0.000000] efi:EFIv2.70byEDKII
[ 0.000000] efi:SMBIOS=0x633f8000SMBIOS3.0=0x633f6000ACPI=0x63466000ACPI2.0=0x63466014MEMATTR=0x6030a198RNG=0x63455018
[ 0.000000] efi:seedingentropypool
[ 0.000000] random:crnginitdone
[ 0.000000] efi:memattr:UnexpectedEFIMemoryAttributestableversion2
[ 0.000000] secureboot:Securebootdisabled
[ 0.000000] SMBIOS3.0.0present.
[ 0.000000] DMI:IntelAvenueCityCRB/AvenueCityCRB,BIOS24.08-1681-ge90fc546e75e-dirty03/03/2025
[ 0.000000] tsc:Detected2400.000MHzprocessor
[ 0.000022] e820:update [mem 0x00000000-0x00000fff] usable==>reserved
[ 0.000031] e820:remove [mem 0x000a0000-0x000fffff] usable
[ 0.000053] last_pfn=0x43c0804000max_arch_pfn=0x10000000000
[ 0.000927] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.005359] totalRAMcovered: 260096M
[ 0.005688] Foundoptimalsettingformtrrcleanup
[ 0.005690] gran_size: 64K chunk_size: 64K num_reg: 7 lose cover RAM: 0G
[ 0.007933] e820: update [mem 0x80000000-0xffffffff] usable ==> reserved
[ 0.007941] e820: update [mem 0x4000000000-0x43c0803ffffff] usable ==> reserved
[ 0.007948] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 4227072MB of RAM.
[ 0.007951] updatee820formtrr
[ 0.007966] modifiedphysicalRAMmap:
[ 0.007967] modified: [mem 0x0000000000000000-0x0000000000000fff] reserved
[ 0.007972] modified: [mem 0x0000000000001000-0x000000000009ffff] usable
[ 0.007977] modified: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.007982] modified: [mem 0x0000000000100000-0x0000000062e57fff] usable
[ 0.007986] modified: [mem 0x0000000062e58000-0x0000000062e5bfff] reserved
[ 0.007990] modified: [mem 0x0000000062e5c000-0x0000000063241fff] usable
[ 0.007994] modified: [mem 0x0000000063242000-0x0000000063449fff] reserved
[ 0.007998] modified: [mem 0x000000006344a000-0x0000000063454fff] usable
[ 0.008001] modified: [mem 0x0000000063455000-0x0000000063466fff] ACPIdata
[ 0.008006] modified: [mem 0x0000000063467000-0x0000000063467fff] usable
[ 0.008009] modified: [mem 0x0000000063468000-0x000000008fffffff] reserved
[ 0.008013] modified: [mem 0x00000000ff020000-0x00000000ff05ffff] reserved
[ 0.008017] modified: [mem 0x000000107f000000-0x000000107fffffff] reserved
[ 0.008021] modified: [mem 0x0004380004000000-0x00043c0803ffffff] reserved
[ 0.008026] last_pfn=0x63468max_arch_pfn=0x10000000000
[ 0.008031] x2apic: enabled by BIOS, switching to x2apic ops
[ 0.033808] UsingGBpagesfordirectmapping
[ 0.035735] secureboot: Secure boot disabled
[ 0.035737] RAMDISK: [mem 0x511da000-0x5949efff]
-------------CUT----------------------------------------
[ 0.036485] ACPI: SRAT: Node 0 PXM 0 [mem 0x80000000-0x83ffffff]
[ 0.036490] ACPI: SRAT: Node 0 PXM 0 [mem 0x4380004000000-0x43c0803ffffff]
[ 0.036502] NUMA: Initialized distance table, cnt=2[ 0.036525] NUMA: nodes only cover 0MB of your 1585MB e820 RAM. Not used.-------------CUT----------------------------------------

Ubuntu 22.04.2 LTS ubuntu ttyS0

ubuntu login: [ 93.934333] Outofmemory:Killedprocess2834(Xorg)total-vm:2410176kB,anon-rss:19688kB,file-rss:60kB,shmem-rss:0kB,UID:0pgtables:528kBoom_score_adj:0
[ 109.368462] Outofmemory: Killed process 2752 (ubiquity-dm) total-vm:50252kB, anon-rss:9864kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:116kB oom_score_adj:0
[ 132.992458] Outofmemory: Killed process 2680 (networkd-dispat) total-vm:50060kB, anon-rss:9280kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:108kB oom_score_adj:0
[ 149.140831] Outofmemory: Killed process 2806 (unattended-upgr) total-vm:127148kB, anon-rss:8664kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:128kB oom_score_adj:0
[ 157.427804] Outofmemory: Killed process 2742 (zsysd) total-vm:1241788kB, anon-rss:4492kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:192kB oom_score_adj:0
[ 173.943224] Outofmemory: Killed process 3017 ((sd-pam)) total-vm:169992kB, anon-rss:4116kB, file-rss:0kB, shmem-rss:0kB, UID:999 pgtables:88kB oom_score_adj:0
[ 182.849249] Outofmemory: Killed process 2631 (systemd-resolve) total-vm:25272kB, anon-rss:3992kB, file-rss:0kB, shmem-rss:0kB, UID:101 pgtables:96kB oom_score_adj:0
[ 186.329839] Outofmemory: Killed process 2683 (rsyslogd) total-vm:222452kB, anon-rss:2804kB, file-rss:0kB, shmem-rss:0kB, UID:104 pgtables:76kB oom_score_adj:0
[ 192.928732] Outofmemory: Killed process 2673 (NetworkManager) total-vm:269532kB, anon-rss:2516kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:136kB oom_score_adj:0
[ 215.287255] Outofmemory: Killed process 2734 (udisksd) total-vm:392540kB, anon-rss:1948kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:128kB oom_score_adj:0
It seems that there is a problem with edk when programming the MTRRs and I lot of ram is not covered. In the log it's written:

WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 4227072MB of RAM
which means i dont have 4128Gbytes of ram which is also something I don't understand because the platform has only about 128Gb of ram. Anyways in the log it says there is only 1500Mbs ram available. What happened to the rest of it? what's going on?
Is there anything useful I could study? on other hints?
I should also mention that I have disabled the ASLR in the kernel

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

On Monday, March 10th, 2025 at 5:23 PM, memristor2 via groups.io <memristor2=proton.me@groups.io> wrote:

> 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 (#121189): https://edk2.groups.io/g/devel/message/121189
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: 35356 bytes --]

  parent reply	other threads:[~2025-03-12 10:05 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
     [not found]             ` <182B756C71707289.31525@groups.io>
2025-03-12 10:05               ` memristor2 via groups.io [this message]
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='enoaafJ8awLkRakT9GrBO4CFKm7gNkfAGZs5vwJD9PmDO-HFP4o0vgeq03sB-prfLS3AUB7jCnKOg8DyzaggX2mmwHe3VPDpURbjHBtNxOM=@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