Lines Matching +full:no +full:- +full:dump +full:- +full:oops
6 - arch/s390/kernel/debug.c
7 - arch/s390/include/asm/debug.h
10 ------------
24 -------
31 which are written by event- and exception-calls.
33 An event-call writes the specified debug entry to the active debug
39 An exception-call writes the specified debug entry to the log and
48 There are four versions for the event- and exception-calls: One for
50 and one for sprintf-like formatted strings.
54 - Timestamp
55 - Cpu-Number of calling task
56 - Level of debug entry (0...6)
57 - Return Address to caller
58 - Flag, if entry is an exception or not
61 the debugfs-filesystem. Under the toplevel directory "``s390dbf``" there is
80 The actual debug level can be changed with the help of the debugfs-filesystem
83 by using "-" on the ``level`` debugfs file.
87 > echo "-" > /sys/kernel/debug/s390dbf/dasd/level
98 The second trigger which stops the debug feature is a kernel oops.
100 happened before the oops. After an oops you can reactivate the debug feature
110 ------------------
112 .. kernel-doc:: arch/s390/kernel/debug.c
113 .. kernel-doc:: arch/s390/include/asm/debug.h
116 -----------------
118 .. code-block:: c
125 --------
127 .. code-block:: c
130 * hex_ascii-view Example
160 .. code-block:: c
163 * sprintf-view Example
194 -----------------
196 debugfs-files:
202 > cat /sys/kernel/debug/s390dbf/dasd/hex_ascii | sort -k2,2 -s
203 00 00974733272:680099 2 - 02 0006ad7e 07 ea 4a 90 | ....
204 00 00974733272:682210 2 - 02 0006ade6 46 52 45 45 | FREE
205 00 00974733272:682213 2 - 02 0006adf6 07 ea 4a 90 | ....
207 01 00974733272:682284 2 - 02 0006ab16 45 43 4b 44 | ECKD
208 01 00974733272:682287 2 - 02 0006ab28 00 00 00 04 | ....
209 01 00974733272:682289 2 - 02 0006ab3e 00 00 00 20 | ...
210 01 00974733272:682297 2 - 02 0006ad7e 07 ea 4a 90 | ....
211 01 00974733272:684384 2 - 00 0006ade6 46 52 45 45 | FREE
212 01 00974733272:684388 2 - 00 0006adf6 07 ea 4a 90 | ....
217 ------------------------
229 --------------------
231 area (0...n) to the debugfs file "flush". When using "-" all debug areas
242 > echo "-" > /sys/kernel/debug/s390dbf/dasd/flush
245 ------------------------------------
257 --------------------------
269 ----------------
270 The ``crash`` tool since v5.1.0 has a built-in command
273 to investigate the debug logs on a live system and with a memory dump after
277 ------------------------
281 It is possible to find the anchor of the debug-logs through
283 to follow the correct pointers of the data-structures defined
284 in debug.h and find the debug-areas in memory.
286 a global variable with the pointer to the debug-logs. Following
296 ----------------
315 get an OOPS when inspecting the debug feature, because then the debug feature
320 than the sprintf-event and -exception functions.
324 - Number of area
325 - Timestamp (formatted as seconds and microseconds since 00:00:00 Coordinated
327 - level of debug entry
328 - Exception flag (* = Exception)
329 - Cpu-Number of calling task
330 - Return Address to caller
331 - data field
337 --------------------------------------------------------------------------
338 00 00964419409:440690 1 - 00 88023fe
342 --------------
347 .. code-block:: c
360 .. code-block:: c
405 00 00964419409:440761 2 - 00 88023ec
412 .. code-block:: c
434 if (id->buf_size >= 4) {
436 if (msg_nr < sizeof(messages) / sizeof(char*) - 1)
446 NULL, /* no prolog */
449 NULL, /* no input function */
450 NULL /* no private data */
456 .. code-block:: c
469 00 00964419734:611402 1 - 00 88042ca This error...........
470 00 00964419734:611405 1 - 00 88042ca That error...........
471 00 00964419734:611408 1 - 00 88042ca Problem..............
472 00 00964419734:611411 1 - 00 88042ca Something went wrong.
473 00 00964419734:611414 1 - 00 88042ca Everything ok........
474 00 00964419734:611417 1 - 00 88042ca data: 00000005
475 00 00964419734:611419 1 - 00 88042ca data: 00000006
476 00 00964419734:611422 1 - 00 88042ca data: 00000007
477 00 00964419734:611425 1 - 00 88042ca data: 00000008
478 00 00964419734:611428 1 - 00 88042ca data: 00000009