From owner-freebsd-bugs@freebsd.org Thu Oct 19 18:22:50 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 75E74E43964 for ; Thu, 19 Oct 2017 18:22:50 +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 647F376337 for ; Thu, 19 Oct 2017 18:22:50 +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 v9JIMm70046894 for ; Thu, 19 Oct 2017 18:22:50 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: Thu, 19 Oct 2017 18:22:48 +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: freebsd@ruka.org X-Bugzilla-Status: Open 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: Thu, 19 Oct 2017 18:22:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203129 Richard Russo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@ruka.org --- Comment #7 from Richard Russo --- This seems to be related to a possibly inadvertent change I noticed on our 11.1-RELEASE (p1) hosts: the serial console device can now have its baud ra= te and modem control settings changed other than at boot. On 10.3 and below, m= odem control was prohibited for serial console, and baud rate was fixed at boot. We had /etc/ttys configured to do "/usr/libexec/getty std.9600", but the se= rial console is actually set for 115200, with no modem control. On 10.3 and earl= ier, the getty config was ignored, but on 11.1, the config is used, and since our console connection (also Supermicro IPMI SOL) isn't doing modem control (or= not properly), this made output to the serial console block -- which was causing segfaulting processes to never exit. This seems to be resolvable, by setting /etc/ttys to the proper settings (3wire.115200 in our case), but I didn't see a kernel change that looked li= ke it was intentionally changing this, and sys/kern/tty.c:323 still seems to be trying to prevent modem control on the console port. --=20 You are receiving this mail because: You are the assignee for the bug.=