Home
last modified time | relevance | path

Searched refs:oops (Results 1 – 10 of 10) sorted by relevance

/Zephyr-latest/arch/x86/core/ia32/
Dfatal.c49 struct arch_esf oops = { in arch_syscall_oops() local
55 if (oops.cs == USER_CODE_SEG) { in arch_syscall_oops()
56 oops.esp = ssf_ptr->esp; in arch_syscall_oops()
59 z_x86_fatal_error(K_ERR_KERNEL_OOPS, &oops); in arch_syscall_oops()
/Zephyr-latest/arch/arm64/core/
Dswitch.S163 beq oops
208 oops: label
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst11 invoked panic or oops conditions.
41 a default implementation with weak linkage which invokes a kernel oops if
158 A kernel oops is a software triggered fatal error invoked by
174 and doing so will generate a kernel oops instead. Otherwise, the fatal error
/Zephyr-latest/tests/ztest/error_hook/
DREADME.txt157 E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
168 E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
188 E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
/Zephyr-latest/tests/arch/arm/arm_interrupt/
DREADME.txt79 E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
/Zephyr-latest/doc/hardware/porting/
Darch.rst793 * :c:func:`arch_syscall_oops` which generates a kernel oops when system
794 call parameters can't be validated, in such a way that the oops appears to be
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst334 :c:macro:`K_OOPS()` can be used to induce a kernel oops which will kill the
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst239 system errors (e.g. Kernel oops or panic), or implement IRQ offloading.
/Zephyr-latest/doc/releases/
Drelease-notes-2.6.rst1188 * :github:`35202` - smp atomic_t global_lock will never be cleared when a thread oops with global_l…
Drelease-notes-1.14.rst1201 * :github:`15037` - xtensa: context returns to thread after kernel oops