Arch Linux

avnothdmi

Member

Registered: 2023-05-07

Posts: 5

Unable to handle page fault for address: ffffffffffffff8c

Hi there! I recently updated my system after a while and upon boot, it spat out this error message: https://imgur.com/a/bBcY2w5

Hardware:
- i5 7400
- 8GB 3000MHz RAM (DDR4)
- Radeon Pro 555

I’ve already tried:
- Reinstalling the kernel
- Rebuilding the initramfs (both manually and automatically)
- Running memtest86+ to check for any RAM issues.

I really don’t want to lose this install, so is there any way to remedy this?

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,568

Re: Unable to handle page fault for address: ffffffffffffff8c

Did you include the CPU registers when you ran MemTest?
What I can suggest is try booting from an updated live Arch USB. If you're getting the same error, then it could be hardware.
It's difficult to read the actual logs from the photos. You can get more help if you can post legible logs.
An iMac?

avnothdmi

Member

Registered: 2023-05-07

Posts: 5

Re: Unable to handle page fault for address: ffffffffffffff8c

It is an iMac 2017. I can boot the installer (created 3 hours ago using the latest ISO) just fine, but the install's still borked.

Logs (from what I can decipher):

[8.028794] BUG: unable to handle page fault for address: ffffffffffffff8c
[8.020858] BPF: supervisor write access in kernel mode
[8.020901] BPF: error_code(0x0002) - not-present page
[8.020941] PGD 24d625067 P4D 24d625067 PUD 24d627067 PMD 0
[8.020991] Oops: 0002 [#1] PREEMPT SMP PTI
[8.021026] CPU: 2 PID: 1 Comm: systemd Not tainted 6.3.1-arch1-1 #1 2f4443c3fa3529b1ac13dc02f36f7de43ede3ecd
[8.021102] Hardware name: Apple Inc. iMac18,2/Mac-77F1D7DA9285301, BIOS 451.148.1.0.0 04/11/2022
[8.021178] RIP: 0010:__bpf_tramp_enter+0xc.0x40
[8.021212] Code: ff e9 58 e5 ad 00 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 53 48 89 fb e8 09 72 ed <ff> 48 8b 83 60 82 88 88 a8 83 75 0a 65 48 ff 88 5b e9 1e ad ed ff
[8.021347] RSP: 0018:ffffa9220005fbc0 EFLAGS: 00010286
[8.021391] RAX: 0000000000000001 RBX: ffffffff84ad4dc8 RCX: 0000000500000000
[8.021445] RDX: 0000000000000000 RSI: 0000000000000064 RDI: ffff9b234d8a0800
[8.021499] RBP: ffffa9220005fbf8 R08: ffff9b23411d07a0 R09: ffff9b2341f3f480
[8.021554] R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000000
[8.021608] R13: 0000000000000000 R14: ffff9b234ab80b10 R15: ffffa9220005fe24
[8.021662] FS: 00007fe292aca840(0000) GS: ffff9b24a6d00000(0000) knlGS: 0000000000000000
[8.021724] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[8.021769] CR2: ffffffffffffff8c CR3: 00000001011d6006 CR4: 00000000003706e0
[8.021823] Call Trace:
[8.021846] <TASK>
[8.021868] ? bpf_trampoline_6442511372_0+0x3d/0x1000
[8.021916] ? bpf_lsm_file_open+0x9/0x10
[8.021953] ? security_file_open+0x30/0x50
[8.021990] ? do_dentry_open+0xf8/0x460
[8.022025] ? path_openat+0xd47/0x1178
[8.022059] ? security_inode_permission+0x3e/0x60
[8.022101] ? __legitimize_path+0x27/0x60
[8.022136] ? do_filp_open+0xb3/0x160
[8.022175] ? do_sys_openat2+0xaf/0x170
[8.022211] ? __x64_sys+openat+0x57/0xa8
[8.022246] ? do_syscall_64+0x60/0x90
[8.023962] ? do_mkdirat+0xeb/0x170
[8.025470] ? __x86_return_skl+0x71/0x88
[8.026955] ? __x86_return_skl+0x6b/0x88
[8.028376] ? __x86_return_skl+0x65/0x88
[8.029563] ? __x86_return_skl+0x5f/0x88
[8.030737] ? __x86_return_skl+0x59/0x88
[8.031895] ? __x86_return_skl+0x53/0x88
[8.033029] ? __x86_return_skl+0x4d/0x88
[8.033996] ? __x86_return_skl+0x47/0x88
[8.034935] ? __x86_return_skl+0x41/0x88
[8.035860] ? __x86_return_skl+0x3b/0x88
[8.036779] ? __x86_return_skl+0x35/0x88
[8.037694] ? __x86_return_skl+0x2f/0x88
[8.038561] ? __x86_return_skl+0x29/0x88
[8.039365] ? __x86_return_skl+0x23/0x88
[8.040172] ? entry_SYSCALL_64_after_hwframe+0x72/0xdc 
[8.040999] </TASK>
[8.041827] Modules linked in: bpf_preload ip_tabes x_tables ext4 crc32c_generic crc16 abcache jbd2 ses enclosure scsi_transport_sas hid_apple uas usb_storage usbhid amdgpu i2c_algo_bit drm_ttm_helper sdhci_pci ttm cqhci drm_buddy gpu_sched crc32c_intel sdhci drm_display_helper xhci_pci mmc_core xhci_pci_renesas cec video wmi
[8.043727] CR2: ffffffffffffff8c
[8.045550] RIP: 0010:__bpf_tramp_enter+0xc/0x40
[8.046482] Code: ff e9 58 e5 ad 00 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 53 48 89 fb e8 09 72 ed <ff> 48 8b 83 60 82 88 88 a8 83 75 0a 65 48 ff 88 5b e9 1e ad ed ff
[8.047509] RSP: 0018:ffffa9220005fbc0 EFLAGS: 00010286
[8.048553] RAX: 0000000000000001 RBX: ffffffff84ad4dc8 RCX: 0000000500000000
[8.049577] RDX: 0000000000000000 RSI: 0000000000000064 RDI: ffff9b234d8a0800

Last edited by avnothdmi (2023-05-07 18:22:53)

avnothdmi

Member

Registered: 2023-05-07

Posts: 5

Re: Unable to handle page fault for address: ffffffffffffff8c

Did you include the CPU registers when you ran MemTest?

How would I do that, exactly?

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,568

Re: Unable to handle page fault for address: ffffffffffffff8c

How would I do that, exactly?

It is an option in memtest.

avnothdmi

Member

Registered: 2023-05-07

Posts: 5

Re: Unable to handle page fault for address: ffffffffffffff8c

UPDATE: Fixed the system. It seems like kernel 6.3 really hates the retbleed=stuff parameter, for some reason. Removing that fixed it.

cyayon

Member

Registered: 2016-09-05

Posts: 35

Re: Unable to handle page fault for address: ffffffffffffff8c

Hi,

I have crash with kernel > 6.3.7 https://bbs.archlinux.org/viewtopic.php?id=287005
Did you have retbleed= in kernel params ?
On my side, no params except pcie_aspm=off nvme_core.default_ps_max_latency_us=0

Did you solved your issue ?
thanks

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,645

Re: Unable to handle page fault for address: ffffffffffffff8c

The OP has not been back since May, so I am going to consider this thread abandoned and close it now.