From owner-cvs-all Mon Apr 29 10:12: 7 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3379E37B400; Mon, 29 Apr 2002 10:12:03 -0700 (PDT) Received: (from rwatson@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3THC3c34707; Mon, 29 Apr 2002 10:12:03 -0700 (PDT) (envelope-from rwatson) Message-Id: <200204291712.g3THC3c34707@freefall.freebsd.org> From: Robert Watson Date: Mon, 29 Apr 2002 10:12:02 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/kern kern_malloc.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG rwatson 2002/04/29 10:12:02 PDT Modified files: sys/kern kern_malloc.c Log: Revert a portion of kern_malloc.c:1.99, which (in addition to adding malloc profiling) also modified the set of pre-defined buckets for the memory allocator. For reasons unknown to me, this resulted in extensive memory corruption in the kernel, in particular on SMP boxes, so I'm committing this work-around until Jeff gets a chance to debug it properly. David Wolfskill pointed me at this commit as the one that might be a problem; I've been running this code on two dual-processor burn-in boxes for about 12 hours now, and the rate of panics due to memory corruption has dropped to zero (from one every five minutes). Hopefully not treading on the toes of: jeff Revision Changes Path 1.101 +3 -1 src/sys/kern/kern_malloc.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message