[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 --- Comment #9 from h...@shrubbery.net --- I haven't tried dropping modem control yet, which is how my console server is configured. This seems like a bug to not treat the console specially; without an active connection, the console server

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 --- Comment #8 from j.catry...@proximedia.be --- 3wire.115200 seemed to have fixed the issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.or

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Richard Russo changed: What|Removed |Added CC||free...@ruka.org --- Comment #7 fr

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-10-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Ed Maste changed: What|Removed |Added Hardware|arm64 |Any --- Comment #6 from Ed Maste --- H

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 h...@shrubbery.net changed: What|Removed |Added CC||h...@shrubbery.net --- Comment

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-08-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Paul Macdonald changed: What|Removed |Added CC||p...@ifdnrg.com --- Comment #4 fr

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 --- Comment #3 from j.catry...@proximedia.be --- Commenting out the /dev/console line in syslog.conf is a workaround. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 j.catry...@proximedia.be changed: What|Removed |Added CC||j.catry...@proximedia.be

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-04-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2017-04-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 pvo...@uos.de changed: What|Removed |Added CC||pvo...@uos.de --- Comment #1 from p

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2015-11-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Ed Maste changed: What|Removed |Added Blocks||203349 -- You are receiving this mail

[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64

2015-09-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Bug ID: 203129 Summary: syslogd: /dev/console: Interrupted system call on arm64 Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any