From owner-freebsd-arm@freebsd.org Fri Jul 19 20:07:23 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 B6512AAD1D for ; Fri, 19 Jul 2019 20:07:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2856084B5C for ; Fri, 19 Jul 2019 20:07:23 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1563566835; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=qBcs6BQ6jY4vllfS4s9W6kjuLdE3ASupSHnQJxDijMIaui9BJGgIpdQ+Soev1oWi8wcOn31Q9Gan4 hp41hvXcsCpdWornrM6CH1E2aEWMjmC+vQJt+NEMahJdMkN0OFlJTiFc3IeKf53P3JDkXoLq31gvE4 kiaFBr/ffqEs6HQ2hH6sHlgwT5zHZWfecO7TNmEJyJae7tyLy7zCedYisabMB383HDyupq7CcewU/U XKstdQA4s5YF5QYZhzzLvSgQU0r4BVYl603G/eLRlXlXaen6xs6KgwxcBnFTD/VXnCC+vXNH/58Zkn yxh4PNTtMJN7feiMLT+qCDNEGy0aXvw== 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=t+1s5DJWaUkxNkXfp1aq0Y2HouogYqdVOZAvFHDr2zM=; b=nzV6e3K8WIhxdPPYFBmSwJ+ts6IuplKleSA81cyZKyD1XzD6IZ5IZLIcydsq7Z9zDjmz2fzPo7aYD 6oqBCxeq2xvhlXhpZjXOxl9VVpXPN+AO/aST35B9dWEenj2swwPrG76RgB5t/O8352aK1pFcrh4k7d xSnO5GuL3X/KkJTjzVzN0unJDc5AEHdj4incUZw+9USdR8T2Hdq1pyC1bhMNu2cgu98embxjYsAEps o8QUJGmUEUVzO3FAl81bkFQDaexFY2/hK3LC4z7RkNs0CQ6rJjlEW4qcORvnQROjRZpIBquLuXL+n1 Deptr7Xy2bQ39AxcMqEpiBM0sdK23nw== ARC-Authentication-Results: i=1; outbound3.eu.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=t+1s5DJWaUkxNkXfp1aq0Y2HouogYqdVOZAvFHDr2zM=; b=N7GoUloB5lma7aVcEG7+MVV/IFT8Gu2oDmKlwKHo9A6e0GGolVKR+Kyy3ZMS60H4aSV3DPJfu0WNN SjbHQVkeYo8x/GoPwIRF5rEq2qWu8N/tiHkCLPGUpdBNJ75zqWjnUcsIS+/VHuKfVOdB5g4PDg+Bsl dlwb2X8djfq+Ie8szOmKlwroOk09gWY+th5SNriQF0Jps7MNZWUJiK1mIECrPeAbPmxMCch8u6Q+4B /8hbHxTkqCZW5kcpi3vvlVtW+nBUTZmKvaZrU9gkCw+rMgoHftAGvFILtOfQ/GKHMSvgIKyZNips7B Z4W0r0u/z8AfNZbk3S4qaGDwVIioptg== X-MHO-RoutePath: aGlwcGll X-MHO-User: cb23664c-aa60-11e9-9ec3-cb046d117d09 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 (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id cb23664c-aa60-11e9-9ec3-cb046d117d09; Fri, 19 Jul 2019 20:07:13 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x6JK7AhP050406; Fri, 19 Jul 2019 14:07:10 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0 From: Ian Lepore To: Stefan Parvu , freebsd-arm@freebsd.org Date: Fri, 19 Jul 2019 14:07:10 -0600 In-Reply-To: <5F7CD5C3-5107-48BE-B301-3193B4E7A4A2@kronometrix.org> 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> <5F7CD5C3-5107-48BE-B301-3193B4E7A4A2@kronometrix.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 2856084B5C X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US] 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 20:07:23 -0000 On Fri, 2019-07-19 at 22:51 +0300, Stefan Parvu wrote: > 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 > 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 > It's a bit frustrating that the Afterthough site has no info on what's different between various revs of the rasclock. My v4.2 has a row of through-holes on the edge of the card where you can add pins and get at various signals. One of the signals is VBAT, any chance you could get a scope or meter on that and see if the voltage really is low, and whether it drops over time, like something really is draining the battery? Also, I wonder if there's any difference between its behavior when it's mounted on the rpi versus if you take it off and set it aside for a few hours. Like maybe on an rpi3 there is current somehow leaking back into the rpi circuitry. -- Ian