Date: Sun, 17 Jan 2021 06:33:01 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: rhurlin@freebsd.org Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Waiting for bufdaemon Message-ID: <YAO9/cxnbGv5u3Bg@kib.kiev.ua> In-Reply-To: <9ae3cc65-193a-39c3-4067-0d42e9f634b0@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> <9ae3cc65-193a-39c3-4067-0d42e9f634b0@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 16, 2021 at 07:41:01PM +0100, Rainer Hurling wrote: > 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 This means that BIOS code faulted during RTC settime call. I doubt that it is related. On the other hand, it is good that the onfault EFI RT code got tested finally.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YAO9/cxnbGv5u3Bg>