From owner-freebsd-bugs@freebsd.org Sun Apr 2 14:43:35 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C823D2AED2 for ; Sun, 2 Apr 2017 14:43:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BD2C405 for ; Sun, 2 Apr 2017 14:43:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v32EhZ5O063395 for ; Sun, 2 Apr 2017 14:43:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203129] syslogd: /dev/console: Interrupted system call on arm64 Date: Sun, 02 Apr 2017 14:43:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: 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: freebsd-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.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2017 14:43:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203129 pvoigt@uos.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pvoigt@uos.de --- Comment #1 from pvoigt@uos.de --- I can observe this on 11.0-RELEASE-p8 (amd64) rather regularly as well. The message occurs nearly every time when cron starts newsyslog every hour which in turn triggers a restart of syslogd. After the first occurance of the message there are no more messages written= to /dev/console. Sometimes syslogd even hangs in a state where it is still vis= ible in the process list but does not do any logging anymore. And a restart even fails. I have discussed this issue on IRC and besides other advice I have been tol= d it is somehow related to the serial console. I have been playing with different speeds with no effect. But after disabling agetty on ttyu0 the messages are gone. At this point I am a bit lost, because need serial console logins with my headless server. And I cannot decide, if my uart device is somehow broken o= r if agetty/syslogd may have an error. --=20 You are receiving this mail because: You are the assignee for the bug.=