From owner-freebsd-arm@freebsd.org Fri Jul 19 19:52:09 2019 Return-Path: Delivered-To: freebsd-arm@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 9BFDEAA549 for ; Fri, 19 Jul 2019 19:52:09 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E52EC83D81 for ; Fri, 19 Jul 2019 19:52:03 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.164] (82-203-140-69.bb.dnainternet.fi [82.203.140.69]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id x6JJptIw051314 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 19 Jul 2019 19:51:56 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 82-203-140-69.bb.dnainternet.fi [82.203.140.69] claimed to be [192.168.1.164] From: Stefan Parvu Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0 Date: Fri, 19 Jul 2019 22:51:49 +0300 References: <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <2AC05799-7D11-4200-8D16-38E3718470BB@kronometrix.org> <91E26684-07A0-4F03-92BC-8D49359B1358@kronometrix.org> <5F33E59B-7EA5-4B8B-A95A-CD1FB569ACDC@kronometrix.org> <6a39f74088d2984b5426e8585b5f7e864a6766f8.camel@freebsd.org> <571EABD9-364C-4D91-9177-CC25CB382D76@kronometrix.org> <2dd107308cb7fc21bab793218d8e37039dbc108e.camel@freebsd.org> <77885EA9-6AA4-4106-B447-3A83FB6033BA@kronometrix.org> <7aafd9f1f1cc072081a14c41a0253e72cd449811.camel@freebsd.org> <89879D9D-9432-44FA-B4E0-A6D3EE969E7A@kronometrix.org> To: freebsd-arm@freebsd.org In-Reply-To: <89879D9D-9432-44FA-B4E0-A6D3EE969E7A@kronometrix.org> Message-Id: <5F7CD5C3-5107-48BE-B301-3193B4E7A4A2@kronometrix.org> X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: E52EC83D81 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [1.98 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; HAS_XAW(0.00)[]; NEURAL_SPAM_MEDIUM(0.50)[0.500,0]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.01)[-0.010,0]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[mail.kronometrix.org]; DMARC_NA(0.00)[kronometrix.org]; NEURAL_SPAM_SHORT(0.83)[0.827,0]; IP_SCORE(0.48)[ip: (0.35), ipnet: 95.85.0.0/18(1.01), asn: 14061(1.07), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2019 19:52:09 -0000 Testing the new clock for 5hrs downtime. No go. This is driving me nuts. Something is very odd here, but not sure what. It works fine for short=20= periods of time, but then somehow for longer periods of time nope = (>1-2hrs) $ kldstat Id Refs Address Size Name 1 9 0xffff000000000000 13d1480 kernel 3 1 0xffff000001415000 40ea8 nxprtc.ko 4 1 0xffff000053600000 41000 tmpfs.ko 5 1 0xffff000053641000 31000 mac_ntpd.ko $ dmesg | grep nxp nxprtc0: at addr 0xa2 on iicbus0 nxprtc0: WARNING: RTC battery failed; time is invalid nxprtc0: registered as a time-of-day clock, resolution 0.015625s nxprtc0: RTC clock not running Stefan Parvu sparvu@kronometrix.org > On 19 Jul 2019, at 12.40, Stefan Parvu wrote: >=20 >> The time couldn't have been correct from the RTC if it said the clock >> was not running -- the driver says that instead of returning a time = to >> the kernel. Ntpd must have already set the time before you checked = it. >=20 > Thats correct. Tests were done incorrectly. The power cable was not = removed > the board still had power.=20 >=20 > I have repected fresh all tests. Now, very strange everything is fine. = I cant explain > what has happened except: >=20 > * kldunload / load nxprtc=20 >=20 > * creating a new hints file=20 >=20 > * removing and re-inserting the battery=20 >=20 > I have powered off the board for 2hrs and the time functions = correctly. I will soon > setup another RBPI board and re-test all over with the new ko module.=20= >=20 > Stefan > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"