Home
last modified time | relevance | path

Searched refs:buggy (Results 1 – 25 of 54) sorted by relevance

123

/Linux-v6.1/Documentation/firmware-guide/acpi/
Dacpi-lid.rst22 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-v6.1/Documentation/translations/zh_CN/dev-tools/
Dkasan.rst149 The buggy address belongs to the object at ffff8801f44ec300
151 The buggy address is located 123 bytes inside of
153 The buggy address belongs to the page:
160 Memory state around the buggy address:
/Linux-v6.1/arch/ia64/scripts/
Dcheck-gas12 echo buggy
/Linux-v6.1/arch/ia64/
DMakefile32 ifeq ($(GAS_STATUS),buggy)
/Linux-v6.1/drivers/pnp/pnpbios/
DKconfig35 Also some buggy systems will fault when accessing certain features
/Linux-v6.1/drivers/staging/qlge/
DTODO17 * the flow control implementation in firmware is buggy (sends a flood of pause
/Linux-v6.1/Documentation/hwmon/
Dasus_wmi_sensors.rst69 * The WMI implementation in some of Asus' BIOSes is buggy. This can result in
/Linux-v6.1/tools/kvm/kvm_stat/
Dkvm_stat.txt19 Often conclusions about performance or buggy behavior can be drawn from the
/Linux-v6.1/tools/memory-model/Documentation/
Daccess-marking.txt289 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-v6.1/fs/jffs2/
Ddebug.c707 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-v6.1/Documentation/power/
Ds2ram.rst21 always it's a driver that is buggy. Thank God for the suspend/resume
/Linux-v6.1/Documentation/admin-guide/acpi/
Dinitrd_table_override.rst37 allows you to upgrade the buggy tables before your platform/BIOS vendor
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-ata139 be buggy and only unqueued TRIM commands
/Linux-v6.1/Documentation/dev-tools/
Dkasan.rst199 The buggy address belongs to the object at ffff8801f44ec300
201 The buggy address is located 123 bytes inside of
203 The buggy address belongs to the page:
210 Memory state around the buggy address:
/Linux-v6.1/Documentation/locking/
Dlocktorture.rst50 Simulates a buggy lock implementation.
/Linux-v6.1/Documentation/networking/device_drivers/fddi/
Dskfp.rst213 - Synchronization on SMP machines was buggy
/Linux-v6.1/Documentation/scheduler/
Dsched-nice-design.rst86 proof, and a buggy SCHED_FIFO app can also lock up the system for good.
/Linux-v6.1/Documentation/power/regulator/
Doverview.rst166 overvoltage or overcurrent caused by buggy client drivers. It also
/Linux-v6.1/Documentation/sound/designs/
Dprocfile.rst120 buggy) hardware that doesn't give smooth pointer updates.
/Linux-v6.1/arch/powerpc/kvm/
DKconfig175 those buggy L1s which saves the L2 state, at the cost of performance
/Linux-v6.1/Documentation/ABI/stable/
Dsysfs-class-tpm64 Durations can be modified in the case where a buggy chip
/Linux-v6.1/Documentation/input/devices/
Diforce-protocol.rst370 At first glance, this software seems, hum, well... buggy. In fact, data appear with a
/Linux-v6.1/Documentation/RCU/
Drcu_dereference.rst75 the following (quite strange) code is buggy::
87 As before, the reason this is buggy is that relational operators
/Linux-v6.1/Documentation/filesystems/
Dhpfs.rst120 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-v6.1/Documentation/process/
Dhandling-regressions.rst581 Guys, whether something was buggy or not DOES NOT MATTER.
598 Anybody who uses "but it was buggy" as an argument is entirely missing
599 the point. As far as the USER was concerned, it wasn't buggy - it
694 actually buggy. In fact, it was doing exactly what it set out to do,

123