From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 20 02:36:32 2003 Return-Path: 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 CBB1137B401; Sun, 20 Apr 2003 02:36:32 -0700 (PDT) Received: from demos.su (mx.demos.su [194.87.0.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E96843F75; Sun, 20 Apr 2003 02:36:31 -0700 (PDT) (envelope-from mitya@fling-wing.demos.su) Received: from [194.87.5.69] (HELO fling-wing.demos.su) by demos.su (CommuniGate Pro SMTP 4.0.6/D4) with ESMTP-TLS id 67653534; Sun, 20 Apr 2003 13:36:29 +0400 Received: from fling-wing.demos.su (localhost [127.0.0.1]) by fling-wing.demos.su (8.12.9/8.12.6) with ESMTP id h3K9aTAu078075; Sun, 20 Apr 2003 13:36:29 +0400 (MSD) (envelope-from mitya@fling-wing.demos.su) Received: (from mitya@localhost) by fling-wing.demos.su (8.12.9/8.12.6/Submit) id h3K9aS3v078074; Sun, 20 Apr 2003 13:36:28 +0400 (MSD) Date: Sun, 20 Apr 2003 13:36:28 +0400 From: Dmitry Sivachenko To: Don Lewis Message-ID: <20030420093628.GA76333@fling-wing.demos.su> References: <20030420073047.GA64397@fling-wing.demos.su> <200304200816.h3K8GGXB020865@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200304200816.h3K8GGXB020865@gw.catspoiler.org> WWW-Home-Page: http://mitya.pp.ru/ X-PGP-Key: http://mitya.pp.ru/mitya.asc User-Agent: Mutt/1.5.4i cc: hackers@FreeBSD.org Subject: Re: Repeated similar panics on -STABLE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2003 09:36:33 -0000 On Sun, Apr 20, 2003 at 01:16:16AM -0700, Don Lewis wrote: > On 20 Apr, Dmitry Sivachenko wrote: > > On Sat, Apr 19, 2003 at 03:15:20PM -0700, Don Lewis wrote: > If we don't get into the "if" block, these will contain leftover > garbages from the stack. > > > (kgdb) p va > > $16 = 0x5cdd8000
> > Interesting ... how does va get the same value as kbp? Is it coming > from the > va = (caddr_t) kmem_malloc() > assignment in the "if" block that we don't think we're executing, or the > va = kbp->kb_next; > assignment that is causing the panic? > > If kbp is pointing to a non-existent page, why does Terry's patch seem > to fix the problem for you? Well, here is probably a misunderstanding.. We did NOT apply Terry's patch. Let me quote a bit from my e-mail to Terry: TL> Did my patch fix your problem? TL> TL> Or did you tune your kernel, as I suggested, to fix your problem? TL> TL> Or is it still a problem? DS>We changed maxusers from 512 to 0 and decreased the number of DS>NMBCLUSTERS. Now everything is working fine, but since these panics occured DS>about once a week I can't say for sure they are completely gone. DS>Let's wait at least one more week... Thus I wanted to say that we only tuned maxusers and NMBCLUSTERS. We run virgin -STABLE kernel without any patches. Probably my english leaves much to be desired ;-(( > > I wonder if things are getting further munged after the trap occurs? > That would make it more difficult to track down the problem from the > core file. > > Something else of interest to print is > bucket[7] > bucket[7].kb_next and bucket[7].kb_last might shed some light. > (kgdb) up 22 #22 0xc015daff in malloc (size=72, type=0xc029fee0, flags=0) at /mnt/se3/releng_4/src/sys/kern/kern_malloc.c:243 243 va = kbp->kb_next; (kgdb) p bucket[7] $1 = {kb_next = 0x5cdd8000
, kb_last = 0xc8fcb000 "", kb_calls = 2127276, kb_total = 4256, kb_elmpercl = 32, kb_totalfree = 1264, kb_highwat = 160, kb_couldfree = 5497} (kgdb) p bucket[7].kb_next $2 = 0x5cdd8000
(kgdb) p bucket[7].kb_last $3 = 0xc8fcb000 "" (kgdb) > > Something interesting is that the fault address, and the values of va > and kbp are the same in both stack frames ... > > > One other question ... is your kernel compiled with INVARIANTS? That > changes the definition of struct freelist. Without. PS: If you need additional information, feel free to ask. I am more than willing to help.