Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp434334imm; Thu, 5 Jul 2018 02:56:59 -0700 (PDT) X-Google-Smtp-Source: AAOMgpehJ1Y4PK8V13Hro45Q8/PSHTf/C6o0a8Vo1fTJAvYwfRLtGGXAAHbdPUuNfaWllKrVKPks X-Received: by 2002:a62:c699:: with SMTP id x25-v6mr5820264pfk.16.1530784619430; Thu, 05 Jul 2018 02:56:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530784619; cv=none; d=google.com; s=arc-20160816; b=NazP0uYzkychuC3Wel3K7NN722ALkPvGjFKspA6qui20Lh30aj2HMhQ5Kow0imVWQZ 4DRF0Mv/t1AZAt/mbqsRHr55uHwmpHCuJMBFfabWwC56+7Y/kNcWLy4FwG0oOAxg2psc S+QuauSyv90kwAcyzhb8mIjYvWe0+l28biVRTl+F9KeU5Lw3yZzTXxbSkyx4vxkXQdUG jnZ0xEIbS2YIKPure1fE9fawpHx/LVOmjcHa/57pefwxIPZziO+JPxvm0UA5TbwKGsrX 8h4mveADauJj5RlsVIUr7pRA+QzoHz7kseJl+XYzkj9n8Y2LdM5Ztk2Qb9RiMTXJwhEq N1Jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=CYVt74mmHn+AQ/Yc5Y8FfPDRhusx1SwKnv3nQUwFTgA=; b=Gd2uZj2FHj+rBU2WbX1vXAIVX762x3hBFZ0sfN18GWttKUBzDuMh4bv+dTDf8/k4D/ 8v5x20LzeTFNtQNnyIeGM2Quh4v8aUXvpxiueLk7IZU0W3j/KdeMFC8APmSvXWxNbU7X LEwnTt54Zt8HbH7o2d29u3/Da6dJwOchC4j8d+iURGk/va41Wjkuxlv8RUGIH8MAjHE0 1Yb0TLs9JpFrrDLUemoo8ykF9koaeUtDJC1vVIaBIq9VTDsTTo8ntLMHsQTfth7e4RdO SS2GXedoEDr+bC6Be950a1jcFw0rWh85VrP+fmMQPD0j44E5BE8CSTgrg+3Dl+uUJ70q 5zWQ== ARC-Authentication-Results: i=1; mx.google.com; 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 r87-v6si5902165pfj.331.2018.07.05.02.56.45; Thu, 05 Jul 2018 02:56:59 -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; 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 S1753372AbeGEJyw (ORCPT + 99 others); Thu, 5 Jul 2018 05:54:52 -0400 Received: from smtp1.it.da.ut.ee ([193.40.5.66]:34979 "EHLO smtp1.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753070AbeGEJyv (ORCPT ); Thu, 5 Jul 2018 05:54:51 -0400 Received: from math.ut.ee (unknown [IPv6:2001:bb8:2002:2400:5054:ff:fe3b:8db9]) by smtp1.it.da.ut.ee (Postfix) with ESMTP id B314B901AA; Thu, 5 Jul 2018 12:54:49 +0300 (EEST) Received: by math.ut.ee (Postfix, from userid 1014) id 9562B2207B4; Thu, 5 Jul 2018 12:54:47 +0300 (EEST) Received: from localhost (localhost [127.0.0.1]) by math.ut.ee (Postfix) with ESMTP id 986002206D8; Thu, 5 Jul 2018 12:54:47 +0300 (EEST) Date: Thu, 5 Jul 2018 12:54:47 +0300 (EEST) From: Meelis Roos To: Arnd Bergmann cc: Linux Kernel list Subject: Re: 4.18-rc* regression: x86-32 troubles (with timers?) In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > 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. -- Meelis Roos (mroos@linux.ee)