Date: Tue, 22 Oct 2019 16:19:52 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: thread on sleepqueue does not wake up after timeout Message-ID: <9c131a2a-cc94-4d93-1ba8-595c0151e366@FreeBSD.org> In-Reply-To: <20191022131633.GN73312@kib.kiev.ua> References: <aff7b1e5-c380-9d86-d638-047e618894e6@FreeBSD.org> <20191022104434.GM73312@kib.kiev.ua> <3a67f9a9-31cf-5814-4a68-8bdd6063b21e@FreeBSD.org> <20191022131633.GN73312@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22/10/2019 16:16, Konstantin Belousov wrote: > On Tue, Oct 22, 2019 at 02:48:56PM +0300, Andriy Gapon wrote: >> On 22/10/2019 13:44, Konstantin Belousov wrote: >>> On Tue, Oct 22, 2019 at 01:08:59PM +0300, Andriy Gapon wrote: >>>> Has anyone seen anything like this problem? >>> Yes, but it was very long time ago. See r303426. >> >> Yeah, we are based off r329000 plus a bunch of merges for various fixes. >> One thing I forgot to mention is that it seems to happen only on VMware guests, >> but maybe it's only because we have many more virtual test boxes than we have >> physical ones. >> One thing I suspected was that binuptime() could somehow jump backwards... > Do you use any of suspend/migration ? No, the VMs are pinned to hosts. No suspension and no migration. > Perhaps record sbinuptime() in the struct thread in sleepq_timeout() and > keep the original value of td_sleeptimo around to see what did happen. Thank you for the idea. I will try it. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9c131a2a-cc94-4d93-1ba8-595c0151e366>