From owner-freebsd-current@FreeBSD.ORG Sun Feb 4 21:48:10 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 DCB5916A402 for ; Sun, 4 Feb 2007 21:48:10 +0000 (UTC) (envelope-from flo@kasimir.com) Received: from config.solomo.org (h994948.serverkompetenz.net [85.214.51.166]) by mx1.freebsd.org (Postfix) with ESMTP id 5A8D013C491 for ; Sun, 4 Feb 2007 21:48:10 +0000 (UTC) (envelope-from flo@kasimir.com) Received: (qmail 65470 invoked from network); 4 Feb 2007 22:21:28 +0100 Received: from i53879797.versanet.de (HELO nibbler-osx.local) (83.135.151.151) by config.solomo.org with SMTP; 4 Feb 2007 22:21:28 +0100 Message-ID: <45C64E3A.7050407@kasimir.com> Date: Sun, 04 Feb 2007 22:20:58 +0100 From: "Florian C. Smeets" User-Agent: Thunderbird 2.0b2 (Macintosh/20070116) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 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: Sun, 04 Feb 2007 21:48:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i can trigger this kind of panic quite easily where running mldonkey-devel port and downloading something via BitTorrent. This is -current as of Feb 03 2007. I upgraded this box from -stable to - -current end November 2006 and it has been happening since. When i do not run mldonkey the box is quite stable e.g. no other panics. Google turned up only one other occurrence of this on a german BSD forum, mldonkey was also involved there... I already have "options SOCKBUF_DEBUG" enabled. What can i do to get more useful information ? I have a dump but it seems to be corrupted... I'll try to get a usable dump. This happens with stock FreeBSD ppp as well as with mdp4 from ports. Kernel is a stripped down GENERIC wich pf added. Here the trace from ddb: panic: sbflush_internal: cc 4294966301 || mb 0 || mbcnt 0 KDB: enter: panic [thread pid 53458 tid 100128 ] Stopped at kdb_enter+0x2b: nop db> where Tracing pid 53458 tid 100128 td 0xc12abcb0 kdb_enter(c06ace58) at kdb_enter+0x2b panic(c06b0aae,fffffc1d,0,0,c133919c,...) at panic+0xbb sbflush_internal(c133919c,c8109aa0,c05516ee,c133919c,c133914c,...) at sbflush_internal+0x6f sbflush_locked(c133919c) at sbflush_locked+0xb sbflush(c133919c,c133914c,c1316150,0,c133914c,...) at sbflush+0x3a tcp_disconnect(c134eb28) at tcp_disconnect+0x4b tcp_usr_disconnect(c133914c,c8109af8,c05525b9,c133914c,0,...) at tcp_usr_disconnect+0x88 sodisconnect(c133914c,0,c13213a8,0,0,...) at sodisconnect+0x26 soclose(c133914c) at soclose+0x31 soo_close(c13213a8,c12abcb0) at soo_close+0x5f fdrop_locked(c13213a8,c12abcb0,c18cd900,c8109ba4,c04ef3c7,...) at fdrop_locked+0xc8 fdrop(c13213a8,c12abcb0,c0f74b84,c093ab80,0,...) at fdrop+0x3d closef(c13213a8,c12abcb0) at closef+0x407 fdfree(c12abcb0) at fdfree+0x56b exit1(c12abcb0,0,c8109d2c,c0680b12,c12abcb0,...) at exit1+0x427 exit1(c12abcb0,c8109d00) at exit1 syscall(c8109d38) at syscall+0x2a2 Xint0x80_syscall() at Xint0x80_syscall+0x20 - --- syscall (3, FreeBSD ELF32, read), eip = 0x2, esp = 0x292, ebp = 0 --- Let me know if i can do anything more to help tracking this down. Cheers Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFFxk46A+1tjUZ1YScRAhp3AJ9hLrTU8kSqLAMIvTC25n1XPhWyygCgnenx HrUVO/p96QSgeytpJE7j7xc= =p0WP -----END PGP SIGNATURE-----