Searched refs:buggy (Results 1 – 25 of 53) sorted by relevance
123
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 22 exceptional buggy platforms, special restrictions and expections should be
31 However the word of "current" has ambiguity, some buggy AML tables return
42 There are buggy AML tables never notifying when the lid device state is
66 triggered events to the userspace. However, given the fact that the buggy
85 isn't ready to handle the buggy AML tables.
114 handle the buggy AML tables.
|
| /Linux-v5.4/arch/ia64/scripts/ |
| D | check-gas | 12 echo buggy
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kasan.rst | 114 The buggy address belongs to the object at ffff8801f44ec300
116 The buggy address is located 123 bytes inside of
118 The buggy address belongs to the page:
125 Memory state around the buggy address:
|
| /Linux-v5.4/drivers/pnp/pnpbios/ |
| D | Kconfig | 35 Also some buggy systems will fault when accessing certain features
|
| /Linux-v5.4/arch/ia64/ |
| D | Makefile | 34 ifeq ($(GAS_STATUS),buggy)
|
| /Linux-v5.4/tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 19 Often conclusions about performance or buggy behavior can be drawn from the
|
| /Linux-v5.4/drivers/staging/qlge/ |
| D | TODO | 26 * the flow control implementation in firmware is buggy (sends a flood of pause
|
| /Linux-v5.4/fs/jffs2/ |
| D | debug.c | 707 int buggy = 0; in __jffs2_dbg_dump_fragtree_nolock() local
721 buggy = 1; in __jffs2_dbg_dump_fragtree_nolock()
729 if (buggy) { in __jffs2_dbg_dump_fragtree_nolock()
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | asm-offsets.c | 43 #error Your compiler is too buggy; it is known to miscompile kernels
|
| D | unwind.c | 22 #warning Your compiler is too buggy; it is known to not compile ARM unwind support.
|
| /Linux-v5.4/Documentation/power/ |
| D | s2ram.rst | 21 always it's a driver that is buggy. Thank God for the suspend/resume
|
| /Linux-v5.4/Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 37 allows you to upgrade the buggy tables before your platform/BIOS vendor
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-ata | 138 be buggy and only unqueued TRIM commands
|
| /Linux-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 67 - calxeda,smmu-secure-config-access : Enable proper handling of buggy
|
| /Linux-v5.4/Documentation/locking/ |
| D | locktorture.rst | 50 Simulates a buggy lock implementation.
|
| /Linux-v5.4/Documentation/networking/ |
| D | skfp.txt | 186 - Synchronization on SMP machines was buggy
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-nice-design.rst | 86 proof, and a buggy SCHED_FIFO app can also lock up the system for good.
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | overview.rst | 166 overvoltage or overcurrent caused by buggy client drivers. It also
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | procfile.rst | 120 buggy) hardware that doesn't give smooth pointer updates.
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 64 Durations can be modified in the case where a buggy chip
|
| /Linux-v5.4/Documentation/input/devices/ |
| D | iforce-protocol.rst | 370 At first glance, this software seems, hum, well... buggy. In fact, data appear with a
|
| /Linux-v5.4/Documentation/RCU/ |
| D | rcu_dereference.txt | 66 the following (quite strange) code is buggy:
78 As before, the reason this is buggy is that relational operators
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | hpfs.txt | 108 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
124 would cause more problems than benefit with such buggy implementation in OS/2.
|
| /Linux-v5.4/Documentation/m68k/ |
| D | buddha-driver.rst | 87 a buggy firmware and pull the IRQ line up
|
| /Linux-v5.4/Documentation/cdrom/ |
| D | ide-cd.rst | 258 likely cause is that you have a buggy IDE adapter which doesn't
267 - Note that many MS-DOS CDROM drivers will work with such buggy
|
123
