From owner-freebsd-stable Mon Oct 28 2:19: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1EAE37B401 for ; Mon, 28 Oct 2002 02:19:02 -0800 (PST) Received: from util.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 159BF43E42 for ; Mon, 28 Oct 2002 02:19:02 -0800 (PST) (envelope-from spork@inch.com) Received: from inch.com (inch.com [216.223.192.20]) by util.inch.com (8.12.6/8.12.6/UTIL-INCH-3.0.9) with ESMTP id g9SAItiN024806 for ; Mon, 28 Oct 2002 05:18:55 -0500 (EST) (envelope-from spork@inch.com) Date: Mon, 28 Oct 2002 05:18:55 -0500 (EST) From: Charles Sprickman To: stable@freebsd.org Subject: Problems with large memory configs? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I seem to be seeing a pattern here as we upgrade some boxes from 1GB to 2GB of memory... We get random lockups. No panic, just a hang. And only during high cpu load. Been through the hardware (server boards are both Supermicro and Intel) and we're not seeing any heat problems, all the fans are spinning, etc. I seem to recall a few threads not too long ago where people with busy machines running 2GB+ of memory and high loads were seeing similar. Wish I had a crashdump to share, but it's just hanging. Can anyone comment on recent vm changes from 4.6.2 -> 4.7 -> -stable? These boxes are all a step behind at 4.6.2. And if anyone has general troubleshooting tips for this sort of situation, I'd appreciate it. We are collecting a whole mess of stats (vmstat,iostat,ps,pstat,netstat -m,netstat) every five minutes. But all that's telling me is when the machine works hard, it locks up... Thanks, Charles -- Charles Sprickman spork@inch.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message