Date: Tue, 18 Mar 2003 09:26:45 +0600 From: "Evgueni V. Gavrilov" <aquatique@rusunix.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Kirk McKusick <mckusick@McKusick.COM>, dwmalone@FreeBSD.org, Mike Makonnen <mtm@identd.net>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: kern/42277 Message-ID: <3E7691F5.9070902@rusunix.org> In-Reply-To: <20030317162051.R66343-100000@mail.chesapeake.net> References: <20030317162051.R66343-100000@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson wrote: >>The simple way to nail the culprint would be to move things out of >>the 128 bucket by adding to their malloc byte counts, but for such >>a strategy to work, we obviously need to be able to reproduce it >>fairly consistently. > > UMA has a facility to track the previous owner of the memory. Assuming > that is the problem I could give you a way to cache this information so we > can print it out when we detect corruption. I can work on this tonight. > What is the repro? As I told before the repro is funny: hard jobs such as world/release building runs fine. Panic occurs upon minimal activity. Maximal uptime achieved about 3 days. But usually panic comes faster - in 10-12 hours. In order to track down the issue before tarballing 4.8 I can apply any overbold patches/ideas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E7691F5.9070902>