Searched full:oops (Results 1 – 25 of 68) sorted by relevance
123
| /Documentation/admin-guide/ |
| D | pstore-blk.rst | 3 pstore block oops/panic logger
9 pstore block (pstore/blk) is an oops/panic logger that writes its logs to a
78 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
79 It's optional if you do not care about the oops/panic log.
81 There are multiple chunks for oops/panic front-end depending on the remaining
84 pstore/blk will log to oops/panic chunks one by one, and always overwrite the
93 Unlike oops/panic front-end, there is only one chunk for pmsg front-end.
116 Similar to oops front-end, there are multiple chunks for ftrace front-end
166 Block device is large enough for uncompressed oops data. Actually we do not
168 the first line of oops/panic data. For example::
[all …]
|
| D | bug-hunting.rst | 42 the issue, it may also contain the word **Oops**, as on this one::
47 Oops: 0002 [#1] PREEMPT SMP
50 Despite being an **Oops** or some other sort of stack trace, the offended
52 we'll refer to "Oops" for all kinds of stack traces that need to be analyzed.
66 Where is the Oops message is located?
69 Normally the Oops text is read from the kernel buffers by klogd and
112 number of the OOPS from the ``vmlinux`` file.
120 EIP value from the OOPS::
130 offset from the OOPS::
221 .byte .... /* bytes from Code: part of OOPS dump */
[all …]
|
| D | ramoops.rst | 1 Ramoops oops/panic logger
11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
132 reserve_mem=2M:4096:oops ramoops.mem_name=oops
|
| D | tainted-kernels.rst | 16 ('kernel oops') or a non-recoverable error ('kernel panic') and writes debug
21 Tainted flag in bugs, oops or panics messages
29 Oops: 0002 [#1] SMP PTI
92 7 _/D 128 kernel died recently, i.e. there was an OOPS or BUG
158 7) ``D`` if the kernel has died recently, i.e. there was an OOPS or BUG.
|
| D | reporting-issues.rst | 138 * If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
150 like the output/screenshot of an Oops or the output from ``lspci``. Once
406 fatal error where the kernel stop itself) with a 'Oops' (a recoverable error),
498 problem (a 'kernel bug'), a recoverable error (a 'kernel Oops') or a
509 1. A recoverable error (a 'kernel Oops') occurred and the kernel tainted
514 Oops: 0000 [#1] SMP
516 That's the first Oops since boot-up, as the '#1' between the brackets shows.
517 Every Oops and any other problem that happens after that point might be a
518 follow-up problem to that first Oops, even if both look totally unrelated.
519 Rule this out by getting rid of the cause for the first Oops and reproducing
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 7 title: Ramoops oops/panic logger
10 ramoops provides persistent RAM storage for oops and panics, so they can be
19 Any remaining space will be used for a circular buffer of oops and panic
95 no-dump-oops:
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | bug-hunting.rst | 49 严重性，它还可能包含 **“Oops”** 一词，比如::
54 Oops: 0002 [#1] PREEMPT SMP
57 尽管有 **Oops** 或其他类型的堆栈跟踪，但通常需要找到出问题的行来识别和处理缺
58 陷。在本章中，我们将参考“Oops”来了解需要分析的各种堆栈跟踪。
211 .byte .... /* bytes from Code: part of OOPS dump */
318 Aug 29 09:51:01 blizard kernel: Oops: 0002
320 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
329 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
|
| D | reporting-issues.rst | 118 * 如果失败涉及“panic”、“Oops”、“warning”或“BUG”，请考虑解码内核日志以查找触
309 的问题。注意：不要混淆“panic”（内核停止自身的致命错误）和“Oops”（可恢复错误），
381 为什么当内核报告内部问题（“kernel bug”）、可恢复错误（“kernel Oops”）或停止
390 1. 发生了一个可恢复的错误（“kernel Oops”），内核污染了自己，因为内核知道在
394 Oops: 0000 [#1] SMP
676 如后文所述。还要注意，预编译的内核可能缺少在出现panic、Oops、warning或BUG时
695 注意：如果您正在处理来自内核的pannc、Oops、warning或BUG，请在配置内核时尝试
746 *如果失败涉及“panic”、“Oops”、“warning”或“BUG”，请考虑解码内核日志以查找
752 请考虑解码内核日志中的信息。这将使我们更容易理解是什么导致了“panic”、“Oops”、
897 * 如果你处理的是内核的“warning”、“OOPS”或“panic”，请包含它。如果你不能复制
|
| D | tainted-kernels.rst | 20 bug”）、可恢复错误（“kernel oops”）或不可恢复错误（“kernel panic”）时会打印
32 Oops: 0002 [#1] SMP PTI
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | bug-hunting.rst | 52 嚴重性，它還可能包含 **“Oops”** 一詞，比如::
57 Oops: 0002 [#1] PREEMPT SMP
60 儘管有 **Oops** 或其他類型的堆棧跟蹤，但通常需要找到出問題的行來識別和處理缺
61 陷。在本章中，我們將參考“Oops”來了解需要分析的各種堆棧跟蹤。
214 .byte .... /* bytes from Code: part of OOPS dump */
321 Aug 29 09:51:01 blizard kernel: Oops: 0002
323 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
332 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
|
| D | reporting-issues.rst | 119 * 如果失敗涉及“panic”、“Oops”、“warning”或“BUG”，請考慮解碼內核日誌以查找觸
310 的問題。注意：不要混淆“panic”（內核停止自身的致命錯誤）和“Oops”（可恢復錯誤），
382 爲什麼當內核報告內部問題（“kernel bug”）、可恢復錯誤（“kernel Oops”）或停止
391 1. 發生了一個可恢復的錯誤（“kernel Oops”），內核污染了自己，因爲內核知道在
395 Oops: 0000 [#1] SMP
677 如後文所述。還要注意，預編譯的內核可能缺少在出現panic、Oops、warning或BUG時
696 注意：如果您正在處理來自內核的pannc、Oops、warning或BUG，請在配置內核時嘗試
747 *如果失敗涉及“panic”、“Oops”、“warning”或“BUG”，請考慮解碼內核日誌以查找
753 請考慮解碼內核日誌中的信息。這將使我們更容易理解是什麼導致了“panic”、“Oops”、
898 * 如果你處理的是內核的“warning”、“OOPS”或“panic”，請包含它。如果你不能複製
|
| D | tainted-kernels.rst | 23 bug”）、可恢復錯誤（“kernel oops”）或不可恢復錯誤（“kernel panic”）時會打印
35 Oops: 0002 [#1] SMP PTI
|
| /Documentation/ABI/testing/ |
| D | pstore | 39 data saved on each oops/panic. Pstore saves (possibly
|
| /Documentation/arch/parisc/ |
| D | debugging.rst | 23 an HPMC instead of a kernel oops. To debug an HPMC, try to find
|
| /Documentation/isdn/ |
| D | credits.rst | 18 Volker Götz (volker@oops.franken.de)
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 38 - ビルドエラー(CONFIG_BROKENになっているものを除く), oops, ハング、デー
|
| /Documentation/arch/x86/ |
| D | buslock.rst | 55 |warn |Kernel OOPs |Warn once per task and |
67 |fatal |Kernel OOPs |Send SIGBUS to user. |
|
| D | orc-unwinder.rst | 67 mission critical oops code.
177 ORC stands for Oops Rewind Capability.
|
| /Documentation/fb/ |
| D | cirrusfb.rst | 77 * Assertions no longer cause an oops on purpose.
|
| /Documentation/arch/s390/ |
| D | s390dbf.rst | 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
315 get an OOPS when inspecting the debug feature, because then the debug feature
|
| /Documentation/trace/ |
| D | debugging.rst | 59 crash occurs. This could be from the oops message in printk, or one could
68 buffer when a oops occurs to the console. This can be useful if the console
|
| D | boottime-trace.rst | 40 Dump ftrace on Oops. If MODE = 1 or omitted, dump trace buffer
41 on all CPUs. If MODE = 2, dump a buffer on a CPU which kicks Oops.
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 103 0.99.05 - Fix an oops on certain passthru commands
|
| /Documentation/translations/it_IT/process/ |
| D | changes.rst | 202 Se l'impensabile succede e il kernel va in oops, potrebbe servirvi lo strumento
208 ricompilarlo e riprodurre l'oops con quell'opzione abilitata, allora potete
209 usare ksymoops per decodificare l'oops.
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 202 do so will create race conditions and/or oops when trying
320 that there are no oops or hangs.
|
123