From: Pavel Machek <pavel@ucw.cz>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: 4.18-rc* regression: x86-32 troubles (with timers?)
Date: Tue, 10 Jul 2018 11:32:44 +0200 [thread overview]
Message-ID: <20180710093244.GB31518@amd> (raw)
In-Reply-To: <alpine.LRH.2.21.1807041414080.3671@math.ut.ee>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Wed 2018-07-04 14:41:08, Meelis Roos wrote:
> I tried 4.18.0-rc1-00023-g9ffc59d57228 and now
> 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other
> 32-bit machines, and got half-failed bootup - kernel and userspace come
> up but some services fail to start, including network and
> systemd-journald:
>
> systemd-journald[85]: Assertion 'clock_gettime(map_clock_id(clock_id), &ts) == 0' failed at ../src/basic/time-util.c:53, function now(). Aborting.
>
> I then tried multiple other machines. All x86-64 machines seem
> unaffected, some x86-32 machines are affected (Athlon with AMD750
> chipset, Fujitsu RX100-S2 with P4-3.4, and P4 with Intel 865 chipset),
> some very similar x86-32 machines are unaffected. I have different
> customized kernel configuration on them, so far I have not pinpointed
> any configuration option to be at fault.
>
> All machines run Debian unstable.
>
> 4.17.0 was working fine.
>
> Will continue with bisecting between 4.17.0 and
> 4.18.0-rc1-00023-g9ffc59d57228.
Details of my tests (.config, dmesg, versions) can be found in
https://github.com/pavelmachek/missy/tree/master/db/notebook/lenovo/thinkpad/x60/pavel/2018.3648830947643
(and nearby directories).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-07-10 9:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 11:41 4.18-rc* regression: x86-32 troubles (with timers?) Meelis Roos
2018-07-04 21:02 ` Arnd Bergmann
2018-07-05 9:54 ` Meelis Roos
2018-07-05 11:04 ` Arnd Bergmann
2018-07-15 15:05 ` Meelis Roos
2018-07-15 20:51 ` Arnd Bergmann
2018-07-16 16:49 ` Meelis Roos
2018-07-16 19:00 ` Meelis Roos
2018-07-20 20:56 ` Meelis Roos
2018-07-20 23:01 ` bisected: " Meelis Roos
2018-07-23 16:03 ` Arnd Bergmann
2018-07-23 19:41 ` Daniel Borkmann
2018-07-23 20:34 ` Meelis Roos
2018-07-23 22:04 ` Daniel Borkmann
2018-07-24 4:47 ` Meelis Roos
2018-07-24 18:40 ` Daniel Borkmann
2018-07-24 6:11 ` Meelis Roos
2018-07-10 9:30 ` Pavel Machek
2018-07-10 9:32 ` Pavel Machek [this message]
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=20180710093244.GB31518@amd \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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.