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 _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
