It’s not Apple first-party hardware, it just shows that way because it’s being spoofed so MacOS will run on it. (This is almost certainly unrelated to the current failure, as I have been doing it since before I installed EndeavourOS.)
I also wonder if there’s a tool for boot comparisons. For now, I just kludged together something that will show lines from one log that don’t appear in another one. I’m comparing the failed boot with a boot from before the failure started happening, and with my current successful boot (that still has the stalls).
In comparing the failed boot with the error-less boot, I found the following in the failed boot logs that looked odd, and that I couldn’t find anything useful about online:
Feb 09 11:35:47 faith kernel: ------------[ cut here ]------------
Feb 09 11:35:47 faith kernel: kernel BUG at arch/x86/kernel/cet.c:132!
Feb 09 11:35:47 faith kernel: Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Feb 09 11:35:47 faith kernel: CPU: 5 UID: 0 PID: 420 Comm: (udev-worker) Tainted: P W OE 6.12.68-1-lts #1 197b0df12b18a5652e0116eb9837614f544be626
Feb 09 11:35:47 faith kernel: Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Feb 09 11:35:47 faith kernel: Hardware name: Acidanthera MacPro7,1/Mac-27AD2F918AE68F61, BIOS 2087.0.0.0.0 05/30/2025
Feb 09 11:35:47 faith kernel: RIP: 0010:exc_control_protection+0x2ae/0x2b0
Feb 09 11:35:47 faith kernel: Code: d8 b9 09 00 00 00 48 8b 93 80 00 00 00 be 80 00 00 00 48 c7 c7 73 91 27 be e8 8e e0 1c ff 80 a3 8a 00 00 00 fb e9 26 fe ff ff <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00
Feb 09 11:35:47 faith kernel: RSP: 0018:ffffd0c70424b2d0 EFLAGS: 00010002
Feb 09 11:35:47 faith kernel: RAX: 000000000000002d RBX: ffffd0c70424b2f8 RCX: 0000000000000000
Feb 09 11:35:47 faith kernel: RDX: 0000000000000000 RSI: ffff8e3a0f8a1900 RDI: ffff8e3a0f8a1900
Feb 09 11:35:47 faith kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: 00000000ffffefff
Feb 09 11:35:47 faith kernel: R10: ffffffffbec5d560 R11: ffffd0c70424b170 R12: 0000000000000000
Feb 09 11:35:47 faith kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Feb 09 11:35:47 faith kernel: FS: 000075151153e840(0000) GS:ffff8e3a0f880000(0000) knlGS:0000000000000000
Feb 09 11:35:47 faith kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 11:35:47 faith kernel: CR2: 000075deb076dd88 CR3: 000000010d2f8001 CR4: 0000000000f70ef0
Feb 09 11:35:47 faith kernel: PKRU: 55555554
Feb 09 11:35:47 faith kernel: Call Trace:
Feb 09 11:35:47 faith kernel: <TASK>
Feb 09 11:35:47 faith kernel: asm_exc_control_protection+0x26/0x30
Feb 09 11:35:47 faith kernel: RIP: 0010:otp_read_bit+0x8ce/0x106c [wl]
Feb 09 11:35:47 faith kernel: Code: f0 41 5e c9 c3 48 81 c3 a4 00 00 00 48 89 df e8 5c df 17 00 25 ff ff f0 ff 48 89 de 0d 00 00 0c 00 89 c7 e8 b8 df 17 00 eb ae <55> 48 89 e5 41 57 41 56 41 55 41 54 49 89 fc 53 48 83 ec 08 8b 47
Feb 09 11:35:47 faith kernel: usb 2-5: new SuperSpeed USB device number 3 using xhci_hcd
Feb 09 11:35:47 faith kernel: RSP: 0018:ffffd0c70424b3a8 EFLAGS: 00010202
Feb 09 11:35:47 faith kernel: RAX: ffffffffc0c8a900 RBX: ffff8e2ed2471800 RCX: 0000000000000070
Feb 09 11:35:47 faith kernel: RDX: 0000000000000cfc RSI: 0000000000000206 RDI: ffff8e2ed2471800
Feb 09 11:35:47 faith kernel: RBP: ffffd0c70424b3d0 R08: ffffd0c70424b45e R09: 0000000000000000
Feb 09 11:35:47 faith kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8e2ed2482001
Feb 09 11:35:47 faith kernel: R13: 0000000000000010 R14: ffffd0c70424b45e R15: 0000000000000000
Feb 09 11:35:47 faith kernel: ? otp_init+0xa5/0xc3 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: otp_read_word+0x51/0x9d [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? si_set_sromctl+0x50/0x5b [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: wlc_phy_attach_acphy+0x164d/0x182d [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? _wl_timer+0xd0/0xd0 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: wlc_phy_attach+0x818/0xfc2 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: wlc_bmac_attach+0x8ee/0x1215 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? warn_thunk_thunk+0x1a/0x30
Feb 09 11:35:47 faith kernel: ? wlc_scan_attach+0x161/0x1b9 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: wlc_attach+0x283/0x1a93 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? iomem_map_sanity_check+0xc0/0xf0
Feb 09 11:35:47 faith kernel: ? wl_pci_probe+0x2a7/0xf40 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: wl_pci_probe+0x328/0xf40 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? local_pci_probe+0x3f/0x90
Feb 09 11:35:47 faith kernel: ? pci_device_probe+0x24a/0x280
Feb 09 11:35:47 faith kernel: ? sysfs_do_create_link_sd+0x6d/0xd0
Feb 09 11:35:47 faith kernel: ? really_probe+0xdb/0x340
Feb 09 11:35:47 faith kernel: ? pm_runtime_barrier+0x55/0x90
Feb 09 11:35:47 faith kernel: ? __driver_probe_device+0x78/0x140
Feb 09 11:35:47 faith kernel: ? driver_probe_device+0x1f/0xa0
Feb 09 11:35:47 faith kernel: ? __pfx___driver_attach+0x10/0x10
Feb 09 11:35:47 faith kernel: ? __driver_attach+0xcb/0x1e0
Feb 09 11:35:47 faith kernel: ? bus_for_each_dev+0x87/0xe0
Feb 09 11:35:47 faith kernel: ? bus_add_driver+0x10b/0x1f0
Feb 09 11:35:47 faith kernel: ? orc_header+0x1658/0x1658 [wl 957a08f071633b7892c6aa42826db4e3e8f69ead]
Feb 09 11:35:47 faith kernel: ? driver_register+0x75/0xe0
Feb 09 11:35:47 faith kernel: ? do_one_initcall+0x59/0x310
Feb 09 11:35:47 faith kernel: ? do_init_module+0x62/0x240
Feb 09 11:35:47 faith kernel: ? init_module_from_file+0x8b/0xe0
Feb 09 11:35:47 faith kernel: ? init_module_from_file+0x8b/0xe0
Feb 09 11:35:47 faith kernel: ? idempotent_init_module+0x11e/0x310
Feb 09 11:35:47 faith kernel: ? __x64_sys_finit_module+0x5e/0xb0
Feb 09 11:35:47 faith kernel: ? do_syscall_64+0x7b/0x190
Feb 09 11:35:47 faith kernel: ? xas_load+0xd/0xd0
Feb 09 11:35:47 faith kernel: ? filemap_get_read_batch+0x164/0x2c0
Feb 09 11:35:47 faith kernel: ? filemap_get_pages+0xa7/0x700
Feb 09 11:35:47 faith kernel: ? current_time+0x3f/0xf0
Feb 09 11:35:47 faith kernel: ? atime_needs_update+0xa2/0x120
Feb 09 11:35:47 faith kernel: ? touch_atime+0x5d/0x120
Feb 09 11:35:47 faith kernel: ? filemap_read+0x36d/0x390
Feb 09 11:35:47 faith kernel: ? vfs_read+0x15c/0x380
Feb 09 11:35:47 faith kernel: ? vfs_read+0x15c/0x380
Feb 09 11:35:47 faith kernel: ? __x64_sys_pread64+0x97/0xd0
Feb 09 11:35:47 faith kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 09 11:35:47 faith kernel: ? do_syscall_64+0x87/0x190
Feb 09 11:35:47 faith kernel: ? irqentry_exit_to_user_mode+0x2c/0x1b0
Feb 09 11:35:47 faith kernel: ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 09 11:35:47 faith kernel: </TASK>
Feb 09 11:35:47 faith kernel: Modules linked in: wl(POE+) crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel btrfs cfg80211 gf128mul nvme crypto_simd blake2b_generic libcrc32c cryptd nvme_core crc32c_generic crc32c_intel rfkill xor nvme_auth video raid6_pq wmi pinctrl_alderlake uinput i2c_dev pkcs8_key_parser crypto_user
Feb 09 11:35:47 faith kernel: ---[ end trace 0000000000000000 ]---
Feb 09 11:35:47 faith kernel: RIP: 0010:exc_control_protection+0x2ae/0x2b0
Feb 09 11:35:47 faith kernel: Code: d8 b9 09 00 00 00 48 8b 93 80 00 00 00 be 80 00 00 00 48 c7 c7 73 91 27 be e8 8e e0 1c ff 80 a3 8a 00 00 00 fb e9 26 fe ff ff <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00
Feb 09 11:35:47 faith kernel: RSP: 0018:ffffd0c70424b2d0 EFLAGS: 00010002
Feb 09 11:35:47 faith kernel: RAX: 000000000000002d RBX: ffffd0c70424b2f8 RCX: 0000000000000000
Feb 09 11:35:47 faith kernel: RDX: 0000000000000000 RSI: ffff8e3a0f8a1900 RDI: ffff8e3a0f8a1900
Feb 09 11:35:47 faith kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: 00000000ffffefff
Feb 09 11:35:47 faith kernel: R10: ffffffffbec5d560 R11: ffffd0c70424b170 R12: 0000000000000000
Feb 09 11:35:47 faith kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Feb 09 11:35:47 faith kernel: FS: 000075151153e840(0000) GS:ffff8e3a0f880000(0000) knlGS:0000000000000000
Feb 09 11:35:47 faith kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 09 11:35:47 faith kernel: CR2: 000075deb076dd88 CR3: 000000010d2f8001 CR4: 0000000000f70ef0
Feb 09 11:35:47 faith kernel: PKRU: 55555554
Feb 09 11:35:47 faith kernel: note: (udev-worker)[420] exited with irqs disabled
Feb 09 11:35:47 faith systemd-udevd[369]: 0000:09:00.0: Worker [420] terminated by signal 11 (SEGV).
The following (appearing in the failed log) appears to be where the dracut initqueue hook stall happens:
Feb 09 11:36:48 faith systemd-udevd[369]: 0000:00:14.3: Worker [416] processing SEQNUM=3023 is taking a long time.
Feb 09 11:37:47 faith dracut-initqueue[450]: Timed out while waiting for udev queue to empty.
Feb 09 11:37:47 faith systemd[1]: Finished dracut initqueue hook.
The following (appearing in the failed log) appears to be where the Rule-based Manager stall happens:
Feb 09 11:37:48 faith systemd[1]: Stopping Rule-based Manager for Device Events and Files...
Feb 09 11:37:48 faith systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
Feb 09 11:37:48 faith systemd[1]: Stopped Virtual Console Setup.
Feb 09 11:37:48 faith systemd[1]: initrd-cleanup.service: Deactivated successfully.
Feb 09 11:37:48 faith systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
Feb 09 11:38:58 faith systemd-udevd[369]: 0000:00:14.3: Worker [416] processing SEQNUM=3023 killed.
Feb 09 11:38:58 faith systemd-udevd[369]: 0000:00:14.3: Worker [416] terminated by signal 9 (KILL).
Feb 09 11:38:58 faith systemd[1]: systemd-udevd.service: Deactivated successfully.
Feb 09 11:38:58 faith systemd[1]: Stopped Rule-based Manager for Device Events and Files.
And now I discover something strange: the logs apparently indicate that the system boots normally and successfully. They do not stop after systemd[1]: bpf-restrict-fs: LSM BPF program attached, but rather continue through all the normal boot steps, all the way to waiting for my password.
This would seem to indicate that it’s not the boot process breaking, but rather something about the display output that breaks at that exact point. However, so far, I can find no messages indicating anything unusual happening at that point in the boot.