| /Linux-v4.19/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-v4.19/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-v4.19/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()
|
| D | main.c | 1949 goto oops; in handle_goto()
1961 goto oops; in handle_goto()
1972 goto oops; in handle_goto()
1974 oops: in handle_goto()
|
| /Linux-v4.19/arch/alpha/lib/ |
| D | dbg_stackcheck.S | 25 1: stq $31, -8($31) # oops me, damn it.
|
| /Linux-v4.19/fs/pstore/ |
| D | Kconfig | 115 messages, even if no oops or panic happened.
141 tristate "Log panic/oops to a RAM buffer"
149 This enables panic and oops messages to be logged to a circular
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | tainted-kernels.rst | 4 Some oops reports contain the string **'Tainted: '** after the program
17 3) ``S`` if the oops occurred on an SMP kernel running on hardware that
|
| 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
|
| /Linux-v4.19/Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 38 - ビルドエラー(CONFIG_BROKENになっているものを除く), oops, ハング、デー
|
| D | SubmittingPatches | 549 障害の症状(カーネルログメッセージや oops メッセージ等)を記載することは問題に
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | rk3288-veyron-pinky.dts | 23 * really should be 1.8V (oops). The external pulldown will help
|
| /Linux-v4.19/Documentation/fb/ |
| D | cirrusfb.txt | 78 * Assertions no longer cause an oops on purpose.
|
| /Linux-v4.19/Documentation/parisc/ |
| D | debugging | 17 an HPMC instead of a kernel oops. To debug an HPMC, try to find
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | pstore | 38 data saved on each oops/panic. Pstore saves (possibly
|
| /Linux-v4.19/drivers/media/common/saa7146/ |
| D | saa7146_vbi.c | 256 goto oops; in buffer_prepare()
267 oops: in buffer_prepare()
|
| D | saa7146_video.c | 1125 goto oops; in buffer_prepare()
1128 goto oops; in buffer_prepare()
1135 oops: in buffer_prepare()
|
| /Linux-v4.19/drivers/net/appletalk/ |
| D | ltpc.c | 503 int oops; in idle() local
518 oops = 100; in idle()
521 if (0>oops--) { in idle()
|
| /Linux-v4.19/Documentation/isdn/ |
| D | CREDITS | 14 Volker Götz (volker@oops.franken.de)
|
| /Linux-v4.19/Documentation/scsi/ |
| D | ChangeLog.ips | 103 0.99.05 - Fix an oops on certain passthru commands
|
| /Linux-v4.19/Documentation/s390/ |
| D | s390dbf.txt | 90 The second trigger which stops the debug feature is a kernel oops.
92 happened before the oops. After an oops you can reactivate the debug feature
178 used in case of a kernel oops.
|
| /Linux-v4.19/lib/ |
| D | Kconfig.kgdb | 114 catastrophic error, i.e. for a panic or oops.
|
| /Linux-v4.19/arch/openrisc/ |
| D | Kconfig | 185 Now this puts kernel into infinite loop after first oops. Till
|
| /Linux-v4.19/drivers/mtd/ |
| D | Kconfig | 299 tristate "Log panic/oops to an MTD buffer"
301 This enables panic and oops messages to be logged to a circular
|
| /Linux-v4.19/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.
|
