Skip to content

Troubleshooting

Installation Issues

By default, Memory Viewer will install to /opt/memverge. If there are issues during the installation, see /var/log/memverge/package_install.log for details.

Modifications to 'cxl_user_defined.json' are not shown in the UI

After modifying the /etc/memverge/cxl_user_defined.json file, the changes are not seen in the UI. Check the /var/log/memverge/mmlet log file for errors. For example, the UI will ignore the cxl_user_defined.json if the contents are not valid JSON. The log file may contain errors similar to:

$ tail -1 /var/log/memverge/mmlet
2023/10/04 21:56:48 Failed to parse /etc/memverge/cxl_user_defined.json: invalid character '{' looking for beginning of object key string

Restarting the mmlet.service should re-read the file and display the changes:

$ sudo systemctl restart mmlet

One or more CXL Devices appear without a connection to a CPU

When Memory Viewer cannot automatically identify the correct CPU to which a CXL device is physically attached to, that device will appear in the UI within the "CXL Devices with Unidentified CPU IDs" section of the System Topology view. For example:

Screenshot 2023-10-05 at 8.38.19 PM

To resolve this issue, use the cxl_user_defined.json file described in Section 4.0 to set CPUPackageID to the correct CPU Socket ID. For example, the following will connect the CXL Device on Bus, Device, Function "108:00.0" to CPU Socket 0.

$ sudo vim /etc/memverge/cxl_user_defined.json
[
    {
      "PCIBusID": "0000:108:00.0",
      "CPUPackageID": 0
    }
]