Date: Wed, 27 May 2020 16:32:20 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <current@FreeBSD.org> Subject: Re: acpi timer reads all ones [Was: efirtc + atrtc at the same time] Message-ID: <fc2b9dae-a3ad-6c5f-77b3-19c9695ebe47@FreeBSD.org> In-Reply-To: <618658d9-b892-9255-2747-c5efbada0210@FreeBSD.org> References: <021d8df4-a4f8-620d-73b6-b6103d0bf7f1@FreeBSD.org> <199c8845-e42c-fbee-3f13-0b3d0d7234dc@FreeBSD.org> <20200526185528.GA48478@kib.kiev.ua> <b6f5429a-fa0b-3d85-1250-a11807757ef7@FreeBSD.org> <114f788a-3947-0783-5472-173cf3a30d32@FreeBSD.org> <da33c67e-7fbd-59cc-a9b3-1b6f24fafeb2@FreeBSD.org> <618658d9-b892-9255-2747-c5efbada0210@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27/05/2020 16:27, John Baldwin wrote:
> The "solution" I think is to have resume be multi-pass and to resume all the bridges
> first before trying to resume leaf devices (including timers), but that's a fair bit
> of work. It might be that we just need to resume timer interrupts later after the
> new-bus resume (I think we currently do it before?), though the reason for that was
> to allow resume methods in devices to sleep (I'm not sure if any do).
But it's not only about timers.
{sbin,bin,micro,etc}uptime() calls can return garbage as well and confuse their
callers.
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc2b9dae-a3ad-6c5f-77b3-19c9695ebe47>