diff options
Diffstat (limited to 'Documentation/s390/s390dbf.txt')
| -rw-r--r-- | Documentation/s390/s390dbf.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/s390/s390dbf.txt b/Documentation/s390/s390dbf.txt index 000230cd26db..0eb7c58916de 100644 --- a/Documentation/s390/s390dbf.txt +++ b/Documentation/s390/s390dbf.txt | |||
| @@ -36,7 +36,7 @@ switches to the next debug area. This is done in order to be sure | |||
| 36 | that the records which describe the origin of the exception are not | 36 | that the records which describe the origin of the exception are not |
| 37 | overwritten when a wrap around for the current area occurs. | 37 | overwritten when a wrap around for the current area occurs. |
| 38 | 38 | ||
| 39 | The debug areas itselve are also ordered in form of a ring buffer. | 39 | The debug areas themselves are also ordered in form of a ring buffer. |
| 40 | When an exception is thrown in the last debug area, the following debug | 40 | When an exception is thrown in the last debug area, the following debug |
| 41 | entries are then written again in the very first area. | 41 | entries are then written again in the very first area. |
| 42 | 42 | ||
| @@ -55,7 +55,7 @@ The debug logs can be inspected in a live system through entries in | |||
| 55 | the debugfs-filesystem. Under the toplevel directory "s390dbf" there is | 55 | the debugfs-filesystem. Under the toplevel directory "s390dbf" there is |
| 56 | a directory for each registered component, which is named like the | 56 | a directory for each registered component, which is named like the |
| 57 | corresponding component. The debugfs normally should be mounted to | 57 | corresponding component. The debugfs normally should be mounted to |
| 58 | /sys/kernel/debug therefore the debug feature can be accessed unter | 58 | /sys/kernel/debug therefore the debug feature can be accessed under |
| 59 | /sys/kernel/debug/s390dbf. | 59 | /sys/kernel/debug/s390dbf. |
| 60 | 60 | ||
| 61 | The content of the directories are files which represent different views | 61 | The content of the directories are files which represent different views |
| @@ -87,11 +87,11 @@ There are currently 2 possible triggers, which stop the debug feature | |||
| 87 | globally. The first possibility is to use the "debug_active" sysctl. If | 87 | globally. The first possibility is to use the "debug_active" sysctl. If |
| 88 | set to 1 the debug feature is running. If "debug_active" is set to 0 the | 88 | set to 1 the debug feature is running. If "debug_active" is set to 0 the |
| 89 | debug feature is turned off. | 89 | debug feature is turned off. |
| 90 | The second trigger which stops the debug feature is an kernel oops. | 90 | The second trigger which stops the debug feature is a kernel oops. |
| 91 | That prevents the debug feature from overwriting debug information that | 91 | That prevents the debug feature from overwriting debug information that |
| 92 | happened before the oops. After an oops you can reactivate the debug feature | 92 | happened before the oops. After an oops you can reactivate the debug feature |
| 93 | by piping 1 to /proc/sys/s390dbf/debug_active. Nevertheless, its not | 93 | by piping 1 to /proc/sys/s390dbf/debug_active. Nevertheless, its not |
| 94 | suggested to use an oopsed kernel in an production environment. | 94 | suggested to use an oopsed kernel in a production environment. |
| 95 | If you want to disallow the deactivation of the debug feature, you can use | 95 | If you want to disallow the deactivation of the debug feature, you can use |
| 96 | the "debug_stoppable" sysctl. If you set "debug_stoppable" to 0 the debug | 96 | the "debug_stoppable" sysctl. If you set "debug_stoppable" to 0 the debug |
| 97 | feature cannot be stopped. If the debug feature is already stopped, it | 97 | feature cannot be stopped. If the debug feature is already stopped, it |