June 2017
Intermediate to advanced
478 pages
13h 14m
English
When the kernel performs an invalid memory access or executes an illegal instruction, a kernel Oops message is written to the kernel log. The most useful part of this is the backtrace, and I want to show you how to use the information there to locate the line of code that caused the fault. I will also address the problem of preserving Oops messages if they cause the system to crash.
This Oops message was generated by writing to the mailbox driver in MELP/chapter_14/mbx-driver-oops:
Unable to handle kernel NULL pointer dereference at virtual address 00000004pgd = dd064000[00000004] *pgd=9e58a831, *pte=00000000, *ppte=00000000Internal error: Oops: 817 [#1] PREEMPT ARMModules linked in: mbx(O)CPU: 0 PID: 408 Comm: sh Tainted: ...
Read now
Unlock full access