From owner-freebsd-isp Wed Jun 2 13:25:51 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bluerose.windmoon.nu (c66498-a.plstn1.sfba.home.com [24.1.123.43]) by hub.freebsd.org (Postfix) with ESMTP id EE6B414E0B for ; Wed, 2 Jun 1999 13:25:44 -0700 (PDT) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (Windmoon-Patched/8.9.3/8.9.3) with ESMTP id NAA18004 for ; Wed, 2 Jun 1999 13:31:50 -0700 (PDT) Date: Wed, 2 Jun 1999 13:31:50 -0700 (PDT) From: =?ISO-9550?B?o8C359TCv82jwA==?= To: freebsd-isp@FreeBSD.ORG Subject: What is likely to be wrong? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi guys, I've a AMD K2-400MHZ w/64MB RAM two IDE HD. Last night I did a 3.2 FTP install, it all went fine. Then, I configure and rebuild the kernel, and reboot the box with the new kernel, it hanged after printing "Init network setup: hostname" while the kernel.GENERIC just boots fine. So, I cvsup'ed enitre source to 3.2-stable, and did a make depend in single user mode, after a long while, the mkdep process core dumped (signal 11). It sounds like a bad memory chip to me, so I replaced the 64MB with a 32MB ram from another box and did a make clean;make depend again, again, the mkdep core dumped with signal 6. I then put back the 64MB memory and wrote a little program to test the memory; while (1){ if (p = malloc (1000000)) { memset (p,0,1000000); memcpy (p,buf,1000000); memcpy (buf,p,1000000); } usleep (500); } Have that run for a long while until it uses up the entire swap space. In this case, I assume the memory is actually OK. So, my question is what else could be wrong? The entire motherboard or maybe even the CPU? Any hints where to look for the problem? Thanks in adv!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message