From owner-freebsd-current@FreeBSD.ORG Wed Feb 14 20:54:30 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC66516A408 for ; Wed, 14 Feb 2007 20:54:30 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id C5C9E13C471 for ; Wed, 14 Feb 2007 20:54:30 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id D9AE01AF34D; Wed, 14 Feb 2007 15:34:03 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 14 Feb 2007 15:34:03 -0500 X-Sasl-enc: uDiNucMNzG4mYDOGdzIRVolhw0wdcaHQsLGzt9ElyAgw 1171485243 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id CB3033060; Wed, 14 Feb 2007 15:34:02 -0500 (EST) Message-ID: <45D37239.1020100@FreeBSD.org> Date: Wed, 14 Feb 2007 20:34:01 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: "Florian C. Smeets" References: <45C64E3A.7050407@kasimir.com> In-Reply-To: <45C64E3A.7050407@kasimir.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: panic: sbflush_internal: cc 4294966301 || mb 0 || mbcnt 0 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: Wed, 14 Feb 2007 20:54:31 -0000 Florian C. Smeets wrote: > i can trigger this kind of panic quite easily where running > mldonkey-devel port and downloading something via BitTorrent. > I just triggered this same panic with -CURRENT as of 1430 UTC today. A ping(1) was backed up due to link layer problems; after I manually repatched to a different switch port, CTRL-C'ing the ping process triggered the panic: a--- 192.168.123.ni18 ping statistic:cs --- sbflush_internal: cc 84 || mb 0 || mbcnt 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x3a panic() at panic+0x1d5 sbflush_internal() at sbflush_internal+0x6a sbrelease_internal() at sbrelease_internal+0x1c sofree() at sofree+0x141 soclose() at soclose+0x380 soo_close() at soo_close+0x52 fdrop_locked() at fdrop_locked+0xe6 closef() at closef+0x366 fdfree() at fdfree+0x5ca exit1() at exit1+0x34b sys_exit() at sys_exit+0xe syscall() at syscall+0x264 Xfast_syscall() at Xfast_syscall+0xab --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x80092a79c, rsp = 0x7ffffffee718, rbp = 0x7ffffffee8d0 --- Regards, BMS