From owner-freebsd-hackers Thu Apr 5 9: 2:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from forkbomb.martini.nu (forkbomb.martini.nu [204.118.247.250]) by hub.freebsd.org (Postfix) with ESMTP id DC69037B424 for ; Thu, 5 Apr 2001 09:02:12 -0700 (PDT) (envelope-from reich@forkbomb.martini.nu) Received: (from reich@localhost) by forkbomb.martini.nu (8.11.1/8.11.1) id f35GAh811135 for hackers@freebsd.org; Thu, 5 Apr 2001 09:10:43 -0700 (PDT) (envelope-from reich) Date: Thu, 5 Apr 2001 09:10:42 -0700 From: Mahlon Smith To: hackers@freebsd.org Subject: Re: pmap bomb on 4.0-STABLE Message-ID: <20010405091042.A7805@internetcds.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9AFB@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9AFB@l04.research.kpn.com>; from "K.J.Koster@kpn.com" on Thu, Apr 05, 2001 at 09:57:10AM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Can anyone tell me what this means - and even better, a fix? It's > > my understanding that pmap concerns shared memory, is it possible > > I have a bad stick of ram floating around? > > > Bad memory sticks are easy to find. Just rip out half the RAM and let the > box run for a few days, then let it run off the other half for a while. Of course, this is pretty far from scientific troubleshooting, especially when it crashes at random times. It's also highly undesirable to cripple the machine, considering it's a production box. I just need to know if pmap_entry really does have anything to do with physical ram, before I go off on a ram swapping goose chase, just to find out a month down the road the problem isn't fixed. -- Mahlon Smith InternetCDS http://www.internetcds.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message