Searched refs:corruption (Results 1 – 25 of 64) sorted by relevance
123
| /linux-2.6.39/arch/x86/kernel/ |
| D | check.c | 117 int corruption = 0; in check_for_bios_corruption() local
131 corruption = 1; in check_for_bios_corruption()
136 WARN_ONCE(corruption, KERN_ERR "Memory corruption detected in low memory\n"); in check_for_bios_corruption()
|
| /linux-2.6.39/mm/ |
| D | Kconfig.debug | 10 of memory corruption.
16 that would result in incorrect warnings of memory corruption after
|
| /linux-2.6.39/Documentation/vm/ |
| D | slub.txt | 191 INFO: <corruption start>-<corruption_end> <more info>
208 Can be useful if the corruption does not stop with the start of the
214 corruption by a write after free.
234 of the corruption is may be more likely found by looking at the function that
267 may be optimized further by locating the slab that experiences corruption
274 If the corruption occurs by writing after the end of the object then it
|
| D | hwpoison.txt | 16 * When the current CPU tries to consume corruption the currently
19 * just ignore it because no corruption has been consumed yet. Instead
|
| D | pagemap.txt | 92 hardware detected memory corruption on this page: don't touch the data!
|
| /linux-2.6.39/drivers/memstick/core/ |
| D | Kconfig | 14 in most cases result in data corruption.
|
| /linux-2.6.39/drivers/mmc/core/ |
| D | Kconfig | 12 in most cases result in data corruption.
|
| /linux-2.6.39/Documentation/ |
| D | memory.txt | 20 corruption of memory is usually a sign of serious hardware trouble.
|
| D | io_ordering.txt | 47 possible data corruption.
|
| D | stable_kernel_rules.txt | 12 marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
|
| /linux-2.6.39/fs/ubifs/ |
| D | recovery.c | 716 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
723 "starts at %d", lnum, offs, corruption); in ubifs_recover_leb()
725 offs += corruption; in ubifs_recover_leb()
726 buf += corruption; in ubifs_recover_leb()
|
| /linux-2.6.39/Documentation/block/ |
| D | data-integrity.txt | 5 protect against data corruption. However, the detection of the
6 corruption is done at read time which could potentially be months
27 integrity of the I/O and reject it if corruption is detected. This
28 allows not only corruption prevention but also isolation of the point
|
| /linux-2.6.39/drivers/staging/tidspbridge/ |
| D | Kconfig | 58 This can lead to heap corruption. Say Y, to enforce the check for 128
|
| /linux-2.6.39/Documentation/x86/x86_64/ |
| D | machinecheck | 56 with the risk of a crash or even corruption (for tolerant >= 3).
|
| /linux-2.6.39/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 117 suspend to see if there has been any corruption of the contents.
|
| /linux-2.6.39/Documentation/cdrom/ |
| D | packet-writing.txt | 82 filesystem corruption if the disc wears out.
|
| D | ide-cd | 331 f. Data corruption.
333 - Random data corruption was occasionally observed with the Hitachi
334 CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"
|
| /linux-2.6.39/Documentation/i2c/busses/ |
| D | i2c-piix4 | 55 crashes, data corruption, etc.). Try this only as a last resort (try BIOS
|
| /linux-2.6.39/Documentation/networking/ |
| D | skfp.txt | 218 - data corruption with kernel versions below 2.0.33.
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | ceph.txt | 119 must rely on TCP's error correction to detect data corruption
|
| D | ubifs.txt | 88 of this option is that corruption of the contents
|
| /linux-2.6.39/Documentation/PCI/ |
| D | pci-error-recovery.txt | 19 corruption; for example, to halt system memory corruption due to DMA's
289 may result in hung devices, kernel panics, or silent data corruption.
|
| /linux-2.6.39/drivers/scsi/arm/ |
| D | fas216.c | 229 int corruption = 0; in __fas216_checkmagic() local
232 corruption++; in __fas216_checkmagic()
236 corruption++; in __fas216_checkmagic()
238 if (corruption) { in __fas216_checkmagic()
|
| /linux-2.6.39/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 24 can lead to data corruption, both of user data or of kernel data,
47 corruption caused by the bad DMA. A number of device driver
|
| /linux-2.6.39/arch/arm/plat-samsung/ |
| D | Kconfig | 341 corruption over suspend and resume. A smaller value will mean that
|
123