Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Jun 1999 16:40:48 -0400 (EDT)
From:      Chuck Robey <chuckr@picnic.mat.net>
To:        =?ISO-9550?B?o8C359TCv82jwA==?= <fengyue@bluerose.windmoon.nu>
Cc:        freebsd-isp@FreeBSD.ORG
Subject:   Re: What is likely to be wrong?
Message-ID:  <Pine.BSF.4.10.9906021637460.82061-100000@picnic.mat.net>
In-Reply-To: <Pine.BSF.4.10.9906021316170.17995-100000@bluerose.windmoon.nu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Jun 1999, [ISO-9550] £À·çÔ¿ͣÀ wrote:

> 
> 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!!

First, your memory test is worthless on too many grounds to go into;
it's not only basically worthless, the test isn't even being performed
on the memory you think it is.

Second, just how long did you wait on booting, before deciding it was
hung?  It sure sounds like it was trying to do a network lookup, and
hung up for maybe 5 minutes while it was waiting network timeout, for a
namerserver it was probably incorrectly set for.  Be a little more
patient, it'll probably work.

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@picnic.mat.net       | communications topic, C programming, and Unix.
213 Lakeside Drive Apt T-1  |
Greenbelt, MD 20770         | I run picnic (FreeBSD-current)
(301) 220-2114              | and jaunt (Solaris7).
----------------------------+-----------------------------------------------






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906021637460.82061-100000>