OK, I have managed to recreate the problem with plain Arch on EXT4, no ZFS stuff.

• Acpi Processor Aggregator
• Acpi Processor Aggregator Driver

The problem lies with the mkinitcpio-netconf module. If I include the netconf hook in /etc/mkinitcpio.conf together with ip=:::::eth2:dhcp kernel parameter I get no boot. I have to use acpi=off, remove the ip kernel parameter or remove the netconf hook to achieve successful boot. Nothing gets written to the journal on failed boots for some reason.

I have found others reporting problems with netconf: https://bbs.archlinux.org/viewtopic.php?id=213372

Commit b981513f806d (ACPI / scan: bail out early if failed to parse APIC ID for CPU) emits an error message if ACPI processor driver fails to query APIC ID for the CPU. All ACPI functionality is transparent to higher-level drivers. These drivers must make no assumptions about the presence or absence of an ACPI filter in any given device stack. Acpi.sys and the ACPI BIOS support the basic functions of an ACPI device. To enhance the functionality of an ACPI device, the device vendor can supply a WDM function driver. 6.2 1795 ACPI Table Signature Reservation Table 5-30 6.2 1781 Clarify ResourceUsage Descriptor Argument Table 6-193 6.2 1780 Add DescriptorName to PinFunction and PinConfig Macros Section 19.6.102 and Section 19.6.103 6.2 1770 Update Revision History Revision History 6.2 1769 FADT Format: ACPI Version update to reflect 6.2 versus 6.1 Table 5-33.

Any ideas on how to investigate further? Should a bug report be filed?

Edit: The issue is that Arch expects predictable interface names while netconf requires traditional interface names. Kudos to u/MrAbzDH on reddit: https://www.reddit.com/r/archlinux/comm … &context=3

is a workaround by using traditional interface names. There is no mention that I could find about this in the Wiki either on https://wiki.archlinux.org/index.php/ZF … ypted_root or https://wiki.archlinux.org/index.php/Dm … yssh,_ppp).

I am goint to work on an mkinitcpio-systemd-tool approach to this: https://github.com/random-archer/mkinit … /issues/62.
The Wiki should probably be updated on these topics.

Edit: This did not work for me. I tried to move from a busybox initramfs to a systemd initramfs only to discover that the required module for zfs on systemd initramfs (mkinitcpio-sd-zfs) does not support native ZFS encryption. This might work for people with LUKS.

Ultimately, my solution was to ditch mkinitcpio altogether and use dracut. I was using dracut with Centos and it seems much more capable of handling -at least- ZFS encrypted datasets.

What you need to make dracut work with this is:

dracut, obviously
systemd-networkd, not really needed but is my prefered way to handle networking. It is used to handle networking in early user space.
https://aur.archlinux.org/packages/dracut-sshd-git/ to handle the unlocking of the ZFS dataset through ssh

Here is my dracut conf:

systemd-networkd conf:

kernel command line parameters:

replace the pool/dataset as per your configuration.

Acpi Processor Aggregator

I will try to make a writeup on the Wiki at some point.

Last edited by rootpeer (2020-11-26 16:49:04)

Acpi Processor Aggregator Driver

Table A.1 acpi Driver List

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices