RAM problems

2006-10-01 Thread Dino Vliet
Dear bsd people,

I have this amd64 system running freebsd 6.1 with 1 GB
of RAM and everything worked very well. Then I've
added some  more ram, 2 gb extra, to be precise and
aft first it seemd everything worked fine. I could
load larger files and my java apps didn't give me
out-of -memory problems anymore.

But everytime I want to upgrade my ports or compile a
new kernel, the machine would freeze and the only way
to go was to use the reset button. I don't like the
look of that.

Has anyone had similar experiences? I've had two 512MB
corsair memory banks, and added two 1GB banks (oem).

I find it really strange that I can use the bigger RAM
but compiling gives problems. Could it also be that
the banks could be attached better in my motherboard?

What should I do now? Continue using it, without
portupgrading or compiling a new kernel or ask a new
pair of banks at the store?

Thanks

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RAM problems

2006-10-01 Thread stan
On Sun, Oct 01, 2006 at 09:00:39AM -0700, Dino Vliet wrote:
 Dear bsd people,
 
 I have this amd64 system running freebsd 6.1 with 1 GB
 of RAM and everything worked very well. Then I've
 added some  more ram, 2 gb extra, to be precise and
 aft first it seemd everything worked fine. I could
 load larger files and my java apps didn't give me
 out-of -memory problems anymore.
 
 But everytime I want to upgrade my ports or compile a
 new kernel, the machine would freeze and the only way
 to go was to use the reset button. I don't like the
 look of that.
 
 Has anyone had similar experiences? I've had two 512MB
 corsair memory banks, and added two 1GB banks (oem).
 
 I find it really strange that I can use the bigger RAM
 but compiling gives problems. Could it also be that
 the banks could be attached better in my motherboard?
 
 What should I do now? Continue using it, without
 portupgrading or compiling a new kernel or ask a new
 pair of banks at the store?

I would start by making a memtest86 bootable disk/CD
and let it run ovenight, myself.

-- 
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RAM problems

2006-10-01 Thread Atom Powers

On 10/1/06, Dino Vliet [EMAIL PROTECTED] wrote:

Dear bsd people,

I have this amd64 system running freebsd 6.1 with 1 GB
of RAM and everything worked very well. Then I've
added some  more ram, 2 gb extra, to be precise and
aft first it seemd everything worked fine. I could
load larger files and my java apps didn't give me
out-of -memory problems anymore.



Does your system ever use more than 1GB memory during normal operation?

Based on the information you gave it seems to be an obvious problem,
bad or incompatible memory. To be certain, take out the memory upgrade
and try to buildworld again. No crash = bad memory.

It's probably a timing problem, if your new memory uses a slightly
different timing than the original memory it will appear to work
correctly untill you start to use it, then you will get crashes and
other weird behavior. Or it could be the memory slot, dust in it or
something. Or it could be the chipset, single-sided vs double-sided
memory. Or nearly a dozen other things. But it is probably not your
OS.

--
--
Perfection is just a word I use occasionally with mustard.
--Atom Powers--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: RAM problems

2006-10-01 Thread Tamouh H.
 
 Dear bsd people,
 
 I have this amd64 system running freebsd 6.1 with 1 GB of RAM 
 and everything worked very well. Then I've added some  more 
 ram, 2 gb extra, to be precise and aft first it seemd 
 everything worked fine. I could load larger files and my java 
 apps didn't give me out-of -memory problems anymore.
 
 But everytime I want to upgrade my ports or compile a new 
 kernel, the machine would freeze and the only way to go was 
 to use the reset button. I don't like the look of that.
 
 Has anyone had similar experiences? I've had two 512MB 
 corsair memory banks, and added two 1GB banks (oem).
 
 I find it really strange that I can use the bigger RAM but 
 compiling gives problems. Could it also be that the banks 
 could be attached better in my motherboard?
 
 What should I do now? Continue using it, without 
 portupgrading or compiling a new kernel or ask a new pair of 
 banks at the store?
 
 Thanks

Mixing memory brands/specs is a BAD idea. As previous suggested , do MEMTEST86 
on the new RAM by itself to spot any issues. But it could also be a conflict if 
using two different versions of RAM.

Tamouh


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RAM problems

2006-10-01 Thread Chris


On Oct 1, 2006, at 9:00 AM, Dino Vliet wrote:



What should I do now? Continue using it, without
portupgrading or compiling a new kernel or ask a new
pair of banks at the store?


I actually had a strikingly similar problem. I would freeze on  
portsnap updates. A -j8 buildworld would always get random  
segmentation faults. The handbook states the latter is a memory  
problem. The vendor insisted it was a FreeBSD problem but suggested I  
read the mobo manual (something I try to avoid). It turned out that  
when adding the additional memory, they had used consecutive slots  
rather than skip DIMM banks as the manual suggested (e.g., in my case  
using only 2 sticks required going to DIMM0 and DIMM2 leaving DIMM1  
empty on each of the CPU bank slots, though your details will vary).  
If your problem was as mine was, it isn't a FreeBSD problem but a  
mobo set up, bad stick or possibly memory incompatibility issue.


I'd think continuing as is will just cause the problem to appear in  
other ways and if incompatibility or failed stick, you are losing  
your money. BTW, on AMD64, I used the port memtest to find a bad stick.


Chris 
 
___

freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]