| /linux/arch/arm/ |
| A D | Kconfig.debug | 119 prompt "Kernel low-level debugging port"
131 bool "Kernel low-level debugging via asm9260 UART"
172 bool "Kernel low-level debugging on SAMA5D2 UART1"
180 bool "Kernel low-level debugging on SAMA5D4 USART3"
188 bool "Kernel low-level debugging via SAMV7 USART1"
225 bool "Kernel low-level debugging on BCM IPROC UART3"
244 bool "Kernel low-level debugging on BCM63XX UART"
677 bool "Kernel low-level debugging via OMAP1 UART1"
685 bool "Kernel low-level debugging via OMAP1 UART2"
693 bool "Kernel low-level debugging via OMAP1 UART3"
[all …]
|
| /linux/net/mac80211/ |
| A D | Kconfig | 101 bool "Select mac80211 debugging features"
123 bool "Verbose debugging output"
145 bool "Verbose station debugging"
154 bool "Verbose HT debugging"
166 bool "Verbose OCB debugging"
177 bool "Verbose IBSS debugging"
188 bool "Verbose powersave mode debugging"
200 bool "Verbose mesh peer link debugging"
213 bool "Verbose mesh path debugging"
261 bool "Verbose mesh powersave debugging"
[all …]
|
| /linux/arch/powerpc/ |
| A D | Kconfig.debug | 155 bool "Early debugging (dangerous)"
165 prompt "Early debugging console"
169 enable debugging for the wrong type of machine your kernel
203 Select this to enable early debugging via the RTAS panel.
216 Select this to enable early debugging for Maple.
222 Select this to enable early debugging for PA Semi.
226 bool "Early serial debugging for IBM/AMCC 44x CPUs"
234 bool "Early serial debugging for IBM/AMCC 40x CPUs"
245 Select this to enable early debugging for Freescale chips
250 bool "Early debugging through the USB Gecko adapter"
[all …]
|
| /linux/fs/jbd2/ |
| 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
|
| /linux/net/dccp/ccids/ |
| 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
|
| /linux/drivers/infiniband/ulp/ipoib/ |
| 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
|
| /linux/Documentation/power/ |
| 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).
|
| /linux/drivers/gpu/drm/i915/ |
| 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
150 Choose this option to turn on extra driver debugging that may affect
158 bool "Enable additional driver debugging for GuC"
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| 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
|
| /linux/fs/cachefiles/ |
| A D | Kconfig | 18 This permits debugging to be dynamically enabled in the filesystem
19 caching on files module. If this is set, the debugging output may be
21 by including a debugging specifier in /etc/cachefilesd.conf.
|
| /linux/kernel/debug/kdb/ |
| A D | kdb_cmds | 7 # Standard debugging information for first level support, just type archkdb
10 defcmd dumpcommon "" "Common kdb debugging"
20 defcmd dumpall "" "First line debugging"
|
| /linux/fs/ntfs/ |
| A D | Kconfig | 31 bool "NTFS debugging support"
36 performed by the driver as well as additional debugging messages to
37 be written to the system log. Note that debugging messages are
41 you can enable debugging messages by doing (as root):
45 If you leave debugging messages disabled, this results in little
50 debugging messages while the misbehaviour was occurring.
|
| /linux/drivers/atm/ |
| 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
170 bool "Enable extended debugging"
176 Note that extended debugging may create certain race conditions
222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
257 bool "Enable debugging messages"
281 bool "Enable debugging messages"
314 bool "Enable debugging messages"
[all …]
|
| /linux/Documentation/vm/ |
| A D | slub.rst | 10 SLUB can enable debugging only for selected slabs in order to avoid
15 to the kernel command line. That will enable full debugging for
28 available without debugging on and validation can only partially
29 be performed if debugging was not switched on.
35 debugging is enabled. Format:
58 O Switch debugging off for caches that would have
60 - Switch all debugging off (useful if the kernel is
87 switch off debugging for such caches by default, use::
93 kmalloc. All other slabs will not get any debugging enabled::
306 will be used (unlike full debugging).
[all …]
|
| /linux/Documentation/firmware-guide/acpi/ |
| 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"
|
| /linux/fs/afs/ |
| A D | Kconfig | 17 bool "AFS dynamic debugging"
20 Say Y here to make runtime controllable debugging messages appear.
34 bool "AFS server cursor debugging"
|
| /linux/block/ |
| A D | Kconfig.iosched | 39 bool "BFQ IO controller debugging"
42 Enable some debugging help. Currently it exports additional stat
43 files in a cgroup which can be useful for debugging.
|
| /linux/fs/fscache/ |
| A D | Kconfig | 28 debugging purposes. Saying 'Y' here is recommended.
36 This permits debugging to be dynamically enabled in the local caching
37 management module. If this is set, the debugging output may be
|
| /linux/Documentation/core-api/ |
| A D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
34 Together with a early initialization of the OHCI-1394 controller for debugging,
37 fails to boot and other means for debugging (serial port) are either not
44 DMA by default, which is more secure but not suitable for remote debugging.
53 Remote debugging over FireWire early on boot) and pass the parameter
147 4) Prepare for debugging with early OHCI-1394 initialization:
162 With the FireWire cable connected, the OHCI-1394 driver on the debugging
166 Then, on the debugging host, run firescope, for example by using -A::
|
| /linux/scripts/ |
| A D | checkversion.pl | 13 my $debugging;
66 if ($debugging) {
|
| /linux/arch/nios2/ |
| A D | Kconfig.debug | 4 bool "Activate early kernel debugging"
10 This is useful for kernel debugging when your machine crashes very
|
| /linux/fs/jffs2/ |
| A D | Kconfig | 16 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
20 This controls the amount of debugging messages produced by the JFFS2
22 testing and debugging, it's advisable to set it to one. This will
23 enable a few assertions and will print debugging messages at the
25 is unlikely to be useful - it enables extra debugging in certain
26 areas which at one point needed debugging, but when the bugs were
|
| /linux/drivers/memstick/ |
| A D | Kconfig | 17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
|
| /linux/drivers/infiniband/hw/mthca/ |
| A D | Kconfig | 11 bool "Verbose debugging output" if EXPERT
15 This option causes debugging code to be compiled into the
|
| /linux/drivers/net/wireless/zydas/zd1211rw/ |
| A D | Kconfig | 14 bool "ZyDAS ZD1211 debugging"
17 ZD1211 debugging messages. Choosing Y will result in additional debug
|