Date: Thu, 18 Jul 2019 23:33:45 +0300 From: Stefan Parvu <sparvu@kronometrix.org> To: freebsd-arm@freebsd.org Subject: Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0 Message-ID: <E6E790AC-D301-4F8E-AA7D-8147B6C9F292@kronometrix.org> In-Reply-To: <B596A43F-6985-4639-9AB3-652CEE8C1387@kronometrix.org> References: <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <AB510253-52D9-469C-B06E-5EC73C5F188E@kronometrix.org> <fd9991c4e6aaccb812a59ff86c9c8564ebd1d767.camel@freebsd.org> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <c52f9d9ab358ac0dc09af411bf97625945579b4e.camel@freebsd.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <BE321299-8569-4B2E-98FD-FD5210E1B6AF@kronometrix.org> <A9FD7D2B-9382-4EAE-B245-5F4DE643DBB7@gromit.dlib.vt.edu> <C93E2C64-6280-464D-AB5F-B1E968690CEF@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <BD0BE075-9E69-4CB0-826A-5DF2D160E9B1@kronometrix.org> <d71fc4e3db26242ffa817814d6cd92b8899fc2ab.camel@freebsd.org> <EF94BC84-4B8D-455C-952F-4FD1CC5557CE@kronometrix.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> <A53C9BE4-B3A7-4F15-808F-AB9846674625@kronometrix.org> <2dd107308cb7fc21bab793218d8e37039dbc108e.camel@freebsd.org> <C32068F6-862A-4863-B055-52621209F7D9@kronometrix.org> <F4FB90D0-9777-41EE-9005-9BA441D721A6@kronometrix.org> <b4970b3cf77a854dba71a3319d0ada8619efbd7c.camel@freebsd.org> <77885EA9-6AA4-4106-B447-3A83FB6033BA@kronometrix.org> <B596A43F-6985-4639-9AB3-652CEE8C1387@kronometrix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
hang on. something is odd. Take a look: after copying the new nxprtc.ko = do I need to=20 regenrate the linker.hints file ? root@k1:~ # dmesg | grep nxp nxprtc0: <NXP PCF2129 RTC> 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 nxprtc0: detached warning: KLD '/boot/kernel/nxprtc.ko' is newer than the linker.hints = file nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0 nxprtc0: registered as a time-of-day clock, resolution 0.015625s What I did was: 1. Boot system, which had wrong time. RTC present. 2. Fixed the time using date command, Started NTPD 3. kldunload and kldload again nxprtc driver which dumped this warning: Stefan Parvu sparvu@kronometrix.org > On 18 Jul 2019, at 23.29, Stefan Parvu <sparvu@kronometrix.org> wrote: >=20 > check. all good. battery installation is all good. >=20 > In fact the clock functions but for very short periods of time. thats = what I have seen. Its like=20 > keeping the time for 5-10 minutes or so. If I stop the system for 1hr+ = time is lost. I can check > again >=20 >=20 > Stefan Parvu > sparvu@kronometrix.org >=20 >=20 >=20 >> On 18 Jul 2019, at 23.25, Stefan Parvu <sparvu@kronometrix.org> = wrote: >>=20 >> LOL . Well u never know that. Let me check. With 2 kids around = everything is=20 >> possible.=20 >>=20 >> Stefan Parvu >> sparvu@kronometrix.org >>=20 >>=20 >>=20 >>> On 18 Jul 2019, at 23.22, Ian Lepore <ian@freebsd.org> wrote: >>>=20 >>> On Thu, 2019-07-18 at 23:16 +0300, Stefan Parvu wrote: >>>> I think after your latest commit I see a function from nxprtc = module >>>> which does not=20 >>>> exist in the original module. Take a look: >>>>=20 >>>> root@k1:/var/tmp # nm -A -a /boot/kernel/nxprtc.ko | grep readfrom >>>> /boot/kernel/nxprtc.ko:0000000000010ab8 t nxprtc_readfrom >>>>=20 >>>> which I do not see under original nxprtc module such thing.=20 >>>>=20 >>>> root@k1:/var/tmp # nm -A -a /var/tmp/nxprtc.original.ko | grep >>>> readfrom >>>> /var/tmp/nxprtc.original.ko: U iicdev_readfrom >>>>=20 >>>> Is this right ? Is this something you have fixed on the latest and >>>> the greatest >>>> nxprtc version ? >>>>=20 >>>>=20 >>>=20 >>> Yep, that is good confirmation that the fix is in that module. >>>=20 >>> I almost hesitate to say it, but... the symptoms you're seeing are >>> exactly what would happen if the battery was installed upside-down. = :) >>>=20 >>> -- Ian >>=20 >> _______________________________________________ >> 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" >=20 > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6E790AC-D301-4F8E-AA7D-8147B6C9F292>