From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 1 07:18:02 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 448B316A41F for ; Thu, 1 Dec 2005 07:18:02 +0000 (GMT) (envelope-from SRS0=bYBb3nBG=Z6=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ECBC43D5F for ; Thu, 1 Dec 2005 07:18:00 +0000 (GMT) (envelope-from SRS0=bYBb3nBG=Z6=metro.cx=fbsd@sonologic.nl) Received: from [192.168.0.24] ([212.41.157.237]) (authenticated bits=0) by mx1.sonologic.nl (8.13.3/8.13.3) with ESMTP id jB17Hprv027624 for ; Thu, 1 Dec 2005 07:17:57 GMT Message-ID: <438EA3C7.4070509@metro.cx> Date: Thu, 01 Dec 2005 08:18:31 +0100 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 212.41.157.237 is authenticated by a trusted mechanism) Subject: RELENG-5 20050101 panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 07:18:02 -0000 Hi All, I am wondering if the trace below rings a bell to someone. I'm trying to find out what is wrong with 5.4 on a certain box i have (see panic in propagate priority thread earlier on). Since debugging did not seem to help much, i'm now trying the hard way: cvsupping kernels from RELENG-5 at points along the 5.3 --> 5.4 dates, effectivelly doing a binary search to pinpoint where the problem was introduced (5.3 runs fine on the problem boxes). But now i am getting the trace below, since it is different from what I had before, i am wondering if this is maybe some bug that got fixed long ago. The kernel i have running now is from 2005-01-01. For some more info on my original problem, i put some stuff online at http://www.sonologic.nl/fbsd/. Best, Koen (ps, upgrading to 6.x is not an option at this point, since i now it to be running fine on 5.3 but not on 5.4, i want to find out first whether this particular unstability was fixed in 6.x because once i'm on 6.x, downgrading to 5.3 is less feasible if things turn out to go even worse) Limiting closed port RST response from 247 to 200 packets/sec Limiting closed port RST response from 237 to 200 packets/sec mode = 0100600, inum = 652933, fs = /var panic: ffs_valloc: dup alloc cpuid = 1 KDB: stack backtrace: kdb_backtrace(100,c32567d0,c58e8e38,603,c3086000) at kdb_backtrace+0x29 panic(c069abcc,c069abab,8180,9f685,c30860d4) at panic+0x114 ffs_valloc(c3b80000,8180,c32d7680,e8fc0900,e8fc094c) at ffs_valloc+0x149 ufs_makeinode(8180,c3b80000,e8fc0bf8,e8fc0c0c) at ufs_makeinode+0x59 ufs_create(e8fc0a84,e8fc0b40,c0552c20,e8fc0a84,d6ea7648) at ufs_create+0x26 ufs_vnoperate(e8fc0a84) at ufs_vnoperate+0x13 vn_open_cred(e8fc0be4,e8fc0ce4,180,c32d7680,18a) at vn_open_cred+0x174 vn_open(e8fc0be4,e8fc0ce4,180,18a,c3f1b000) at vn_open+0x1e kern_open(c32567d0,97fca20,0,603,180) at kern_open+0xe3 open(c32567d0,e8fc0d14,3,c65,286) at open+0x18 syscall(2f,2f,bfbf002f,602,180) at syscall+0x283 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x283876bb, esp = 0xbfbfd01c, ebp = 0xbfbfd048 --- KDB: enter: panic [thread 100185] Stopped at kdb_enter+0x2b: nop db> continue -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/