[bootlin/training-materials updates] master: Kernel debugging lab: remove obsolete instructions (247e623a)

Michael Opdenacker michael.opdenacker at bootlin.com
Tue Mar 31 11:20:57 CEST 2020

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/247e623abc026a610d691ff3baa56e7b8c6109dd


commit 247e623abc026a610d691ff3baa56e7b8c6109dd
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Tue Mar 31 11:17:38 2020 +0200

    Kernel debugging lab: remove obsolete instructions
    - CONFIG_ARM_UNWIND is now set by default, at least in the omap2plus
      configuration. No longer needed to elaborate on this setting.
    - By the way, CONFIG_UNWINDER_ARM is also set by default
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
    Reported-by: Dale Stewart <dale.stewart at meresoftware.com>


 labs/kernel-debugging/kernel-debugging.tex | 18 ++----------------
 1 file changed, 2 insertions(+), 16 deletions(-)

diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index d999bb21..aa6b84a7 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -79,22 +79,8 @@ that have been transmitted by your driver.
 Go to the \code{~/linux-kernel-labs/modules/nfsroot/root/debugging/} directory.
-Make sure your kernel is built with the following options:
-\item The \code{CONFIG_ARM_UNWIND} configuration option
-  (\code{Kernel Hacking} section) disabled. This option enables a
-  new mechanism to handle stack backtraces, but this new mechanism is
-  not yet as functional and reliable as the old mechanism based on frame
-  pointers. In our case, with our board, you get a backtrace only if
-  this option is disabled.
-Compile the \code{drvbroken} module provided in \code{nfsroot/root/debugging}.
-On your board, load the \code{drvbroken.ko} module. See it crashing
-in a nice way.
+Compile the \code{drvbroken} in this directory, and load it on your
+board. See it crashing in a nice way.
 \section{Analyzing the crash message}

More information about the training-materials-updates mailing list