Date: Mon, 29 Apr 2013 17:53:38 +0200 From: Fabian Wenk <fabian@wenks.ch> To: freebsd-stable@freebsd.org Subject: Re: [Solved] [UART] GPS 18-5Hz LVC and COM1 silence, OK on Linux though... Message-ID: <517E9782.2050701@wenks.ch> In-Reply-To: <CADWvR2gQug_vvp6URn5_mi74GBAEph0nqWmRNgfeLn=cCqAj0g@mail.gmail.com> References: <CADWvR2gUqifxF4562%2BTdBea9h%2BSEk-=7fUk8%2B18B-31Y0rh=wA@mail.gmail.com> <517DB738.4060902@restecp.com> <CADWvR2jTF4wFjCf2MvKuQWq-gWXmsKwfx73gjTcdq7Hvk_0N_w@mail.gmail.com> <CADWvR2jUCu64Kh0jStQHj1Jhe59btSoYEMG5QKBanuz=Eaaciw@mail.gmail.com> <CADWvR2gQug_vvp6URn5_mi74GBAEph0nqWmRNgfeLn=cCqAj0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Igor On 29.04.2013 04:06, Igor Mozolevsky wrote: > Once I narrowed down the problem (acpi uart), I stumbled across > > http://forums.freebsd.org/archive/index.php/t-15740.html > > Preventing the ACPI driver from seizing control of UART seems to work > and cuau0 is now functional. I have a similar problem, but with a DCF77 Gude mouseCLOCK (connected to on-board COM2), which was working just fine on this system when running FreeBSD 7.4 (sio). But since I have upgraded to FreeBSD 9.1 (uart), ntpd does only get partial data from the mouseCLOCK. So today I tried with the above hint, but this did not help. Without any modification (and also with disabled acpi for the uart) I do see messages like this (sorry for the line wrapping): Apr 29 16:31:39 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 0 bits Apr 29 16:31:39 superman ntpd[1737]: PARSE receiver #0: interval for following error message class is at least 00:01:00 Apr 29 16:31:39 superman ntpd[1737]: PARSE receiver #0: FAILED TIMECODE: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00..." (check receiver configuration / wiring) Apr 29 16:31:41 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 1 bits Apr 29 16:31:43 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Apr 29 16:31:52 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 11 bits [...] Apr 29 16:33:01 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 4 bits Apr 29 16:33:08 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 8 bits Apr 29 16:33:16 superman ntpd[1737]: PARSE receiver #0: no data from device within poll interval (check receiver / wiring) When I also add the following line to /boot/device.hints it does improve a little bit and ntpd sees more bits, but still not enough to be working (log entries below): hint.uart.1.flags="0x100" Apr 29 16:46:06 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 0 bits Apr 29 16:46:06 superman ntpd[1737]: PARSE receiver #0: interval for following error message class is at least 00:01:00 Apr 29 16:46:06 superman ntpd[1737]: PARSE receiver #0: FAILED TIMECODE: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00..." (check receiver configuration / wiring) Apr 29 16:46:21 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 1 bits Apr 29 16:46:53 superman ntpd[1737]: PARSE receiver #0: interval for following error message class is at least 00:01:00 Apr 29 16:46:53 superman ntpd[1737]: PARSE receiver #0: no data from device within poll interval (check receiver / wiring) Apr 29 16:47:00 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 45 bits Apr 29 16:47:41 superman ntpd[1737]: parse: convert_rawdcf: parity check FAILED for "--##--####-####RADMLS-24--24p-24---P1--81--2412-81-2481--8P_?" Apr 29 16:47:41 superman ntpd[1737]: PARSE receiver #0: 2 messages where suppressed, error condition class persists for 00:01:35 Apr 29 16:47:41 superman ntpd[1737]: PARSE receiver #0: FAILED TIMECODE: "--##--####-####RADMLS-24--24p-24---P1--81--2412-81-2481--8P_" (check receiver configuration / wiring) Apr 29 16:47:58 superman ntpd[1737]: PARSE receiver #0: no data from device within poll interval (check receiver / wiring) Apr 29 16:48:00 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 23 bits Apr 29 16:48:45 superman ntpd[1737]: parse: convert_rawdcf: parity check FAILED for "--##-------##-#-AD--S1--8124p-24--2P12-8121-4-2481--48-248P__" Apr 29 16:48:45 superman ntpd[1737]: PARSE receiver #0: 1 message was suppressed, error condition class persists for 00:02:39 Apr 29 16:48:45 superman ntpd[1737]: PARSE receiver #0: FAILED TIMECODE: "--##-------##-#-AD--S1--8124p-24--2P12-8121-4-2481--48-248P_" (check receiver configuration / wiring) Apr 29 16:49:00 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 18 bits Apr 29 16:49:44 superman ntpd[1737]: parse: convert_rawdcf: parity check FAILED for "------#########---MLs-24--24p---81-P1--8121-41-4811--81-48P?_" Apr 29 16:50:00 superman ntpd[1737]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 18 bits Apr 29 16:50:00 superman ntpd[1737]: PARSE receiver #0: 2 messages where suppressed, error condition class persists for 00:03:54 Apr 29 16:50:00 superman ntpd[1737]: PARSE receiver #0: FAILED TIMECODE: "---##--####--#---" (check receiver configuration / wiring) Apr 29 16:50:08 superman ntpd[1737]: PARSE receiver #0: no data from device within poll interval (check receiver / wiring) Is there anything else I could try? bye Fabian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?517E9782.2050701>