Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp495704imm; Thu, 5 Jul 2018 04:06:14 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcjcNqTvU/8vd0IuIJs5ZDiHgEwj2Y2mRJep2Kv6CM7nLClGWw+qBazdHw+cYqK6SeCA08N X-Received: by 2002:a17:902:280b:: with SMTP id e11-v6mr5694972plb.298.1530788774194; Thu, 05 Jul 2018 04:06:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530788774; cv=none; d=google.com; s=arc-20160816; b=ReuUdSeSFMjHPU4hli/KefhLniLidb6KuB5n/sELTN4iAzfNO7vTsHOXyYBVBzS9ZJ TxGxEFQ43Bbz/pFVpIkM6S77Up7hk2bnmWrVK8/U3abUQNocdoe8SydwRDsc4EkiHkuu v3OxmtEK1K40sud0OvHxn7dy9Jd0Qi4zDrr41TvGQwz5VFLebUnDTvks1lnHNHFq0AbG 109fhLxXsc5U9d5A+3diV4L3EfoBGlNGxzmnm+bzt9g+iOpZIhIIsyI7dFGmnauWvOcY PlsyeoVSKiaLmUwxizkIANRnsbEN49xtv7CrgOF9SefvSnrIFwz79zOMVMjGMFEaMdjd rJog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=SBIU8mJwqceYPkVd6F5eyRUeCJ0GWkoAyBk5rLNHqJc=; b=zSz/qQAyo0I0VOsExZFCmsz0dq3O8+ciB7EttWkw7rkldS5hzeiAR/p8gM0GGAa1Xw 7aYZr20hRzgWLQugKFuncvB4fFmMN6ebU2LWQTbAQb9I4/SXwR/p+5Ho3Ud6NY6V+Mf0 pU2V4Mg37gjWkV083asFHqTHh+9wkckQGLualIyyQdTqEGxU8Frco5Eoi/pVFluQI0DS YtbvVzjsdV0Q3W+LBTr6xJvcu73yNBiWV7xbkxZl9U/MO1ZePTdlTWTWx4SacIbk6tgn 2k4A3VllyKrV+TVyHoYxNi9a8Aos8I4/OTumVgnovBtAwbUyst5LWJTTTH//jq0mUV7V YBcQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=pF4Q7tWh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n9-v6si5162462pgp.558.2018.07.05.04.05.59; Thu, 05 Jul 2018 04:06:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=pF4Q7tWh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753667AbeGELE1 (ORCPT + 99 others); Thu, 5 Jul 2018 07:04:27 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:38753 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753437AbeGELE0 (ORCPT ); Thu, 5 Jul 2018 07:04:26 -0400 Received: by mail-lf0-f65.google.com with SMTP id a4-v6so6608346lff.5 for ; Thu, 05 Jul 2018 04:04:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SBIU8mJwqceYPkVd6F5eyRUeCJ0GWkoAyBk5rLNHqJc=; b=pF4Q7tWhgU1NcbbhuChThPR3ts2IXXt8cUtJcVC/As1JI4VXBhQWIaT1gYlFQW62NZ r4Mh1KJmiyvvXfoB8J/usYQi11+9QXL724nATKCUCDxZzUKSatYlaKytND9/hxHZCOoi egz5bLaJZYsVYd53Hq0QZkxTHejBfX3bQuC/Dn0Cxzer4suemcAM/WC9abQfTnQFP4Ff myhZExzXevuORwhG3OMpCMXMw0o6X2g8hpLzCJdM5nm87R/9zyYSawyXU8TeEJZSm2Kp a3wm9DuExvzwmcbDLfZSLC8Uu785gTkeyGcZyyjpAGGFYs4JjTX/Oz4+ynbcGNmmxfFs nEoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=SBIU8mJwqceYPkVd6F5eyRUeCJ0GWkoAyBk5rLNHqJc=; b=CbMn4m9/Pu7rtmmcogJs9Aacp6xVPdYnz0nxQfp3m+dOzw5lb7SiApO3HaaSyFK1Fy dGX3UlHkLlfcRI7YjjuAh1iCvAh5OH9tj0QOMNyPqI8X2sDskQEeOWKFtbmiZiG3l4fd JkjXeE7DKedRjzPKmdUeD9HXbMoMx/EZG+O0W6AR8dBSj2biibuSIeWiOfN/gOr/hYZi AlIXqGGSmdS4CbGkgIjlDJvA+eJ3BpmB/PiUB8IanXrcrdHvoikoF9+zm3CLUeyRbQ7/ s/E3ODw2uTaUc8kBaDv81WeLFNvajSbnzScDzCCRRSeW/OgZFaZLEMC6C3/yTdunEyiB 2sQw== X-Gm-Message-State: APt69E2SmMyvCHp7ZneBAqe35yRSf3eVvgUe/lOhN2IaCCGxe/1UZ9wC nPcI+RbLam10wTgaAmQGxSpJokPE2M5bIefNrQCNqVKG X-Received: by 2002:a19:a705:: with SMTP id q5-v6mr2885843lfe.148.1530788664764; Thu, 05 Jul 2018 04:04:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:41c1:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 04:04:23 -0700 (PDT) In-Reply-To: References: From: Arnd Bergmann Date: Thu, 5 Jul 2018 13:04:23 +0200 X-Google-Sender-Auth: H8BWQi4P54BTIxik_ofiqn0FCdk Message-ID: Subject: Re: 4.18-rc* regression: x86-32 troubles (with timers?) To: Meelis Roos Cc: Linux Kernel list Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 5, 2018 at 11:54 AM, 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. >> >> That does sound like it is related to my patches indeed. If you are not >> yet done bisecting, please checkout commit e27c49291a7f ("x86: Convert >> x86_platform_ops to timespec64") before you try anything else, that >> one is the top of the branch with my changes. If that fails, the bisection >> will be much quicker. > > This commit was fine. So it's likely something else. Ok, at least that's a relief for me, even if it didn't help you ;-) I looked at the sources a bit and found that the assertion is triggered in systemd whenever we try to read a clock that the kernel does not provide. You have CONFIG_POSIX_TIMERS and CLOCK_RTC_CLASS set, so all the normal clocks should be operational, and I don't see anything unusual being passed into clock_gettime() from systemd. If you are able to find out what clock_id is passed in here, and what the return code is, that might still lead to a solution more quickly than continuing the bisection. Arnd