Messages in this thread | | | Subject | [VDSO] [x86_32] v5-3-rc1 needs vdso32=0 to get systemd-journald running | From | Paul Bolle <> | Date | Fri, 26 Jul 2019 18:13:54 +0200 |
| |
My first attempts to boot v5.3-rc1 on my (ancient) ThinkPad X41 made systemd- journald crash. I kept ending up with nasty my messages on the console:
Starting Journal Service... [...] [ 7.143552] systemd-journald[213]: Assertion 'clock_gettime(map_clock_id(clock_id), &ts) == 0' failed at ../src/basic/time-util.c:55, function now(). Aborting. [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ 7.220367] systemd-coredump[217]: Cannot resolve systemd-coredump user. Proceeding to dump core as root: No such process [ OK ] Stopped Journal Service.
And without systemd-journald I couldn't get userspace up and running.
A bit of tinkering showed that "vdso32=0" on the kernel command line allows me to get a usable userspace.
Any idea where I should look next to pinpoint this?
Thanks,
Paul Bolle
| |