Searched refs:debugging (Results 1 – 25 of 365) sorted by relevance
12345678910>>...15
| /linux-3.3/arch/arm/ |
| D | Kconfig.debug | 12 be used by people debugging the kernel.
54 sometimes helpful for debugging but serves no purpose on a
68 bool "Kernel low-level debugging functions (read help!)"
72 in the kernel. This is helpful if you are debugging code that
81 prompt "Kernel low-level debugging port"
85 bool "No low-level debugging UART"
89 definition internally in order for low-level debugging to
93 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
104 bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
108 bool "Kernel low-level debugging on 9263, 9g45 and cap9"
[all …]
|
| /linux-3.3/net/mac80211/ |
| D | Kconfig | 111 bool "Select mac80211 debugging features"
122 easier debugging of problems in the transmit and receive
133 bool "Verbose debugging output"
137 many debugging messages. It should not be selected
144 bool "Verbose HT debugging"
156 bool "Verbose TKIP debugging"
160 very verbose TKIP debugging messages. It should not
167 bool "Verbose IBSS debugging"
171 very verbose IBSS debugging messages. It should not
178 bool "Verbose powersave mode debugging"
[all …]
|
| /linux-3.3/arch/powerpc/ |
| D | Kconfig.debug | 143 bool "Early debugging (dangerous)"
145 Say Y to enable some early debugging facilities that may be available
153 prompt "Early debugging console"
156 Use the selected console for early debugging. Careful, if you
157 enable debugging for the wrong type of machine your kernel
164 Select this to enable early debugging for a machine with a HVC
171 Select this to enable early debugging for a machine with a HVSI
178 Select this to enable early debugging for Apple G5 machines.
184 Select this to enable early debugging via the RTAS panel.
191 Select this to enable early debugging via the RTAS console.
[all …]
|
| /linux-3.3/fs/jbd/ |
| D | Kconfig | 17 bool "JBD (ext3) debugging support"
22 enable debugging output while the system is running, in order to
24 debugging output will be turned off.
26 If you select Y here, then you will be able to turn on debugging
28 number between 1 and 5, the higher the number, the more debugging
29 output is generated. To turn debugging off again, do
|
| /linux-3.3/fs/jbd2/ |
| D | Kconfig | 20 bool "JBD2 (ext4) debugging support"
25 allows you to enable debugging output while the system is running,
27 By default, the debugging output will be turned off.
29 If you select Y here, then you will be able to turn on debugging
31 number between 1 and 5. The higher the number, the more debugging
32 output is generated. To turn debugging off again, do
|
| /linux-3.3/net/dccp/ccids/ |
| 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-3.3/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 27 bool "IP-over-InfiniBand debugging" if EXPERT
31 This option causes debugging code to be compiled into the
37 debugfs, which contains files that expose debugging
42 bool "IP-over-InfiniBand data path debugging"
45 This option compiles debugging code into the data path
48 turned off, this debugging code will have some performance
|
| /linux-3.3/fs/ubifs/ |
| D | Kconfig | 47 bool "Enable debugging support"
52 This option enables UBIFS debugging support. It makes sure various
53 assertions, self-checks, debugging messages and test modes are compiled
55 and this option also enables them. Self-checks, debugging messages and
57 recommended to have debugging support enabled, and it should not slow
58 down UBIFS. You can then further enable / disable individual debugging
|
| /linux-3.3/fs/fscache/ |
| D | Kconfig | 25 debugging purposes. Saying 'Y' here is recommended.
42 useful for debugging purposes. Saying 'N' here is recommended.
50 This permits debugging to be dynamically enabled in the local caching
51 management module. If this is set, the debugging output may be
57 bool "Maintain global object list for debugging purposes"
61 retrieved through /proc/fs/fscache/objects for debugging purposes
|
| /linux-3.3/arch/unicore32/ |
| D | Kconfig.debug | 12 be used by people debugging the kernel.
24 This is useful for kernel debugging when your machine crashes very
32 bool "Kernel low-level debugging functions"
36 in the kernel. This is helpful if you are debugging code that
40 bool "Kernel low-level debugging via On-Chip-Debugger"
|
| /linux-3.3/Documentation/power/ |
| D | drivers-testing.txt | 17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
18 for more information about the debugging of suspend/resume functionality.
26 (see: Documentation/power/basic-pm-debugging.txt, 1).
29 "platform" modes (see: Documentation/power/basic-pm-debugging.txt, 1).
37 e) Try the test modes of suspend (see: Documentation/power/basic-pm-debugging.txt,
42 (see: Documentation/power/basic-pm-debugging.txt, 2).
|
| /linux-3.3/fs/cachefiles/ |
| D | Kconfig | 17 This permits debugging to be dynamically enabled in the filesystem
18 caching on files module. If this is set, the debugging output may be
20 by including a debugging specifier in /etc/cachefilesd.conf.
36 useful for debugging purposes. Saying 'N' here is recommended.
|
| /linux-3.3/Documentation/pti/ |
| D | pti_intel_mid.txt | 12 pti.c is the driver that enables various debugging features
16 debugging data from a modem. Although n_tracerouter
26 An example debugging usage for this driver system:
28 a console device to further capture debugging messages to PTI.
29 *Hook /dev/ttyPTI1 to modem debugging data to write to PTI HW.
31 *Hook /dev/pti to a user-level debugging application for writing
34 debugging to PTI by first requesting a PTI write address via
|
| /linux-3.3/kernel/debug/kdb/ |
| 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-3.3/Documentation/vm/ |
| D | slub.txt | 6 slab caches. SLUB always includes full debugging but it is off by default.
7 SLUB can enable debugging only for selected slabs in order to avoid
11 In order to switch debugging on one can add a option "slub_debug"
12 to the kernel command line. That will enable full debugging for
22 Some of the modes of operation of slabinfo require that slub debugging
24 available without debugging on and validation can only partially
25 be performed if debugging was not switched on.
31 debugging is enabled. Format:
45 O Switch debugging off for caches that would have
47 - Switch all debugging off (useful if the kernel is
[all …]
|
| /linux-3.3/Documentation/parisc/ |
| D | 00-INDEX | 3 debugging
4 - some debugging hints for real-mode code
|
| /linux-3.3/Documentation/ |
| D | debugging-modules.txt | 10 In the past a debugging message which would fill people's logs was
11 emitted. This debugging message has been removed. The correct way
12 of debugging module problems is something like this:
|
| D | debugging-via-ohci1394.txt | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
30 Together with a early initialization of the OHCI-1394 controller for debugging,
33 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.
46 Remote debugging over FireWire with firewire-ohci) to get unfiltered physical
55 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-3.3/fs/ntfs/ |
| D | Kconfig | 30 bool "NTFS debugging support"
35 performed by the driver as well as additional debugging messages to
36 be written to the system log. Note that debugging messages are
40 you can enable debugging messages by doing (as root):
44 If you leave debugging messages disabled, this results in little
49 debugging messages while the misbehaviour was occurring.
|
| /linux-3.3/scripts/ |
| D | checkversion.pl | 12 my $debugging;
61 if ($debugging) {
|
| /linux-3.3/arch/mips/ |
| D | Kconfig.debug | 17 This is useful for kernel debugging when your machine crashes very
75 drops below a certain limit(2GB on MIPS). The debugging option
85 arch/mips/kernel/smtc.c. This debugging option result in significant
97 bool "Enable run-time debugging"
100 If you say Y here, some debugging macros will do run-time checking.
102 arch/mips/include/asm/debug.h for debugging macros.
106 bool "Enable compressed kernel support debugging"
|
| /linux-3.3/drivers/atm/ |
| D | Kconfig | 54 bool "Enable extended debugging"
57 Extended debugging records various events and displays that list
60 Note that extended debugging may create certain race conditions
169 bool "Enable extended debugging"
172 Extended debugging records various events and displays that list
175 Note that extended debugging may create certain race conditions
221 bool "Enable debugging messages"
224 Somewhat useful debugging messages are available. The choice of
239 for debugging or special applications only, so the safe answer is N.
256 bool "Enable debugging messages"
[all …]
|
| /linux-3.3/drivers/memstick/ |
| D | Kconfig | 16 bool "MemoryStick debugging"
19 say N here. This enables MemoryStick core and driver debugging.
|
| /linux-3.3/drivers/infiniband/hw/mthca/ |
| D | Kconfig | 10 bool "Verbose debugging output" if EXPERT
14 This option causes debugging code to be compiled into the
|
| /linux-3.3/drivers/net/ethernet/mellanox/mlx4/ |
| D | Kconfig | 20 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
24 This option causes debugging code to be compiled into the
|
12345678910>>...15