[lkml]   [2019]   [Jul]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [VDSO] [x86_32] v5-3-rc1 needs vdso32=0 to get systemd-journald running
On Fri, Jul 26, 2019 at 06:13:54PM +0200, Paul Bolle wrote:
> 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?

More than likely it's this:

 \ /
  Last update: 2019-07-26 18:21    [W:0.029 / U:2.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site