Lines Matching refs:erratum

1033 	  fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
1042 	  r1p* erratum. If a code sequence containing an ARM/Thumb
1059 	  erratum. For very specific sequences of memory operations, it is
1073 	  erratum. Any asynchronous access to the L2 cache may encounter a
1086 	  (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
1099 	  (r2p0..r2p2) erratum. Under certain conditions, specific to the
1114 	  r1p0) erratum. On affected cores the LoUIS bit field of the CLIDR
1124 	  r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
1126 	  As a consequence of this erratum, some TLB entries which should be
1137 	  (r2p*) erratum. Under very rare conditions, a faulty
1151 	  to r3p0) erratum. An interrupted ICIALLUIS operation may prevent the
1161 	  r3p*) erratum. A speculative memory access may cause a page table walk
1172 	  r2p0) erratum. The Store Buffer does not have any automatic draining
1183 	  r0p2 erratum (possible cache data corruption with
1194 	  This option enables the workaround for erratum 764369
1209 	 r2p6,r2p8,r2p10,r3p0) erratum. In case a date cache maintenance
1220 	  option enables the Linux kernel workaround for this erratum
1229 	  (up to r0p4) erratum. In certain rare sequences of code, the
1231 	  workaround disables the loop buffer to avoid the erratum.