From owner-freebsd-current@freebsd.org Tue May 26 15:14:27 2020 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 680A42CA7A2 for ; Tue, 26 May 2020 15:14:27 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 49Wcv727Vvz4L7P for ; Tue, 26 May 2020 15:14:27 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 493452CA573; Tue, 26 May 2020 15:14:27 +0000 (UTC) Delivered-To: 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 48FB62CA944 for ; Tue, 26 May 2020 15:14:27 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2k.ore.mailhop.org (outbound2k.ore.mailhop.org [54.148.219.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Wcv65sT0z4Kk5 for ; Tue, 26 May 2020 15:14:26 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1590506065; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=KbL2vWSE2oXuANNj/+H9bZ6yFWcSMauNEUemFBHSBrH6KiDQvyXkcg8Mjgugm7PagxXLKgl+p33K1 2D7yr5V7PUpy595gvblqYuRujQQOpUSifW5jd1NXIZ1Y5ONBsszjDHIwlfgQeGwK6dlJSjMp7ldUFu wwph8hlj3kjVXcTcT9SoWQhT9oJcehWECb4QfuHoR5B6EvMQKMAh+8cDnbIQz27Sn706XK62pcvoou GWfAbsIwLUUfEThEwaFI6kto+94WC/d0ZU4Rh6UiWWWTP8nIDnZH36Onesk41mGpki3T2g9m5KkmoY pLuLPxZrfTK6FdlgAedXbJoRnluXD7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=DOYTZninWeKkY+t7ogHyoQlfrZsMANUBC2KUkHTwySc=; b=YB72Vrr49Z7dSw7lP1iIY2bpn5+aqEY+2IszbWQwx06RV1+q6plZaRo+/d4VFgD0nkl2iiDdHzyZK dg0GF9gBKvfV3SanOabqWgjK+iLcghq2aj+12nvmYvCMOGVhC7/I85bUq3dtHxI2nO3TsCqeq6LddG +ol2QNoUumlTzaAm0HsorDSRZ/Aykzwuca9cDfOE7IcVBrdkMoJcYc/NIWsfRmRZLl8n6ZmzlFvUfJ F8ObE+rDvLfjYLGeA0N8vL7OQ6iGoE5hhTh/5awRI2QuAiID+Yw8kufsnCRlwZZxAl34PW1805Rli/ akPx81gYbSkn3fp+c3+whMBkQWlG5/A== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=DOYTZninWeKkY+t7ogHyoQlfrZsMANUBC2KUkHTwySc=; b=j1pIdMfMWO4rWmM/VJWjE2hc7JPFjDnO4zubVxUbFbQvjl7xPdJkCxvXqax/cLoqZNz7sQSBrBttS BYHb8dHP2UHBs2olfvGW7WUk7y2V7Vnt4NZZUnlCYpF6hVAAL3EwScX2urRvrQcWp9LaR1j4bGAAdp /EjJbY1RGcNDr2UXf35os/vyfHpSeMjlgHLZKYuIYANKeFlDXzUnHkLhUxMIHa308Vfuee1U1GM59E i4/L6HukgNTfEPk0OU+B4nQ802SVis7GgQANtb21zfXhc6PIqwEovP89G2XP0Bfhck7t37zcXHccnq 8PkyLDueVthrdeLxclEVzX0oErbHDfw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 94a9cbad-9f63-11ea-a067-6d02e42e573a X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 94a9cbad-9f63-11ea-a067-6d02e42e573a; Tue, 26 May 2020 15:14:24 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 04QFENAg035829; Tue, 26 May 2020 09:14:23 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <615114ebc4d37a753f02403981ea23e60a6dbe08.camel@freebsd.org> Subject: Re: efirtc + atrtc at the same time From: Ian Lepore To: Andriy Gapon , FreeBSD Current Date: Tue, 26 May 2020 09:14:23 -0600 In-Reply-To: <021d8df4-a4f8-620d-73b6-b6103d0bf7f1@FreeBSD.org> References: <021d8df4-a4f8-620d-73b6-b6103d0bf7f1@FreeBSD.org> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49Wcv65sT0z4Kk5 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 26 May 2020 15:14:27 -0000 On Mon, 2020-05-25 at 11:37 +0300, Andriy Gapon wrote: > I see that on my laptop both efirtc and atrtc get attached. > The latter is via an ACPI attachment: > efirtc0: > efirtc0: registered as a time-of-day clock, resolution 1.000000s > atrtc0: port 0x70-0x71 on acpi0 > atrtc0: registered as a time-of-day clock, resolution 1.000000s > > I am not sure if this is a problem by itself, but it certainly seems redundant > to have two drivers controlling the same(?) hardware via different platform > mechanisms. > Maybe there is a nice way to automatically disable (or "neutralize") one of the > drivers? > I thought I had done something long ago to prevent atrtc and efirtc from both attaching, but apparently not. I intended to, I even mentioned it in https://reviews.freebsd.org/D14399 but it looks like I never followed up and did the work. > Also, there is another issue related to atrtc. > When I have both drivers attached, and also when I have only atrtc attached > (efi.rt.disabled=1), system clock jumps 10 minutes forward after each suspend / > resume cycle (S0 -> S3 -> S0). That does not happen for reboot and shutdown > cycles. I haven't investigated this deeper, but it is a curious problem. > I've looked at the code for messing with the clock around suspend/resume and never felt like it was doing the right thing (or even anything useful). But I've never owned a freebsd machine that could successfully resume from suspend, so I've never been able to experiment with it. -- Ian