From owner-freebsd-current@freebsd.org Fri Jan 15 15:45:15 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 31E2C4E99E6 for ; Fri, 15 Jan 2021 15:45:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DHQVf668Kz57WZ; Fri, 15 Jan 2021 15:45:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 10FFj7ha096344 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 15 Jan 2021 17:45:10 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 10FFj7ha096344 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 10FFj7hD096342; Fri, 15 Jan 2021 17:45:07 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 15 Jan 2021 17:45:07 +0200 From: Konstantin Belousov To: =?utf-8?Q?Mika=C3=ABl?= Urankar Cc: freebsd-current Subject: Re: Waiting for bufdaemon Message-ID: References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4DHQVf668Kz57WZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] 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:45:15 -0000 On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote: > 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) Please show me the output from sysctl kern.timecounter kern.eventtimer and first 100 lines of dmesg from the verbose boot (that contains the CPU ident lines).