From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [VDSO] [x86_32] v5-3-rc1 needs vdso32=0 to get systemd-journald running
Date: Fri, 26 Jul 2019 09:20:44 -0700 [thread overview]
Message-ID: <20190726162044.GA5978@linux.intel.com> (raw)
In-Reply-To: <618de21a4510f20f1b38a894517b5e9011f0da69.camel@tiscali.nl>
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:
https://lkml.kernel.org/r/20190719170343.GA13680@linux.intel.com
next prev parent reply other threads:[~2019-07-26 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 16:13 [VDSO] [x86_32] v5-3-rc1 needs vdso32=0 to get systemd-journald running Paul Bolle
2019-07-26 16:20 ` Sean Christopherson [this message]
2019-07-26 17:12 ` Paul Bolle
2019-07-26 17:57 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190726162044.GA5978@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.