slow boot with udoo quad

[tuxx]

Hi everyone!

I recently bought a udoo quad and the last days I have been experimenting with archlinuxarm. My only problem is the very slow boot. To be more specific:

$this->bbcode_second_pass_code('', 'systemd-analyze time
Startup finished in 2.579s (kernel) + 1min 21.291s (userspace) = 1min 23.870s')

$this->bbcode_second_pass_quote('', 's')ystemd-analyze blame
11.229s systemd-udev-trigger.service
10.309s tmp.mount
9.439s systemd-vconsole-setup.service
8.430s haveged.service
8.420s alsa-restore.service
7.670s dev-mqueue.mount
6.840s systemd-modules-load.service
6.340s sys-kernel-debug.mount
5.919s kmod-static-nodes.service
4.969s systemd-sysctl.service
3.339s systemd-logind.service
2.889s systemd-remount-fs.service
2.559s systemd-rfkill@rfkill0.service
2.308s user@0.service
2.239s systemd-random-seed.service
2.080s systemd-udevd.service
2.009s systemd-backlight@backlight:pwm-backlight.0.service
1.649s systemd-tmpfiles-setup-dev.service
1.630s var-log.mount
1.319s systemd-update-utmp.service
1.301s mnt-nas\x2dnfs.mount
1.233s systemd-journal-flush.service
1.039s systemd-user-sessions.service
974ms systemd-tmpfiles-clean.service
569ms systemd-tmpfiles-setup.service

[WarheadsSE]

Do us a favor:
$this->bbcode_second_pass_code('', '
systemd-analyze plot > udoo-quad-analyze.svg
')

[tuxx]

I tried to create the svg long before I posted here. For some reason, when i try to open the svg I see nothing. I also tested in my desktop pc (archlinux) and it works fine. I don't know what is happening with udoo installation.

Here is the content of the svg file:

http://pastebin.com/tYpGTeZM

[WarheadsSE]

Looks like systemd is suffering from the generation bug. there data is there. Is your system up to date?

[tuxx]

My latest installation was yesterday and the first thing I did was a pacman -Syu. It is fully updated. At the moment I am running a custom kernel (based on github pkgbuild) but the behavior is exactly the same with kernel from core repo.

[tuxx]

I did a clean install and I haven't touch anything this time (all packages are stock), in order to help developers with debugging information.

Please feel free to ask me for anything that might help solve this issue!

Edit: I also plugged an hdmi cable and unfortunately after the initial bootloader srcreen I am not able to see any output. Just a blank screen until it goes to login prompt.

Edit 2: my dmesg output: http://pastebin.com/7P3Yqb2p

Edit 3: is there any older image available I can try?

[andrenam]

adminempire hast set up an archlinuxarm rollback machine. You can find older images there.
viewtopic.php?f=8&t=6544

[tuxx]

thanks andrenam!

[tuxx]

I tested various previous snapshots and it seems that i found a solution, downgrading systemd (along with systemd-sysvcompat) and dbus (along with libdbus)

$this->bbcode_second_pass_code('', '[root@alarm ~]# systemd-analyze time
Startup finished in 2.621s (kernel) + 27.950s (userspace) = 30.572s
')

dbus version (1.8.0-1)
systemd version (208.11)

[tuxx]

I tested older images these days. April's image has exactly the same bad boot behavior. March's image runs fine but when I update systemd next boot is also problematic.

It's definately a systemd issue. Shall I open a bug report? Please, any of the developers feel free to ask me everything in order to help find the bug.

Regards,

Michael