Home
last modified time | relevance | path

Searched refs:debugging (Results 1 – 200 of 389) sorted by relevance

12

/linux-4.1.27/arch/arm/
DKconfig.debug24 be used by people debugging the kernel.
66 sometimes helpful for debugging but serves no purpose on a
80 bool "Kernel low-level debugging functions (read help!)"
84 in the kernel. This is helpful if you are debugging code that
93 prompt "Kernel low-level debugging port"
97 bool "Kernel low-level debugging messages via Alpine UART0"
101 Say Y here if you want kernel low-level debugging support
105 bool "Kernel low-level debugging via asm9260 UART"
126 bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10, 9rl, 9x5, 9n12"
132 bool "Kernel low-level debugging on 9263, 9g45 and sama5d3"
[all …]
/linux-4.1.27/net/mac80211/
DKconfig108 collect all debugging messages, independent of
116 bool "Select mac80211 debugging features"
127 easier debugging of problems in the transmit and receive
138 bool "Verbose debugging output"
142 many debugging messages. It should not be selected
153 debugging messages for the managed-mode MLME. It
160 bool "Verbose station debugging"
164 debugging messages for station addition/removal.
169 bool "Verbose HT debugging"
181 bool "Verbose OCB debugging"
[all …]
/linux-4.1.27/arch/powerpc/
DKconfig.debug126 bool "Early debugging (dangerous)"
128 Say Y to enable some early debugging facilities that may be available
136 prompt "Early debugging console"
139 Use the selected console for early debugging. Careful, if you
140 enable debugging for the wrong type of machine your kernel
147 Select this to enable early debugging for a machine using BootX
154 Select this to enable early debugging for a machine with a HVC
161 Select this to enable early debugging for a machine with a HVSI
168 Select this to enable early debugging for Apple G5 machines.
174 Select this to enable early debugging via the RTAS panel.
[all …]
/linux-4.1.27/fs/jbd/
DKconfig17 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-4.1.27/net/dccp/ccids/
DKconfig4 bool "CCID-2 debugging messages"
6 Enable CCID-2 specific debugging messages.
8 The debugging output can additionally be toggled by setting the
39 bool "CCID-3 debugging messages"
42 Enable CCID-3 specific debugging messages.
44 The debugging output can additionally be toggled by setting the
/linux-4.1.27/fs/jbd2/
DKconfig22 bool "JBD2 (ext4) debugging support"
27 allows you to enable debugging output while the system is running,
29 By default, the debugging output will be turned off.
31 If you select Y here, then you will be able to turn on debugging
33 number between 1 and 5. The higher the number, the more debugging
34 output is generated. To turn debugging off again, do
/linux-4.1.27/drivers/infiniband/ulp/ipoib/
DKconfig27 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-4.1.27/fs/fscache/
DKconfig25 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-4.1.27/arch/unicore32/
DKconfig.debug12 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-4.1.27/Documentation/power/
Ddrivers-testing.txt17 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).
D00-INDEX5 basic-pm-debugging.txt
Dbasic-pm-debugging.txt167 c) Advanced debugging
171 modules cannot be unloaded, you can use one of the more advanced debugging
176 it may be possible to use a FireWire port for debugging with firescope
Dinterface.txt69 To use this debugging feature you should attempt to suspend the machine, then
Ds2ram.txt20 debugging - the thing that Chuck tried to disable. That's often the _only_
/linux-4.1.27/fs/cachefiles/
DKconfig17 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-4.1.27/Documentation/pti/
Dpti_intel_mid.txt12 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-4.1.27/kernel/debug/kdb/
Dkdb_cmds7 # Standard debugging information for first level support, just type archkdb
10 defcmd dumpcommon "" "Common kdb debugging"
20 defcmd dumpall "" "First line debugging"
/linux-4.1.27/Documentation/vm/
Dslub.txt6 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 …]
Dpage_owner.txt18 possibility rather than just keeping it in memory, so bad for debugging.
/linux-4.1.27/Documentation/parisc/
D00-INDEX3 debugging
4 - some debugging hints for real-mode code
Ddebugging1 okay, here are some hints for debugging the lower-level parts of
/linux-4.1.27/arch/score/
DKconfig.debug20 bool "Enable run-time debugging"
23 If you say Y here, some debugging macros will do run-time checking.
25 include/asm-score/debug.h for debugging macros.
/linux-4.1.27/Documentation/
Ddebugging-modules.txt10 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:
Ddebugging-via-ohci1394.txt2 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:
Dkmemcheck.txt24 kmemcheck is a debugging feature for the Linux Kernel. More specifically, it
39 as much memory as normal. For this reason, kmemcheck is strictly a debugging
91 debugging a problem. This option is not mandatory, however, because it slows
119 too -- and this would come in the way of debugging the specific
155 error is detected to help the debugging of a particular problem.
161 The default value should be fine for debugging most problems. It also
202 If SLUB debugging has been enabled in the kernel, it may take precedence over
203 kmemcheck in such a way that the slab caches which are under SLUB debugging
210 slub_debug=,dentry", then SLUB debugging will be used only for the "dentry"
282 because the kernel doesn't load the extra debugging information. This
[all …]
Dramoops.txt51 For quick debugging, you can also reserve parts of memory during boot
109 Persistent function tracing might be useful for debugging software or hardware
DDMA-API.txt202 DMA_NONE no direction (used for debugging)
588 debugging of DMA-API usage" option in your kernel configuration. Enabling this
632 from flooding your kernel log. To support debugging a device driver this can
636 The debugfs directory for the DMA-API debugging code is called dma-api/. In
640 value is not equal to zero the debugging code
646 if the debugging code is disabled. This can
679 'dma_debug=off' as a boot parameter. This will disable DMA-API debugging.
703 routines to enable DMA mapping error check debugging.
Dirqflags-tracing.txt11 and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
D00-INDEX146 debugging-modules.txt
147 - some notes on debugging modules after Linux 2.6.3.
148 debugging-via-ohci1394.txt
275 - documents the kernel probes debugging feature.
Dldm.txt72 debugging code. This will produce a LOT of output. The option is:
Dkernel-parameters.txt350 s3_beep is for debugging; it makes the PC's speaker beep
419 main buffer is allocated. This is handy if debugging
465 Change the amount of debugging information output
806 debug [KNL] Enable kernel debugging (events log level).
811 Print debugging info while doing the locking API
817 debug_objects [KNL] Enable object debugging
820 [KNL] Disable object debugging
850 debugpat [X86] Enable PAT debugging
902 this option disables the debugging code at boot.
906 entries for DMA-API debugging code. One entry is
[all …]
/linux-4.1.27/fs/ntfs/
DKconfig30 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-4.1.27/scripts/
Dcheckversion.pl12 my $debugging;
61 if ($debugging) {
Dunifdef.c168 static bool debugging; /* -d: debugging reports */ variable
280 debugging = true; in main()
576 if (debugging) in flushline()
1208 if (debugging) { in debug()
/linux-4.1.27/drivers/staging/unisys/Documentation/
Dproc-entries.txt5 These entries are provided primarily for debugging.
7 /proc/uislib/info: This entry contains debugging information for the
10 /proc/visorchipset/controlvm: This directory contains debugging
37 /proc/virthba/info: This entry contains debugging information for the
43 /proc/virtnic/info: This entry contains debugging information for the
51 /proc/virtpci/info: This entry contains debugging information for the
/linux-4.1.27/drivers/atm/
DKconfig54 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-4.1.27/drivers/memstick/
DKconfig16 bool "MemoryStick debugging"
19 say N here. This enables MemoryStick core and driver debugging.
/linux-4.1.27/drivers/infiniband/hw/mthca/
DKconfig10 bool "Verbose debugging output" if EXPERT
14 This option causes debugging code to be compiled into the
/linux-4.1.27/drivers/net/wireless/zd1211rw/
DKconfig13 bool "ZyDAS ZD1211 debugging"
16 ZD1211 debugging messages. Choosing Y will result in additional debug
/linux-4.1.27/drivers/mmc/
DKconfig16 bool "MMC debugging"
20 say N here. This enables MMC core and driver debugging.
/linux-4.1.27/arch/nios2/
DKconfig.debug18 bool "Activate early kernel debugging"
24 This is useful for kernel debugging when your machine crashes very
/linux-4.1.27/drivers/md/bcache/
DKconfig11 bool "Bcache debugging"
16 Enables extra debugging tools, allows expensive runtime checks to be
/linux-4.1.27/Documentation/frv/
Dgdbstub.txt35 (*) "Include debugging information"
38 to include debugging information.
56 debugging the serial drivers that'd otherwise be used to pass console
72 computer doing the debugging:
98 Remote debugging using /dev/ttyS0
125 and DBAR registers to assist debugging.
Dconfiguring.txt68 kernel configuration especially for debugging a kernel on this
Dkernel-ABI.txt74 entered only by debugging events obtained from the other two modes.
76 All kernel mode registers may be accessed, plus a few extra debugging
/linux-4.1.27/drivers/misc/cb710/
DKconfig15 bool "Enable driver debugging"
20 say N here. This adds a lot of debugging output to dmesg.
/linux-4.1.27/fs/afs/
DKconfig15 bool "AFS dynamic debugging"
18 Say Y here to make runtime controllable debugging messages appear.
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DKconfig26 bool "Atheros 5xxx debugging"
29 Atheros 5xxx debugging messages.
51 option if you are interested in debugging the driver.
/linux-4.1.27/arch/mips/
DKconfig.debug17 This is useful for kernel debugging when your machine crashes very
91 bool "Enable run-time debugging"
94 If you say Y here, some debugging macros will do run-time checking.
96 arch/mips/include/asm/debug.h for debugging macros.
100 bool "Enable compressed kernel support debugging"
/linux-4.1.27/fs/qnx6/
DKconfig19 bool "QNX6 debugging information"
22 Turns on extended debugging output.
/linux-4.1.27/drivers/scsi/
Dosst.c124 static int debugging = 1; variable
256 if (debugging) { in osst_chk_result()
304 if (debugging) { in osst_chk_result()
756 int dbg = debugging; in osst_wait_ready()
778 if (debugging) { in osst_wait_ready()
781 debugging = 0; in osst_wait_ready()
793 debugging = dbg; in osst_wait_ready()
820 int dbg = debugging; in osst_wait_for_medium()
836 if (debugging) { in osst_wait_for_medium()
839 debugging = 0; in osst_wait_for_medium()
[all …]
Dst.c68 #define DEBC(a) if (debugging) { a ; }
159 static int debugging = DEBUG; variable
320 if (debugging) { st_printk(ST_DEB_MSG, t, fmt, ##a ); }
378 if (debugging) { in st_chk_result()
387 if (!debugging) { /* Abnormal conditions for tape */ in st_chk_result()
432 if (debugging) { in st_chk_result()
659 DEB(if (debugging && retval) in write_behind_check()
1070 if ( DEB( debugging || ) !STp->inited) in check_tape()
2074 if (debugging && STps->eof != ST_NOEOF) in st_read()
2126 if (debugging && STps->eof != ST_NOEOF) in st_read()
[all …]
/linux-4.1.27/fs/jffs2/
DKconfig15 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
19 This controls the amount of debugging messages produced by the JFFS2
21 testing and debugging, it's advisable to set it to one. This will
22 enable a few assertions and will print debugging messages at the
24 is unlikely to be useful - it enables extra debugging in certain
25 areas which at one point needed debugging, but when the bugs were
/linux-4.1.27/net/rxrpc/
DKconfig24 bool "RxRPC dynamic debugging"
27 Say Y here to make runtime controllable debugging messages appear.
/linux-4.1.27/drivers/usb/dwc2/
DKconfig73 Say Y here to enable debugging messages in the DWC2 Driver.
79 Say Y here to enable verbose debugging messages in the DWC2 Driver.
95 Say N here to disable (verbose) debugging messages to be
96 logged for periodic transfers. This allows better debugging of
/linux-4.1.27/lib/
DKconfig.debug68 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
125 debugging info resulting in a larger kernel image.
134 bool "Reduce debugging information"
137 If you say Y here gcc is instructed to generate less debugging
139 need full debugging information (like kgdb or systemtap) won't
140 be happy. But if you merely need debugging information to
171 bool "Provide GDB scripts for kernel debugging"
178 instance. See Documentation/gdb-kernel-debugging.txt for further
261 debugging files into. Enable this option to be able to read and
332 larger and slower, but it gives very useful debugging information
[all …]
DKconfig.kasan13 This is strictly a debugging feature and it requires a gcc version
56 kernel debugging features like kernel address sanitizer.
DKconfig.kmemcheck73 error is detected to help the debugging of a particular problem.
/linux-4.1.27/arch/ia64/hp/sim/boot/
Dbootloader.lds32 /* Stabs debugging sections. */
41 Symbols in the DWARF debugging sections are relative to the beginning
/linux-4.1.27/drivers/net/ethernet/mellanox/mlx4/
DKconfig39 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
43 This option causes debugging code to be compiled into the
/linux-4.1.27/arch/frv/
DKconfig.debug6 bool "Remote GDB kernel debugging"
44 If you are using GDB for remote debugging over a serial port and
/linux-4.1.27/arch/m68k/
DKconfig.debug24 This is useful for kernel debugging when your machine crashes very
33 Enable debugging symbols on kernel build.
/linux-4.1.27/arch/mn10300/
DKconfig.debug30 for kernel debugging, non-intrusive instrumentation and testing.
34 bool "Remote GDB kernel debugging"
68 If you are using GDB for remote debugging over a serial port and
76 This causes debugging messages to be displayed at various points
/linux-4.1.27/Documentation/networking/
Dtlan.txt51 0x01 Turn on general debugging messages.
52 0x02 Turn on receive debugging messages.
53 0x04 Turn on transmit debugging messages.
54 0x08 Turn on list debugging messages.
Dnetif-msg.txt9 The design of the debugging message interface was guided and
Dbatman-adv.txt74 There is a special folder for debugging information:
144 option "B.A.T.M.A.N. debugging".
Dipvs-sysctl.txt89 Higher debugging levels include the messages for lower debugging
/linux-4.1.27/net/sctp/
DKconfig34 kernel's dynamic debugging framework.
45 state in response to incoming packets. It is used for debugging
56 If you say Y, this will enable debugging support for counting the
/linux-4.1.27/arch/x86/
DKconfig.debug14 be used by people debugging the kernel. Note that with PAT support
40 This is useful for kernel debugging when your machine crashes very
52 This is useful for kernel debugging when your machine crashes very
65 This is useful for kernel debugging when your machine crashes very
156 bool "Enable IOMMU debugging"
161 memory and add debugging code. On overflow always panic. And
184 are debugging a buggy device driver that leaks IOMMU mappings.
320 debugging an IMR memory map or are modifying the IMR code and want to
/linux-4.1.27/drivers/pnp/
DKconfig25 bool "PNP debugging messages"
28 Say Y here if you want the PNP layer to be able to produce debugging
/linux-4.1.27/fs/ext4/
DKconfig90 bool "EXT4 debugging support"
93 Enables run-time debugging support for the ext4 filesystem.
95 If you select Y here, then you will be able to turn on debugging
/linux-4.1.27/arch/blackfin/
DKconfig.debug12 explaining what the problem was. This debugging information is
15 debugging but serves no purpose on a production system.
29 bool "Hardware error interrupt debugging"
167 debugging sessions
189 quickly fill up the hardware trace buffer. When debugging crashes,
204 This is useful for kernel debugging when your machine crashes very
212 bool "Enable NMI watchdog to help debugging lockup on SMP"
/linux-4.1.27/net/dccp/
DKconfig37 When compiling DCCP as a module, this debugging output can be toggled
47 state in response to incoming packets. It is used for debugging
/linux-4.1.27/fs/jfs/
DKconfig37 bool "JFS debugging"
41 Y here. This will result in additional debugging messages to be
/linux-4.1.27/arch/alpha/lib/
Dcallback_srm.S98 .long 7 # value is not 1 for link debugging
101 .long 7 # value is not 1 for link debugging
/linux-4.1.27/drivers/net/wireless/ipw2x00/
DKconfig20 for debugging issues and problems.
50 bool "Enable full debugging output in IPW2100 module."
82 driver and for tips for debugging issues and problems.
144 bool "Enable full debugging output in IPW2200 module."
178 bool "Full debugging output for the LIBIPW component"
/linux-4.1.27/Documentation/sound/alsa/
DProcfile.txt9 found in this tree. When you encounter a problem and need debugging,
62 dump). These files would be really helpful for debugging.
112 additionally. This may help the debugging.
149 Shows the AC97 register dump. Useful for debugging.
163 of the given card. This information is very useful for debugging.
DHD-Audio-Models.txt138 test for testing/debugging purpose, almost all controls
147 test for testing/debugging purpose, almost all controls
/linux-4.1.27/fs/ufs/
DKconfig38 bool "UFS debugging"
42 Y here. This will result in _many_ additional debugging messages to be
/linux-4.1.27/net/sunrpc/
DKconfig38 bool "RPC: Enable dprintk debugging"
42 This option enables a sysctl-based debugging interface
/linux-4.1.27/drivers/acpi/apei/
DKconfig54 mainly used for debugging and testing the other parts of
63 if you want to debugging and testing the ERST kernel support
/linux-4.1.27/arch/sparc/
DKconfig.debug10 bool "D-cache flush debugging"
/linux-4.1.27/fs/exofs/
DKconfig10 bool "Enable debugging"
/linux-4.1.27/Documentation/security/
DYama.txt28 builders should be allowed the option to disable this debugging system.
38 between a debugging process and its inferior (crash handlers, etc),
41 against it. Only one such declared debugging process can exists for
/linux-4.1.27/drivers/net/wireless/b43/
DKconfig193 bool "Broadcom 43xx debugging"
196 Broadcom 43xx debugging.
203 Do not enable this, unless you are debugging the driver.
207 Only say Y, if you are debugging a problem in the b43 driver sourcecode.
/linux-4.1.27/drivers/bcma/
DKconfig102 bool "BCMA debugging"
105 This turns on additional debugging messages.
/linux-4.1.27/drivers/isdn/gigaset/
DKconfig65 bool "Gigaset debugging"
67 This enables debugging code in the Gigaset drivers.
/linux-4.1.27/drivers/infiniband/hw/amso1100/
DKconfig9 bool "Verbose debugging output"
/linux-4.1.27/drivers/infiniband/hw/nes/
DKconfig11 bool "Verbose debugging output"
/linux-4.1.27/scripts/ksymoops/
DREADME6 debugging.
/linux-4.1.27/drivers/vlynq/
DKconfig18 Turn on VLYNQ bus debugging.
/linux-4.1.27/fs/xfs/
DKconfig84 are debugging a particular problem.
90 Say Y here to get an XFS build with many debugging features,
95 not useful unless you are debugging a particular problem.
/linux-4.1.27/fs/dlm/
DKconfig11 bool "DLM debugging"
/linux-4.1.27/net/batman-adv/
DKconfig63 bool "B.A.T.M.A.N. debugging"
69 outputting debugging information to the kernel log. The
/linux-4.1.27/fs/ocfs2/
DKconfig66 This option will enlarge your kernel, but it allows debugging of
75 this option for debugging only as it is likely to decrease
/linux-4.1.27/fs/cifs/
DKconfig133 bool "Enable CIFS debugging routines"
137 Enabling this option adds helpful debugging messages to
141 bool "Enable additional CIFS debugging routines"
144 Enabling this option adds a few more debugging routines
148 option can be turned off unless you are debugging
/linux-4.1.27/sound/core/
DKconfig195 You don't need this unless you're debugging ALSA.
206 Say Y here to enable extra-verbose debugging messages.
212 bool "Enable PCM ring buffer overrun/underrun debugging"
216 Say Y to enable the PCM ring buffer overrun/underrun debugging.
/linux-4.1.27/net/rds/
DKconfig25 bool "RDS debugging messages"
/linux-4.1.27/drivers/media/platform/s5p-tv/
DKconfig38 Enables debugging for HDMI driver.
86 Enables debugging for Mixer driver.
/linux-4.1.27/Documentation/arm/
DPorting114 use with the debugging macros in arch/arm/kernel/debug-armv.S.
116 `vio' is the virtual address of the 8MB debugging region.
118 It is expected that the debugging region will be re-initialised
Dmem_alignment16 trap to SIGBUS any code performing unaligned access (good for debugging bad
/linux-4.1.27/drivers/i2c/
DKconfig124 bool "I2C Core debugging messages"
131 bool "I2C Algorithm debugging messages"
139 bool "I2C Bus debugging messages"
/linux-4.1.27/arch/m32r/
DKconfig.debug17 and slower, but it will give very useful debugging information.
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig58 Add a number of spare GPIO entries between each bank for debugging
260 Say Y here if you want verbose debugging from the PM Suspend and
265 bool "SMDK LED suspend/resume debugging"
269 for debugging of the state of the suspend and resume process.
/linux-4.1.27/Documentation/isdn/
DREADME.HiSax351 At this point you can run a 'cat /dev/isdnctrl0' and view debugging messages.
353 At the moment, debugging messages are enabled with the hisaxctrl tool:
359 DebugCmd is 1 for generic debugging
360 11 for layer 1 development debugging
361 13 for layer 3 development debugging
363 where <debugging_flags> is the integer sum of the following debugging
375 0x0080 D-Channel link state debugging
376 0x0100 B-Channel link state debugging
380 0x1000 D-Channel l1 state debugging
381 0x2000 B-Channel l1 state debugging
[all …]
DREADME.gigaset336 Building the driver with the "Gigaset debugging" kernel configuration
338 information useful for debugging.
340 You can control the amount of debugging information the driver produces by
343 switches off debugging output completely,
345 enables a reasonable set of debugging output messages. These values are
346 bit patterns where every bit controls a certain type of debugging output.
354 Generated debugging information can be found
/linux-4.1.27/Documentation/input/
Dappletouch.txt74 You can activate debugging using the 'debug' module parameter. A value of 0
75 deactivates any debugging, 1 activates tracing of invalid samples, 2 activates
Dedt-ft5x06.txt31 For debugging purposes the driver provides a few files in the debug
Delantech.txt102 Turn different levels of debugging ON or OFF.
104 By echoing "0" to this file all debugging will be turned OFF.
106 Currently a value of "1" will turn on some basic debugging and a value of
107 "2" will turn on packet debugging. For hardware version 1 the default is
110 Turning packet debugging on will make the driver dump every packet
/linux-4.1.27/arch/tile/
DKconfig.debug11 This is useful for kernel debugging when your machine crashes very
/linux-4.1.27/arch/cris/
DKconfig213 Disable serial-port debugging.
222 Choose a serial port for kernel debugging. NOTE: This port should
229 Use serial port 0 for kernel debugging.
234 Use serial port 1 for kernel debugging.
239 Use serial port 2 for kernel debugging.
244 Use serial port 3 for kernel debugging.
DKconfig.debug38 delivering a terminating SIGSEGV to allow debugging with gdb.
/linux-4.1.27/Documentation/s390/
D00-INDEX16 - hints for debugging on s390 systems.
DDebugging390.txt28 Compiling programs for debugging on Linux for s/390 & z/Architecture
50 kernel usage only, used for memory management, interrupt control, debugging
86 PER is used to facilitate debugging e.g. single stepping.
110 ( useful info for debugging under VM ).
717 Compiling programs for debugging on Linux for s/390 & z/Architecture
719 -gdwarf-2 now works it should be considered the default debugging
720 format for s/390 & z/Architecture as it is more reliable for debugging
721 shared libraries, normal -g debugging works much better now
731 ( not advisable for shipment ) but it is an aid to the debugging process.
733 This aids debugging because the compiler will copy parameters passed in
[all …]
/linux-4.1.27/drivers/infiniband/hw/cxgb3/
DKconfig21 bool "Verbose debugging output"
/linux-4.1.27/Documentation/sysctl/
Dsunrpc.txt16 The files in there are used to control the debugging flags:
/linux-4.1.27/fs/btrfs/
DKconfig75 bool "Btrfs debugging support"
78 Enable run-time debugging support for the btrfs filesystem. This may
/linux-4.1.27/drivers/usb/gadget/
DKconfig51 Many controller and gadget drivers will print some debugging
55 debugging such a driver. Many drivers will emit so many
62 bool "Verbose debugging Messages (DEVELOPMENT)"
65 Many controller and gadget drivers will print verbose debugging
69 debugging such a driver. Many drivers will emit so many
80 debugging information in files such as /proc/driver/udc
91 debugging information in files under /sys/kernel/debug/.
/linux-4.1.27/kernel/power/
DKconfig150 This option enables various debugging support in the Power Management
151 code. This is helpful when debugging and reporting PM bugs, like
155 bool "Extra PM attributes in sysfs for low-level debugging/testing"
160 developer interested in debugging/testing Power Management, say "no".
218 To use this debugging feature you should attempt to suspend the
/linux-4.1.27/drivers/block/zram/
DKconfig33 This option adds additional debugging code to the compressed
/linux-4.1.27/drivers/usb/chipidea/
DKconfig42 Say Y here to enable debugging output of the ChipIdea driver.
/linux-4.1.27/arch/sh/
DKconfig.debug56 the faulting instruction as a debugging aid. As this does grow
59 Those looking for more verbose debugging output should say Y.
/linux-4.1.27/drivers/scsi/aic7xxx/
DKconfig.aic79xx64 Compile in aic79xx debugging code that can be useful in diagnosing
68 int "Debug code enable mask (16383 for all debugging)"
DKconfig.aic7xxx69 Compile in aic7xxx debugging code that can be useful in diagnosing
73 int "Debug code enable mask (2047 for all debugging)"
/linux-4.1.27/drivers/net/ethernet/microchip/
DKconfig35 Enable the verify after the buffer write useful for debugging purpose.
/linux-4.1.27/drivers/gpu/drm/tegra/
DKconfig34 Say yes here to enable debugging support.
/linux-4.1.27/drivers/pcmcia/
DKconfig214 bool "Enable debugging"
217 Say Y here to enable debugging for the SoC PCMCIA layer.
218 You will need to choose the debugging level either via the
228 In all the above examples, N is the debugging verbosity
/linux-4.1.27/Documentation/filesystems/
Dafs.txt48 Additionally, the following can be turned on to aid debugging:
50 CONFIG_AF_RXRPC_DEBUG - Permit AF_RXRPC debugging to be enabled
51 CONFIG_AFS_DEBUG - Permit AFS debugging to be enabled
53 They permit the debugging messages to be turned on dynamically by manipulating
Dbtrfs.txt59 These debugging options control the behavior of the integrity checking
113 Disable/enable debugging option to be more verbose in some ENOSPC conditions.
270 * btrfs-image: dump filesystem metadata for debugging
Decryptfs.txt71 levels unless you are doing so for the sole purpose of debugging or
Dudf.txt54 The remaining are for debugging and disaster recovery:
Dbefs.txt97 debug The driver will output debugging information to the syslog.
/linux-4.1.27/fs/befs/
DKconfig26 debugging output from the driver.
/linux-4.1.27/drivers/net/wireless/libertas/
DKconfig36 bool "Enable full debugging output in the Libertas module."
/linux-4.1.27/arch/x86/boot/
Dpmjump.S59 # a valid stack if some debugging hack wants to use it.
/linux-4.1.27/net/ceph/
DKconfig25 line to aid debugging. This increases kernel size and slows
/linux-4.1.27/arch/um/
DKconfig.debug37 This is useful for kernel debugging when your machine crashes very
/linux-4.1.27/drivers/net/wireless/ath/ath10k/
DKconfig18 bool "Atheros ath10k debugging"
/linux-4.1.27/mm/
DKconfig.debug5 could be used for debugging features that need to insert extra
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-kernel-boot_params7 platform to userspace for kexec and debugging purpose.
Dsysfs-firmware-memmap18 kexec. Also, the raw memory map is useful for debugging. For
Dsysfs-class-mic.txt137 debugging purpose and early kernel boot messages, the user can
151 debugging purpose and early kernel boot messages, the user can
Ddebugfs-driver-genwqe4 Description: DDCB queue dump used for debugging queueing problems.
Dsysfs-fs-ext490 debugging use only, and should be 0 on production
/linux-4.1.27/drivers/pps/clients/
DKconfig12 If you say yes here you get support for a PPS debugging client
/linux-4.1.27/drivers/ssb/
DKconfig96 bool "SSB debugging"
99 This turns on additional runtime checks and debugging
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-tape.1995-2002176 * debugging output only)
177 * AJN-2) Added more debugging output, and
182 * "debug_level" determines amount of debugging output;
184 * 0 : almost no debugging output
254 * Cosmetic fixes to miscellaneous debugging output messages.
/linux-4.1.27/net/wireless/
DKconfig65 bool "cfg80211 regulatory debugging"
212 bool "lib80211 debugging messages"
216 You can enable this if you want verbose debugging messages
/linux-4.1.27/drivers/pps/
DKconfig26 bool "PPS debugging messages"
/linux-4.1.27/drivers/net/wireless/ath/wil6210/
DKconfig39 option if you are interested in debugging the driver.
/linux-4.1.27/arch/mn10300/kernel/
Dgdb-io-ttysm-low.S71 # debugging interrupt - enter the GDB stub proper
Dmn10300-serial-low.S43 # debugging interrupts
/linux-4.1.27/drivers/dma/
DKconfig17 bool "DMA Engine debugging"
21 say N here. This enables DMA engine core and driver debugging.
24 bool "DMA Engine verbose debugging"
28 say N here. This enables deeper (more verbose) debugging of
480 Simple DMA test client. Say N unless you're debugging a
/linux-4.1.27/drivers/media/usb/pwc/
DKconfig36 Say Y here in order to have the pwc driver generate verbose debugging
/linux-4.1.27/drivers/net/wireless/ath/carl9170/
DKconfig28 Say Y, unless you need the LEDs for firmware debugging.
/linux-4.1.27/arch/powerpc/platforms/embedded6xx/
Dusbgecko_udbg.c284 #error Invalid platform for USB Gecko based early debugging. in ug_early_grab_io_addr()
/linux-4.1.27/drivers/net/ethernet/marvell/
DKconfig102 This option adds the ability to dump driver state for debugging.
137 This option adds the ability to dump driver state for debugging.
/linux-4.1.27/drivers/pnp/pnpbios/
DKconfig40 Unless you are debugging or have other specific reasons, it is
/linux-4.1.27/drivers/net/wireless/ath/
DKconfig23 bool "Atheros wireless debugging"
/linux-4.1.27/drivers/media/v4l2-core/
DKconfig15 Say Y here to enable advanced debugging functionality on some
/linux-4.1.27/drivers/media/usb/pvrusb2/
DKconfig62 on debugging the driver or performing a manual firmware
/linux-4.1.27/arch/ia64/
DKconfig.debug39 can select this option to disable the VHPT for debugging. If you're
/linux-4.1.27/Documentation/fmc/
Dparameters.txt4 The core driver receives two module parameters, meant to help debugging
/linux-4.1.27/drivers/net/wireless/iwlwifi/
DKconfig103 bool "Enable full debugging output in the iwlwifi driver"
138 Enable use of experimental ucode for testing and debugging.
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Didle.fuc55 // count IDLE invocations for debugging purposes
/linux-4.1.27/drivers/firmware/efi/
DKconfig46 mapping the 2nd kernel, but can also be used for debugging purposes.
/linux-4.1.27/drivers/net/wireless/ath/ath6kl/
DKconfig35 bool "Atheros ath6kl debugging"
/linux-4.1.27/drivers/net/wireless/ath/ath9k/
DKconfig60 bool "Atheros ath9k debugging"
175 bool "Atheros ath9k_htc debugging"
/linux-4.1.27/drivers/input/
DKconfig152 tristate "Event debugging"
156 the system log. While this is useful for debugging, it's also
/linux-4.1.27/arch/m68k/q40/
DREADME65 Serial console works and can also be used for debugging, see loader_txt
135 - AT codes as displayed by the q40 debugging ROM
/linux-4.1.27/Documentation/timers/
Dtimer_stats.txt4 timer_stats is a debugging facility to make the timer (ab)usage in a Linux
/linux-4.1.27/Documentation/scsi/
Dadvansys.txt73 2. ADVANSYS_DEBUG - Enable driver debugging (Def: Disabled)
77 very useful for debugging the driver, but it will add to the size
81 The amount of debugging output can be controlled with the global
Daic79xx.txt229 Definition: Enables various levels of debugging information
230 The bit definitions for the debugging mask can
233 Possible Values: 0x0000 = no debugging, 0xffff = full debugging
Daic7xxx.txt204 Definition: Enables various levels of debugging information
205 Possible Values: 0x0000 = no debugging, 0xffff = full debugging
/linux-4.1.27/Documentation/filesystems/caching/
Dcachefiles.txt113 Specify a numeric bitmask to control debugging in the kernel module.
142 Increase the debugging level. This can be specified multiple times and
484 debugging enabled by adjusting the value in:
488 This is a bitmask of debugging streams to enable:
501 will turn on all function entry debugging.
Dfscache.txt353 OBJECT Object debugging ID (appears as OBJ%x in some debug messages)
417 debugging enabled by adjusting the value in:
421 This is a bitmask of debugging streams to enable:
443 will turn on all function entry debugging.
/linux-4.1.27/
DREADME247 "experimental", or "debugging" features.
346 or similar kernel debugging information on your screen or in your
349 help debugging the problem. The text above the dump is also
361 - In debugging dumps like the above, it helps enormously if you can
378 debugging messages will not necessarily match exactly with the
/linux-4.1.27/Documentation/gpio/
Dsysfs.txt8 present on production systems without debugging support.
143 This explicit exporting can help with debugging (by making some kinds
/linux-4.1.27/Documentation/locking/
Dmutex-design.txt103 In addition, the mutex debugging code also implements a number of other
104 features that make lock debugging easier and faster:
/linux-4.1.27/Documentation/video4linux/
Dcafe_ccic7 well, but that is a debugging aid which will be removed shortly). VGA and
/linux-4.1.27/drivers/net/wireless/brcm80211/
DKconfig77 Tracing can be enabled at runtime to aid in debugging wireless
/linux-4.1.27/drivers/usb/dwc3/
DKconfig105 Say Y here to enable debugging messages on DWC3 Driver.
/linux-4.1.27/Documentation/usb/
Diuu_phoenix.txt66 - debug will produce a lot of debugging messages...
/linux-4.1.27/drivers/net/wireless/b43legacy/
DKconfig53 bool "Broadcom 43xx-legacy debugging"
/linux-4.1.27/Documentation/misc-devices/
Dc2port.txt41 banging) designed to enable in-system programming, debugging, and
/linux-4.1.27/net/
DKconfig162 bool "Network packet filtering debugging"
166 debugging the netfilter code.
318 state in response to incoming packets. It is used for debugging
/linux-4.1.27/drivers/net/wireless/iwlegacy/
DKconfig67 bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers"
/linux-4.1.27/drivers/usb/core/
DKconfig10 usually used by distro vendors to help with debugging and to
/linux-4.1.27/drivers/tty/hvc/
DKconfig85 This is meant to be used during HW bring up or debugging when
/linux-4.1.27/fs/reiserfs/
DKconfig39 out in checking for consistency when debugging without fear of its
/linux-4.1.27/arch/arm64/
DKconfig.debug28 be used by people debugging the kernel.
/linux-4.1.27/Documentation/acpi/
Dmethod-customizing.txt11 or just for debugging purposes.
/linux-4.1.27/Documentation/dvb/
Dbt8xx.txt45 Useful parameters for verbosity level and debugging the dst module:
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME61 reproduce your problems. This makes debugging very difficult for me.
/linux-4.1.27/drivers/net/wireless/rtlwifi/
DKconfig135 To use the module option that sets the dynamic-debugging level for,
/linux-4.1.27/drivers/w1/slaves/
DKconfig33 This is slower but useful when debugging chips and/or busses.
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt94 3) If any debugging is placed in the resume path, then it must have the
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dentry.S511 bmi _ugdb_handle_exception ; Go to user mode debugging.
513 ba kgdb_handle_exception ; Go to kernel debugging.
/linux-4.1.27/arch/arc/
DKconfig378 bool "ARC debugging"
391 but not slower, and it will give very useful debugging information.
/linux-4.1.27/arch/cris/arch-v32/
DKconfig107 Choose a serial port for kernel debugging. NOTE: This port should
115 Use serial port 4 for kernel debugging.

12