search

intel / ipmctl

BSD 3-Clause "New" or "Revised" License
184 stars 62 forks source link

ipmctl show -memoryresources ,invalid PCD data #123

Closed chiachuanwu closed 4 years ago

chiachuanwu commented 4 years ago

tag v02.00.00.3658 "ipmctl show -memoryresources" command show invalid PCD data. the full log as below: One or more DIMMs have invalid PCD data. A platform reboot is recommended to restore valid PCD data, then try again.

Hardware Condition: Latest Intel Xeon processor Second generation Intel Optane DIMM.

But Master branch commit ID"a47b0b85fdbcee5ff94385fc2408136baf58f8a7" ipmctl show -memoryresources working fine on the same system.

kellycouch commented 4 years ago

Thanks for reporting, we will investigate this.

kellycouch commented 4 years ago

Is it possible for you to provide a recording file to expedite debug?

ipmctl start -session -mode record
ipmctl show -memoryresources
ipmctl dump -destination show-mr.pbr -session
ipmctl stop -session

Then attach the recorded file 'show-mr.pbr'.

chiachuanwu commented 4 years ago

show-mr.zip here you go.

chiachuanwu commented 4 years ago 
root@clr-f1430a4599d640e3b0b4de485393ee0f~ # ipmctl version
Intel(R) Optane(TM) DC Persistent Memory Command Line Interface Version 01.00.00.9999
 uname -a
Linux clr-f1430a4599d640e3b0b4de485393ee0f 5.3.11-868.native #1 SMP Wed Nov 13 15:46:39 PST 2019 x86_64 GNU/Linux
chiachuanwu commented 4 years ago

Please let me know any other information you need.

kellycouch commented 4 years ago

The error message was misleading/incorrect. This command failed because of inability to parse ACPI PMTT table. ipmctl v2.x is expecting PMTT table version 0.2, while your BIOS apparently published version 0.1. Looks like a defect in backwards compatibility... We'll look into it.

May I ask what platform you are on?

chiachuanwu commented 4 years ago

show-mr_good.zip ipmctl show -memoryresources command working fine on the other same platform, but with newer version of BIOS, i had attached recorded file for comparison.

mp15 commented 4 years ago

I can still replicate this bug using the current testing version of ipmctl (testing b259158292ff8ca43fab0011254256b34da7359f) with the fixes it contains. Would it be helpful for me to provide a debug dump to confirm whether or not this is the same issue?

mp15 commented 4 years ago

Retested and appears fixed with v02.00.00.3709 (7543fc7c1e746addb2fb661951e06eaae1841cef)

Muthu2112 commented 4 years ago

Observing similar issue in IPMCTL 01.00.00.3497. So should i use V02.00.00 series to test this ?

zjs1224522500 commented 1 year ago

Still exists in v02.00.00.3709 with kernel version Linux 5.15.0-69-generic.

nolanhergert commented 1 year ago

@zjs1224522500 Sorry for the delay. Can you try a newer version of ipmctl? There were some additional fixes checked into newer versions, specifically 3882 or newer.

zjs1224522500 commented 1 year ago

ipmctl

Sorry for late reply. After upgrading the version to 02.00.00.3885, this issue is fixed.

Thanks~