Date: Mon, 22 Nov 2021 08:48:51 -0800 From: John Baldwin <jhb@FreeBSD.org> To: tuexen@freebsd.org, Mark Millard <marklmi@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: "Khelp module "ertt" can't unload until its refcount drops from 1 to 0." after "All buffers synced."? Message-ID: <ebf89218-f183-4a3d-c6e9-7eb14a6c1b74@FreeBSD.org> In-Reply-To: <3A646420-0FB9-4C58-BA97-EE1040958B6E@freebsd.org> References: <119DC979-EC2C-4BE4-A6E8-2DBF222115A0.ref@yahoo.com> <119DC979-EC2C-4BE4-A6E8-2DBF222115A0@yahoo.com> <52374B7E-6ABB-4E55-984C-B7EC82B48506@freebsd.org> <E76BD6F5-2170-4E98-B407-7646CF456828@yahoo.com> <3A646420-0FB9-4C58-BA97-EE1040958B6E@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/19/21 4:29 AM, tuexen@freebsd.org wrote: >> On 19. Nov 2021, at 00:11, Mark Millard <marklmi@yahoo.com> wrote: >> >>> On 2021-Nov-18, at 12:31, tuexen@freebsd.org <tuexen@FreeBSD.org> wrote: >>> >>>> On 17. Nov 2021, at 21:13, Mark Millard via freebsd-current <freebsd-current@freebsd.org> wrote: >>>> >>>> I've not noticed the ertt message before in: >>>> >>>> . . . >>>> Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done >>>> All buffers synced. >>>> Uptime: 1d9h57m18s >>>> Khelp module "ertt" can't unload until its refcount drops from 1 to 0. >>> Hi Mark, >>> >>> what kernel configuration are you using? What kernel modules are loaded? >> >> The shutdown was of my ZFS boot media but the machine is >> currently doing builds on the UFS media. (The ZFS media is >> present but not mounted). For now I provide information >> from the booted UFS system. The UFS context is intended >> to be nearly a copy of the brctl selection for main [so: 14] >> from the ZFS media. Both systems have been doing the same >> poudriere builds for various comparison/contrast purposes. >> The current build activity will likely take 16+ hrs. > Hi Mark, > > thanks a lot for the information. I was contemplating whether this message > was related to a recent change in the TCP congestion module handling, but > since it was already there in February, this is not the case. Will try to > reproduce this, but wasn't able up to now. The congestion control changes just probably exacerbated the bug by adding a new reference on this module, just as they exposed the bug with khelp using the wrong SYSINIT subsystem. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ebf89218-f183-4a3d-c6e9-7eb14a6c1b74>