Need help booting allmodconfig on arm64

Need help booting allmodconfig on arm64

[Timur Tabi]

I'm trying to boot an allmodconfig kernel on my arm64 ACPI system, and
although I'm very close, I can't seem to get the kernel to boot the
rootfs.

I build using this command:

make ARCH=arm64 KCONFIG_ALLCONFIG=boot-allmod.config allmodconfig

where boot-allmod.config contains this:

CONFIG_CPU_BIG_ENDIAN=n
CONFIG_SERIAL_AMBA_PL011=y
CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
CONFIG_DEBUG_KOBJECT_RELEASE=n
CONFIG_DEBUG_TEST_DRIVER_REMOVE=n
CONFIG_KASAN=n
CONFIG_FTRACE_STARTUP_TEST=n
CONFIG_DEBUG_BLOCK_EXT_DEVT=n
CONFIG_EXT4_FS=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=y
CONFIG_CMDLINE_FORCE=n
CONFIG_DEBUG_WX=n

The last few lines of dmesg are:

   96.588564] ### dt-test ### FAIL
of_unittest_overlay_high_level():2131 overlay_base_root not
initialized
[   96.597878] ### dt-test ### end of unittest - 142 passed, 1 failed
[   96.604056] PM: Hibernation image not present or could not be loaded.
[   96.610767] Unable to open file: /etc/keys/x509_ima.der (-2)
[   96.610814] Unable to open file: /etc/keys/x509_evm.der (-2)
[   96.621504] Freeing unused kernel memory: 8192K
[   96.630749] rodata_test: all tests were successful
[   96.635768] Failed to execute /init (error -8)

It boots to my initramfs, but not my SATA rootfs.  I think the problem
is that /init is a shell script, and there's no interpreter?

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

Need help booting allmodconfig on arm64

[Russell King - ARM Linux]

On Thu, Jun 01, 2017 at 05:43:20PM -0500, Timur Tabi wrote:
> I'm trying to boot an allmodconfig kernel on my arm64 ACPI system, and
> although I'm very close, I can't seem to get the kernel to boot the
> rootfs.
> 
> I build using this command:
> 
> make ARCH=arm64 KCONFIG_ALLCONFIG=boot-allmod.config allmodconfig
> 
> where boot-allmod.config contains this:
> 
> CONFIG_CPU_BIG_ENDIAN=n
> CONFIG_SERIAL_AMBA_PL011=y
> CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
> CONFIG_DEBUG_KOBJECT_RELEASE=n
> CONFIG_DEBUG_TEST_DRIVER_REMOVE=n
> CONFIG_KASAN=n
> CONFIG_FTRACE_STARTUP_TEST=n
> CONFIG_DEBUG_BLOCK_EXT_DEVT=n
> CONFIG_EXT4_FS=y
> CONFIG_SATA_AHCI=y
> CONFIG_SATA_AHCI_PLATFORM=y
> CONFIG_CMDLINE_FORCE=n
> CONFIG_DEBUG_WX=n
> 
> The last few lines of dmesg are:
> 
>    96.588564] ### dt-test ### FAIL
> of_unittest_overlay_high_level():2131 overlay_base_root not
> initialized
> [   96.597878] ### dt-test ### end of unittest - 142 passed, 1 failed
> [   96.604056] PM: Hibernation image not present or could not be loaded.
> [   96.610767] Unable to open file: /etc/keys/x509_ima.der (-2)
> [   96.610814] Unable to open file: /etc/keys/x509_evm.der (-2)
> [   96.621504] Freeing unused kernel memory: 8192K
> [   96.630749] rodata_test: all tests were successful
> [   96.635768] Failed to execute /init (error -8)
> 
> It boots to my initramfs, but not my SATA rootfs.  I think the problem
> is that /init is a shell script, and there's no interpreter?

Have you checked that BINFMT_SCRIPT is not modular?

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

Need help booting allmodconfig on arm64

[Timur Tabi]

On 06/01/2017 05:50 PM, Russell King - ARM Linux wrote:
>>
>> It boots to my initramfs, but not my SATA rootfs.  I think the problem
>> is that /init is a shell script, and there's no interpreter?
> Have you checked that BINFMT_SCRIPT is not modular?

That helped, thanks.

Now I don't have any /dev/sdX entries, so I can't mount my SATA drive. 
I'm trying to parse the initramfs disks, but I don't know what to look 
for.  How do the /dev/sdX entries normally appear?

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

Need help booting allmodconfig on arm64

[Florian Fainelli]

On 06/01/2017 04:26 PM, Timur Tabi wrote:
> On 06/01/2017 05:50 PM, Russell King - ARM Linux wrote:
>>>
>>> It boots to my initramfs, but not my SATA rootfs.  I think the problem
>>> is that /init is a shell script, and there's no interpreter?
>> Have you checked that BINFMT_SCRIPT is not modular?
> 
> That helped, thanks.
> 
> Now I don't have any /dev/sdX entries, so I can't mount my SATA drive.
> I'm trying to parse the initramfs disks, but I don't know what to look
> for.  How do the /dev/sdX entries normally appear?

What happens when you enable CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT?
-- 
Florian

Need help booting allmodconfig on arm64

[Timur Tabi]

On 6/1/17 6:54 PM, Florian Fainelli wrote:
>> Now I don't have any /dev/sdX entries, so I can't mount my SATA drive.
>> I'm trying to parse the initramfs disks, but I don't know what to look
>> for.  How do the /dev/sdX entries normally appear?

> What happens when you enable CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT?

They are already set to =y.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.

Need help booting allmodconfig on arm64

[Mark Rutland]

On Thu, Jun 01, 2017 at 06:26:34PM -0500, Timur Tabi wrote:
> On 06/01/2017 05:50 PM, Russell King - ARM Linux wrote:
> >>
> >>It boots to my initramfs, but not my SATA rootfs.  I think the problem
> >>is that /init is a shell script, and there's no interpreter?
> >Have you checked that BINFMT_SCRIPT is not modular?
> 
> That helped, thanks.
> 
> Now I don't have any /dev/sdX entries, so I can't mount my SATA
> drive. I'm trying to parse the initramfs disks, but I don't know
> what to look for.  How do the /dev/sdX entries normally appear?

Do you laod the relevant drivers in your initramfs?

Per the commadns you gave, the SATA driver would be modular in your config:

CONFIG_SATA_AHCI=m
CONFIG_SATA_AHCI_PLATFORM=m

Thanks,
Mark.

Need help booting allmodconfig on arm64

[Timur Tabi]

On 6/2/17 3:36 AM, Mark Rutland wrote:
> CONFIG_SATA_AHCI=m
> CONFIG_SATA_AHCI_PLATFORM=m

Ah, I had to set CONFIG_ATA=y for those two lines to take. 
Unfortunately, even with this fix, there still aren't any /dev/sdX 
entries.

I pasted by /dev tree to https://pastebin.com/3najnguB and my dmesg to 
https://pastebin.com/EvFEJJth.

You can see the SATA driver loading and probing, isn't that enough to 
create the /dev entries?

When my /init script runs, I think it's trying to mount the SATA drive:

Begin: Waiting for root file system ... Begin: Running 
/scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

(this repeats for another minute).

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.

Need help booting allmodconfig on arm64

[Russell King - ARM Linux]

On Fri, Jun 02, 2017 at 08:50:08AM -0500, Timur Tabi wrote:
> On 6/2/17 3:36 AM, Mark Rutland wrote:
> >CONFIG_SATA_AHCI=m
> >CONFIG_SATA_AHCI_PLATFORM=m
> 
> Ah, I had to set CONFIG_ATA=y for those two lines to take. Unfortunately,
> even with this fix, there still aren't any /dev/sdX entries.
> 
> I pasted by /dev tree to https://pastebin.com/3najnguB and my dmesg to
> https://pastebin.com/EvFEJJth.
> 
> You can see the SATA driver loading and probing, isn't that enough to create
> the /dev entries?

ATA devices appear via the SCSI layer, which means you need the SCSI disk
driver, CONFIG_BLK_DEV_SD, for ATA disks to be visible as block devices.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

Need help booting allmodconfig on arm64

[Timur Tabi]

On 06/02/2017 03:01 PM, Russell King - ARM Linux wrote:
> ATA devices appear via the SCSI layer, which means you need the SCSI disk
> driver, CONFIG_BLK_DEV_SD, for ATA disks to be visible as block devices.

Great, that fixed that problem.

I also had to set CONFIG_UNIX=y and CONFIG_AUTOFS4_FS=y so that udev 
would start, but it's still not quite 100% there.  lsmod still shows no 
drivers being loaded.  All of the modules were copied on the initramfs, 
why aren't they being loaded?

A couple boot log messages stand out:

[ TIME ] Timed out waiting for device 
dev-disk-by\x2duuid-AB6C\x2d1CCA.device.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File Systems.


-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

Need help booting allmodconfig on arm64

[Russell King - ARM Linux]

On Fri, Jun 02, 2017 at 06:01:55PM -0500, Timur Tabi wrote:
> On 06/02/2017 03:01 PM, Russell King - ARM Linux wrote:
> >ATA devices appear via the SCSI layer, which means you need the SCSI disk
> >driver, CONFIG_BLK_DEV_SD, for ATA disks to be visible as block devices.
> 
> Great, that fixed that problem.
> 
> I also had to set CONFIG_UNIX=y and CONFIG_AUTOFS4_FS=y so that udev would
> start, but it's still not quite 100% there.  lsmod still shows no drivers
> being loaded.  All of the modules were copied on the initramfs, why aren't
> they being loaded?
> 
> A couple boot log messages stand out:
> 
> [ TIME ] Timed out waiting for device
> dev-disk-by\x2duuid-AB6C\x2d1CCA.device.
> [DEPEND] Dependency failed for /boot/efi.
> [DEPEND] Dependency failed for Local File Systems.

Sounds like systemd?  Systemd has a list of requirements that it makes
of the kernel, I guess you're missing some of those requirements.
Check the systemd docs (/usr/share/doc/systemd/README ?) under
"REQUIREMENTS".

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.