Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jan 2021 12:17:10 +0100
From:      Juraj Lutter <otis@FreeBSD.org>
To:        freebsd-current@freebsd.org
Subject:   Re: Waiting for bufdaemon
Message-ID:  <2649F5A1-AB7A-4054-A115-5C7D88DCE720@FreeBSD.org>
In-Reply-To: <20210115.201030.1395690536446474720.yasu@utahime.org>
References:  <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <20210115.201030.1395690536446474720.yasu@utahime.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 15 Jan 2021, at 12:10, Yasuhiro Kimura <yasu@utahime.org> wrote:
>=20
> From: Jakob Alvermark <jakob@alvermark.net>
> 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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2649F5A1-AB7A-4054-A115-5C7D88DCE720>