Date: Sat, 16 Jan 2021 19:41:01 +0100 From: Rainer Hurling <rhurlin@gwdg.de> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Waiting for bufdaemon Message-ID: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de> In-Reply-To: <ed52f8c1-5f43-b71e-1d56-625e2e064a7e@gwdg.de> References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> <YAGua8f8G57SbUMT@kib.kiev.ua> <556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org> <YAG4g7dJbRWM7act@kib.kiev.ua> <ed52f8c1-5f43-b71e-1d56-625e2e064a7e@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 15.01.21 um 19:48 schrieb Rainer Hurling: > Am 15.01.21 um 16:45 schrieb Konstantin Belousov: >> On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote: >>> On 15/01/2021 16:02, Konstantin Belousov wrote: >>>> On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote: >>>>> On 15/01/2021 11:26, Jakob Alvermark wrote: >>>>>> Hi, >>>>>> >>>>>> >>>>>> When rebooting my thinkpad the 'bufdaemon' times out: >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed >>>>>> out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop >>>>>> ... timed out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop >>>>>> ... timed out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop >>>>>> ... timed out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop >>>>>> ... timed out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop >>>>>> ... timed out >>>>>> >>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop >>>>>> ... timed out >>>>>> >>>>>> >>>>>> This started happening recently (within the last week I think). >>>>> >>>>> Hi, >>>>> >>>>> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal. >>>>> >>>>> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned >>>>> groups) "seems" ok >>>>> >>>>> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP >>>>> support), affected by the timeout. >>>>> >>>>> I haven't tried the intermediate commit yet. >>>>> >>>>> My intel machine doesn't seem to be affected >>>> >>>> If you revert only 9e680e4005b7, is it fixed ? >>>> >>> Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests, >>> I can do more if you want) >> Please show me the output from sysctl >> kern.timecounter >> kern.eventtimer >> and first 100 lines of dmesg from the verbose boot (that contains the CPU >> ident lines). > > > I also have this timeout issue only on AMD, here Ryzen 3950X: > > [...] > Waiting for PIDS: 2905 > 90 seconds watchdog timeout expired. Shutdown terminated. > Fri Jan 15 19:21:01 xxxxxx init[1]: /etc/rc.shutdown terminated > abnormally, going to single user mode > Fri Jan 15 19:21:01 xxxxxx syslogd: exiting on signal 15 > wg0: link state changed to DOWN > Waiting (max 69 seconds) for system process `vnlru' to stop... done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining... 22 23 23 1 1 0 0 0 done > Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done > Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... > done > Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... > done > Waiting (max 60 seconds) for system thread `bufspacedaemon-2' to stop... > done > Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... > timeout > Waiting (max 60 seconds) for system thread `bufspacedaemon-4' to stop... > timeout > Waiting (max 60 seconds) for system thread `bufspacedaemon-5' to stop... > done > Waiting (max 60 seconds) for system thread `bufspacedaemon-6' to stop... > > > You will find the wanted output from sysctl and boot -v in the attachment. > > HTH, > Rainer Hurling > During another shutdown after heavy usage of the box, the following messages were also seen: [...] Syncing disks, vnodes remaining... 22 EFI rt_settime call faulted, error 14 efirtc0: CLOCK_SETTIME error 14
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ae3cc65-193a-39c3-4067-0d42e9f634b0>