CPU(core i5 11400)'s PCIe-Ctrl(PEG10) is permanently damaged?

[Oohara]

CPU: core i5 11400 (Rocketlake-S)

MB : ASRock H570M-ITX

    uEFI: BCLK SSC        : Auto  => Disable(Off)

           PCI1-Slot Speed  : Auto => Gen3

OS : Ubuntu 20.04.3 LTS (kernel-5.4)

-----

< Phenomenon>

After PEG10 link-up fail, PEG10 never revive.

I test following step (1) => (2) => (3), I expect PEG10 comes back and link-up success again on step(3), however, PEG10 never shown in Linux lspci.

This is CPU issue not MB, because when I replaced new CPU, it recognized PCIe-Card used on step (1)(3).

Show me how to recover/revive CPU PEG10 ?

I also asked ASRock Tech support about this phenomenon and SRNS/SRIS support, but they did not know.

I already returned broken two CPUs.

----

< Logs >

(1) install Gen3-X8 Card into PCIe-Slot(Gen4-X16) : success

guest@RKL:~/Desktop$ lspci -t
-[0000:00]-+-00.0
+-01.0-[01]----00.0
+-02.0
+-08.0
+-14.0
+-14.2
+-16.0
+-17.0
+-1c.0-[02]----00.0
+-1c.6-[03]----00.0
+-1f.0
+-1f.3
+-1f.4
+-1f.5
\-1f.6

guest@RKL:~/Desktop$ lspci
00:00.0 Host bridge: Intel Corporation Device 4c53 (rev 01)
00:01.0 PCI bridge: Intel Corporation Device 4c01 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device 4c8b (rev 04)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:14.0 USB controller: Intel Corporation Device 43ed (rev 11)
00:14.2 RAM memory: Intel Corporation Device 43ef (rev 11)
00:16.0 Communication controller: Intel Corporation Device 43e0 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 43bd (rev 11)
00:1c.6 PCI bridge: Intel Corporation Device 43be (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4386 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 43c8 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 43a3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 43a4 (rev 11)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11)
01:00.0 Processing accelerators: Hifn Inc. Device 9240 (rev 01)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)

guest@RKL:~/Desktop$

(2) install proprietary Gen3-X1 Card(separate-refclk, no PRSNT-loop) into PCIe-Slot(Gen4-X16) : fail

guest@RKL:~/Desktop$ lspci -t
-[0000:00]-+-00.0
<= missing PEG10 Ctrl
+-02.0
+-08.0
+-14.0
+-14.2
+-16.0
+-17.0
+-1c.0-[01]----00.0
+-1c.6-[02]----00.0
+-1f.0
+-1f.3
+-1f.4
+-1f.5
\-1f.6

guest@RKL:~/Desktop$ lspci
00:00.0 Host bridge: Intel Corporation Device 4c53 (rev 01)
<= missing (00:01.0 PEG10)
00:02.0 VGA compatible controller: Intel Corporation Device 4c8b (rev 04)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:14.0 USB controller: Intel Corporation Device 43ed (rev 11)
00:14.2 RAM memory: Intel Corporation Device 43ef (rev 11)
00:16.0 Communication controller: Intel Corporation Device 43e0 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 43bd (rev 11)
00:1c.6 PCI bridge: Intel Corporation Device 43be (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4386 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 43c8 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 43a3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 43a4 (rev 11)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11)
<= missing (Proprietary-Card)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)

guest@RKL:~/Desktop$

(3) install back Gen3-X8 Card into PCIe-Slot(Gen4-X16) : fail

guest@RKL:~/Desktop$ lspci -t
-[0000:00]-+-00.0
<= missing (00:1.0 PEG10)
+-02.0
+-08.0
+-14.0
+-14.2
+-16.0
+-17.0
+-1c.0-[01]----00.0
+-1c.6-[02]----00.0
+-1f.0
+-1f.3
+-1f.4
+-1f.5
\-1f.6

guest@RKL:~/Desktop$ lspci
00:00.0 Host bridge: Intel Corporation Device 4c53 (rev 01)
<= missing (00:01.0 PEG10)
00:02.0 VGA compatible controller: Intel Corporation Device 4c8b (rev 04)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:14.0 USB controller: Intel Corporation Device 43ed (rev 11)
00:14.2 RAM memory: Intel Corporation Device 43ef (rev 11)
00:16.0 Communication controller: Intel Corporation Device 43e0 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 43bd (rev 11)
00:1c.6 PCI bridge: Intel Corporation Device 43be (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4386 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 43c8 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 43a3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 43a4 (rev 11)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11)
<= missing (Card)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)

guest@RKL:~/Desktop$

----

[DeividA_Intel]

Hello Oohara,  

Thank you for posting on the Intel® communities.   

In order to better assist you, please provide the following:  

1. If possible, run the System Support Utility and attach the result.

- https://downloadcenter.intel.com/download/26735/Intel-System-Support-Utility-for-the-Linux-Operating-System

2. Were the other 2 processors working fine before? and if so, do you know how exactly did they get damaged?

3. Are you able to test the CPU in a different motherboard (different brand if possible)?

Regards,  

Deivid A. 

Intel Customer Support Technician 

[Oohara]

> 1. If possible, run the System Support Utility and attach the result.

> - https://downloadcenter.intel.com/download/26735/Intel-System-Support-Utility-for-the-Linux-Operating...

Ssu does not support Ubuntu-20.04(kernel-5.4) as follows.

----

guest@RKL:~$ sudo ./ssu.sh
RKL.txt exists. Would you like to overwrite it? y/n -->
y
This product is not supported on this operating system.
Would you like to try to scan? (y/n)
y
The None missing package is recommended to retrieve ethtool details.
Would you like to try and install it now? (y/n)
y
Reading package lists... Done
Building dependency tree
Reading state information... Done
guest@RKL:~$

> 2. Were the other 2 processors working fine before?

> and if so, do you know how exactly did they get damaged?

Yes. Before installing "my proprietary card", 2 CPU works well.

After just changing PCIe-card, it may be damaged as described above step-(2).

I'm now using 3rd processor, but never install "my proprietary card", so it works well.

"my proprietary card" works well on other platform, ARM64-CPU.

> 3. Are you able to test the CPU in a different motherboard (different brand if possible)?

I am personal user, I don't have any other CPU and MB.

Is there any other diagnostic tool for

(a) PCIe-Ctrl (PEG10 or PEG60) status

(b) System Agent (Enable/Disable PCIe-Ctrl)

Is there any special procedure to support "Separate Refclk PCIe-card"?

[Oohara]

Ssu logs (current OK case). There are no PCIe.

[DeividA_Intel]

Hello Oohara, 

Thank you for the information provided 

I will proceed to check the issue internally and post back soon with more details. 

Best regards,  

Deivid A.  

Intel Customer Support Technician 

[DeividA_Intel]

Hello Oohara, 

Thanks for the information provided.

Based on the reports and the research performed, looks like an issue related to the motherboard. I recommend you report this to your motherboard manufacturer and if they find a bug in the microcode then, they will work directly with us to fix it.

Regards,  

Deivid A.  

Intel Customer Support Technician  

[Oohara]

Please advice ASRock directly, what is wrong, and what should be corrected in their microcode.

I reported them this, then they requested me to retry(reproduce) on Windows, and send screen shot.

Does it make sense to do? I don't think so.

[DeividA_Intel]

Hello Oohara, 

Thanks for replying, 

In this case, the best action to take would be to check the issue with ASRock. Even though their requests may be unusual, they may have a reason to ask them and they will work on the situation, and if they noticed that the problem is the microcode they will get in contact directly with the engineering team to work on a fix.

At this point I recommend you to continue with the ASRock support and they will either let you know what is the exact problem (may not be related to the microcode) or they will work with us and let you know about any future update. 

Please keep in mind that this thread will no longer be monitored by Intel.  

Regards,  

Deivid A.  

Intel Customer Support Technician