Received: by 10.192.165.148 with SMTP id m20csp4423293imm; Tue, 24 Apr 2018 02:26:48 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+WqATXCxyCXY5DZ2MMaUrcOSzhYPMLO3N6O8dA0grAFTcdB8qKTraqAKvry82dp9L+sP9c X-Received: by 10.98.10.72 with SMTP id s69mr22877483pfi.134.1524562008642; Tue, 24 Apr 2018 02:26:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524562008; cv=none; d=google.com; s=arc-20160816; b=UhNDWDN6DL9BprPCFZUyUrFS6pvslwqU94TjN93hsJT5mJ16Z5AiG4Lf1YHRhSpvrR Wwo8Fi+4J3emNbc3Gap8jzzi8wZx2XOfVk3ESM6gjCcHE2DDQM23hIPC6bkdYNqqQviS dr/TSvVU5qxaNY/0PtD/iuhR5BPblTNhkvYJRWgeiAdRDXSlpmiLof0rDvNwhlbnI4PT ujj6n2rxZc3Y/hJm6KIhcOYevw5ZwtWLVnHTWetz7RCdzXs0MO0ODPFcmBNpmLYHImWL p+QT013nt8PJA549ym6honSpc+0dwSd4YteWHYCxk5GsBQQQIwAxBb4jPk8zbe4GzvsU Ohpw== 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=is33Q4whpSkhY2E/s4AKVAzobnaVpi3OLwWgCINXKk8=; b=dnbhTqeAyqbOKAecVv9kGFymKyDDwXc+t4kjOfrKZ+j5E3KtUyoJedJISoNmMQChU8 myJWxZFgaiY7Rj9y8zf3b9VPJaW2XzRfzJNjCSBN7AQbThqq1OhDPYAKS9FVxwR78fIE LyEOqJ8il1P53cfWA/3m7s/XNIHySTUunAh2JK1aeLF03YMd4N8us/GZN+N5UuIn4OWl 6AwL6wPxjhEnnnSfbCD1tJUUcrSGXeJ06anBVS2Hio4Ldas+2D5UKv51T8FrVqZj/3iv pJ0HhgY8VYD1q4DpJcKugbeniYgfDcjXbaqsijRPRH+U+0MaIPMRKMZN1DQ00RvAa03m tydA== 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 y11-v6si13255653plg.154.2018.04.24.02.26.34; Tue, 24 Apr 2018 02:26:48 -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 S1753440AbeDXJG1 (ORCPT + 99 others); Tue, 24 Apr 2018 05:06:27 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34577 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbeDXJGY (ORCPT ); Tue, 24 Apr 2018 05:06:24 -0400 Received: from p5492e61e.dip0.t-ipconnect.de ([84.146.230.30] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fAtu0-0001KA-Bk; Tue, 24 Apr 2018 11:06:20 +0200 Date: Tue, 24 Apr 2018 11:06:19 +0200 (CEST) From: Thomas Gleixner To: Peter Zijlstra cc: Diego Viola , linux-kernel@vger.kernel.org, len.brown@intel.com, rui.zhang@intel.com, "Rafael J. Wysocki" Subject: Re: Experiencing freezes with kernel 4.16.3 on a desktop with E5500 CPU (bisect included) In-Reply-To: <20180423164425.GS4129@hirez.programming.kicks-ass.net> Message-ID: References: <20180423091633.GU4064@hirez.programming.kicks-ass.net> <20180423114850.GK4082@hirez.programming.kicks-ass.net> <20180423123847.GL4082@hirez.programming.kicks-ass.net> <20180423155801.GQ4129@hirez.programming.kicks-ass.net> <20180423164425.GS4129@hirez.programming.kicks-ass.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 23 Apr 2018, Peter Zijlstra wrote: > On Mon, Apr 23, 2018 at 05:58:01PM +0200, Peter Zijlstra wrote: > > Thomas, we could not find the de-rate stuff, but the above can be > > simplified; what happens is: > > > > cs->flags |= UNSTABLE; > > schedule_work(&watchdog_work) > > kthread_run(clocksource_watchdog_kthread) > > Also, Thomas, do you remember why we spawn a short running kthread from > a work ? Can't we simply run the whole thing from the worker thread? No. I think we did it directly in the early days and then it was changed to that worker/thread stuff for whatever reason. I need to do git archaeology. Thanks, tglx