From owner-freebsd-current@FreeBSD.ORG Thu Nov 10 19:42:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AD0416A41F for ; Thu, 10 Nov 2005 19:42:23 +0000 (GMT) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08ABC43D46 for ; Thu, 10 Nov 2005 19:42:22 +0000 (GMT) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.12.11/8.12.11) with ESMTP id jAAJgLQS093930; Thu, 10 Nov 2005 13:42:21 -0600 (CST) (envelope-from tinguely@casselton.net) Received: (from tinguely@localhost) by casselton.net (8.12.11/8.12.11/Submit) id jAAJgLNq093929; Thu, 10 Nov 2005 13:42:21 -0600 (CST) (envelope-from tinguely) Date: Thu, 10 Nov 2005 13:42:21 -0600 (CST) From: Mark Tinguely Message-Id: <200511101942.jAAJgLNq093929@casselton.net> To: current@freebsd.org, mcsi@mcsi.pp.ru In-Reply-To: <43737817.8030300@mcsi.pp.ru> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ccn.casselton.net Cc: wpaul@windriver.com Subject: Re: CURRENT panics sometimes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 19:42:23 -0000 We are chasing a different panic (kern/88725) where dynamic callout are freed but the callout could be still pending. The freed memory can be re-allocated, modified and then cause errors when the timer wheel is checked. After finding this one occurance, I did a complete search of callouts, and I see a potential simular error in the ntoskrnl_libfini() routine in the file /sys/compat/ndis/subr_ntoskrnl.c and a few other places (7 total). I wanted to make verify each of these 7 occurances before issuing a patch. I suspect a simple test loop could verify that this is a simular error as kern/88725. --Mark Tinguely