Date: Sat, 12 Sep 2020 20:24:07 +0200 From: Guido Falsi <mad@madpilot.net> To: Eric McCorkle <eric@metricspace.net>, freebsd-hackers@freebsd.org, freebsd-current <freebsd-current@FreeBSD.org> Subject: Re: Problem with zfs.ko: lockstat_enabled symbol Message-ID: <4d7a830b-1413-2217-e5d5-c74a65d21219@madpilot.net> In-Reply-To: <4140b983-3d61-e1a4-dd7f-90bce61c45cf@metricspace.net> References: <4140b983-3d61-e1a4-dd7f-90bce61c45cf@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/09/20 13:18, Eric McCorkle wrote: > I recently updated my other laptop, and now I'm getting a problem > loading zfs.ko at boot, relating to the lockstat_enabled symbol not > being defined (this happens during kernel boot and prevents mounting > root, so I can't get an exact trace) > > Looking at the new kernel, it seems that only zfs.ko contains the symbol > lockstat_enabled (notably, kernel does not). In my old kernel, zfs.ko > does not contain a reference to that symbol. > > Has anyone else seen this? Is there a workaround, or was this a one-off > bug? > I was getting this too, should be fixed by r365466. It can also be fixed by adding "options KDTRACE_HOOKS" to your kernel config, so that symbol gets defined. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d7a830b-1413-2217-e5d5-c74a65d21219>