Searched refs:corruption (Results 1 – 8 of 8) sorted by relevance
143 int corruption = 0; in check_for_bios_corruption() local156 corruption = 1; in check_for_bios_corruption()161 WARN_ONCE(corruption, KERN_ERR "Memory corruption detected in low memory\n"); in check_for_bios_corruption()
46 #error and result in filesystem corruption and oopses.
911 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"934 it behave as intended and avoiding data corruption.949 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"956 corruption. This workaround sets a specific bit in the diagnostic996 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"1000 r0p2 erratum (possible cache data corruption with1051 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"1058 lead to either a data corruption or a CPU deadlock. Not fixed in1101 bool "ARM errata: A17: some seqs of opposed cond code instrs => deadlock or corruption"1106 lead to either a data corruption or a CPU deadlock. Not fixed in
280 corruption over suspend and resume. A smaller value will mean that
360 on the AMBA 5 CHI interface, which can cause data corruption if the395 bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption"406 cause data corruption.511 cause register corruption when accessing the timer registers633 bool "Cavium erratum 27456: Broadcast TLBI instructions may cause icache corruption"
1139 kernel if it detects a problem (e.g. overheating, data corruption).1695 bool "Check for low memory corruption"1697 Periodically check for memory corruption in low memory, which1708 of memory and scans it infrequently. It both detects corruption1712 BIOS-originated corruption always affects the same memory,1749 typical corruption patterns.
1017 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
983 corruption.