From owner-freebsd-net@FreeBSD.ORG Mon Jan 30 10:05:23 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA64A16A422 for ; Mon, 30 Jan 2006 10:05:23 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A08B43D5D for ; Mon, 30 Jan 2006 10:05:20 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k0UA5IQ7082348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jan 2006 13:05:18 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k0UA5Imn082347; Mon, 30 Jan 2006 13:05:18 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 30 Jan 2006 13:05:17 +0300 From: Gleb Smirnoff To: Meno Abels Message-ID: <20060130100517.GZ83922@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , Meno Abels , freebsd-net@freebsd.org References: <344de2870601271645j5f9029a3l@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <344de2870601271645j5f9029a3l@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: panic in sbdrop_locked X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2006 10:05:24 -0000 On Sat, Jan 28, 2006 at 01:45:07AM +0100, Meno Abels wrote: M> i have two boxes running currently freebsd-6.0-p3 i386 and they are M> panic around every 24 hour once a time. I just update to -p4 so i will M> see if it working better. I also didn't have the debug kernel ready so M> i can only provide this very weak infos: M> (kgdb) bt M> #0 0xc06e5b2c in doadump () M> #1 0xc06e60c0 in boot () M> #2 0xc06e6409 in panic () M> #3 0xc0731406 in sbdrop_locked () M> #4 0xc07b373e in tcp_input () M> #5 0xc07a93fe in ip_input () M> #6 0xc077a2b9 in netisr_processqueue () M> #7 0xc077a51f in swi_net () M> #8 0xc06cbfe8 in ithread_loop () M> #9 0xc06caebf in fork_exit () M> #10 0xc090fe1c in fork_trampoline () M> M> Is there any procedure to track this problem down other than have a M> debug kernel prepared what i done now-:) And have a very close look to M> the backtrace. I saw it M> happens sometimes in the development branches. Yes, the same backtrace with debugging kernel will be much more informative. Please followup when you got one. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE