Lines Matching full:might

383 …bool "Cortex-A53: 826319: System might deadlock if a write cannot complete until read data is acce…
405 …bool "Cortex-A53: 827319: Data cache clean instructions might cause overlapping transactions to th…
427 bool "Cortex-A53: 824069: Cache line might not be marked as clean after a CleanShared snoop"
438 address, then this erratum might cause a clean cache line to be
450 bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption"
460 maintenance operation to the same address, then this erratum might
478 Affected Cortex-A57 parts might deadlock when exclusive load/store
490 …bool "Cortex-A57: 834220: Stage 2 translation fault might be incorrectly reported in presence of a…
497 Affected Cortex-A57 parts might report a Stage 2 translation
527 bool "Cortex-A53: 845719: a load might read incorrect data"
537 might return incorrect data.
548 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
563 …bool "Cortex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorre…
577 …rse-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect res…
636 …bool "Cortex-A55: Completion of affected memory accesses might not be guaranteed by completion of …
653 …bool "Cortex-A76: Modification of the translation table for a virtual address might lead to read-a…
669 bool "Cortex-A76: Software Step might prevent interrupt recognition"
730 Affected Cortex-A510 might not respect the ordering rules for
846 Affected Neoverse-N2 cores might write to an out-of-range address, not reserved
847 for TRBE. Under some conditions, the TRBE might generate a write to the next
864 Affected Cortex-A710/X2 cores might write to an out-of-range address, not reserved
865 for TRBE. Under some conditions, the TRBE might generate a write to the next
875 …bool "Cortex-A510: Completion of affected memory accesses might not be guaranteed by completion of…
898 Affected Cortex-A510 core might fail to write into system registers after the
916 Affected Cortex-A510 core might cause an inconsistent view on whether trace is
918 might be corrupted. This happens after TRBE buffer has been enabled by setting
923 the trace buffer state might be corrupted.
939 Affected Cortex-A510 core might cause trace data corruption, when being written
1108 bool "Falkor E1041: Speculative instruction fetches might cause errant memory access"
1868 symptoms, the values returned by the register reads might not
2063 Specific errata workaround(s) might also force module PLTs to be
2138 particular case of region exhaustion, modules might be able to fall