This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
lkmp:lkmp_stable_release [2019/04/05 02:20] ShuahKhanLF |
lkmp:lkmp_stable_release [2019/06/17 16:53] (current) ShuahKhanLF |
||
---|---|---|---|
Line 6: | Line 6: | ||
==== Use stable release rc git ==== | ==== Use stable release rc git ==== | ||
- | Clone the git repo specified and in the email. A new directory linux-5.0.y gets created which contains the kernel sources. Starting out with the distribution configuration file is the safest approach for the very first kernel install on any system. You can do so by copying the configuration for your current kernel from /boot. Once this step is complete, it is time to compile the kernel, install the new kernel and run update-grub to add the new kernel to the grub menu. Now it is time to reboot the system to boot the newly installed kernel. | + | Clone the git repository specified and in the email. A new directory linux-5.0.y gets created which contains the kernel sources. Starting out with the distribution configuration file is the safest approach for the very first kernel install on any system. You can do so by copying the configuration for your current kernel from /boot. Once this step is complete, it is time to compile the kernel, install the new kernel and run update-grub to add the new kernel to the grub menu. Now it is time to reboot the system to boot the newly installed kernel. |
<code> | <code> | ||
Line 21: | Line 21: | ||
===== Download stable release patch and apply ==== | ===== Download stable release patch and apply ==== | ||
- | Alternately, you can download and apply the patch. The following is my workflow for getting repo ready, apply the patch, compile, and install. I apply patches and use the same repo to be able to detect regressions. I save dmesg for the current rc to compare with the next rc. Please feel free to make changes to suit your needs. | + | Alternately, you can download and apply the patch. The following is my workflow for getting repository ready, apply the patch, compile, and install. I apply patches and use the same repository to be able to detect regressions. I save dmesg for the current rc to compare with the next rc. Please feel free to make changes to suit your needs. |
<code> | <code> | ||
Line 50: | Line 50: | ||
dmesg -t -l emerg > dmesg_current_emerg | dmesg -t -l emerg > dmesg_current_emerg | ||
dmesg -t -l alert > dmesg_current_alert | dmesg -t -l alert > dmesg_current_alert | ||
- | dmesg -t -l crit > dmesg_current_alert | + | dmesg -t -l crit > dmesg_current_crit |
dmesg -t -l err > dmesg_current_err | dmesg -t -l err > dmesg_current_err | ||
dmesg -t -l warn > dmesg_current_warn | dmesg -t -l warn > dmesg_current_warn | ||
Line 75: | Line 75: | ||
Now restart the system. Once the new kernel comes up, compare the saved dmesg from the old kernel with the new one and see if there are any regressions. If the newly installed kernel fails to boot, you will have to boot a good kernel and then investigate why the new kernel failed to boot. | Now restart the system. Once the new kernel comes up, compare the saved dmesg from the old kernel with the new one and see if there are any regressions. If the newly installed kernel fails to boot, you will have to boot a good kernel and then investigate why the new kernel failed to boot. | ||
- | Run [[https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html|Kernel Selftests]] and check results. | + | Run [[https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html|Kernel Selftests]] and check results. |
<code> | <code> | ||
+ | # Running as root could reboot your system. Run as normal user. | ||
make kselftest | make kselftest | ||
</code> | </code> | ||
**Report results responding to stable release announcement. A summary such as "Compiled, booted, and no regressions" is sufficient if everything looks good or report failures if any.** | **Report results responding to stable release announcement. A summary such as "Compiled, booted, and no regressions" is sufficient if everything looks good or report failures if any.** |