From owner-freebsd-bugs@FreeBSD.ORG Fri Feb 24 07:20:08 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E75216A420 for ; Fri, 24 Feb 2006 07:20:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D67043D46 for ; Fri, 24 Feb 2006 07:20:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1O7K7hs078019 for ; Fri, 24 Feb 2006 07:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1O7K7Y9078018; Fri, 24 Feb 2006 07:20:07 GMT (envelope-from gnats) Date: Fri, 24 Feb 2006 07:20:07 GMT Message-Id: <200602240720.k1O7K7Y9078018@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/92440: Kernel fault in knote when getty opens a serial port X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2006 07:20:08 -0000 The following reply was made to PR kern/92440; it has been noted by GNATS. From: Kris Kennaway To: Paul Marciano Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/92440: Kernel fault in knote when getty opens a serial port Date: Fri, 24 Feb 2006 02:18:31 -0500 On Sat, Jan 28, 2006 at 12:30:07AM +0000, Paul Marciano wrote: > >Description: > My systems all use serial consoles. Upon logging out of a shell session I observed a kernel fault. This has been reported before, I believe, but I couldn't find a PR. > > (http://adam.kungfoohampster.com/lists/freebsd-stable/msg11259.shtml) > > It is imperative that my serial consoles remain reliable. I think this was fixed in 6.0-RELEASE. Can you confirm? Kris