Arm-smmu 8000000.iommu: Unhandled context fault message

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
1

I’m looking at the console of my Orin Nano 8GB dev board and see the following messages :

[ 5528.703781] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffb98000, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[ 5528.719282] mc-err: (255) csr_pcie1r: EMEM address decode error
[ 5528.725503] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[ 5528.733972] mc-err:   secure: yes, access-type: read
[13151.450429] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffaad000, fsynr=0x7f0003, cbfrsynra=0x405, cb=3
[13151.463325] mc-err: (255) csr_pcie1r: EMEM address decode error
[13151.469439] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[13151.477717] mc-err:   secure: yes, access-type: read
[17687.321820] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffab6000, fsynr=0x7f0003, cbfrsynra=0x5, cb=3
[17687.334286] mc-err: (255) csr_pcie1r: EMEM address decode error
[17687.340714] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[17687.349000] mc-err:   secure: yes, access-type: read
[21845.217693] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffb2e000, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[21845.233187] mc-err: (255) csr_pcie1r: EMEM address decode error
[21845.239549] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[21845.247829] mc-err:   secure: yes, access-type: read
[21971.230263] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffae0000, fsynr=0x7f0003, cbfrsynra=0x805, cb=3
[21971.242953] mc-err: Too many MC errors; throttling prints
[27452.048608] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffa86800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[27452.064104] mc-err: (255) csr_pcie1r: EMEM address decode error
[27452.070445] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[27452.078714] mc-err:   secure: yes, access-type: read
[32491.960198] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc30800, fsynr=0x7f0003, cbfrsynra=0x5, cb=3
[32491.972660] mc-err: (255) csr_pcie1r: EMEM address decode error
[32491.978987] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[32491.987251] mc-err:   secure: yes, access-type: read
[50824.409935] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffcd5800, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[50824.425445] mc-err: (255) csr_pcie1r: EMEM address decode error
[50824.431693] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[50824.440095] mc-err:   secure: yes, access-type: read
[50887.444196] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffdab000, fsynr=0x80003, cbfrsynra=0x5, cb=3
[50887.459528] mc-err: (255) csr_pcie1r: EMEM address decode error
[50887.465775] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[50887.474038] mc-err:   secure: yes, access-type: read
[78039.688043] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffdc9000, fsynr=0x7f0003, cbfrsynra=0xc05, cb=3
[78039.700889] mc-err: Too many MC errors; throttling prints

These are appearing throughout the day while the system is not being used.
The OS was built from SDK Manager using JetPack 5.1.2 on Jetson Orin Dev board, L4T 35.4.1
What is causing these messages and how do you fix the issue ?

Thank you

3

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

4

Hello kayccc,

Yes this is still an issue. Checked my console log just now and see :

[37030.842487] mc-err: (255) csr_pcie1r: EMEM address decode error
[37030.848845] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[37030.857175] mc-err:   secure: yes, access-type: read
[52969.418493] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd63000, fsynr=0x7f0003, cbfrsynra=0x405, cb=3
[52969.431112] mc-err: (255) csr_pcie1r: EMEM address decode error
[52969.437554] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[52969.445813] mc-err:   secure: yes, access-type: read```

What does this mean ?
5 
[112124.784625] mc-err: (255) csr_pcie1r: EMEM address decode error
[112124.790838] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[112124.799183] mc-err:   secure: yes, access-type: read
[112628.750936] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffbc6800, fsynr=0x80003, cbfrsynra=0x5, cb=3
[112628.766336] mc-err: (255) csr_pcie1r: EMEM address decode error
[112628.772762] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[112628.781168] mc-err:   secure: yes, access-type: read
[113195.728404] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffb35000, fsynr=0x80003, cbfrsynra=0x805, cb=3
[113195.744036] mc-err: Too many MC errors; throttling prints
[125984.433963] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd5f800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[125984.449607] mc-err: (255) csr_pcie1r: EMEM address decode error
[125984.456037] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[125984.464382] mc-err:   secure: yes, access-type: read
[137702.118002] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd50800, fsynr=0x80003, cbfrsynra=0x805, cb=3
[137702.133547] mc-err: (255) csr_pcie1r: EMEM address decode error
[137702.139910] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[137702.148403] mc-err:   secure: yes, access-type: read
[170776.207782] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd85800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[170776.223437] mc-err: (255) csr_pcie1r: EMEM address decode error
[170776.229855] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[170776.238202] mc-err:   secure: yes, access-type: read
[182997.887262] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd3b000, fsynr=0x80003, cbfrsynra=0x5, cb=3
[182997.902645] mc-err: (255) csr_pcie1r: EMEM address decode error
[182997.909007] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[182997.917358] mc-err:   secure: yes, access-type: read
[216512.968138] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc80000, fsynr=0x80003, cbfrsynra=0x805, cb=3
[216512.983722] mc-err: Too many MC errors; throttling prints
[219410.851852] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc24800, fsynr=0x7f0003, cbfrsynra=0x805, cb=3
[219410.864562] mc-err: (255) csr_pcie1r: EMEM address decode error
[219410.870977] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[219410.879319] mc-err:   secure: yes, access-type: read
[232262.491782] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd1d800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[232262.507356] mc-err: (255) csr_pcie1r: EMEM address decode error
[232262.513708] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[232262.522061] mc-err:   secure: yes, access-type: read```
6

Hello @kayccc - any updates ?

7

I was checking this issue today and see things have become worse!

Is there a way to force a fsck on the boot SD Card on reboot ?

[50197.443883] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffd93000, fsynr=0x7f0003, cbfrsynra=0x5, cb=3
[50197.456359] mc-err: (255) csr_pcie1r: EMEM address decode error
[50197.462566] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[50197.470950] mc-err:   secure: yes, access-type: read
[62608.088414] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffadd000, fsynr=0x7f0003, cbfrsynra=0xc05, cb=3
[62608.101122] mc-err: (255) csr_pcie1r: EMEM address decode error
[62608.107505] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[62608.115764] mc-err:   secure: yes, access-type: read
[92572.709362] EXT4-fs (mmcblk1p1): error count since last fsck: 213
[92572.715768] EXT4-fs (mmcblk1p1): initial error at time 1700601023: ext4_lookup:1706: inode 396451
[92572.724953] EXT4-fs (mmcblk1p1): last error at time 1712753082: ext4_lookup:1706: inode 535542
[112506.595495] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm fwupdmgr: iget: checksum invalid
[112506.747835] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm fwupdmgr: iget: checksum invalid
[113265.030804] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm packagekitd: iget: checksum invalid
[113265.180732] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm packagekitd: iget: checksum invalid
[113272.024866] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm appstreamcli: iget: checksum invalid
[113272.174883] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm appstreamcli: iget: checksum invalid
[113278.526181] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534907: comm apt-check: iget: checksum invalid
[113278.675674] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534907: comm apt-check: iget: checksum invalid
[118646.570039] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #399419: comm updatedb.mlocat: iget: checksum invalid
[128126.297749] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffac9000, fsynr=0x7f0003, cbfrsynra=0x405, cb=3
[128126.310514] mc-err: (255) csr_pcie1r: EMEM address decode error
[128126.316839] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[128126.325305] mc-err:   secure: yes, access-type: read
[129323.260836] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x80000402, iova=0xffc0e800, fsynr=0x7f0003, cbfrsynra=0xc05, cb=3
[129323.273616] mc-err: (255) csr_pcie1r: EMEM address decode error
[129323.280040] mc-err:   status = 0x200640da; hi_addr_reg = 0x000000ff addr = 0xffffffff00
[129323.288382] mc-err:   secure: yes, access-type: read
[144505.495609] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm fwupdmgr: iget: checksum invalid
[144505.659555] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #535542: comm fwupdmgr: iget: checksum invalid
[171666.147584] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #541684: comm (u-report): iget: checksum invalid
[171666.169121] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534897: comm pulseaudio: iget: checksum invalid
[171666.297363] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534897: comm pulseaudio: iget: checksum invalid
[171666.460251] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534897: comm pulseaudio: iget: checksum invalid
[171666.573631] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534897: comm pulseaudio: iget: checksum invalid
[171666.959672] EXT4-fs error (device mmcblk1p1): ext4_lookup:1706: inode #534897: comm pulseaudio: iget: checksum invalid

Thank you

9

Hi,
Please upgrade to Jetpack 5.1.3 and try. See if the issue is present in latest release.

If the issue exists on 5.1.3, please share the method to replicate it on Orin Nano developer kit. We will set up and try.

10

We have started testing on Jetpack 6.0 DP. Seeing similar messages :

[ 2118.148987] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffd48800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[ 2118.151860] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[ 4175.085179] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffc0b000, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[ 4175.088058] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[ 4659.060802] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffc57000, fsynr=0x3f0003, cbfrsynra=0xc05, cb=3
[ 4659.060894] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0x00000000, fsynr=0x80001, cbfrsynra=0x5, cb=3
[ 4659.061003] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[ 4659.061027] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0x00001800, fsynr=0x3f0001, cbfrsynra=0x405, cb=3
[ 4659.061106] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0x00007000, fsynr=0x80001, cbfrsynra=0xc05, cb=3
[ 4659.061185] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0x0000d000, fsynr=0x3f0001, cbfrsynra=0x405, cb=3
[ 4659.063936] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[ 4659.065284] pcieport 0001:00:00.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Receiver ID)
[ 4659.065292] pcieport 0001:00:00.0:   device [10de:229e] error status/mask=00040000/00400000
[ 4659.065297] pcieport 0001:00:00.0:    [18] MalfTLP                (First)
[ 4659.065302] pcieport 0001:00:00.0: AER:   TLP Header: 00000003 01000178 fffffffc 00000000
[24623.552178] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffd82000, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[24623.555057] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[28495.446353] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffaf6000, fsynr=0x80003, cbfrsynra=0x805, cb=3
[28495.449232] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[31399.372498] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffa8e800, fsynr=0x80003, cbfrsynra=0x405, cb=3
[31399.375363] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[43257.041137] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffc78000, fsynr=0x80003, cbfrsynra=0xc05, cb=3
[43257.044017] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)
[64915.443713] arm-smmu 8000000.iommu: Unhandled context fault: fsr=0x402, iova=0xffb1f800, fsynr=0x80003, cbfrsynra=0x805, cb=3
[64915.446601] tegra-mc 2c00000.memory-controller: pcie1r: secure read @0x000000ffffffff00: EMEM address decode error (EMEM decode error)

Thank you

11

Hi,
Please share the steps so that we can set up and try.

12

I boot the Orin and leave it running. I have a console window that shows those messages. I’m not even logged in to the system - so the system is idle.

13

Hi,
Please try 6.0GA(r36.3).

1 Like
15

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