From owner-freebsd-current@freebsd.org Fri Jan 15 15:30:21 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D0884E90E9 for ; Fri, 15 Jan 2021 15:30:21 +0000 (UTC) (envelope-from mikael@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DHQ9T0QpHz56nD for ; Fri, 15 Jan 2021 15:30:21 +0000 (UTC) (envelope-from mikael@FreeBSD.org) Received: from [192.168.1.2] (112.56.88.79.rev.sfr.net [79.88.56.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: mikael) by smtp.freebsd.org (Postfix) with ESMTPSA id C45D2F3CA for ; Fri, 15 Jan 2021 15:30:20 +0000 (UTC) (envelope-from mikael@FreeBSD.org) Subject: Re: Waiting for bufdaemon To: freebsd-current References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> From: =?UTF-8?Q?Mika=c3=abl_Urankar?= Message-ID: <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> Date: Fri, 15 Jan 2021 16:30:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2021 15:30:21 -0000 On 15/01/2021 16:02, Konstantin Belousov wrote: > On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote: >> On 15/01/2021 11:26, Jakob Alvermark wrote: >>> Hi, >>> >>> >>> When rebooting my thinkpad the 'bufdaemon' times out: >>> >>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed >>> out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop >>> ... timed out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop >>> ... timed out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop >>> ... timed out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop >>> ... timed out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop >>> ... timed out >>> >>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop >>> ... timed out >>> >>> >>> This started happening recently (within the last week I think). >> >> Hi, >> >> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal. >> >> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned >> groups) "seems" ok >> >> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP >> support), affected by the timeout. >> >> I haven't tried the intermediate commit yet. >> >> My intel machine doesn't seem to be affected > > If you revert only 9e680e4005b7, is it fixed ? > Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests, I can do more if you want)