Date: Thu, 21 Jul 2005 14:19:23 +0200 From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: Robert Watson <rwatson@FreeBSD.org> Cc: stable@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Serious issue with serial console in 5.4 Message-ID: <E23598E0-03DD-4D03-AF99-47B231828A4B@anduin.net> In-Reply-To: <20050721120340.S97888@fledge.watson.org> References: <20050721050048.GU22430@xor.obsecurity.org> <00DD4399-4317-4579-82C4-5B64AC3F800B@anduin.net> <20050721110222.U97888@fledge.watson.org> <86DDD9F6-A086-48E2-A5C5-1F5EA1C49354@anduin.net> <20050721120340.S97888@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 21, 2005, at 1:04 PM, Robert Watson wrote: > > On Thu, 21 Jul 2005, Eirik =D8verby wrote: > > >>> I've only seen the issue when logging out of a serial console =20 >>> session, and had previously hypothesized that it had to do with =20 >>> the simultaneous timing of a console message from syslog and the =20 >>> opening/closing of the console's tty due to logging out and getty =20= >>> restarting, resulting in a reference count improperly hitting zero. >>> >> >> I did indeed make some changes to my syslog configuration after =20 >> getting the serials online. Your theory might not be entirely off. =20= >> Let me know if I should post my syslog.conf file or anything else =20 >> here or elsewhere... >> > > Since you appear to be able to reliably reproduce the problem =20 > (whereas I was able to reproduce it only after several hours of =20 > quite active serial console work), it would be quite interesting to =20= > answer the following question: > > If you cause syslogd not to send any output to /dev/console, does =20= > the > problem go away? I'm afraid to say it doesn't.... /Eirik > > Thanks, > > Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E23598E0-03DD-4D03-AF99-47B231828A4B>