Dear systemd folks,
I forgot to attach the logs.
Am 13.07.2018 um 20:20 schrieb Paul Menzel:
Trying to decrease the boot time, I got rid of the initrd. Now, there
is a noticeable delay between Linux `run_init_process()` and the first
systemd message.
I added an output line to the Linux function.
```
static int run_init_process(const char *init_filename)
{
argv_init[0] = init_filename;
pr_info("Run %s as init process\n", init_filename);
return do_execve(getname_kernel(init_filename),
(const char __user *const __user *)argv_init,
(const char __user *const __user *)envp_init);
}
```
Here you see the result on a system (ASRock E350M1) with an SDD
(spinning).
```
[ 0.287632] Run /sbin/init as init process
[ 0.547261] systemd[1]: systemd 239 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid)
```
The systemd binary is only 2.3 MB in size, so I do not think that
this is the loading time.
$ ls -lh /lib/systemd/systemd
-rwxr-xr-x 2 root root 2.3M Mar 12 13:44 /lib/systemd/systemd
Is there a way, to get a message from systemd as early as possible
to see where the time is spent?
`log_execution_mode(_boot)` is not at the beginning in
`main()` in `src/core/main.c`. I guess the “console” needs to be
set up first?
Any help is appreciated.
Kind regards,
Paul
[0.00] Linux version 4.18.0-rc4-00097-g33ec366fda95 (root@f2fc51708d66)
(gcc version 7.3.0 (Debian 7.3.0-24)) #96 SMP Fri Jul 13 15:26:28 UTC 2018
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0fff] type 16
[0.00] BIOS-e820: [mem 0x1000-0x0009] usable
[0.00] BIOS-e820: [mem 0x000c-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc7d3bfff] usable
[0.00] BIOS-e820: [mem 0xc7d3c000-0xc7ff] type 16
[0.00] BIOS-e820: [mem 0xc800-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00011eff] usable
[0.00] Notice: NX (Execute Disable) protection cannot be enabled:
non-PAE kernel!
[0.00] SMBIOS 2.7 present.
[0.00] DMI: ASROCK E350M1/E350M1, BIOS TIMELESS 01/01/1970
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0xc7d3c max_arch_pfn = 0x10
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00] 0-9 write-back
[0.00] A-B uncachable
[0.00] C-F write-back
[0.00] MTRR variable ranges enabled:
[0.00] 0 base 0FFC0 mask FFFC0 write-protect
[0.00] 1 base 0C000 mask FF800 write-back
[0.00] 2 base 08000 mask FC000 write-back
[0.00] 3 base 0 mask F8000 write-back
[0.00] 4 disabled
[0.00] 5 disabled
[0.00] 6 disabled
[0.00] 7 disabled
[0.00] TOM2: 00011f00 aka 4592M
[0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[0.00] Scanning 1 areas for low memory corruption
[0.00] initial memory mapped: [mem 0x-0x0fff]
[0.00] Base memory trampoline at [(ptrval)] 9b000 size 16384
[0.00] BRK [0x0fc61000, 0x0fc61fff] PGTABLE
[0.00] log_buf_len: 33554432 bytes
[0.00] early log buf free: 259860(99%)
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0800 24 (v02 CORE )
[0.00] ACPI: XSDT 0xC7D4D0E0 6C (v01 CORE COREBOOT
CORE )
[0.00] ACPI: FACP 0xC7D4F850 F4 (v04 CORE COREBOOT
CORE )
[0.00] ACPI: DSDT 0xC7D4D280 0025C7 (v02 ASROCK COREBOOT
00010001 INTL 20180629)
[0.00] ACPI: FACS 0xC7D4D240 40
[0.00] ACPI: FACS 0xC7D4D240 40
[0.00] ACPI: SSDT 0xC7D4F950 8A (v02 CORE COREBOOT
002A CORE 002A)
[0.00] ACPI: TCPA 0xC7D4F9E0 32 (v02 CORE COREBOOT
CORE )
[0.00] ACPI: APIC 0xC7D4FA20 5C (v01 CORE COREBOOT
CORE )
[0.00] ACPI: HEST 0xC7D4FA80 28 (v01 CORE COREBOOT
CORE )
[0.00] ACPI: SSDT 0xC7D4FAB0 00168E (v02 AMDALIB
0001 MSFT 0400)
[0.00] ACPI: SSDT 0xC7D51140 0003DE (v01 AMDPOWERNOW
0001 AMD 0001)
[0.00] ACPI: VFCT
