Re: Problems with AMD64 and 8 GB RAM?

From: Scott Long (scottl_at_samsco.org)
Date: 03/31/05

  • Next message: Scott Long: "Re: Problems with AMD64 and 8 GB RAM?"
    Date: Wed, 30 Mar 2005 16:01:14 -0700
    To: "Greg 'groggy' Lehey" <grog@freebsd.org>
    
    

    Greg 'groggy' Lehey wrote:
    > On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote:
    >
    >>On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote:
    >>
    >>>None of these problems occur when I use 4 GB memory. About the only
    >>>strangeness, which seems to come from the BIOS, is that it recognizes
    >>>only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB
    >>>memory.
    >>>
    >>>I realize that this isn't enough to diagnose the problem. The reason
    >>>for this message now is to ask:
    >>>
    >>>1. Has anybody else seen this problem?
    >>>2. Has anybody else used this hardware configuration and *not* seen
    >>> this problem?
    >>>3. Where should I look next?
    >>
    >>Have you run sysutils/memtest86 with the 8 GB?
    >
    >
    > Heh. Difficult when the system doesn't run.
    >
    >
    >>I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB
    >>Reg. ECC DIMMs.
    >
    >
    > OK, this makes sense. It might also explain why the 4 GB
    > configuration only recognizes 3.5 GB.
    >

    No, and I'm going to make this an FAQ and post it in a very obvious
    place, since 4+ GB is so easy to get and people don't seem to understand
    the PC architecture very well.

    Almost all systems put the PCI Memory Mapped IO window into the 3.75-4GB
    region of the physical memory map. The registers for the APICs and
    other system resources are also typically in this region. Now with
    PCI-Express, the Memory Mapped PCI config registers are typically being
    mapped in the 3.5-3.75GB range. The memory controllers, host bridges,
    north-bridges, and/or whatever else glues the memory to the bus to the
    CPU decode these addresses into PCI cycles, not RAM cycles. Some
    systems are smart and re-map the RAM that is hidden by these holes into
    a region >4GB. Some systems are dumb, though, and just deny you access
    to the RAM that is covered up. It's very much like the old days of the
    XT/AT architecture when you had 1MB of RAM but everything above 640k was
    hidden by the VGA framebuffer, ISA option ROMs, and system BIOS, but
    some systems where smart enough to relocate the hidden RAM.

    So, your missing .5GB is almost certainly not due to defective RAM, it's
    just due to The Way Things Are. It's a lot harder for Opteron systems
    to be smart about this than Xeon systems since all of the remapping
    magic can happen in the hostbridge on the Xeon, while the Opertons need
    to have their built-in memory controllers programmed specially for it.

    Scott
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: Scott Long: "Re: Problems with AMD64 and 8 GB RAM?"

    Relevant Pages

    • Re: URGENT - 4GB of RAM not recognized in Win XP Pro
      ... "The AMD-760 MPX requires a portion of memory to be reserved for PCI ... money he should install it and not worry about the little that's lost. ... since Windows is using the addresses (not RAM, ...
      (microsoft.public.windowsxp.hardware)
    • Re: huge box of ram?
      ... The hard part is the ECC, the memory ... acquire this is to buy a disk array with a lot of cache RAM. ... Well, fine, what about the same thing without the disks? ... you will have multiple PCI busses at this ...
      (comp.arch.storage)
    • Re: Random Restarts - Please Help
      ... I upgraded my BIOS a long time ago ... Beginners Guides: Diagnosing Bad Memory ... How to diagnose bad RAM ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Alocated Memory Error (SQLSERVR)
      ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
      (microsoft.public.windows.server.sbs)
    • Re: help
      ... choices and found the RAM memory test option and ran it, ... second later that the DIMM RAM chip showed error after error. ... I would bet that the fan ... > inspection, and swapped suspected parts around, and got no boot ...
      (microsoft.public.windowsxp.general)