From owner-freebsd-current@freebsd.org Fri Jan 15 15:03:36 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 D07274E8870 for ; Fri, 15 Jan 2021 15:03:36 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DHPZb5l5Rz54qk for ; Fri, 15 Jan 2021 15:03:35 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l0QdR-0008m5-IL for freebsd-current@freebsd.org; Fri, 15 Jan 2021 16:03:33 +0100 Received: from [192.168.67.27] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l0QdQ-0003L6-V8 for freebsd-current@freebsd.org; Fri, 15 Jan 2021 16:03:32 +0100 Subject: Re: Waiting for bufdaemon To: freebsd-current@freebsd.org References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net> <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> From: Jakob Alvermark Message-ID: <96d7db5d-e4ad-f9bb-0c27-07f94bed8df5@alvermark.net> Date: Fri, 15 Jan 2021 16:03:32 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DHPZb5l5Rz54qk X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.96 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[alvermark.net:+]; NEURAL_HAM_SHORT(-0.46)[-0.464]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/24, country:IT]; 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 15:03:36 -0000 On 1/15/21 3:56 PM, 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 I observed the same here. It seems to only happen on my AMD laptop. I have an Intel laptop which seems fine. Jakob