Tom Nabarro

> > LGTM, this PR is adding the incarnation information into the database and a subsequent PR will use the added information. > > Thanks, Tom. Just a clarification: The...

Relevant output from `ipmctl show -system` showing the "ProximityDomain` values: ``` ---TableType=0x0 Length: 56 bytes TypeEquals: SpaRange AddressRangeType: 66f0d379-b4f3-4074-ac43-0d3318b78cdb SpaRangeDescriptionTableIndex: 0x1 Flags: 0x2 ProximityDomain: 0x3 SystemPhysicalAddressRangeBase: 0x4080000000 SystemPhysicalAddressRangeLength: 0xfc00000000 MemoryMappingAttribute:...

Also have an almost identical IceLake system which maps region0 to NUMA-1 and region1 to NUMA-0: ``` [root@wolf-220 ~]# ndctl list -Rv { "regions":[ { "dev":"region1", "size":1082331758592, "align":16777216, "available_size":0, "max_available_extent":0,...

_Maybe you could at lest try the current ndctl?_ I am on the latest version provided by the distro I am running: ``` [root@wolf-220 ~]# ndctl -v 71.1 [root@wolf-220 ~]#...

I re-provisioned the problem IceLake host with Leap15.3 and upgraded ipmctl to v03 and ndctl to v73 (exact versions below), problem persists (pmem0 on numa1 & pmem1 on numa0): ```...

Two systems have been mentioned, one has both pmem mapped to zero (wolf-216) and the other has pmem1 mapped to numa0 and pmem0 mapped to numa1 (wolf-220). Neither issue has...

> I don't see a problem with pmem1 mapped to numa0 - the device order is not guaranteed. > > As for both regions mapped to numa0 you did not...

I got access to the system, re-provisioned to leap15.3 and updated ipmctl and ndctl to latest. After removing regions, rebooting, creating regions, rebooting, the same issue persists where both regions...

Not directly related to https://github.com/intel/ipmctl/issues/156 as ProximityDomain field values are nonzero: ``` ---TableType=0x0 Length: 56 bytes TypeEquals: SpaRange AddressRangeType: 66f0d379-b4f3-4074-ac43-0d3318b78cdb SpaRangeDescriptionTableIndex: 0x1 Flags: 0x2 ProximityDomain: 0x3 SystemPhysicalAddressRangeBase: 0x4080000000 SystemPhysicalAddressRangeLength: 0xfc00000000...

related/duplicate https://github.com/pmem/ndctl/issues/130