Kernel Panic in Linux - What, Reason, Configure, Generate

-
What is Kernel Panic

 Kernel Panic is an error in the kernel code. On Kernel Panic, kernel stop running immediately to avoid data loss or other damage. The reason to stop running is to protect your computer, for example, if the module which is controlling the fan fails to load, kernel generates a panic and freezes the system.

What are the reasons for Kernel Panic
  • Hardware or Software Issue (e.g. unable to start init process)
  • Bug in the kernel driver
  • Defective or Incompatible RAM
What happens during Kernel Panic

When kernel decides to Panic, it calls the panic() function which dumps some debug information and depending on the configuration reboots the system

Configure Kernel to reboot on Kernel Panic

By default, the kernel will not reboot on Kernel Panic. There are two ways by which you can instruct the kernel to reboot

1. Kernel Command line: Add "panic=N" to the kernel command line, for the kernel to reboot after N seconds
2. Proc File system: echo N > /proc/sys/kernel/debug , for kernel to reboot after N seconds on reboot. Note this setting is not persistent on reboot.

Sample Code to generate Kernel Panic:

Make sure you configure the kernel to reboot else you need to hard reset the system



#include <linux/kernel.h>
#include <linux/module.h>

MODULE_LICENSE("GPL");
static int test_panic_init(void)
{
    printk(KERN_INFO"%s: In init\n", __func__);
    panic("Hello Kernel I am causing the panic\n");
    return 0;
}

static void test_panic_exit(void)
{
    printk(KERN_INFO"%s: In exit\n", __func__);
}

module_init(test_panic_init);
module_exit(test_panic_exit);

Loading the module will either freeze or reboot the kernel depending on your kernel configuration

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more