debugging: slides: "oops behavior": reorganize content

Move around bullets and reword sentences for clarity and to keep related info together (especially the two ways to enable panic-on-oops). Signed-off-by: Luca Ceresoli <[email protected]>
bootlin · Dec 14, 2023 · ca9e8df · ca9e8df
1 parent 24cc4d8
commit ca9e8df
Showing 1 changed file with 7 additions and 6 deletions.
diff --git a/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex b/slides/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -156,17 +156,18 @@ \section{Kernel Debugging}
     \item Sometimes, crash might be so bad that the kernel will panic and halt
           its execution entirely by stopping scheduling application and staying
           in a busy loop.
-    \item \kconfig{CONFIG_PANIC_ON_OOPS}: Always panic when an oops is
-          triggered
-    \item \kconfig{CONFIG_PANIC_TIMEOUT}: Number of second after which the
-          kernel will reboot
+    \item Automatic reboot on panic can be enabled via
+      \kconfig{CONFIG_PANIC_TIMEOUT}
     \begin{itemize}
       \item 0: never reboots
       \item Negative value: reboot immediately
       \item Positive value: seconds to wait before rebooting
     \end{itemize}
-    \item OOPS can be configured at boot time to force a \code{panic()} call
-          using the \code{oops=panic} command line parameter.
+    \item OOPS can be configured to always panic:
+    \begin{itemize}
+      \item at boot time, adding \code{oops=panic} to the command line
+      \item at build time, setting \kconfigval{CONFIG_PANIC_ON_OOPS}{y}
+    \end{itemize}
   \end{itemize}
 \end{frame}