Searched full:buggy (Results 1 – 25 of 371) sorted by relevance
12345678910>>...15
22 exceptional buggy platforms, special restrictions and exceptions should be31 However the word of "current" has ambiguity, some buggy AML tables return42 There are buggy AML tables never notifying when the lid device state is66 triggered events to the userspace. However, given the fact that the buggy85 isn't ready to handle the buggy AML tables.114 handle the buggy AML tables.
11 * This file provides support for disabling the buggy read-ahead33 "(buggy RZ1000/RZ1001)\n", pci_name(dev)); in rz1000_disable_readahead()37 "(buggy RZ1000/RZ1001)\n", pci_name(dev)); in rz1000_disable_readahead()
34 /* Make sure driver is not buggy or using the old API */ in iw_handler_set_spy()83 /* Make sure driver is not buggy or using the old API */ in iw_handler_get_spy()118 /* Make sure driver is not buggy or using the old API */ in iw_handler_set_thrspy()145 /* Make sure driver is not buggy or using the old API */ in iw_handler_get_thrspy()200 /* Make sure driver is not buggy or using the old API */ in wireless_spy_update()
86 #define UART_BUG_QUOT (1 << 0) /* UART has buggy quot LSB */87 #define UART_BUG_TXEN (1 << 1) /* UART has buggy TX IIR status */88 #define UART_BUG_NOMSR (1 << 2) /* UART has buggy MSR status bits (Au1x00) */89 #define UART_BUG_THRE (1 << 3) /* UART has buggy THRE reassertion */
7 * livepatch-shadow-mod.c - Shadow variables, buggy module demo25 * Step 1 - Load the buggy demonstration module:74 MODULE_DESCRIPTION("Buggy module for shadow variable demo");
231 * buggy implementations we reserve boot services region during EFI374 * (duplicate) 1:1 mappings were also created as a quirk for buggy firmware. So,428 * code/data regions were mapped as a quirk for buggy firmware. in efi_free_boot_services()710 * Service is buggy. in efi_recover_from_page_fault()716 * Buggy efi_reset_system() is handled differently from other EFI in efi_recover_from_page_fault()724 pr_info("efi_reset_system() buggy! Reboot through BIOS\n"); in efi_recover_from_page_fault()
146 pr_err("The buggy address belongs to the object at %px\n" in describe_object_addr()164 pr_err("The buggy address is located %d bytes %s of\n" in describe_object_addr()396 pr_err("The buggy address belongs to the variable:\n"); in print_address_description()401 pr_err("The buggy address belongs to the page:\n"); in print_address_description()432 pr_err("Memory state around the buggy address:\n"); in print_shadow_for_address()
108 * is used so disable the HPI feature for such buggy cards.114 * feature is used so disable the HPI feature for such buggy cards.
111 The buggy address belongs to the object at ffff8801f44ec300113 The buggy address is located 123 bytes inside of115 The buggy address belongs to the page:122 Memory state around the buggy address:
12 echo buggy
97 "time. Buggy U3 ?"); in dart_tlb_invalidate_all()129 "time. Buggy U4 ?"); in dart_tlb_invalidate_one()215 * not doing it is that we won't catch buggy device drivers doing in dart_free()
43 /* the buggy hook is removed? */ in test__perf_hooks()
15 * already-configured bus numbers - to be used for buggy BIOSes
14 * Some versions of gcc implement strchr() with a buggy macro. So,
7 * already-configured bus numbers - to be used for buggy BIOSes
18 * be buggy. So let's have a correct XMM trap
9 * out before rolling your own buggy implementation in assembly language.
35 Also some buggy systems will fault when accessing certain features
43 bool pxa_u16_align4; /* PXA buggy u16 writes on 4*n+2 addresses */
56 * to avoid userspace of buggy BIOSes.
25 * numbers - to be used for buggy BIOSes or architectures with incomplete PCI setup by the
55 the bus. Also some SBS battery fuel gauges are known to have a buggy multi-
205 * Catch buggy drivers that fail to destroy their connections. in greybus_probe()253 /* Catch buggy drivers that fail to destroy their connections. */ in greybus_remove()
23 * the flow control implementation in firmware is buggy (sends a flood of pause
6 already-configured bus numbers - to be used for buggy BIOSes
