Date: Thu, 5 Apr 2001 12:55:07 -0400 From: "Joseph Gleason" <clash@fireduck.com> To: "Mahlon Smith" <reich@internetcds.com>, <hackers@FreeBSD.ORG> Subject: Re: pmap bomb on 4.0-STABLE Message-ID: <002801c0bdf1$2b5124c0$dc02010a@battleship> References: <59063B5B4D98D311BC0D0001FA7E452205FD9AFB@l04.research.kpn.com> <20010405091042.A7805@internetcds.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A friend of mine swears by this memory testing utility: http://reality.sgi.com/cbrady_denver/memtest86/ Apparently it tries a bunch of diffrent test patters that are likely to find memory problems that a simple test wouldn't find. It is cool because you just just write the image to a 1.44mb floppy and boot from that to do the test. A major downside is how long it takes. It takes around 8 hours on my laptop to do the full suite of tests. Not very useful for a production server..but something that probably be done on every system you create before you move it to producton. Joe Gleason ----- Original Message ----- From: "Mahlon Smith" <reich@internetcds.com> To: <hackers@FreeBSD.ORG> Sent: Thursday, April 05, 2001 12:10 Subject: Re: pmap bomb on 4.0-STABLE > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002801c0bdf1$2b5124c0$dc02010a>