| /Linux-v5.4/Documentation/translations/zh_CN/ |
| D | oops-tracing.txt | 33 和你所做的事情相关的代码的负责人。 如果可重现试着描述怎样重构。 那甚至比oops更有
51 本。（注意：这需要vesafb，所以对‘早期’的oops没有帮助）
70 主要的窍门是有五年和这些烦人的oops消息打交道的经验;-)
78 得到oops发生的函数及函数内的偏移）。
92 decodecode < oops.txt
109 汇编代码及其反汇编得到的代码（另外还有从“oops”消息得到的寄存器状态-对了解毁坏的
165 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
174 Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system_…
188 一些oops报告在程序记数器之后包含字符串'Tainted: '。这表明内核已经被一些东西给污
197 3：'S'如果oops发生在SMP内核中，运行于没有证明安全运行多处理器的硬件。 当前这种
|
| /Linux-v5.4/Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.txt | 1 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
33 - record-size: maximum size in bytes of each dump done on oops/panic
48 - no-dump-oops: if present, only dump panics (defaults to panics and oops)
|
| /Linux-v5.4/sound/soc/sof/xtensa/ |
| D | core.c | 84 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()
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()
|
| /Linux-v5.4/drivers/staging/speakup/ |
| D | speakup_keypc.c | 131 static char *oops(void) in oops() function
156 return oops(); in synth_immediate()
211 oops(); in do_catch_up()
227 oops(); in do_catch_up()
244 oops(); in do_catch_up()
|
| D | speakup_decpc.c | 343 goto oops; in testkernel()
354 oops: synth_release_region(speakup_info.port_tts, SYNTH_IO_EXTENT); in testkernel()
|
| /Linux-v5.4/sound/soc/sof/ |
| D | sof-priv.h | 212 void (*dsp_oops)(struct snd_sof_dev *sdev, void *oops);
213 void (*dsp_stack)(struct snd_sof_dev *sdev, void *oops,
574 u32 tracep_code, void *oops,
614 static inline void sof_stack(struct snd_sof_dev *sdev, void *oops, u32 *stack, in sof_stack() argument
618 sof_arch_ops(sdev)->dsp_stack(sdev, oops, stack, stack_words); in sof_stack()
621 static inline void sof_oops(struct snd_sof_dev *sdev, void *oops) in sof_oops() argument
624 sof_arch_ops(sdev)->dsp_oops(sdev, oops); in sof_oops()
|
| D | core.c | 161 u32 tracep_code, void *oops, in snd_sof_get_status() argument
193 sof_oops(sdev, oops); in snd_sof_get_status()
194 sof_stack(sdev, oops, stack, stack_words); in snd_sof_get_status()
|
| /Linux-v5.4/arch/alpha/lib/ |
| D | dbg_stackcheck.S | 25 1: stq $31, -8($31) # oops me, damn it.
|
| /Linux-v5.4/fs/pstore/ |
| D | Kconfig | 116 messages, even if no oops or panic happened.
142 tristate "Log panic/oops to a RAM buffer"
149 This enables panic and oops messages to be logged to a circular
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ramoops.rst | 1 Ramoops oops/panic logger
11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
35 power of two) and each oops/panic writes a ``record_size`` chunk of
|
| 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
87 2 _/S 4 SMP kernel oops on an officially SMP incapable processor
119 2) ``S`` if the oops occurred on an SMP kernel running on hardware that
|
| /Linux-v5.4/Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 38 - ビルドエラー(CONFIG_BROKENになっているものを除く), oops, ハング、デー
|
| /Linux-v5.4/Documentation/fb/ |
| D | cirrusfb.rst | 77 * Assertions no longer cause an oops on purpose.
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | rk3288-veyron-pinky.dts | 30 * really should be 1.8V (oops). The external pulldown will help
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | pstore | 38 data saved on each oops/panic. Pstore saves (possibly
|
| /Linux-v5.4/Documentation/parisc/ |
| D | debugging.rst | 23 an HPMC instead of a kernel oops. To debug an HPMC, try to find
|
| /Linux-v5.4/drivers/media/common/saa7146/ |
| D | saa7146_vbi.c | 256 goto oops; in buffer_prepare()
267 oops: in buffer_prepare()
|
| /Linux-v5.4/drivers/net/appletalk/ |
| D | ltpc.c | 503 int oops; in idle() local
518 oops = 100; in idle()
521 if (0>oops--) { in idle()
|
| /Linux-v5.4/Documentation/isdn/ |
| D | credits.rst | 18 Volker Götz (volker@oops.franken.de)
|
| /Linux-v5.4/Documentation/translations/it_IT/process/ |
| D | changes.rst | 158 Se l'impensabile succede e il kernel va in oops, potrebbe servirvi lo strumento
164 ricompilarlo e riprodurre l'oops con quell'opzione abilitata, allora potete
165 usare ksymoops per decodificare l'oops.
|
| /Linux-v5.4/drivers/mtd/ |
| D | Kconfig | 167 tristate "Log panic/oops to an MTD buffer"
169 This enables panic and oops messages to be logged to a circular
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.ips | 103 0.99.05 - Fix an oops on certain passthru commands
|
| /Linux-v5.4/Documentation/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
|
| /Linux-v5.4/lib/ |
| D | Kconfig.kgdb | 115 catastrophic error, i.e. for a panic or oops.
|
| /Linux-v5.4/arch/openrisc/ |
| D | Kconfig | 178 Now this puts kernel into infinite loop after first oops. Till
|
