| /openbmc/linux/Documentation/livepatch/ |
| H A 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
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/timer/ |
| H A D | arm,arch_timer.yaml | 74 where reading certain values from the counter is unreliable. This also
80 that reading the counter is unreliable unless the same value is returned
87 says that reading the counters is unreliable in some cases, and reads may
|
| /openbmc/linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap3-beagle-ab4.dts | 16 /* Unusable as clocksource because of unreliable oscillator */
21 /* Unusable as clockevent because of unreliable oscillator, allow to idle */
|
| /openbmc/linux/arch/powerpc/kernel/ |
| H A D | stacktrace.c | 60 * This function returns an error if it detects any unreliable features of the
120 /* Mark stacktraces with exception frames as unreliable. */ in arch_stack_walk_reliable()
139 * as unreliable. in arch_stack_walk_reliable()
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A 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
|
| /openbmc/linux/drivers/bluetooth/ |
| H A D | hci_bcsp.c | 46 struct sk_buff_head unrel; /* Unreliable packets queue */
182 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt()
186 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt()
190 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt()
277 /* First of all, check for unreliable messages in the queue, in bcsp_dequeue()
330 /* if so, craft an empty ACK pkt and send it on BCSP unreliable in bcsp_dequeue()
553 "reliable" : "unreliable"); in bcsp_complete_rx_pkt()
|
| /openbmc/linux/drivers/hwmon/ |
| H A D | k10temp.c | 326 * may be unreliable. in has_erratum_319()
411 int unreliable = has_erratum_319(pdev); in k10temp_probe() local
417 if (unreliable) { in k10temp_probe()
420 "unreliable CPU thermal sensor; monitoring disabled\n"); in k10temp_probe()
424 "unreliable CPU thermal sensor; check erratum 319\n"); in k10temp_probe()
|
| /openbmc/linux/Documentation/PCI/ |
| H A D | pcieaer-howto.rst | 115 to be unreliable. Depending on those error conditions, uncorrectable
117 Non-fatal errors cause the particular transaction to be unreliable,
119 the other hand, cause the link to be unreliable.
|
| /openbmc/linux/arch/arm64/tools/ |
| H A D | cpucaps | 8 # Unreliable: use system_supports_32bit_el0() instead.
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0/ |
| H A D | run-ptest | 18 # Known unreliable tests as per subprojects/gst-devtools/validate/launcher/testsuites/check.py:
|
| /openbmc/linux/net/dccp/ |
| H A D | Kconfig | 12 congestion-controlled, unreliable datagrams. It should be suitable
|
| /openbmc/linux/drivers/ras/ |
| H A D | Kconfig | 29 so have ideal availability, but may be unreliable, with frequent
|
| /openbmc/linux/arch/s390/kernel/ |
| H A D | stacktrace.c | 46 * as unreliable. in arch_stack_walk_reliable()
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
| /openbmc/linux/drivers/misc/genwqe/ |
| H A D | card_sysfs.c | 137 * unreliable data in very rare cases. This makes this sysfs
138 * unreliable up to the point were a new CPLD version is being used.
|
| /openbmc/linux/tools/include/linux/ |
| H A D | objtool_types.h | 25 * a truncated and unreliable stack unwind.
|
| /openbmc/linux/include/linux/ |
| H A D | objtool_types.h | 25 * a truncated and unreliable stack unwind.
|
| /openbmc/qemu/include/standard-headers/linux/ |
| H A D | virtio_ring.h | 53 * you add a buffer. It's unreliable, so it's simply an optimization. Guest
57 * when you consume a buffer. It's unreliable, so it's simply an
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | virtio_ring.h | 55 * you add a buffer. It's unreliable, so it's simply an optimization. Guest
59 * when you consume a buffer. It's unreliable, so it's simply an
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_display_limits.h | 105 HPD_TV = HPD_NONE, /* TV is known to be unreliable */
|
| /openbmc/openbmc/poky/meta/recipes-devtools/strace/strace/ |
| H A D | skip-load.patch | 6 Skip tests which are known to be unreliable under load, typically because they
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | init.rst | 19 --> initial console unavailable. E.g. some serial consoles are unreliable
|
| /openbmc/linux/fs/isofs/ |
| H A D | util.c | 43 * The timezone offset is unreliable on some disks, in iso_date()
|
| /openbmc/linux/drivers/scsi/ |
| H A D | sr.h | 49 bool ignore_get_event:1; /* GET_EVENT is unreliable, use TUR */
|