Home
last modified time | relevance | path

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

12345678910>>...30

/kernel/linux/linux-5.10/arch/c6x/kernel/
Dtraps.c94 { "Oops - instruction fetch", SIGBUS, BUS_ADRERR },
95 { "Oops - fetch packet", SIGBUS, BUS_ADRERR },
96 { "Oops - execute packet", SIGILL, ILL_ILLOPC },
97 { "Oops - undefined instruction", SIGILL, ILL_ILLOPC },
98 { "Oops - resource conflict", SIGILL, ILL_ILLOPC },
99 { "Oops - resource access", SIGILL, ILL_PRVREG },
100 { "Oops - privilege", SIGILL, ILL_PRVOPC },
101 { "Oops - loops buffer", SIGILL, ILL_ILLOPC },
102 { "Oops - software exception", SIGILL, ILL_ILLTRP },
103 { "Oops - unknown exception", SIGILL, ILL_ILLOPC }
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dpstore-blk.rst3 pstore block oops/panic logger
9 pstore block (pstore/blk) is an oops/panic logger that writes its logs to a
75 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
76 It's optional if you do not care oops/panic log.
78 There are multiple chunks for oops/panic front-end depending on the remaining
81 pstore/blk will log to oops/panic chunks one by one, and always overwrite the
90 Unlike oops/panic front-end, there is only one chunk for pmsg front-end.
113 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 …]
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 …]
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
87 2 _/S 4 SMP kernel oops on an officially SMP incapable processor
92 7 _/D 128 kernel died recently, i.e. there was an OOPS or BUG
119 2) ``S`` if the oops occurred on an SMP kernel running on hardware that
138 7) ``D`` if the kernel has died recently, i.e. there was an OOPS or BUG.
/kernel/linux/linux-6.6/Documentation/admin-guide/
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 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 …]
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 …]
/kernel/linux/linux-6.6/drivers/accessibility/speakup/
Dgenmap.c40 oops("too many shift states", NULL); in get_shift_value()
87 oops("unknown key/modifier", cp); in main()
90 oops("modifiers must come first", cp); in main()
95 oops("bad modifier or key", cp); in main()
99 oops("no = found", NULL); in main()
103 oops("no speakup function after =", NULL); in main()
107 oops("invalid speakup function", cp); in main()
114 oops("two functions on same key combination", cp); in main()
/kernel/linux/linux-6.6/arch/riscv/kernel/
Dtraps.c138 do_trap_error(regs, signo, code, regs->epc, "Oops - " str); \
142 do_trap_error(regs, signo, code, regs->epc, "Oops - " str); \
169 "Oops - illegal instruction"); in do_trap_insn_illegal()
176 "Oops - illegal instruction"); in do_trap_insn_illegal()
186 SIGBUS, BUS_ADRALN, "Oops - load address misaligned");
188 SIGBUS, BUS_ADRALN, "Oops - store (or AMO) address misaligned");
200 "Oops - load address misaligned"); in do_trap_load_misaligned()
208 "Oops - load address misaligned"); in do_trap_load_misaligned()
221 "Oops - store (or AMO) address misaligned"); in do_trap_store_misaligned()
229 "Oops - store (or AMO) address misaligned"); in do_trap_store_misaligned()
[all …]
/kernel/linux/linux-6.6/fs/pstore/
DKconfig72 messages, even if no oops or panic happened.
106 fault log for BlackBox when oops or panic happened.
111 tristate "Log panic/oops to a RAM buffer"
118 This enables panic and oops messages to be logged to a circular
134 tristate "Log panic/oops to a block device"
140 This enables panic and oops message to be logged to a block dev
181 This just sets size of kmsg dump (oops, panic, etc) log for
/kernel/linux/linux-5.10/fs/pstore/
DKconfig116 messages, even if no oops or panic happened.
150 fault log for BlackBox when oops or panic happened.
155 tristate "Log panic/oops to a RAM buffer"
162 This enables panic and oops messages to be logged to a circular
178 tristate "Log panic/oops to a block device"
185 This enables panic and oops message to be logged to a block dev
226 This just sets size of kmsg dump (oops, panic, etc) log for
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/reserved-memory/
Dramoops.txt1 Ramoops oops/panic logger
4 ramoops provides persistent RAM storage for oops and panics, so they can be
13 Any remaining space will be used for a circular buffer of oops and panic
55 - no-dump-oops: deprecated, use max_reason instead. If present, and
/kernel/linux/linux-6.6/arch/csky/kernel/
Dtraps.c147 do_trap_error(regs, signo, code, regs->pc, "Oops - " str); \
164 "Oops - load/store address misaligned"); in do_trap_misaligned()
184 "Oops - illegal trap exception"); in do_trap_bkpt()
207 "Oops - illegal instruction exception"); in do_trap_illinsn()
216 "Oops - fpu instruction exception"); in do_trap_fpe()
227 "Oops - illegal privileged exception"); in do_trap_priv()
/kernel/linux/linux-5.10/arch/csky/kernel/
Dtraps.c149 do_trap_error(regs, signo, code, regs->pc, "Oops - " str); \
166 "Oops - load/store address misaligned"); in do_trap_misaligned()
186 "Oops - illegal trap exception"); in do_trap_bkpt()
209 "Oops - illegal instruction exception"); in do_trap_illinsn()
218 "Oops - fpu instruction exception"); in do_trap_fpe()
229 "Oops - illegal privileged exception"); in do_trap_priv()
/kernel/linux/linux-5.10/arch/riscv/kernel/
Dtraps.c97 do_trap_error(regs, signo, code, regs->epc, "Oops - " str); \
112 SIGBUS, BUS_ADRALN, "Oops - load address misaligned");
114 SIGBUS, BUS_ADRALN, "Oops - store (or AMO) address misaligned");
124 "Oops - load address misaligned"); in do_trap_load_misaligned()
132 "Oops - store (or AMO) address misaligned"); in do_trap_store_misaligned()
/kernel/linux/linux-6.6/Documentation/translations/zh_CN/admin-guide/
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…
/kernel/linux/linux-6.6/Documentation/translations/zh_TW/admin-guide/
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…
/kernel/linux/linux-5.10/drivers/misc/lkdtm/
Dusercopy.c99 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_stack()
120 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_stack()
171 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_heap_size()
183 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_heap_size()
246 pr_warn("copy_to_user failed, but lacked Oops\n"); in do_usercopy_heap_whitelist()
258 pr_warn("copy_from_user failed, but lacked Oops\n"); in do_usercopy_heap_whitelist()
330 pr_warn("copy_to_user failed, but lacked Oops\n"); in lkdtm_USERCOPY_KERNEL()
/kernel/linux/linux-6.6/sound/soc/sof/xtensa/
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()
/kernel/linux/linux-5.10/sound/soc/sof/xtensa/
Dcore.c84 static void xtensa_dsp_oops(struct snd_sof_dev *sdev, void *oops) in xtensa_dsp_oops() argument
86 struct sof_ipc_dsp_oops_xtensa *xoops = oops; in xtensa_dsp_oops()
89 dev_err(sdev->dev, "error: DSP Firmware Oops\n"); in xtensa_dsp_oops()
109 static void xtensa_stack(struct snd_sof_dev *sdev, void *oops, u32 *stack, in xtensa_stack() argument
112 struct sof_ipc_dsp_oops_xtensa *xoops = oops; in xtensa_stack()
/kernel/linux/linux-6.6/drivers/misc/lkdtm/
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()
/kernel/linux/linux-5.10/arch/powerpc/kernel/
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 …]
/kernel/linux/linux-6.6/arch/powerpc/kernel/
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 …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/reserved-memory/
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:
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
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 */
/kernel/linux/linux-6.6/arch/powerpc/include/asm/
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 */

12345678910>>...30