Date: Thu, 12 Apr 2018 21:42:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 203129] syslogd: /dev/console: Interrupted system call Message-ID: <bug-203129-227-lYBvNhI7Wr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203129-227@https.bugs.freebsd.org/bugzilla/> References: <bug-203129-227@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=3D203129 --- Comment #12 from Adam Bernstein <adam@electricembers.coop> --- Sorry for my untidy commenting, but two additions to make: 1. The workaround of removing any /dev/console logging from syslog.conf did= do the trick for us, it's just not really an ideal or complete fix. 2. It took us a long time to identify syslogd as the root cause among all t= he symptoms and to notice the right error message (the interrupted system call) that led us to this bug. Instead, the only visible error message we were aw= are of for a while was this one, repeated every 30 seconds in the messages log whenever we attempted to connect to the serial console: init: getty repeating too quickly on port /dev/ttyu0, sleeping 30 secs But a web search on that error turned up a lot of stuff, none of it relevan= t. FWIW, 'ps' showed the getty process for the serial port with just "-" in it= s TT column instead of "u0", and lacking the "s+" in its STAT column that the healthy gettys had. I hope that will help someone else find this bug quicker. --=20 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-227-lYBvNhI7Wr>