Searched refs:unreliable (Results 1 – 25 of 37) sorted by relevance
12
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | omap3-devkit8000.dts | 18 /* Unusable as clocksource because of unreliable oscillator */
23 /* Unusable as clockevent because if unreliable oscillator, allow to idle */
|
| D | omap3-beagle.dts | 307 /* Unusable as clocksource because of unreliable oscillator */
312 /* Unusable as clockevent because if unreliable oscillator, allow to idle */
|
| /Linux-v5.15/Documentation/admin-guide/device-mapper/ |
| D | dm-flakey.rst | 6 unreliable behaviour periodically. It's been found useful in simulating
10 <up interval> seconds, then exhibits unreliable behaviour for <down
|
| /Linux-v5.15/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 70 If the userspace hasn't been prepared to ignore the unreliable "opened"
71 events and the unreliable initial state notification, Linux users can use
96 If the userspace has been prepared to ignore the unreliable "opened" events
97 and the unreliable initial state notification, Linux users should always
|
| /Linux-v5.15/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 46 the stack or other unwind state is corrupt or otherwise unreliable. The
125 unreliable to unwind from, e.g.
151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions
176 unwinder must report these cases as unreliable.
221 middle of return_to_handler and can report this as unreliable. Architectures
250 such cases, or report the unwinding as unreliable.
263 assumption can lead to unreliable stack traces. For example, consider the
|
| /Linux-v5.15/net/dccp/ |
| D | Kconfig | 12 congestion-controlled, unreliable datagrams. It should be suitable
|
| /Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/diag/ |
| D | fw_tracer.h | 143 u8 unreliable; member
|
| D | fw_tracer.c | 468 tracer_event->timestamp_event.unreliable = !!(urts >> 2); in poll_trace()
470 tracer_event->timestamp_event.unreliable = !!(urts & 1); in poll_trace()
654 if (!tracer_event->timestamp_event.unreliable) in mlx5_tracer_handle_trace()
|
| /Linux-v5.15/drivers/hwmon/ |
| D | k10temp.c | 395 int unreliable = has_erratum_319(pdev); in k10temp_probe() local
401 if (unreliable) { in k10temp_probe()
|
| /Linux-v5.15/drivers/ras/ |
| D | Kconfig | 29 so have ideal availability, but may be unreliable, with frequent
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
| /Linux-v5.15/Documentation/PCI/ |
| D | pcieaer-howto.rst | 116 to be unreliable. Depending on those error conditions, uncorrectable
118 Non-fatal errors cause the particular transaction to be unreliable,
120 the other hand, cause the link to be unreliable.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | init.rst | 19 --> initial console unavailable. E.g. some serial consoles are unreliable
|
| D | svga.rst | 71 of chipsets is turned off by default as it's inherently unreliable due to
|
| /Linux-v5.15/arch/arm64/ |
| D | Makefile | 36 $(warning Detected assembler with broken .inst; disassembly will be unreliable)
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | index.rst | 79 but this point also applies to testing. If your tests are slow, unreliable, are
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | parport-lowlevel.rst | 1497 times out, the return value may be unreliable.
1535 times out, the return value may be unreliable.
1573 times out, the return value may be unreliable.
1613 times out, the return value may be unreliable.
|
| /Linux-v5.15/Documentation/trace/ |
| D | mmiotrace.rst | 28 supported, but tracing is unreliable and may miss events if more than one CPU
|
| /Linux-v5.15/Documentation/admin-guide/blockdev/ |
| D | floppy.rst | 181 flushings, and slightly more unreliable. Please verify your
|
| /Linux-v5.15/Documentation/networking/ |
| D | udplite.rst | 43 UDP-Lite provides a connectionless, unreliable datagram service and hence
|
| D | dccp.rst | 20 Datagram Congestion Control Protocol (DCCP) is an unreliable, connection
|
| /Linux-v5.15/Documentation/process/ |
| D | 3.Early-stage.rst | 118 unreliable. This concern (among others) kept AppArmor out of the
|
| /Linux-v5.15/Documentation/usb/ |
| D | gadget_serial.rst | 103 The gadget serial driver only provides simple unreliable data
|
| /Linux-v5.15/Documentation/power/ |
| D | basic-pm-debugging.rst | 194 unreliable, the platform firmware may be responsible for the failures.
|
| /Linux-v5.15/tools/objtool/Documentation/ |
| D | stack-validation.txt | 110 stack traces need to be reliable (or an unreliable condition needs to
|
12
