From owner-freebsd-questions@freebsd.org Thu Jan 11 18:05:05 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFCC5E72A0A for ; Thu, 11 Jan 2018 18:05:05 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1C47D1A5 for ; Thu, 11 Jan 2018 18:05:05 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x22e.google.com with SMTP id d10so2835633oti.7 for ; Thu, 11 Jan 2018 10:05:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=V0CHOSgX4UMctpC8aFC+8LD8CGa5aRazfsyG7LrNGNU=; b=Y1SA2kcWJi6G7rWaLVcsRYC3qMD6xsPo+XAI7oBW/baT12q9eplcIi+sVOquu9xc4h fFh8EYiUkkRtxDWAj7LD8QHBu5pGNx8RVJv+IFUJcP/AZGCa/wy3He8nDfCw9UVxhc4f pqI/URaI4v+rpIv2tqgwKnXsTuIzOUZ2hFbG9A1PAq2wQ3FrYaGTKS+WZxql9zzttj26 tBLzzen+up5cfWPqLSCb3f31PwhZ01SfkbqD1UOlPTQ3jcpyY0o5LWz0sJWTd2TCUo9y 07vzJw5G39agUfQeyAqn3qcvtIMxuFyTK2wvvFwPyiRyM+jMrthC4q/4zCTzrOTFRNPE 2T4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=V0CHOSgX4UMctpC8aFC+8LD8CGa5aRazfsyG7LrNGNU=; b=etyC0mvoS4mXCeiDSAgaACla2OkvRc/O9rfs3CNzfFTunit5QeyNHIIy1hZWhkzIjo KuGglnrfdteTvbLFpvAE8fKl0Eqqe4GDKsfB4nYSYC4JwO0YuIAgD8f1ySNNOrapBOzE q6lbVCQm2HLtKUmIesAj4de67BhTH6QW9msIIdyLZOEgD3IFReKMEdLghrV5Oo6rIp9y 8jbjJnszg+h6/Mk5gW3Ua/3Cl/k9zlpUhzFsYI4dNH+nuoocv9tSu+x/gPKHzbZ2gogl Sz8nqxVCZMUhGe56zdt+KRkzsw03C3lfBu7EzkNVCaOTKljChCetsOhJIisDXvTGjDQB XhxQ== X-Gm-Message-State: AKwxyte+EG5gpEuAKlA4rIaue9a2asomNYwxBhaKLbeQV0/pWO0kx94B lE2GxVqHvnBQMvuVvZTQ9zaxWPqR/hh6mwhmM3Y= X-Google-Smtp-Source: ACJfBotf72eJlxhBj2V39Dvj5ntc3Pt0Jd31o4oQJrC9pWQOJMH6jtpfZjIr+pHix7jfHDldSss7qp4yf8HfNEzplnI= X-Received: by 10.157.9.33 with SMTP id 30mr13008250otp.344.1515693904584; Thu, 11 Jan 2018 10:05:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.0.2 with HTTP; Thu, 11 Jan 2018 10:05:03 -0800 (PST) In-Reply-To: References: <44wp0ofr1w.fsf@be-well.ilk.org> <50615.108.68.170.208.1515682927.squirrel@cosmo.uchicago.edu> From: Mehmet Erol Sanliturk Date: Thu, 11 Jan 2018 21:05:03 +0300 Message-ID: Subject: Re: OT: Max system physical memory To: Aryeh Friedman Cc: galtsev@kicp.uchicago.edu, Lowell Gilbert , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 18:05:05 -0000 On Thu, Jan 11, 2018 at 6:08 PM, Aryeh Friedman wrote: > On Thu, Jan 11, 2018 at 10:02 AM, Valeri Galtsev < > galtsev@kicp.uchicago.edu> > wrote: > > > > > On Thu, January 11, 2018 7:44 am, Lowell Gilbert wrote: > > > Aryeh Friedman writes: > > > > > >> My computer (HP Pavilion P7-1234, FreeBSD 11.1-RELEASE [amd64]) has 2 > > >> 240 > > >> pin DIMM (DDR3, PC3-10600) the manual says the max memory is 8 GB but > I > > >> see > > >> some 16 GB packages (2x8GB). If I put one or two of these in will it > > >> see > > >> the extra memory? > > > > > > Probably not. > > > > > > > It is hit and miss. It is possible that specifications were written based > > on largest available modules at the moment of writing. If replacement > > modules are compatible with memory controller (i.e., say, the same > > PC3-10600), it is possible they will work. There still is the chance they > > will not work reliably, _IF_ there are some less trivial specs of memory > > controller are involved. Such may be: bus amplifiers may only handle up > to > > this capacitive load before signals go out of specs. In general, larger > > RAM has larger numbers of address inputs connected to given lead, which > > may entail larger capacitive load. System board layout may have its > impact > > here as well. Apart from that (and maybe some internal schematic > specifics > > of memory controller), there is nothing fundamental about 8 GB RAM limit, > > so it may work. But chance is it will not. > > > > > sysutils/dmidecode disagrees with the manual thus deeping my confusion (I > bought the memory and use it in an other machine that does support upto > 32GB and only has 8 spread across 2 VM's): > > oot@lilith:~ # dmidecode -t memory > # dmidecode 3.1 > Scanning /dev/mem for entry point. > SMBIOS 2.7 present. > > Handle 0x000A, DMI type 16, 23 bytes > Physical Memory Array > Location: System Board Or Motherboard > Use: System Memory > Error Correction Type: None > Maximum Capacity: 128 GB > Error Information Handle: Not Provided > Number Of Devices: 2 > > Handle 0x000C, DMI type 17, 34 bytes > Memory Device > Array Handle: 0x000A > Error Information Handle: Not Provided > Total Width: 64 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: A1_DIMM0 > Bank Locator: A1_BANK0 > Type: DDR3 > Type Detail: Synchronous > Speed: 1333 MT/s > Manufacturer: Samsung > Serial Number: 938D8E07 > Asset Tag: A1_AssetTagNum0 > Part Number: M378B5273CH0-CH9 > Rank: 2 > Configured Clock Speed: 667 MT/s > > Handle 0x000E, DMI type 17, 34 bytes > Memory Device > Array Handle: 0x000A > Error Information Handle: Not Provided > Total Width: 64 bits > Data Width: 64 bits > Size: 4096 MB > Form Factor: DIMM > Set: None > Locator: A1_DIMM1 > Bank Locator: A1_BANK1 > Type: DDR3 > Type Detail: Synchronous > Speed: 1333 MT/s > Manufacturer: Samsung > Serial Number: 938D8C71 > Asset Tag: A1_AssetTagNum1 > Part Number: M378B5273CH0-CH9 > Rank: 2 > Configured Clock Speed: 667 MT/s > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > > Another problem may be required energy to feed higher capacity memory chips . If the currently available slots are not able to support the required energy , over time they may cause hardware failure and/or memory access errors . Mehmet Erol Sanliturk