From owner-freebsd-current@FreeBSD.ORG Tue Nov 8 21:37:44 2005 Return-Path: X-Original-To: freebsd-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 921FA16A41F for ; Tue, 8 Nov 2005 21:37:44 +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 2F64543D48 for ; Tue, 8 Nov 2005 21:37:44 +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 jA8LbeWl097917; Tue, 8 Nov 2005 15:37:40 -0600 (CST) (envelope-from tinguely@casselton.net) Received: (from tinguely@localhost) by casselton.net (8.12.11/8.12.11/Submit) id jA8Lbdkm097916; Tue, 8 Nov 2005 15:37:39 -0600 (CST) (envelope-from tinguely) Date: Tue, 8 Nov 2005 15:37:39 -0600 (CST) From: Mark Tinguely Message-Id: <200511082137.jA8Lbdkm097916@casselton.net> To: freebsd-current@freebsd.org, snezhko@indorsoft.ru In-Reply-To: X-Spam-Status: No, score=0.6 required=5.0 tests=REPLY_TO_EMPTY autolearn=no version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ccn.casselton.net X-Mailman-Approved-At: Wed, 09 Nov 2005 05:26:10 +0000 Cc: max@love2party.net Subject: Re: CURRENT + amd64 + user-ppp = panic 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: Tue, 08 Nov 2005 21:37:44 -0000 This is great, you caught the kernel trashing a callout entry in uma_dbg. I cannot figure out how #14 linked the function sorecieved() to the inline function uma_zfree(). (thinking as I am typing) Could someone changed the recieve function call for this socket? In my opinion, you can remove the callout_check_callwheel function and calls. You want to always catch it before it corrupts, and that is done in the uma_dbg. Once you catch the corruption, we know it will panic in the near future, unless we are in the debugger long enough, for the timer to expire and be removed. I would completely delete the compile directory and "config" and do a fresh make. --Mark Tinguely