Hi,
I have been trying to boot the Mustang branch with acpi=force, but it stalls during the process I need to powercycle every time I enter that state. Checking setup_arch(), acpi_boot_table_init() seems to be ok, but it can not continue booting if disable_acpi() is not called before the block below:
if (acpi_disabled) { unflatten_device_tree(); psci_dt_init(); } else { psci_acpi_init(); }
Instead, calling disable_acpi() right after the block above ends up stalling. psci_acpi_init() does nothing on Mustang as it does not support the interface. Has anyone has an idea as to what's blocking the acpi=force boot process?
Itaru
On 08/17/2015 01:20 AM, Itaru Kitayama wrote:
I have been trying to boot the Mustang branch with acpi=force, but it stalls during the process I need to powercycle every time I enter that state.
Where does it "stall"? What's the last message you see? And if you're not using earlycon, please do so; that will help determine how far the boot is getting.
Checking setup_arch(), acpi_boot_table_init() seems to be ok, but it can not
How were those checked?
continue booting if disable_acpi() is not called before the block below:
if (acpi_disabled) { unflatten_device_tree(); psci_dt_init(); } else { psci_acpi_init(); }
Instead, calling disable_acpi() right after the block above ends up stalling.
Of course it does. The kernel has contradicting instructions: it has been told to *only* use ACPI tables (acpi=force), but then calling disable_acpi() tells the kernel to ignore ACPI tables. So, the kernel has no way to configure any of the devices on the motherboard.
psci_acpi_init() does nothing on Mustang as it does not support the interface. Has anyone has an idea as to what's blocking the acpi=force boot process?
Itaru
The kernel boots on the mustang I test with; I've attached a copy of the .config I use, just in case. Without at least some console output, I cannot determine anything. While it is true mustang does not support PSCI, it does boot.
Also, please make sure that the firmware being used is the very latest from APM (version 1.15, I believe). Without that firmware, there are several other problems that will show up that have already been fixed.