[ECI] It seems nothing happen after execute esdq for ECI

[milian1]

Hi All,

Recently, I've referred to the following guide and installed docker, real-time kernel, ECI and esdq for ECI on my target system:

Install Docker guidebook 

Guide book for ECI v3.3 (I choose ECI APT repository link to install.)

Intel ESDQ for Intel ECI 

Installation is successful. However, the first time I executed "esdq --verbose module run --arg "-a" RTPM".  It shows nothing but the topology of Target system's PCIe  and the message "Verifying system dependencies\n Verifying all dependencies\n Running 'RTPM' module\n ====RTPM START EXECUTING Tue May 20 15:17:00 CST 2025 ====. I've waited roughly an hour, then press ctrl+C, part of result were shown.

After the first time execution, every time I pressed ctrl+C after execute "esdq --verbose module run --are "-a" RTPM", it shows nothing but "Aborted".

The attachment: ESDQ.log shows the esdq log message, you may referred to it if it does help!

Here my questions are:

1. Will this test consume a long time?(more than an hour)

2. Or is there something I miss, so the test cannot successfully be executed?

Thanks in advanced.

* Target System Information:

CPU: 12th Gen Intel® Core™ i5-12500E

OS: Ubuntu 22.04.4 LTS

kernel version(uname -a): Linux ibase-desktop5.15.129-rt67-intel-ese-standard-lts-rt #1 SMP PREEMPT_RT Mon, 30 Sep2024 10:48:03 +0000 x86_64 x86_64 GNU/Linux

ESDQ version: v11.0.0 ( Download from here , the version I chose is 2024.1)

Best Regards,

Milian

[Peh_Intel]

Hi Milian,

Could you try to run one of these three commands instead of esdq --verbose module run --arg "-a" RTPM"?

• esdq --verbose module run --arg “” RTPM
• esdq --verbose module run --arg “invalid parameters” RTPM
• esdq --verbose module run RTPM

Regards,

Peh

[milian1]

Hi Peh,

Thanks for your suggestion.

Actually, I've tried these three commands before posting the issue. 

However, even for esdq --version module run RTPM, which only check configuration, still shows the same result(That is, only pcie topology and "RTPM START EXECUTING" were shown, and "Aborted" was appeared after I pressed ctrl+C).

Should I provide complete commands which I used to install the tool, or the complete kernel message to you?

Best Regards,

Milian

[Peh_Intel]

Hi Milian,

It will be helpful if you wish to provide the complete commands and the complete kernel message.

Before that, based on your log file, I noticed a message as below:

2025-05-20T13:14:19.783+0800 | suite | INFO | Successfully generated the test report at: /home/ibase/edge_software_device_qualification/Edge_Software_Device_Qualification_For_RTPM_2024.1/ESDQ/reports/

Could you check the directory and see any test reported generated?

Regards,

Peh

[milian1]

Hi Peh,

Sorry, I found that I forgot to save kernel message log So here I can only provide the command I used to you.

Attachment: ECI_history_20250520.log is the whole commands I used from installing docker to execute the ECI test. Below are the further explanation to some of the commands in this file.

1. line1: sudo su, I used to type sudo su at the beginning. However, I realize that the document is with the "sudo" prefix of most of commands, so actually I used "exit" to exit the super user, then continue to execute line2.

2. line47~52 is roughly the same as line 39~44: This is because I misunderstand the steps. so I re-executed them. I think these will not effect the result?

3. line 75:  make all && sudo make install. If I just type make install, it will not install successfully, so here I add sudo.

Furthermore, the attachment: report.zip is the result the screen shows me  after I use ctrl+C to stop the test:

2025-05-20T13:14:19.783+0800 | suite | INFO | Successfully generated the test report at: /home/ibase/edge_software_device_qualification/Edge_Software_Device_Qualification_For_RTPM_2024.1/ESDQ/reports/

However, after I copy the report.zip to my USB device and check it on my notebook, I found that there's nothing in this zip file.

Here I provide the report_html.zip, which is the report.html file that was generated after I pressed ctrl+C, hope it will help!

Best Regards,

Milian

[Peh_Intel]

Hi Milian,

Thanks for sharing your complete commands. 

I run the RTPM test by following your commands and able to generate the report in few minutes with ESDQ command.

Please follow the instructions below.

1. Re-install ESDQ and ECI with sudo:

sudo ./edgesoftware install

2. Navigate to the test module folder.

cd edge_software_device_qualification/Edge_Software_Device_Qualification_For_RTPM_2024.1/ESDQ

3. Ensure you get RTPM test module ID.

esdq module list

4. Run ESDQ command:

esdq --verbose module run --arg “-a” RTPM

Regards,

Peh

[milian1]

Hi Peh,

Thanks for providing the advice.

However, it seems the issue is not solved after re-install ESDQ and ECI with sudo, though esdq module list shows:

Verifying system dependencies

Listening all modules 

TSN

RTPM

Even I re-install the whole test environment(that is, reinstall OS, docker, kernel, and ECI & ESDQ), didn't help.

Here I have some questions:

1. I found that there are some errors appeared when installing eci-realtime, like:

Error! The /var/lib/dkms/mmio-latency-dkms/1.2/6.5.0-18-generic/x86_64/dkms.conf for module mmio-late
ncy-dkms includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Skipped.

You can refer to attachment: install_error.log to view the whole console log. I'm wondering if these error should be handle or not, since they were skipped.

2. May you share your test environment(OS, kernel version) and how long it will take to run a ECI test with command: esdq --verbose module run --arg “-a” RTPM"?

Thank you.

Best Regards,

Milian

[milian1 · Accepted solution]

Hi Peh,

I found out that in my use case, I have to close the window which show PCIe topology of target system so the test will be continued.

Now the issue is solved, thanks for your help so long!

Best Regards,

Milian

[Peh_Intel]

Hi Milian,

Yes, I also closed the window before.

Thanks for letting me know. This thread will no longer be monitored since this issue has been resolved. If you need any additional information from Intel, please submit a new question.

Regards,

Peh