HPE ProLiant DL380 Gen9 memory address range

[PVacca]

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"

sesame@server03:~> sudo dmidecode -t 17 | grep 32\ G | wc -l

24

sesame@server03:~> sudo dmidecode -t 19

# dmidecode 3.2

Getting SMBIOS data from sysfs.

SMBIOS 2.8 present.

Handle 0x0024, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x00000000000

Ending Address: 0x0007FFFFFFF

Range Size: 2 GB

Physical Array Handle: 0x000A

Partition Width: 1

Handle 0x0025, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x0000000100000000k

Ending Address: 0x000000907FFFFFFFk

Range Size: 574 GB

Physical Array Handle: 0x000B

Partition Width: 1

In other (non HPE) systems it shows each DIMM (this server has 4x 32GB)

[kansas] sesame@ctl-01:~$ sudo dmidecode -t 19

# dmidecode 3.1

Getting SMBIOS data from sysfs.

SMBIOS 3.0.0 present.

Handle 0x0037, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x00000000000

Ending Address: 0x007FFFFFFFF

Range Size: 32 GB

Physical Array Handle: 0x0036

Partition Width: 4

Handle 0x003D, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x00800000000

Ending Address: 0x00FFFFFFFFF

Range Size: 32 GB

Physical Array Handle: 0x003C

Partition Width: 4

Handle 0x0043, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x01000000000

Ending Address: 0x017FFFFFFFF

Range Size: 32 GB

Physical Array Handle: 0x0042

Partition Width: 4

Handle 0x0049, DMI type 19, 31 bytes

Memory Array Mapped Address

Starting Address: 0x01800000000

Ending Address: 0x01FFFFFFFFF

Range Size: 32 GB

Physical Array Handle: 0x0048

Partition Width: 4

[support_s]

System recommended content:

1. HPE ProLiant DL380 Gen9 Server - Overview

2. HP ProLiant DL380 G4, DL360 G4p Servers - Dual-Ranked DIMMS Information

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[PVacca]

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".

[Suman_1978]

Hi,

There are some resources outside, please see if they can help your query.

https://stackoverflow.com/questions/41107702/how-to-programmatically-get-physical-memory-address-range-in-linux
https://unix.stackexchange.com/questions/108035/is-it-possible-to-find-the-physical-address-range-of-a-dimm
https://www.linuxtechi.com/dmidecode-command-examples-linux/

Thank You!
I work with HPE but opinions expressed here are mine.
Recent Support Video Releases