Searched full:debug (Results 1 – 25 of 307) sorted by relevance
12345678910>>...13
| /Documentation/s390/ |
| D | s390dbf.rst | 2 S390 Debug Feature
6 - arch/s390/kernel/debug.c
7 - arch/s390/include/asm/debug.h
11 The goal of this feature is to provide a kernel debug logging API
13 (e.g. device drivers) can have one separate debug log.
14 One purpose of this is to inspect the debug logs after a production system crash
18 it is possible to look at the debug logs on a live system via the Linux
21 The debug feature may also very useful for kernel and driver development.
25 Kernel components (e.g. device drivers) can register themselves at the debug
28 debug log for the caller. For each debug log exists a number of debug areas
[all …]
|
| D | common_io.rst | 13 Enable logging of debug information in case of ccw device timeouts.
121 * /sys/kernel/debug/s390dbf/cio_*/ (S/390 debug feature)
123 Some views generated by the debug feature to hold various debug outputs.
125 - /sys/kernel/debug/s390dbf/cio_crw/sprintf
129 - /sys/kernel/debug/s390dbf/cio_msg/sprintf
130 Various debug messages from the common I/O-layer.
132 - /sys/kernel/debug/s390dbf/cio_trace/hex_ascii
138 /sys/kernel/debug/s390dbf/cio_*/level a number between 0 and 6; see the
139 documentation on the S/390 debug feature (Documentation/s390/s390dbf.rst)
|
| /Documentation/trace/ |
| D | coresight-cpu-debug.rst | 2 Coresight CPU Debug Module
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
12 (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate
13 debug module and it is mainly used for two modes: self-hosted debug and
14 external debug. Usually the external debug mode is well known as the external
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
22 debug mechanism, Linux kernel can access these related registers from mmio
36 - At the time this documentation was written, the debug driver mainly relies on
[all …]
|
| D | events.rst | 27 /sys/kernel/debug/tracing/available_events.
30 to /sys/kernel/debug/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
39 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
43 # echo > /sys/kernel/debug/tracing/set_event
47 # echo *:* > /sys/kernel/debug/tracing/set_event
56 # echo 'irq:*' > /sys/kernel/debug/tracing/set_event
61 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
66 # echo 1 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
70 # echo 0 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
[all …]
|
| D | mmiotrace.rst | 38 $ mount -t debugfs debugfs /sys/kernel/debug
39 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
40 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
42 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker
43 $ echo nop > /sys/kernel/debug/tracing/current_tracer
50 Make sure debugfs is mounted to /sys/kernel/debug.
53 $ mount -t debugfs debugfs /sys/kernel/debug
59 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
63 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
71 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cpu-debug.txt | 1 * CoreSight CPU Debug Component:
3 CoreSight CPU debug component are compliant with the ARMv8 architecture
4 reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug'. The
5 external debug module is mainly used for two modes: self-hosted debug and
6 external debug, and it can be accessed from mmio region from Coresight
7 and eventually the debug module connects with CPU for debugging. And the
8 debug module provides sample-based profiling extension, which can be used
10 usually every CPU has one dedicated debug module to be connected.
14 - compatible : should be "arm,coresight-cpu-debug"; supplemented with
25 mandatory. The interface between the debug logic and the
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 2 USB3 debug port
11 This is a HOWTO for using the USB3 debug port on x86 systems.
14 debug port, you need to::
16 1) check whether any USB3 debug port is available in
24 The xHCI debug capability (DbC) is an optional but standalone
28 When DbC is initialized and enabled, it will present a debug
29 device through the debug port (normally the first USB3
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
33 (the system under debugging) and a debug host.
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-zip | 1 What: /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
4 Description: Dump of compression cores related debug registers.
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
10 Description: Dump of decompression cores related debug registers.
13 What: /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
16 Description: Compression/decompression core debug registers read clear
22 What: /sys/kernel/debug/hisi_zip/<bdf>/current_qm
29 What: /sys/kernel/debug/hisi_zip/<bdf>/qm/qm_regs
32 Description: Dump of QM related debug registers.
34 has one debug register.
[all …]
|
| D | debugfs-driver-habanalabs | 1 What: /sys/kernel/debug/habanalabs/hl<n>/addr
11 What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
18 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
25 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
32 What: /sys/kernel/debug/habanalabs/hl<n>/data32
46 What: /sys/kernel/debug/habanalabs/hl<n>/device
54 What: /sys/kernel/debug/habanalabs/hl<n>/engines
61 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_addr
68 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_bus
75 What: /sys/kernel/debug/habanalabs/hl<n>/i2c_data
[all …]
|
| D | debugfs-driver-genwqe | 1 What: /sys/kernel/debug/genwqe/genwqe<n>_card/ddcb_info
6 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_regs
12 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid0
18 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid1
24 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid2
30 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_regs
37 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid0
43 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid1
49 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid2
55 What: /sys/kernel/debug/genwqe/genwqe<n>_card/info
[all …]
|
| D | sysfs-driver-st | 6 This file allows you to turn debug output from the st driver
8 Note that debug output requires that the module be compiled
9 with the #define DEBUG set to a non-zero value (this is the
10 default). If DEBUG is set to 0 then this file will not
11 appear in sysfs as its presence is conditional upon debug
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 6 USB3 controllers) are often implemented with the Debug
7 Capability (DbC). It can present a debug device which
10 serial link for debug purpose.
12 The DbC debug device shares a root port with xHCI host.
14 to the Debug Capability. Otherwise, it will be assigned
|
| D | ppc-memtrace | 1 What: /sys/kernel/debug/powerpc/memtrace
9 What: /sys/kernel/debug/powerpc/memtrace/enable
22 What: /sys/kernel/debug/powerpc/memtrace/<node-id>
29 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/size
35 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/start
41 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/trace
|
| D | debugfs-cros-ec | 1 What: /sys/kernel/debug/<cros-ec-device>/console_log
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
22 This file provides the port role, muxes and power debug
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
36 What: /sys/kernel/debug/<cros-ec-device>/last_resume_result
|
| /Documentation/admin-guide/wimax/ |
| D | wimax.rst | 44 files will appear in /sys/kernel/debug/wimax:wmxX can tweak for
47 2.1. Obtaining debug information: debugfs entries
50 The WiMAX stack is compiled, by default, with debug messages that can
54 debug settings.
60 2.1.1. Increasing debug output
63 The files named *dl_* indicate knobs for controlling the debug output
66 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
67 /sys/kernel/debug/wimax:wmx0/wimax_dl_stack
68 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_rfkill
69 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_reset
[all …]
|
| D | i2400m.rst | 162 5.2. Debug operations: debugfs entries
166 debug settings. There are three main container directories where
170 * /sys/kernel/debug/wimax:DEVNAME/ for the generic WiMAX stack
172 * /sys/kernel/debug/wimax:DEVNAME/i2400m for the i2400m generic
174 * /sys/kernel/debug/wimax:DEVNAME/i2400m-usb (or -sdio) for the
178 /sys/kernel/debug, those paths will change.
180 5.2.1. Increasing debug output
183 The files named *dl_* indicate knobs for controlling the debug output
186 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
187 /sys/kernel/debug/wimax:wmx0/i2400m-usb/dl_tx
[all …]
|
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 32 debugfs entries under /sys/kernel/debug/mmc0/fail_mmc_request
38 under /sys/kernel/debug/fail_function. No boot option supported.
43 debugfs entries under /sys/kernel/debug/nvme*/fault_inject. The default
57 - /sys/kernel/debug/fail*/probability:
65 /sys/kernel/debug/fail*/interval for such testcases.
67 - /sys/kernel/debug/fail*/interval:
75 - /sys/kernel/debug/fail*/times:
80 - /sys/kernel/debug/fail*/space:
86 - /sys/kernel/debug/fail*/verbose
93 to debug the problems revealed by fault injection.
[all …]
|
| D | notifier-error-inject.rst | 18 /sys/kernel/debug/notifier-error-inject/pm/actions/<notifier event>/error
28 # cd /sys/kernel/debug/notifier-error-inject/pm/
37 /sys/kernel/debug/notifier-error-inject/memory/actions/<notifier event>/error
46 # cd /sys/kernel/debug/notifier-error-inject/memory
55 /sys/kernel/debug/notifier-error-inject/pSeries-reconfig/actions/<notifier event>/error
68 /sys/kernel/debug/notifier-error-inject/netdev/actions/<notifier event>/error
84 # cd /sys/kernel/debug/notifier-error-inject/netdev
|
| /Documentation/admin-guide/ |
| D | btmrvl.rst | 10 Path: /debug/btmrvl/config/
27 echo 0xff80 > /debug/btmrvl/config/gpiogap
28 echo 1 > /debug/btmrvl/config/hscfgcmd
31 echo 0x03ff > /debug/btmrvl/config/gpiogap
32 echo 1 > /debug/btmrvl/config/hscfgcmd
45 echo 1 > /debug/btmrvl/config/psmode
46 echo 1 > /debug/btmrvl/config/pscmd
49 echo 0 > /debug/btmrvl/config/psmode
50 echo 1 > /debug/btmrvl/config/pscmd
64 echo 1 > /debug/btmrvl/config/hsmode
[all …]
|
| /Documentation/x86/ |
| D | earlyprintk.rst | 8 USB2 Debug port key and a debug cable, on x86 systems.
10 You need two computers, the 'USB debug key' special gadget and
13 [host/target] <-------> [USB debug key] <-------> [client/console]
18 a) Host/target system needs to have USB debug port capability.
20 You can check this capability by looking at a 'Debug port' bit in
35 Capabilities: [58] Debug port: BAR=1 offset=00a0
42 If your system does not list a debug port capability then you probably
43 won't be able to use the USB debug key.
45 b) You also need a NetChip USB debug cable/key:
55 debug port on the "host/target" system. You cannot use a USB hub in
[all …]
|
| /Documentation/networking/ |
| D | netif-msg.txt | 15 integer variable that controls the debug message level. The message
33 were consistently renamed to "debug" and allowed to be set as a module
47 Retaining the per-driver integer variable "debug" as a module
52 1 << debug
54 debug < 0 ? 0 : 1 << min(sizeof(int)-1, debug)
57 if (debug > 1)
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dcsr.txt | 2 Debug Control and Status Register (DCSR) Binding
11 Debug Control and Status Register Memory Map
17 debug blocks defined within this memory space.
80 two interrupt signals based on debug event sources within the SoC.
166 CoreNet Debug Controller
169 the CoreNet Debug controller.
184 The CoreNet Debug controller occupies two regions in the DCSR space
187 The first register range describes the CoreNet Debug Controller
190 The second register range describes the CoreNet Debug Controller
191 functionalty to trigger event notifications and debug traces.
[all …]
|
| /Documentation/filesystems/ |
| D | 9p.txt | 81 debug=n specifies debug level. The debug level is a bitmask.
83 0x02 = developer debug (DEBUG_CURRENT)
86 0x10 = display Marshalling debug
87 0x20 = display RPC debug
88 0x40 = display transport debug
89 0x80 = display allocation debug
90 0x100 = display protocol message debug
91 0x200 = display Fid debug
92 0x400 = display packet debug
93 0x800 = display fscache tracing debug
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 8 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
21 # mount -t debugfs nodev /sys/kernel/debug/
25 # cat /sys/kernel/debug/kmemleak
29 # echo scan > /sys/kernel/debug/kmemleak
33 # echo clear > /sys/kernel/debug/kmemleak
35 New leaks will then come up upon reading ``/sys/kernel/debug/kmemleak``
43 ``/sys/kernel/debug/kmemleak`` file. The following parameters are supported:
110 /sys/kernel/debug/kmemleak
121 Upon initial bootup your /sys/kernel/debug/kmemleak output page may be
125 /sys/kernel/debug/kmemleak output. By issuing a 'scan' after a 'clear'
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 4 ACPI Debug Output
7 The ACPI CA, the Linux ACPI core, and some ACPI drivers can generate debug
13 ACPI debug output is globally enabled by CONFIG_ACPI_DEBUG. If this config
14 option is turned off, the debug messages are not even built into the
24 the debug messages.
132 Enable all AML "Debug" output (stores to the Debug object while interpreting
137 Enable PCI and PCI interrupt routing debug messages::
|
12345678910>>...13