ASM1806 PCIE Switcher cause csr_pcie5r: EMEM address decode error

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
, ,
1

I found the same question in this link:

He solved the problem with update L4T version ,which we can’t do that.

Now my L4T version is 32.7.3,and hardware is Jetson Xavier NX for SOM + our customized carried board.
Can you help me solve this problem?
Here is the log:

root@tegra-ubuntu:~# [ 2022.273002] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2022.273213] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2022.273358] mc-err:   secure: yes, access-type: read
[ 2022.273496] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2022.273519] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2022.280992] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2022.281193] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2022.281358] mc-err:   secure: yes, access-type: read
[ 2022.281476] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2022.281498] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2022.288988] mc-err: Too many MC errors; throttling prints
[ 2022.289221] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2034.178149] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2034.178301] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2034.178427] mc-err:   secure: yes, access-type: read
[ 2034.178526] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2034.178546] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2034.186145] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2034.186291] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2034.186416] mc-err:   secure: yes, access-type: read
[ 2034.186519] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2034.186539] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2034.194124] mc-err: Too many MC errors; throttling prints
[ 2034.194282] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2049.939691] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2049.939833] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2049.939953] mc-err:   secure: yes, access-type: read
[ 2049.940049] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2049.940072] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2049.947664] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2049.947876] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2049.948060] mc-err:   secure: yes, access-type: read
[ 2049.948178] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2049.948197] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2049.955663] mc-err: Too many MC errors; throttling prints
[ 2049.955821] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2062.740922] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2062.741069] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2062.741190] mc-err:   secure: yes, access-type: read
[ 2062.741282] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2062.741304] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2062.748921] mc-err: (255) csr_pcie5r: EMEM address decode error
[ 2062.749068] mc-err:   status = 0x200640e2; addr = 0xffffffff00; hi_adr_reg=ff08
[ 2062.749195] mc-err:   secure: yes, access-type: read
[ 2062.749297] mc-err: mcerr: unknown intr source intstatus = 0x00000000, intstatus_1 = 0x00000000
[ 2062.749317] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
[ 2062.756943] mc-err: Too many MC errors; throttling prints
[ 2062.757071] t19x-arm-smmu 12000000.iommu: Unhandled context fault: smmu1, iova=0x4ff736000, fsynr=0x100003, cb=1, sid=91(0x5b - PCIE5), pgd=26097c003, pud=26097c003, pmd=237d9a003, pte=0
3

Hi Xzz,

Are you using the devkit or custom board for Xavier NX?

Is there any issue in your use case with there error messages?

Do you connect any PCIe device?

I’ve found there’s a thread with similar errors as yours.
Please refer the following thread to check if it could help.
When start DMA ,system restart, jetson nx - #6 by vidyas

4

Hi, KevinFFF：

I use our customized carried board.

There only have error log , but everything works ok.

After ASM1806 PCIE Switcher, there are 2 PCIE ethernet phy (intel i210) .

I just running simple test, like iperf3 or read and wirte usb storage.
Despite the occurrence of error logs, everything works well, and this is what I am confused about

5

It should be fine if that error message not affect your use case.

Or have you tried to remove these ethernet phy from PCIe and check if the error meesages still exist?

6

Thank you for reply,
I will pay attention to this log and possible error phenomenon !

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.