<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Query: HPE ProLiant DL380 Gen9 memory address range in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171352#M59189</link>
    <description>&lt;P&gt;Thank you for the reply but the system POSTs fine, it is fully populated with ther same DIMMs. I did not see anything in the overview that explains why this servrer groups all DIMMs into a sinlge "Memory Array Mapped Address".&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jul 2022 15:37:02 GMT</pubDate>
    <dc:creator>PVacca</dc:creator>
    <dc:date>2022-07-29T15:37:02Z</dc:date>
    <item>
      <title>HPE ProLiant DL380 Gen9 memory address range</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171340#M59187</link>
      <description>&lt;P&gt;Running dmidecode only shows the entire memory range, it does not break it up by DIMM. It does list all 24 32GB DIMMs but they are all grouped into "Main Memory"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;sesame@server03:~&amp;gt; sudo dmidecode -t 17 | grep 32\ G | wc -l&lt;/DIV&gt;&lt;DIV&gt;24&lt;/DIV&gt;&lt;DIV&gt;sesame@server03:~&amp;gt; sudo dmidecode -t 19&lt;/DIV&gt;&lt;DIV&gt;# dmidecode 3.2&lt;/DIV&gt;&lt;DIV&gt;Getting SMBIOS data from sysfs.&lt;/DIV&gt;&lt;DIV&gt;SMBIOS 2.8 present.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x0024, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x00000000000&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x0007FFFFFFF&lt;/DIV&gt;&lt;DIV&gt;Range Size: 2 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x000A&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 1&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x0025, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x0000000100000000k&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x000000907FFFFFFFk&lt;/DIV&gt;&lt;DIV&gt;Range Size: 574 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x000B&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 1&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;In other (non HPE) systems it shows each DIMM (this server has 4x 32GB)&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;[kansas] sesame@ctl-01:~$ sudo dmidecode -t 19&lt;/DIV&gt;&lt;DIV&gt;# dmidecode 3.1&lt;/DIV&gt;&lt;DIV&gt;Getting SMBIOS data from sysfs.&lt;/DIV&gt;&lt;DIV&gt;SMBIOS 3.0.0 present.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x0037, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x00000000000&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x007FFFFFFFF&lt;/DIV&gt;&lt;DIV&gt;Range Size: 32 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x0036&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 4&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x003D, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x00800000000&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x00FFFFFFFFF&lt;/DIV&gt;&lt;DIV&gt;Range Size: 32 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x003C&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 4&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x0043, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x01000000000&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x017FFFFFFFF&lt;/DIV&gt;&lt;DIV&gt;Range Size: 32 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x0042&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 4&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Handle 0x0049, DMI type 19, 31 bytes&lt;/DIV&gt;&lt;DIV&gt;Memory Array Mapped Address&lt;/DIV&gt;&lt;DIV&gt;Starting Address: 0x01800000000&lt;/DIV&gt;&lt;DIV&gt;Ending Address: 0x01FFFFFFFFF&lt;/DIV&gt;&lt;DIV&gt;Range Size: 32 GB&lt;/DIV&gt;&lt;DIV&gt;Physical Array Handle: 0x0048&lt;/DIV&gt;&lt;DIV&gt;Partition Width: 4&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 01 Aug 2022 06:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171340#M59187</guid>
      <dc:creator>PVacca</dc:creator>
      <dc:date>2022-08-01T06:39:23Z</dc:date>
    </item>
    <item>
      <title>Query: HPE ProLiant DL380 Gen9 memory address range</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171347#M59188</link>
      <description>&lt;P style="margin: 0;"&gt;&lt;STRONG&gt;System recommended content:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;1. &lt;A href="https://hpe.to/6600zFT2G" target="_blank" rel="noopener"&gt;HPE ProLiant DL380 Gen9 Server - Overview&lt;/A&gt;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;2. &lt;A href="https://hpe.to/6601zFT2H" target="_blank" rel="noopener"&gt;HP ProLiant DL380 G4, DL360 G4p Servers - Dual-Ranked DIMMS Information&lt;/A&gt;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Please click on "Thumbs Up/Kudo" icon to give a "Kudo".&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Thank you for being a HPE valuable community member.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2022 15:21:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171347#M59188</guid>
      <dc:creator>support_s</dc:creator>
      <dc:date>2022-07-29T15:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: Query: HPE ProLiant DL380 Gen9 memory address range</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171352#M59189</link>
      <description>&lt;P&gt;Thank you for the reply but the system POSTs fine, it is fully populated with ther same DIMMs. I did not see anything in the overview that explains why this servrer groups all DIMMs into a sinlge "Memory Array Mapped Address".&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2022 15:37:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171352#M59189</guid>
      <dc:creator>PVacca</dc:creator>
      <dc:date>2022-07-29T15:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: HPE ProLiant DL380 Gen9 memory address range</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171389#M59190</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;There are some resources outside, please see if they can help your query.&lt;/P&gt;&lt;P&gt;&lt;A href="https://stackoverflow.com/questions/41107702/how-to-programmatically-get-physical-memory-address-range-in-linux" target="_blank"&gt;https://stackoverflow.com/questions/41107702/how-to-programmatically-get-physical-memory-address-range-in-linux&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://unix.stackexchange.com/questions/108035/is-it-possible-to-find-the-physical-address-range-of-a-dimm" target="_blank"&gt;https://unix.stackexchange.com/questions/108035/is-it-possible-to-find-the-physical-address-range-of-a-dimm&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.linuxtechi.com/dmidecode-command-examples-linux/" target="_blank"&gt;https://www.linuxtechi.com/dmidecode-command-examples-linux/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank You!&lt;BR /&gt;I work with HPE but opinions expressed here are mine.&lt;BR /&gt;&lt;A href="https://support.hpe.com/connect/s/search?language=en_US#t=Videos&amp;amp;sort=%40hpescuniversaldate%20descending&amp;amp;layout=card&amp;amp;numberOfResults=100" target="_blank"&gt;Recent Support Video Releases&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Jul 2022 10:23:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpe-proliant-dl380-gen9-memory-address-range/m-p/7171389#M59190</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2022-07-30T10:23:29Z</dc:date>
    </item>
  </channel>
</rss>

