From owner-freebsd-bugs@FreeBSD.ORG Wed May 21 08:10:15 2003 Return-Path: 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 9A0F337B401 for ; Wed, 21 May 2003 08:10:15 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4309143F3F for ; Wed, 21 May 2003 08:10:15 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4LFAEUp016850 for ; Wed, 21 May 2003 08:10:14 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4LFAEC6016849; Wed, 21 May 2003 08:10:14 -0700 (PDT) Date: Wed, 21 May 2003 08:10:14 -0700 (PDT) Message-Id: <200305211510.h4LFAEC6016849@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Tor.Egge@cvsup.no.freebsd.org Subject: Re: kern/51964: panic: race condition with realitexpire() called for zombie X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tor.Egge@cvsup.no.freebsd.org List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 15:10:15 -0000 The following reply was made to PR kern/51964; it has been noted by GNATS. From: Tor.Egge@cvsup.no.freebsd.org To: jilles@stack.nl Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/51964: panic: race condition with realitexpire() called for zombie Date: Wed, 21 May 2003 15:06:18 GMT > The system has not panicked since I upgraded and applied the patch > (about 8 days ago), so it seems to be fixed. The X server has been > started and shut down many times (we use X -once -query ...). The patch > should perhaps be committed. I've been told that a hopefully better fix (without overhead in the common case) is being worked on. > The race condition (when callout_stop() is called, another thread may > still be executing in the callout function) may be present in other > parts of the system as well. Correct. - Tor Egge