From owner-freebsd-bugs@freebsd.org Tue Oct 29 23:27:10 2019 Return-Path: Delivered-To: freebsd-bugs@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 0CE97167CC8 for ; Tue, 29 Oct 2019 23:27:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 472nmY6V17z4BD0 for ; Tue, 29 Oct 2019 23:27:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DEB33167CC7; Tue, 29 Oct 2019 23:27:09 +0000 (UTC) Delivered-To: bugs@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 DE762167CC6 for ; Tue, 29 Oct 2019 23:27:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 472nmY5RQkz4BCx for ; Tue, 29 Oct 2019 23:27:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9F07515C8 for ; Tue, 29 Oct 2019 23:27:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9TNR94n099647 for ; Tue, 29 Oct 2019 23:27:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9TNR9rG099646 for bugs@FreeBSD.org; Tue, 29 Oct 2019 23:27:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 224173] serial driver from 10.4 onwards doesn't correctly work in ntpd/DCF77 "parse" clock mode Date: Tue, 29 Oct 2019 23:27:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pvoigt@uos.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 23:27:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224173 pvoigt@uos.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pvoigt@uos.de --- Comment #1 from pvoigt@uos.de --- Well, this issue is rather old and still has status "new". I reply because I have just obviuosly run into the same situation: I have an USB DCF77 receiv= er which can never pass a full correct signal to ntpd. It is a GUDE Expert Mou= se Clock 0107 which is correctly recognized by FreeBSD 11.3-RELEASE-p4. I have built net/ntp from ports with enabled RAWDCF option. However, ntp log is fu= ll of "INCOMPLETE DATA" and "start bit / parity check FAILED" messages. The sa= me receiver works immediately when connected to a Debian Buster machine. Is there currently any work in progress on this issue? Is there an issue in ucom/uftdi kernel modules or in the RAWDCF driver of ntp? --=20 You are receiving this mail because: You are the assignee for the bug.=