From owner-freebsd-current@freebsd.org Sat Mar 6 10:01:48 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 145B355FC7D for ; Sat, 6 Mar 2021 10:01:48 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from maybe.home.utahime.org (gate.home.utahime.org [183.180.29.210]) (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 4Dt0WH1L1Tz3PwM for ; Sat, 6 Mar 2021 10:01:46 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by maybe.home.utahime.org (Postfix) with ESMTPS id 06AE52DA04 for ; Sat, 6 Mar 2021 19:01:37 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=utahime.org; s=maybe2019112701; t=1615024897; bh=82B30qpFplCpdDPD/ymx/gVX9lHSCkH7wUUxzwtYsRA=; h=Date:To:Subject:From:In-Reply-To:References; b=PH4WMbyNzJTDt0EDUwtbHfaEhCV/ALoEqbjz15jTsKC8vLeR7KNXWqps7IzAKxDXg UYo2rgCTjSFZ1IReAwKvU/kzz5Ci/tFRMrF0oJ4Wrjhwg4nkkVmHpXRjL08coGG6Q8 j1zdjdtGJRBeeUsmPTVEkhpErTUbuQ1jd4V+vHqguQ3oeJ2sHlz1CvzuxHp9LfmzBL 2od/6UyljTpj1LHOi/RGCScjN/dU0Qoj8Fu5Ijc+nYM31d1/QJwvXSmo8KORNGTHn8 oktBOnAUin45qf+jNikeK5MoklJjQw6EoyepxRLFel4MFuE3XRm6RtqHAosEV48fZu LHADRfhbUhRKg== Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 6AB462F153; Sat, 6 Mar 2021 19:01:34 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.1 at eastasia.home.utahime.org Date: Sat, 06 Mar 2021 18:59:55 +0900 (JST) Message-Id: <20210306.185955.1096959917131550098.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon From: Yasuhiro Kimura In-Reply-To: <20210306.083323.1112779300812727243.yasu@utahime.org> <20210306005643.45feb56d@bsd64.grem.de> <8a549830a3087998c1e2f80a5fb58199@bsdforge.com> References: <20210305.160311.867123118349124334.yasu@utahime.org> <20210306.083323.1112779300812727243.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dt0WH1L1Tz3PwM X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=utahime.org header.s=maybe2019112701 header.b=PH4WMbyN; dmarc=none; spf=pass (mx1.freebsd.org: domain of yasu@utahime.org designates 183.180.29.210 as permitted sender) smtp.mailfrom=yasu@utahime.org X-Spamd-Result: default: False [-0.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; TO_DN_NONE(0.00)[]; HFILTER_HELO_IP_A(1.00)[maybe.home.utahime.org]; HFILTER_HELO_NORES_A_OR_MX(0.30)[maybe.home.utahime.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[utahime.org:+]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[183.180.29.210:from]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[utahime.org:s=maybe2019112701]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[utahime.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[183.180.29.210:from:127.0.2.255]; MID_CONTAINS_FROM(1.00)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] 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: Sat, 06 Mar 2021 10:01:48 -0000 From: Yasuhiro Kimura Subject: Re: Waiting for bufdaemon Date: Sat, 06 Mar 2021 08:33:23 +0900 (JST) >> My belief is that this commit helps more users than it hurts. Namely, >> the VMWare and KVM users, which are majority, use fast timecounter, >> comparing to the more niche hypervisors like VirtualBox. >> >> For you, a simple but manual workaround, setting the timecounter to >> ACPI (?) or might be HPET, with a loader tunable, should do it. > > Then please let me know the name of it. From: Michael Gmelin Subject: Re: Waiting for bufdaemon Date: Sat, 6 Mar 2021 00:56:43 +0100 > see `man 4 timecounters': > > https://www.freebsd.org/cgi/man.cgi?query=timecounters From: Mark Millard via freebsd-current Subject: Re: Waiting for bufdaemon Date: Fri, 5 Mar 2021 17:35:14 -0800 > Its somewhat messy but there is a technique of using > the "timecounter" in kib's wording to explore: ... From: Chris Subject: Re: Waiting for bufdaemon Date: Fri, 05 Mar 2021 18:54:05 -0800 > Not exactly what you're asking for. But sysctl sysctl(3) and loader(8) > will provide some good clues. Thank you for reply. On the system in question 'kern.timecounter.choice' and 'kern.timecounter.hardware' tunables have following values. ---------------------------------------------------------------------- yasu@rolling-vm-freebsd1[1002]% sysctl kern.timecounter.choice kern.timecounter.choice: ACPI-fast(900) i8254(0) TSC-low(-100) dummy(-1000000) yasu@rolling-vm-freebsd1[1003]% sysctl kern.timecounter.hardware kern.timecounter.hardware: ACPI-fast yasu@rolling-vm-freebsd1[1004]% ---------------------------------------------------------------------- So I tried setting the latter to 'i8254', 'TSC-low' and 'dummy', and checked if the problem disappear. But unfortunately it still happened. On the contrary changing the value from default made thing worse. If it is set to either 'i8254' or 'TSC-low', timeout of bufdaemon also happens when I shutdown the system just after bootstrap is completed. And if it is set to 'dummy', the sytem hung up in the middle of bootstrap. So setting 'kern.timecounter.hardware' tunable doesn't work in my case. Then is there any way to try? --- Yasuhiro Kimura