Date: Sun, 02 Apr 2017 14:43:35 +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-ZCyhziOsrY@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=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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203129-8-ZCyhziOsrY>