Date: Thu, 19 Oct 2017 18:22:48 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203129] syslogd: /dev/console: Interrupted system call on arm64 Message-ID: <bug-203129-8-HnjGJt7O9y@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203129-8@https.bugs.freebsd.org/bugzilla/> References: <bug-203129-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Richard Russo <freebsd@ruka.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@ruka.org --- Comment #7 from Richard Russo <freebsd@ruka.org> --- 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 rate and modem control settings changed other than at boot. On 10.3 and below, modem 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 serial console is actually set for 115200, with no modem control. On 10.3 and earlier, 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 like it was intentionally changing this, and sys/kern/tty.c:323 still seems to be trying to prevent modem control on the console port. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203129-8-HnjGJt7O9y>