From owner-freebsd-stable@FreeBSD.ORG Thu Jul 21 11:04:30 2005 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91D9D16A420 for ; Thu, 21 Jul 2005 11:04:30 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C1B743D73 for ; Thu, 21 Jul 2005 11:04:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id F176C46B0C; Thu, 21 Jul 2005 07:04:12 -0400 (EDT) Date: Thu, 21 Jul 2005 12:04:39 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?ISO-8859-1?Q?Eirik_=D8verby?= In-Reply-To: <86DDD9F6-A086-48E2-A5C5-1F5EA1C49354@anduin.net> Message-ID: <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> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2065818662-1121943879=:97888" Cc: stable@FreeBSD.org, Kris Kennaway Subject: Re: Serious issue with serial console in 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2005 11:04:30 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2065818662-1121943879=:97888 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 21 Jul 2005, Eirik =D8verby wrote: >> I've only seen the issue when logging out of a serial console session,= =20 >> and had previously hypothesized that it had to do with the simultaneous= =20 >> timing of a console message from syslog and the opening/closing of the= =20 >> console's tty due to logging out and getty restarting, resulting in a=20 >> reference count improperly hitting zero. > > I did indeed make some changes to my syslog configuration after getting= =20 > the serials online. Your theory might not be entirely off. Let me know=20 > if I should post my syslog.conf file or anything else here or=20 > elsewhere... Since you appear to be able to reliably reproduce the problem (whereas I=20 was able to reproduce it only after several hours of quite active serial=20 console work), it would be quite interesting to answer the following=20 question: If you cause syslogd not to send any output to /dev/console, does the problem go away? Thanks, Robert N M Watson --0-2065818662-1121943879=:97888--