- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- HPE ProLiant DL380 Gen9 address decoding scheme
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2022 07:40 AM - last edited on 07-31-2022 11:20 PM by support_s
07-29-2022 07:40 AM - last edited on 07-31-2022 11:20 PM by support_s
HPE ProLiant DL380 Gen9 address decoding scheme
Is it possible to find the address decoding scheme for the HPE ProLiant DL380 Gen9? Attempting to use memtest86 and would like to be able to properly map memory addresses to DIMM slot/channel.
What i'm looking for if possible: (From memtest troubleshooting page)
If I know the address decoding scheme, can I configure MemTest86 to report the failing module?
For systems where the address decoding scheme is known, MemTest86 provides several configuration file parameters to aid users in determining the faulty module that corresponds to the memory address:
ADDR2CHBITS=12,9,7 ADDR2SLBITS=3,4 ADDR2CSBITS=8For each of these 3 parameters, a list of bit positions can be used to specify which address bits of a memory address to exclusive-or (XOR) in order to determine the corresponding [memory channel|slot|chip select (CS)] (0 or 1) of the failing module. This is only useful if you know that the memory controller maps a particular address to a [memory channel|slot|chip select (CS)] using this XOR-based decoding scheme. If these parameters are specified and MemTest86 detects a memory error, the [memory channel|slot|chip select (CS)] will be calculated and displayed along with the faulting address.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2022 08:40 AM
07-29-2022 08:40 AM
Query: HPE ProLiant DL380 Gen9 address decoding scheme
System recommended content:
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2022 03:23 AM
07-30-2022 03:23 AM
Re: HPE ProLiant DL380 Gen9 address decoding scheme
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
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
