From owner-freebsd-current@freebsd.org Fri Jan 15 11:17:13 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 D8BBC4E16E7 for ; Fri, 15 Jan 2021 11:17:13 +0000 (UTC) (envelope-from SRS0=AybF=GS=FreeBSD.org=otis@ns2.wilbury.net) Received: from ns2.wilbury.net (ns2.wilbury.net [92.60.51.55]) (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 (2048 bits) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DHJYP0Wynz4nCY for ; Fri, 15 Jan 2021 11:17:12 +0000 (UTC) (envelope-from SRS0=AybF=GS=FreeBSD.org=otis@ns2.wilbury.net) Received: from chemex.owhome.lan (gw-upc.owhome.net [188.167.168.254]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id B987C45D061 for ; Fri, 15 Jan 2021 12:17:10 +0100 (CET) From: Juraj Lutter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: Waiting for bufdaemon Date: Fri, 15 Jan 2021 12:17:10 +0100 References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <20210115.201030.1395690536446474720.yasu@utahime.org> To: freebsd-current@freebsd.org In-Reply-To: <20210115.201030.1395690536446474720.yasu@utahime.org> Message-Id: <2649F5A1-AB7A-4054-A115-5C7D88DCE720@FreeBSD.org> X-Mailer: Apple Mail (2.3608.120.23.2.4) X-Rspamd-Queue-Id: 4DHJYP0Wynz4nCY X-Spamd-Bar: - X-Spamd-Result: default: False [-1.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; TO_DN_NONE(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[otis@FreeBSD.org,SRS0=AybF=GS=FreeBSD.org=otis@ns2.wilbury.net]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[92.60.51.55:from]; ASN(0.00)[asn:44185, ipnet:92.60.48.0/22, country:SK]; R_DKIM_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_NEQ_ENVFROM(0.00)[otis@FreeBSD.org,SRS0=AybF=GS=FreeBSD.org=otis@ns2.wilbury.net]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[92.60.51.55:from:127.0.2.255]; DMARC_NA(0.00)[FreeBSD.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; 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: Fri, 15 Jan 2021 11:17:13 -0000 > On 15 Jan 2021, at 12:10, Yasuhiro Kimura wrote: >=20 > From: Jakob Alvermark > Subject: Waiting for bufdaemon > Date: Fri, 15 Jan 2021 11:26:47 +0100 >=20 >> When rebooting my thinkpad the 'bufdaemon' times out: >>=20 >> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop >> ... timed out >>=20 >> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop >> ... timed out >>=20 >>=20 >> This started happening recently (within the last week I think). >>=20 >>=20 >> Any ideas? >=20 > I have been experiencing same problem with my 13-CURRENT amd64 > VirtualBox VM for about a month. The conditions that the problem > happens are unclear and all what I can say is >=20 > * It happens only after I login in the VM and do something for a > while. If I boot the VM and shut it down immediately, it never > happens. > * When the problem happens, one or more unkillable processes seem to > be left. I have been fighting with situations like this for month or two, opened = more PRs about it. My observation was that after putting some load on the machine, = mysterious mrsas(4) timeouts started to happen, processes were unkillable, reboots could not = complete in time... For sake of bisect, main-c255656-gb500c184b656 is known to work OK for = me as of now.