Home
last modified time | relevance | path

Searched full:bad (Results 1 – 25 of 3414) sorted by relevance

12345678910>>...137

/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Ddm-dust.rst4 This target emulates the behavior of bad sectors at arbitrary
11 drive with bad sectors).
15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
19 1. Remove the block from the "bad block list".
22 This emulates the "remapped sector" behavior of a drive with bad
25 Normally, a drive that is encountering bad sectors will most likely
26 encounter more bad sectors, at an unknown time or location.
28 messages to add arbitrary bad blocks at new locations, and the
30 configured "bad blocks" will be treated as bad, or bypassed.
[all …]
/openbmc/linux/include/linux/ceph/
H A Ddecode.h57 #define ceph_decode_need(p, end, n, bad) \ argument
60 goto bad; \
63 #define ceph_decode_64_safe(p, end, v, bad) \ argument
65 ceph_decode_need(p, end, sizeof(u64), bad); \
68 #define ceph_decode_32_safe(p, end, v, bad) \ argument
70 ceph_decode_need(p, end, sizeof(u32), bad); \
73 #define ceph_decode_16_safe(p, end, v, bad) \ argument
75 ceph_decode_need(p, end, sizeof(u16), bad); \
78 #define ceph_decode_8_safe(p, end, v, bad) \ argument
80 ceph_decode_need(p, end, sizeof(u8), bad); \
[all …]
/openbmc/linux/tools/testing/ktest/
H A Dconfig-bisect.pl9 # config-bisect.pl [options] good-config bad-config [good|bad]
12 # Compares a good config to a bad config, then takes half of the diffs
14 # the bad config. That is, the resulting config will start with the
16 # the good and bad configs match the bad config. It tries because of
24 # $ config-bisect.pl /path/to/good/config /path/to/bad/config
27 # so do not make that be one of the good or bad configs), and then
30 # the good config. It does the same for the bad config as well.
35 # and the bad config to /path/to/bad/config.tmp (just appends ".tmp" to the
39 # After the first run, determine if the result is good or bad then
43 # $ config-bisect.pl /path/to/good/config /path/to/bad/config good
[all …]
/openbmc/u-boot/include/linux/mtd/
H A Dbbm.h5 * NAND family Bad Block Management (BBM) header file
6 * - Bad Block Table (BBT) implementation
24 * struct nand_bbt_descr - bad block table descriptor
37 * bad) block in the stored bbt
38 * @pattern: pattern to identify bad block table or factory marked good /
39 * bad blocks, can be NULL, if len = 0
41 * Descriptor for the bad block table marker and the descriptor for the
42 * pattern which identifies good and bad blocks. The assumption is made
58 /* Options for the bad block table descriptors */
66 /* The bad block table is in the last good block of the device */
[all …]
/openbmc/openbmc-test-automation/redfish/update_service/
H A Dtest_redfish_image_upload.robot3 ... This test expects the following bad tarball image files
12 # Refer below document to generate bad firmware images for testing.
13 # openbmc/openbmc-test-automation/blob/master/docs/code_update.md#generating-bad-firmware-image-for…
19 # BAD_IMAGES_DIR_PATH The path to the directory which contains the bad image files.
45 Redfish Failure To Upload BMC Image With Bad Manifest
46 [Documentation] Upload a BMC firmware with a bad MANIFEST file.
48 [Template] Redfish Bad Firmware Update
57 [Template] Redfish Bad Firmware Update
63 Redfish Failure To Upload Host Image With Bad Manifest
64 [Documentation] Upload a PNOR firmware with a bad MANIFEST file.
[all …]
/openbmc/qemu/tests/qapi-schema/
H A Dmeson.build27 'args-bad-boxed.json',
34 'args-member-array-bad.json',
39 'bad-base.json',
40 'bad-data.json',
41 'bad-ident.json',
42 'bad-if.json',
43 'bad-if-all.json',
44 'bad-if-empty.json',
45 'bad-if-empty-list.json',
46 'bad-if-key.json',
[all …]
/openbmc/linux/drivers/nvme/host/
H A Dfc.h110 "Bad CR_ASSOC Length",
111 "Bad CR_ASSOC Rqst Length",
113 "Bad CR_ASSOC Cmd Length",
114 "Bad Ersp Ratio",
117 "Bad CR_CONN Length",
118 "Bad CR_CONN Rqst Length",
120 "Bad Association ID Length",
123 "Bad Connection ID Length",
126 "Bad CR_CONN Cmd Length",
127 "Bad DISCONN Length",
[all …]
/openbmc/linux/drivers/mtd/nand/onenand/
H A Donenand_bbt.c3 * Bad Block Table support for the OneNAND driver
26 * Check for a pattern at the given place. Used to search bad block
27 * tables and good / bad block identifiers. Same as check_pattern, but
46 * create_bbt - [GENERIC] Create a bad block table by scanning the device
49 * @bd: descriptor for the good/bad block search pattern
53 * Create a bad block table by scanning the device
54 * for the given good/bad block identify pattern
67 printk(KERN_INFO "Scanning device for bad blocks\n"); in create_bbt()
97 /* If it is a initial bad block, just ignore it */ in create_bbt()
105 "initial bad block\n", i >> 1); in create_bbt()
[all …]
/openbmc/u-boot/drivers/mtd/onenand/
H A Donenand_bbt.c4 * Bad Block Table support for the OneNAND driver
32 * Check for a pattern at the given place. Used to search bad block
33 * tables and good / bad block identifiers. Same as check_pattern, but
52 * create_bbt - [GENERIC] Create a bad block table by scanning the device
55 * @param bd descriptor for the good/bad block search pattern
59 * Create a bad block table by scanning the device
60 * for the given good/bad block identify pattern
74 printk(KERN_INFO "Scanning device for bad blocks\n"); in create_bbt()
105 /* If it is a initial bad block, just ignore it */ in create_bbt()
113 "Bad eraseblock %d at 0x%08x\n", i >> 1, in create_bbt()
[all …]
/openbmc/linux/include/linux/mtd/
H A Dbbm.h3 * NAND family Bad Block Management (BBM) header file
4 * - Bad Block Table (BBT) implementation
19 * struct nand_bbt_descr - bad block table descriptor
32 * bad) block in the stored bbt
33 * @pattern: pattern to identify bad block table or factory marked good /
34 * bad blocks, can be NULL, if len = 0
36 * Descriptor for the bad block table marker and the descriptor for the
37 * pattern which identifies good and bad blocks. The assumption is made
53 /* Options for the bad block table descriptors */
61 /* The bad block table is in the last good block of the device */
[all …]
/openbmc/linux/drivers/mtd/nand/raw/
H A Dnand_bbt.c4 * Bad block table support for the NAND driver
10 * When nand_scan_bbt is called, then it tries to find the bad block table
13 * marked good / bad blocks. This information is used to create a memory BBT.
14 * Once a new bad block is discovered then the "factory" information is updated
21 * If the tables are not versioned, then we "or" the bad block information.
24 * good / bad blocks and the bad block tables are created.
29 * The auto generated bad block table is located in the last good blocks
40 * 00b: block is factory marked bad
41 * 01b, 10b: block is marked bad due to wear
43 * The memory bad block table uses the following scheme:
[all …]
/openbmc/u-boot/drivers/mtd/nand/raw/
H A Dnand_bbt.c3 * Bad block table support for the NAND driver
13 * When nand_scan_bbt is called, then it tries to find the bad block table
16 * marked good / bad blocks. This information is used to create a memory BBT.
17 * Once a new bad block is discovered then the "factory" information is updated
24 * If the tables are not versioned, then we "or" the bad block information.
27 * good / bad blocks and the bad block tables are created.
32 * The auto generated bad block table is located in the last good blocks
43 * 00b: block is factory marked bad
44 * 01b, 10b: block is marked bad due to wear
46 * The memory bad block table uses the following scheme:
[all …]
/openbmc/linux/tools/testing/ktest/examples/include/
H A Dbisect.conf23 # You must set the commit that was considered bad (git bisect bad)
28 # that requires to run a test to know if the bisect was good or bad.
29 # The test should exit with 0 on good, non-zero for bad. But see
33 # It is usually a good idea to confirm that the GOOD and the BAD
34 # commits are truly good and bad respectively. Having BISECT_CHECK
35 # set to 1 will check both that the good commit works and the bad
37 # set BISECT_CHECK to 'good' or to 'bad'.
40 #BISECT_CHECK = bad
66 # if the commit was good or bad. Instead, it will ask you to tell
76 # Currently (which hopefully will be fixed soon), the bad config
[all …]
/openbmc/linux/fs/ceph/
H A Dmdsmap.c57 #define __decode_and_drop_type(p, end, type, bad) \ argument
60 goto bad; \
64 #define __decode_and_drop_set(p, end, type, bad) \ argument
68 ceph_decode_32_safe(p, end, n, bad); \
70 ceph_decode_need(p, end, need, bad); \
74 #define __decode_and_drop_map(p, end, ktype, vtype, bad) \ argument
78 ceph_decode_32_safe(p, end, n, bad); \
80 ceph_decode_need(p, end, need, bad); \
91 ceph_decode_need(p, end, sizeof(u64) + sizeof(u32), bad); in __decode_and_drop_compat_set()
99 bad); in __decode_and_drop_compat_set()
[all …]
/openbmc/linux/drivers/tee/optee/
H A Drpc.c20 goto bad; in handle_rpc_func_cmd_get_time()
23 goto bad; in handle_rpc_func_cmd_get_time()
31 bad: in handle_rpc_func_cmd_get_time()
66 goto bad; in handle_rpc_func_cmd_i2c_transfer()
70 goto bad; in handle_rpc_func_cmd_i2c_transfer()
75 goto bad; in handle_rpc_func_cmd_i2c_transfer()
81 goto bad; in handle_rpc_func_cmd_i2c_transfer()
99 goto bad; in handle_rpc_func_cmd_i2c_transfer()
118 bad: in handle_rpc_func_cmd_i2c_transfer()
134 goto bad; in handle_rpc_func_cmd_wq()
[all …]
/openbmc/linux/arch/mips/include/asm/sn/
H A Dfru.h20 confidence_t km_confidence; /* confidence level that the memory is bad
24 /* confidence level that dimm[i] is bad
31 confidence_t kc_confidence; /* confidence level that cpu is bad */
32 confidence_t kc_icache; /* confidence level that instr. cache is bad */
33 confidence_t kc_dcache; /* confidence level that data cache is bad */
34 confidence_t kc_scache; /* confidence level that sec. cache is bad */
35 confidence_t kc_sysbus; /* confidence level that sysad/cmd/state bus is bad */
39 confidence_t kpb_belief; /* confidence level that the pci bus is bad */
41 /* confidence level that the pci dev is bad */
/openbmc/linux/drivers/misc/lkdtm/
H A Dperms.c78 pr_info("attempting bad execution at %px\n", dst); in execute_location()
100 pr_info("attempting bad execution at %px\n", dst); in execute_user_location()
111 pr_info("attempting bad rodata write at %px\n", ptr); in lkdtm_WRITE_RO()
113 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO()
130 pr_info("attempting bad ro_after_init write at %px\n", ptr); in lkdtm_WRITE_RO_AFTER_INIT()
132 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO_AFTER_INIT()
144 pr_info("attempting bad %zu byte write at %px\n", size, ptr); in lkdtm_WRITE_KERN()
147 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_KERN()
161 pr_info("attempting bad %zu bytes write at %px\n", size, do_nothing); in lkdtm_WRITE_OPD()
163 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_OPD()
[all …]
/openbmc/linux/Documentation/driver-api/
H A Dmtdnand.rst424 use bad block tables on FLASH, because the ECC layout is interfering
425 with the bad block marker positions. See bad block table support for
428 Bad block table support
431 Most NAND chips mark the bad blocks at a defined position in the spare
432 area. Those blocks must not be erased under any circumstances as the bad
433 block information would be lost. It is possible to check the bad block
435 the first page in the block. This is time consuming so a bad block table
438 The nand driver supports various types of bad block tables.
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
[all …]
/openbmc/linux/net/ceph/
H A Ddecode.c21 goto bad; in ceph_decode_entity_addr_versioned()
26 ceph_decode_copy_safe(p, end, &addr->type, sizeof(addr->type), bad); in ceph_decode_entity_addr_versioned()
28 ceph_decode_copy_safe(p, end, &addr->nonce, sizeof(addr->nonce), bad); in ceph_decode_entity_addr_versioned()
30 ceph_decode_32_safe(p, end, addr_len, bad); in ceph_decode_entity_addr_versioned()
32 goto bad; in ceph_decode_entity_addr_versioned()
36 ceph_decode_copy_safe(p, end, &addr->in_addr, addr_len, bad); in ceph_decode_entity_addr_versioned()
45 bad: in ceph_decode_entity_addr_versioned()
56 ceph_decode_skip_n(p, end, 3, bad); in ceph_decode_entity_addr_legacy()
63 ceph_decode_copy_safe(p, end, &addr->nonce, sizeof(addr->nonce), bad); in ceph_decode_entity_addr_legacy()
66 sizeof(addr->in_addr), bad); in ceph_decode_entity_addr_legacy()
[all …]
/openbmc/linux/drivers/gpu/drm/ci/
H A Dtestlist.txt54 kms_addfb_basic@bad-pitch-0
55 kms_addfb_basic@bad-pitch-32
56 kms_addfb_basic@bad-pitch-63
57 kms_addfb_basic@bad-pitch-128
58 kms_addfb_basic@bad-pitch-256
59 kms_addfb_basic@bad-pitch-1024
60 kms_addfb_basic@bad-pitch-999
61 kms_addfb_basic@bad-pitch-65536
68 kms_addfb_basic@addfb25-bad-modifier
324 kms_ccs@pipe-A-bad-pixel-format-y_tiled_ccs
[all …]
/openbmc/linux/drivers/mtd/ubi/
H A Dio.c106 * that this eraseblock may become bad soon (but do not have to);
217 * bad.
305 * %-EIO is returned, the physical eraseblock most probably went bad.
355 * torture_peb - test a supposedly bad physical eraseblock.
412 ubi_msg(ubi, "PEB %d passed torture test, do not mark it as bad", pnum); in torture_peb()
422 ubi_err(ubi, "read problems on freshly erased PEB %d, must be bad", in torture_peb()
521 * eraseblock is bad.
565 * ubi_io_is_bad - check if a physical eraseblock is bad.
569 * This function returns a positive number if the physical eraseblock is bad,
583 ubi_err(ubi, "error %d while checking if PEB %d is bad", in ubi_io_is_bad()
[all …]
/openbmc/u-boot/drivers/mtd/ubi/
H A Dio.c112 * that this eraseblock may become bad soon (but do not have to);
223 * bad.
323 * %-EIO is returned, the physical eraseblock most probably went bad.
397 * torture_peb - test a supposedly bad physical eraseblock.
454 ubi_msg(ubi, "PEB %d passed torture test, do not mark it as bad", pnum); in torture_peb()
464 ubi_err(ubi, "read problems on freshly erased PEB %d, must be bad", in torture_peb()
559 * eraseblock is bad.
596 * ubi_io_is_bad - check if a physical eraseblock is bad.
600 * This function returns a positive number if the physical eraseblock is bad,
614 ubi_err(ubi, "error %d while checking if PEB %d is bad", in ubi_io_is_bad()
[all …]
/openbmc/linux/tools/testing/selftests/x86/
H A Dtest_FCOMI.c75 printf("[BAD]\tfcomi_1_pi with flags:%lx\n", flags); in test()
79 printf("[BAD]\tfcomi_pi_1 with flags:%lx->%lx\n", flags, res_fcomi_pi_1 & ARITH); in test()
83 printf("[BAD]\tfcomi_1_1 with flags:%lx\n", flags); in test()
87 printf("[BAD]\tFE_INVALID is set in %s\n", __func__); in test()
112 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in test_qnan()
116 printf("[BAD]\tFE_INVALID is not set in %s\n", __func__); in test_qnan()
141 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in testu_qnan()
145 printf("[BAD]\tFE_INVALID is set in %s\n", __func__); in testu_qnan()
172 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in testu_snan()
177 printf("[BAD]\tFE_INVALID is not set in %s\n", __func__); in testu_snan()
[all …]
/openbmc/qemu/tests/unit/
H A Dtest-crypto-block.c587 g_test_add_data_func("/crypto/block/luks/bad/cipher-name-nul-term", in main()
590 g_test_add_data_func("/crypto/block/luks/bad/cipher-mode-nul-term", in main()
593 g_test_add_data_func("/crypto/block/luks/bad/hash-spec-nul-term", in main()
596 g_test_add_data_func("/crypto/block/luks/bad/cipher-name-empty", in main()
599 g_test_add_data_func("/crypto/block/luks/bad/cipher-name-unknown", in main()
602 g_test_add_data_func("/crypto/block/luks/bad/cipher-xts-size", in main()
605 g_test_add_data_func("/crypto/block/luks/bad/cipher-cbc-size", in main()
608 g_test_add_data_func("/crypto/block/luks/bad/cipher-mode-empty", in main()
611 g_test_add_data_func("/crypto/block/luks/bad/cipher-mode-unknown", in main()
614 g_test_add_data_func("/crypto/block/luks/bad/ivgen-separator", in main()
[all …]
/openbmc/linux/block/
H A Dbadblocks.c3 * Bad block management
20 * badblocks_check() - check a given range for bad sectors
27 * We can record which blocks on each device are 'bad' and so just
29 * Entries in the bad-block table are 64bits wide. This comprises:
30 * Length of bad-range, in sectors: 0-511 for lengths 1-512
31 * Start of bad-range, sector offset, 54 bits (allows 8 exbibytes)
36 * Locking of the bad-block table uses a seqlock so badblocks_check
38 * We will sometimes want to check for bad blocks in a bi_end_io function,
41 * When looking for a bad block we specify a range and want to
42 * know if any block in the range is bad. So we binary-search
[all …]

12345678910>>...137