it did boot into the kernel but now it panics at this:
3.158250] DMAR: SATC flags: 0x0
[ 3.162182] DMAR-IR: IOAPIC id 0 under DRHD base 0x907e0000 IOMMU 15
[ 3.169612] DMAR-IR: HPET id 0 under DRHD base 0x907e0000
[ 3.175862] DMAR-IR: Queued invalidation will be enabled to support x2apic a.
[ 3.195752] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 3.207576] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 3.231463] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2s
[ 3.243344] Calibrating delay loop (skipped), value calculated using timer f)
[ 3.247339] pid_max: default: 196608 minimum: 1536
S[Rxmedenbyltedsrcxg//Coaff0oc * as *
[ 3.255337] kernel tried to execute N)
[ 3.255337] BUG: unable to handle page fault for address: 0000000063441850
[ 3.255337] #PF: supervisor instruction fetch in kernel mode
[ 3.255337] #PF: error_code(0x0011) - permissions violation
[ 3.255337] PGD 4a35063 P4D 4a36063 PUD 4a3b063 PMD 4a3c063 PTE 8000000063443
[ 3.255337] Oops: 0011 [#1] PREEMPT SMP NOPTI
[ 3.255337] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.19.0-32-generic #33~u
[ 3.255337] Hardware name: Intel Avenue City CRB/Avenue City CRB, BIOS 24.085
[ 3.255337] RIP: 0010:0x63441850
[ 3.255337] Code: Unable to access opcode bytes at RIP 0x63441826.
[ 3.255337] RSP: 0000:ffffffff830035d8 EFLAGS: 00010002
[ 3.255337] RAX: 0000000063441850 RBX: ffffffff83003758 RCX: 0000000090000002
[ 3.255337] RDX: 0000000003050007 RSI: 00000000000000e7 RDI: 0000000000000078
[ 3.255337] RBP: ffffffff83003710 R08: 0000000000000000 R09: 0000000063334000
[ 3.255337] R10: 00000000000003f8 R11: 0000000000000000 R12: 00000000633400e0
[ 3.255337] R13: 0000000090000002 R14: 0000000003050007 R15: 0000000063333435
[ 3.255337] FS: 0000000000000000(0000) GS:ff1100005ae00000(0000) knlGS:00000
[ 3.255337] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3.255337] CR2: 0000000063441850 CR3: 0000000004ac4002 CR4: 00000000000616f0
[ 3.255337] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 3.255337] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
[ 3.255337] Call Trace:
[ 3.255337]
[ 3.255337] ? put_dec+0x1c/0xb0
[ 3.255337] ? number+0x3a3/0x3f0
[ 3.255337] ? rmqueue_pcplist.constprop.0+0x1ca/0x1f0
[ 3.255337] ? get_page_from_freelist+0x307/0x490
[ 3.255337] ? post_alloc_hook+0xdf/0x120
[ 3.255337] ? __efi_call+0x25/0x30
[ 3.255337] ? kernel_fpu_begin_mask+0x2b/0xc0
[ 3.255337] ? efi_set_virtual_address_map+0x73/0xb9
[ 3.255337] ? __efi_enter_virtual_mode+0x1a2/0x219
[ 3.255337] ? efi_enter_virtual_mode+0x38/0x4c
[ 3.255337] ? start_kernel+0x43b/0x4e4
[ 3.255337] ? x86_64_start_reservations+0x24/0x2c
[ 3.255337] ? x86_64_start_kernel+0xee/0x103
[ 3.255337] ? secondary_startup_64_no_verify+0xe5/0xeb
[ 3.255337]
[ 3.255337] Modules linked in:
[ 3.255337] CR2: 0000000063441850
[ 3.255337] ---[ end trace 0000000000000000 ]---
[ 3.255337] RIP: 0010:0x63441850
[ 3.255337] Code: Unable to access opcode bytes at RIP 0x63441826.
[ 3.255337] RSP: 0000:ffffffff830035d8 EFLAGS: 00010002
[ 3.255337] RAX: 0000000063441850 RBX: ffffffff83003758 RCX: 0000000090000002
[ 3.255337] RDX: 0000000003050007 RSI: 00000000000000e7 RDI: 0000000000000078
[ 3.255337] RBP: ffffffff83003710 R08: 0000000000000000 R09: 0000000063334000
[ 3.255337] R10: 00000000000003f8 R11: 0000000000000000 R12: 00000000633400e0
[ 3.255337] R13: 0000000090000002 R14: 0000000003050007 R15: 0000000063333435
[ 3.255337] FS: 0000000000000000(0000) GS:ff1100005ae00000(0000) knlGS:00000
[ 3.255337] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3.255337] CR2: 0000000063441850 CR3: 0000000004ac4002 CR4: 00000000000616f0
[ 3.255337] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 3.255337] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
[ 3.255337] Kernel panic - not syncing: Attempted to kill the idle task! [ 3.255337] ---[ end Kernel panic - not syncing: Attempted to kill the idle -
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
On Monday, March 10th, 2025 at 4:59 PM, memristor2 wrote:
> Wow I was definitely NOT expecting that to work. Thanks a lot you're a life saver So I got very curious why does this happen and how to give it a permanent fix within the since the firmware might be provided to some other end users and we can't just tell them to disable ASLR for each linux they might be installing.
>
> Sent with [Proton Mail](https://proton.me/mail/home) secure email.
>
> On Monday, March 10th, 2025 at 4:41 PM, Ajan wrote:
>
>> On Mon, Mar 10, 2025 at 08:57 PM, memristor2 wrote:
>>
>>> I don't see any option for this in edk2 or coreboot or while building the kernel. there are some guides on how to due this but they are only when you are ins
>>
>> Append "nokaslr" in "CONFIG_CMDLINE" when building kernel.
>>
>> keyword "nokaslr" in https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html
>> and "built-in kernel command string" https://www.kernelconfig.io/config_cmdline
>>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121172): https://edk2.groups.io/g/devel/message/121172
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]
-=-=-=-=-=-=-=-=-=-=-=-