Searched refs:buggy (Results 1 – 25 of 51) sorted by relevance
123
| /Linux-v5.15/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 22 exceptional buggy platforms, special restrictions and exceptions 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.15/Documentation/translations/zh_CN/dev-tools/ |
| D | kasan.rst | 118 The buggy address belongs to the object at ffff8801f44ec300
120 The buggy address is located 123 bytes inside of
122 The buggy address belongs to the page:
129 Memory state around the buggy address:
|
| /Linux-v5.15/arch/ia64/scripts/ |
| D | check-gas | 12 echo buggy
|
| /Linux-v5.15/arch/ia64/ |
| D | Makefile | 32 ifeq ($(GAS_STATUS),buggy)
|
| /Linux-v5.15/drivers/pnp/pnpbios/ |
| D | Kconfig | 35 Also some buggy systems will fault when accessing certain features
|
| /Linux-v5.15/drivers/staging/qlge/ |
| D | TODO | 17 * the flow control implementation in firmware is buggy (sends a flood of pause
|
| /Linux-v5.15/tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 19 Often conclusions about performance or buggy behavior can be drawn from the
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | access-marking.txt | 289 buggy lockless writes, read_foo_diagnostic() can be updated as follows:
304 However, in order for KCSAN to detect buggy lockless writes, your kernel
344 of the ASSERT_EXCLUSIVE_WRITER() is to allow KCSAN to check for a buggy
511 ASSERT_EXCLUSIVE_ACCESS() allows KCSAN to flag buggy concurrent unmarked
513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| /Linux-v5.15/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.15/Documentation/power/ |
| D | s2ram.rst | 21 always it's a driver that is buggy. Thank God for the suspend/resume
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | kasan.rst | 116 The buggy address belongs to the object at ffff8801f44ec300
118 The buggy address is located 123 bytes inside of
120 The buggy address belongs to the page:
127 Memory state around the buggy address:
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-ata | 138 be buggy and only unqueued TRIM commands
|
| /Linux-v5.15/Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 37 allows you to upgrade the buggy tables before your platform/BIOS vendor
|
| /Linux-v5.15/Documentation/locking/ |
| D | locktorture.rst | 50 Simulates a buggy lock implementation.
|
| /Linux-v5.15/Documentation/networking/device_drivers/fddi/ |
| D | skfp.rst | 213 - Synchronization on SMP machines was buggy
|
| /Linux-v5.15/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.15/Documentation/power/regulator/ |
| D | overview.rst | 166 overvoltage or overcurrent caused by buggy client drivers. It also
|
| /Linux-v5.15/Documentation/sound/designs/ |
| D | procfile.rst | 120 buggy) hardware that doesn't give smooth pointer updates.
|
| /Linux-v5.15/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.15/Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 64 Durations can be modified in the case where a buggy chip
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | hpfs.rst | 120 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
136 would cause more problems than benefit with such buggy implementation in OS/2.
|
| /Linux-v5.15/Documentation/RCU/ |
| D | rcu_dereference.rst | 75 the following (quite strange) code is buggy::
87 As before, the reason this is buggy is that relational operators
|
| /Linux-v5.15/Documentation/m68k/ |
| D | buddha-driver.rst | 87 a buggy firmware and pull the IRQ line up
|
| /Linux-v5.15/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
|
| /Linux-v5.15/arch/x86/ |
| D | Kconfig.debug | 112 are debugging a buggy device driver that leaks IOMMU mappings.
|
123
