Home
last modified time | relevance | path

Searched full:oops (Results 1 – 25 of 316) sorted by relevance

12345678910>>...13

/linux/Documentation/admin-guide/
H A Dpstore-blk.rst3 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 …]
H A Dbug-hunting.rst42 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 …]
H A Dramoops.rst1 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
H A Dtainted-kernels.rst16 ('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.
/linux/drivers/accessibility/speakup/
H A Dgenmap.c39 oops("too many shift states", NULL); in get_shift_value()
86 oops("unknown key/modifier", cp); in main()
89 oops("modifiers must come first", cp); in main()
94 oops("bad modifier or key", cp); in main()
98 oops("no = found", NULL); in main()
102 oops("no speakup function after =", NULL); in main()
106 oops("invalid speakup function", cp); in main()
113 oops("two functions on same key combination", cp); in main()
H A Dutils.h46 static inline int oops(const char *msg, const char *info) in oops() function
88 oops("out of key table space, enlarge MAXKEYS", NULL); in add_key()
92 oops("attempt to add duplicate key", name); in add_key()
H A Dspeakup_keypc.c140 static char *oops(void) in oops() function
165 return oops(); in synth_immediate()
220 oops(); in do_catch_up()
236 oops(); in do_catch_up()
253 oops(); in do_catch_up()
/linux/fs/pstore/
H A DKconfig42 messages, even if no oops or panic happened.
69 tristate "Log panic/oops to a RAM buffer"
76 This enables panic and oops messages to be logged to a circular
92 tristate "Log panic/oops to a block device"
98 This enables panic and oops message to be logged to a block dev
139 This just sets size of kmsg dump (oops, panic, etc) log for
/linux/arch/riscv/kernel/
H A Dtraps.c154 do_trap_error(regs, signo, code, regs->epc, "Oops - " str); \
158 do_trap_error(regs, signo, code, regs->epc, "Oops - " str); \
185 "Oops - illegal instruction"); in do_trap_insn_illegal()
192 "Oops - illegal instruction"); in do_trap_insn_illegal()
208 "Oops - load address misaligned"); in do_trap_load_misaligned()
216 "Oops - load address misaligned"); in do_trap_load_misaligned()
229 "Oops - store (or AMO) address misaligned"); in do_trap_store_misaligned()
237 "Oops - store (or AMO) address misaligned"); in do_trap_store_misaligned()
350 "Oops - environment call from U-mode"); in do_trap_ecall_u()
/linux/arch/csky/kernel/
H A Dtraps.c148 do_trap_error(regs, signo, code, regs->pc, "Oops - " str); \
165 "Oops - load/store address misaligned"); in do_trap_misaligned()
185 "Oops - illegal trap exception"); in do_trap_bkpt()
208 "Oops - illegal instruction exception"); in do_trap_illinsn()
217 "Oops - fpu instruction exception"); in do_trap_fpe()
228 "Oops - illegal privileged exception"); in do_trap_priv()
/linux/Documentation/translations/zh_TW/admin-guide/
H A Dbug-hunting.rst52 嚴重性，它還可能包含 **“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…
H A Dreporting-issues.rst119 * 如果失敗涉及“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”，請包含它。如果你不能複製
/linux/Documentation/translations/zh_CN/admin-guide/
H A Dbug-hunting.rst49 严重性，它还可能包含 **“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…
H A Dreporting-issues.rst118 * 如果失败涉及“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”，请包含它。如果你不能复制
/linux/drivers/misc/lkdtm/
H A Dusercopy.c100 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_stack()
121 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_stack()
172 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_slab_size()
184 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_slab_size()
249 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_slab_whitelist()
261 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_slab_whitelist()
335 pr_warn("copy_to_user failed, but lacked Oops\n"); in lkdtm_USERCOPY_KERNEL()
379 pr_warn("Good, copy_to_user() failed, but lacked Oops(?!)\n"); in do_usercopy_page_span()
/linux/arch/powerpc/kernel/
H A Dnvram_64.c60 .name = "lnx,oops-log",
71 "lnx,oops-log",
83 * For capturing and compressing an oops or panic report...
87 * oops_buf[] holds the compressed text, preceded by a oops header.
88 * oops header has u16 holding the version of oops header (to differentiate
105 * We preallocate these buffers during init to avoid kmalloc during oops/panic.
360 pr_err("nvram: logging uncompressed oops/panic report\n"); in zip_oops()
381 * Called by pstore_dump() when an oops or panic report is logged in the
417 * Reads the oops/panic report, rtas, of-config and common partition.
506 /* Old format oops header had 2-byte record size */ in nvram_pstore_read()
[all …]
/linux/sound/soc/sof/xtensa/
H A Dcore.c84 static void xtensa_dsp_oops(struct snd_sof_dev *sdev, const char *level, void *oops) in xtensa_dsp_oops() argument
86 struct sof_ipc_dsp_oops_xtensa *xoops = oops; in xtensa_dsp_oops()
89 dev_printk(level, sdev->dev, "error: DSP Firmware Oops\n"); in xtensa_dsp_oops()
115 static void xtensa_stack(struct snd_sof_dev *sdev, const char *level, void *oops, in xtensa_stack() argument
118 struct sof_ipc_dsp_oops_xtensa *xoops = oops; in xtensa_stack()
/linux/Documentation/devicetree/bindings/reserved-memory/
H A Dramoops.yaml7 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:
/linux/drivers/gpu/drm/ci/xfails/
H A Dvkms-none-skips.txt6 # Oops: 0000 [#1] PREEMPT SMP NOPTI
57 # Oops: 0000 [#1] PREEMPT SMP NOPTI
108 # Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
159 # Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
210 # Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
/linux/arch/powerpc/include/asm/
H A Dnvram.h14 * Set oops header version to distinguish between old and new format header.
15 * lnx,oops-log partition max size is 4000, header version > 4000 will
80 /* Initialize NVRAM oops partition */
/linux/include/sound/sof/
H A Dheader.h183 * OOPS header architecture specific data.
187 uint32_t totalsize; /* Total size of oops message */
191 * OOPS header platform specific data.
198 * oops message
/linux/arch/alpha/lib/
H A Ddbg_stackcheck.S6 * Verify that we have not overflowed the stack. Oops if we have.
25 1: stq $31, -8($31) # oops me, damn it.
/linux/drivers/mtd/
H A DKconfig170 tristate "Log panic/oops to an MTD buffer"
172 This enables panic and oops messages to be logged to a circular
177 tristate "Log panic/oops to an MTD buffer based on pstore"
180 This enables panic and oops messages to be logged to a circular
/linux/scripts/
H A Ddecodecode4 # usage: decodecode < oops.file
7 # e.g., to decode an i386 oops on an x86_64 system, use:
8 # AFLAGS=--32 decodecode < 386.oops
9 # PC=hex - the PC (program counter) the oops points to
/linux/kernel/
H A Dpanic.c47 * Should we dump all CPUs backtraces in an oops event?
351 * Avoid nested stack-dumping if a panic occurs during oops processing in panic()
409 * panic() is not being callled from OOPS. in panic()
638 /* This CPU may now print the oops message */ in do_oops_enter_exit()
664 * Return true if the calling CPU is allowed to print oops-related info.
673 * Called when the architecture enters its oops handler, before it prints
674 * anything. If this is the first CPU to oops, and it's oopsing the first
704 * Called when the architecture exits its oops handler, after printing
858 early_param("oops", oops_setup);

12345678910>>...13