| /openbmc/linux/arch/arm/ |
| H A D | Kconfig.debug | 101 sometimes helpful for debugging but serves no purpose on a
115 bool "Kernel low-level debugging functions (read help!)"
119 in the kernel. This is helpful if you are debugging code that
128 prompt "Kernel low-level debugging port"
132 bool "Kernel low-level debugging messages via Alpine UART0"
136 Say Y here if you want kernel low-level debugging support
140 bool "Kernel low-level debugging via asm9260 UART"
161 bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU"
165 Say Y here if you want kernel low-level debugging support
171 bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU"
[all …]
|
| /openbmc/linux/net/mac80211/ |
| H A D | Kconfig | 93 collect all debugging messages, independent of
101 bool "Select mac80211 debugging features"
112 easier debugging of problems in the transmit and receive
123 bool "Verbose debugging output"
127 many debugging messages. It should not be selected
138 debugging messages for the managed-mode MLME. It
145 bool "Verbose station debugging"
149 debugging messages for station addition/removal.
154 bool "Verbose HT debugging"
166 bool "Verbose OCB debugging"
[all …]
|
| /openbmc/linux/arch/powerpc/ |
| H A D | Kconfig.debug | 155 bool "Early debugging (dangerous)"
157 Say Y to enable some early debugging facilities that may be available
165 prompt "Early debugging console"
168 Use the selected console for early debugging. Careful, if you
169 enable debugging for the wrong type of machine your kernel
176 Select this to enable early debugging for a machine using BootX
183 Select this to enable early debugging for a machine with a HVC
190 Select this to enable early debugging for a machine with a HVSI
197 Select this to enable early debugging for Apple G5 machines.
203 Select this to enable early debugging via the RTAS panel.
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-bus-vmbus | 71 Users: tools/hv/lsvmbus and other debugging tools
78 Users: Debugging tools
87 Users: Debugging tools
94 Users: Debugging tools
103 Users: Debugging tools
110 Users: Debugging tools
117 Users: Debugging tools
124 Users: Debugging tools
131 Users: Debugging tools
138 Users: Debugging tools and userspace drivers
[all …]
|
| /openbmc/linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 20 bool "Enable additional driver debugging"
45 Choose this option to turn on extra driver debugging that may affect
110 Enable additional and verbose debugging output that will spam
111 ordinary tests, but may be vital for post-mortem debugging when
124 Enable additional and verbose debugging output that will spam
125 ordinary tests, but may be vital for post-mortem debugging when
133 bool "Enable additional driver debugging for fence objects"
138 Choose this option to turn on extra driver debugging that may affect
146 bool "Enable additional driver debugging for detecting dependency cycles"
150 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/abseil-cpp/abseil-cpp/ |
| H A D | 0004-abseil-ppc-fixes.patch | 21 absl/debugging/internal/examine_stack.cc | 8 +++++++-
22 absl/debugging/internal/stacktrace_config.h | 2 +-
61 diff --git a/absl/debugging/internal/examine_stack.cc b/absl/debugging/internal/examine_stack.cc
63 --- a/absl/debugging/internal/examine_stack.cc
64 +++ b/absl/debugging/internal/examine_stack.cc
88 diff --git a/absl/debugging/internal/stacktrace_config.h b/absl/debugging/internal/stacktrace_confi…
90 --- a/absl/debugging/internal/stacktrace_config.h
91 +++ b/absl/debugging/internal/stacktrace_config.h
95 "absl/debugging/internal/stacktrace_x86-inl.inc"
99 "absl/debugging/internal/stacktrace_powerpc-inl.inc"
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-grpcio/ |
| H A D | abseil-ppc-fixes.patch | 19 .../abseil-cpp/absl/debugging/internal/examine_stack.cc | 8 +++++++-
20 .../absl/debugging/internal/stacktrace_config.h | 2 +-
59 …ff --git a/third_party/abseil-cpp/absl/debugging/internal/examine_stack.cc b/third_party/abseil-cp…
61 --- a/third_party/abseil-cpp/absl/debugging/internal/examine_stack.cc
62 +++ b/third_party/abseil-cpp/absl/debugging/internal/examine_stack.cc
86 … --git a/third_party/abseil-cpp/absl/debugging/internal/stacktrace_config.h b/third_party/abseil-c…
88 --- a/third_party/abseil-cpp/absl/debugging/internal/stacktrace_config.h
89 +++ b/third_party/abseil-cpp/absl/debugging/internal/stacktrace_config.h
93 "absl/debugging/internal/stacktrace_x86-inl.inc"
97 "absl/debugging/internal/stacktrace_powerpc-inl.inc"
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi | 9 Users: Debugging, any userspace test suite
20 Users: Debugging, any userspace test suite
28 Users: Debugging, any userspace test suite
36 Users: Debugging, any userspace test suite
44 Users: Debugging, any userspace test suite
52 Users: Debugging, any userspace test suite
61 Users: Debugging, any userspace test suite
70 Users: Debugging, any userspace test suite
|
| H A D | debugfs-scmi-raw | 14 Users: Debugging, any userspace test suite
32 Users: Debugging, any userspace test suite
43 Users: Debugging, any userspace test suite
54 Users: Debugging, any userspace test suite
66 Users: Debugging, any userspace test suite
90 Users: Debugging, any userspace test suite
117 Users: Debugging, any userspace test suite
|
| /openbmc/linux/fs/jbd2/ |
| H A D | Kconfig | 23 bool "JBD2 (ext4) debugging support"
28 allows you to enable debugging output while the system is running,
30 By default, the debugging output will be turned off.
32 If you select Y here, then you will be able to turn on debugging
34 number between 1 and 5. The higher the number, the more debugging
35 output is generated. To turn debugging off again, do
|
| /openbmc/linux/net/dccp/ccids/ |
| H A D | Kconfig | 5 bool "CCID-2 debugging messages"
7 Enable CCID-2 specific debugging messages.
9 The debugging output can additionally be toggled by setting the
40 bool "CCID-3 debugging messages"
43 Enable CCID-3 specific debugging messages.
45 The debugging output can additionally be toggled by setting the
|
| /openbmc/linux/drivers/infiniband/ulp/ipoib/ |
| H A D | Kconfig | 28 bool "IP-over-InfiniBand debugging" if EXPERT
32 This option causes debugging code to be compiled into the
38 debugfs, which contains files that expose debugging
43 bool "IP-over-InfiniBand data path debugging"
46 This option compiles debugging code into the data path
49 turned off, this debugging code will have some performance
|
| /openbmc/linux/drivers/usb/dwc2/ |
| H A D | Kconfig | 68 bool "Enable Debugging Messages"
70 Say Y here to enable debugging messages in the DWC2 Driver.
73 bool "Enable Verbose Debugging Messages"
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
88 bool "Enable Debugging Messages For Periodic Transfers"
92 Say N here to disable (verbose) debugging messages to be
93 logged for periodic transfers. This allows better debugging of
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | debugging.rst | 3 Debugging Tools and Techniques
6 The exact method for debugging build failures depends on the nature of
8 Standard debugging practices such as comparison against the last known
13 provides some general tips to aid in debugging given a variety of
18 A useful feature for debugging is the error reporting tool.
28 The following list shows the debugging topics in the remainder of this
31 - ":ref:`dev-manual/debugging:viewing logs from failed tasks`" describes
35 - ":ref:`dev-manual/debugging:viewing variable values`" describes how to
39 - ":ref:`dev-manual/debugging:viewing package information with \`\`oe-pkgdata-util\`\``"
44 - ":ref:`dev-manual/debugging:viewing dependencies between recipes and tasks`"
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb3-debug-port.rst | 13 Before using any kernel debugging functionality based on USB3
18 2) check which port is used for debugging purposes;
19 3) have a USB 3.0 super-speed A-to-A debugging cable.
33 (the system under debugging) and a debug host.
39 this feature is kernel debugging. For example, when your machine
44 On the debug target system, you need to customize a debugging
63 should be a USB 3.0 super-speed A-to-A debugging cable.
126 speed A-to-A debugging cable. You can see /dev/ttyDBC0 created
151 The debug device works now. You can use any communication or debugging
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/aufs-util/aufs-util/ |
| H A D | aufs-util-don-t-strip-executables.patch | 9 …G: File '/sbin/mount.aufs' from aufs-util was already stripped, this will prevent future debugging!
10 …NING: File '/sbin/auplink' from aufs-util was already stripped, this will prevent future debugging!
11 …: File '/sbin/umount.aufs' from aufs-util was already stripped, this will prevent future debugging!
12 …NING: File '/sbin/auibusy' from aufs-util was already stripped, this will prevent future debugging!
13 …le '/usr/lib/libau.so.2.6' from aufs-util was already stripped, this will prevent future debugging!
|
| /openbmc/linux/Documentation/power/ |
| H A D | drivers-testing.rst | 21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
22 for more information about the debugging of suspend/resume functionality.
31 (see: Documentation/power/basic-pm-debugging.rst, 1).
34 "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
43 Documentation/power/basic-pm-debugging.rst, 2). [As far as the STR tests are
48 (see: Documentation/power/basic-pm-debugging.rst, 2).
|
| /openbmc/linux/fs/ntfs/ |
| H A D | Kconfig | 32 bool "NTFS debugging support"
37 performed by the driver as well as additional debugging messages to
38 be written to the system log. Note that debugging messages are
42 you can enable debugging messages by doing (as root):
46 If you leave debugging messages disabled, this results in little
51 debugging messages while the misbehaviour was occurring.
|
| /openbmc/linux/kernel/configs/ |
| H A D | debug.config | 1 # Help: Debugging for CI systems and finding regressions
27 # Generic Kernel Debugging Instruments
43 # Memory Debugging
89 # Lock Debugging (spinlocks, mutexes, etc...)
98 # RCU Debugging
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.debug | 130 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
207 debugging but costs about 70-100K of memory.
212 bool "Kernel debugging"
244 that will include debugging info resulting in a larger kernel image.
255 Do not build the kernel with debugging information, which will
304 bool "Reduce debugging information"
306 If you say Y here gcc is instructed to generate less debugging
308 need full debugging information (like kgdb or systemtap) won't
309 be happy. But if you merely need debugging information to
329 bool "Compress debugging information with zlib"
[all …]
|
| /openbmc/linux/sound/core/ |
| H A D | Kconfig | 168 You don't need this unless you're debugging ALSA.
189 Say Y here to enable extra-verbose debugging messages.
191 Let me repeat: it enables EXTRA-VERBOSE DEBUGGING messages.
195 bool "Enable PCM ring buffer overrun/underrun debugging"
199 Say Y to enable the PCM ring buffer overrun/underrun debugging.
215 bool "Enable debugging feature for control API"
218 Say Y to enable the debugging feature for ALSA control API.
234 Say Y if you are debugging via jack injection interface.
|
| /openbmc/linux/drivers/atm/ |
| H A D | Kconfig | 55 bool "Enable extended debugging"
58 Extended debugging records various events and displays that list
61 Note that extended debugging may create certain race conditions
192 bool "Enable debugging messages"
195 Somewhat useful debugging messages are available. The choice of
210 for debugging or special applications only, so the safe answer is N.
235 bool "Enable debugging messages"
238 Somewhat useful debugging messages are available. The choice of
292 int "Debugging level (0-3)"
296 Specifies the level of debugging messages issued by the driver.
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | slub.rst | 7 slab caches. SLUB always includes full debugging but it is off by default.
8 SLUB can enable debugging only for selected slabs in order to avoid
12 In order to switch debugging on one can add an option ``slub_debug``
13 to the kernel command line. That will enable full debugging for
24 Some of the modes of operation of ``slabinfo`` require that slub debugging
26 available without debugging on and validation can only partially
27 be performed if debugging was not switched on.
33 debugging is enabled. Format:
56 O Switch debugging off for caches that would have
58 - Switch all debugging off (useful if the kernel is
[all …]
|
| /openbmc/u-boot/arch/arm/ |
| H A D | Kconfig.debug | 4 bool "Low-level debugging functions"
8 in U-Boot. This is helpful if you are debugging code that
12 prompt "Low-level debugging port"
16 bool "Low-level debugging via 8250 UART"
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 26 ACPICA subsystem provides debugging outputs when CONFIG_ACPI_DEBUG is
27 enabled. The debugging messages which are deployed via
34 evaluations, the quantity of the debugging outputs may still be too
101 interpretation, thus can aid issue debugging and performance tuning. Note
200 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
206 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
212 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
218 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
224 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
|