|
- How to determine which module taints the kernel?
and [root@Eiger ~]# cat proc sys kernel tainted 4096 I've not been able to find documentation for what the 4096 bitmask means, but the G flag means that an external GPL module is loaded into the kernel How do I find out which module is tainting the kernel?
- lsmod outputs: Not tainted - Unix Linux Stack Exchange
A running instance of the Linux kernel becomes “tainted” when something dodgy happens The kernel boots in non-tainted state, and becomes tainted if one such dodgy thing happens The full list of dodgy events is documented in sysctl kernel txt, and the kernel's current taint state can be read from proc sys kernel tainted (0 means not tainted) The most common reason for tainting is loaded
- Unable to Get Kernel Crash Dump on Kernel Panic
The serial console freezes with standard kernel panic stacktrace One of the logs specific to Kdump is: [14645 1099571] CPU: 2 PID: 20518 Comm: tee Kdump: loaded Not tainted 4 19 35-g9e41bb234b42 #2 The system however does not reboot One thing to note is that I can boot into the crash kernel if I want to explicitly:
- How can I un-taint my DKIM config after exim upgrade?
Debian upgrade to exim4 4 94 brings new headache: tainted variables I have several virtual domains handled by my exim and hence I use variable expansion to obtain DKIM domain, selector and key
- Random system freeze, vmware tainted modules - Unix Linux Stack Exchange
Keep getting system freezes, no keyboard or mouse response, only reboot works Problem Reporting reports error: A kernel problem occurred, but your kernel has been tainted (flags:GDOE) Explanation
- switch_root from initramfs is failing - Unix Linux Stack Exchange
We found the solution Basically, for testing purpose, we were executing our exec switch_root from a bin bash opened at the end of the init script The problem is that switch_root requires to run with PID 1 but, in our setup, that PID was not available since it was occupied by init PID 1: init PID x: bin bash => exec switch_root from bin bash would assign the PID x to switch_root That's
- Understanding the reasoning behind an OOM invokation
The java process that ended up being killed had PID 20639 whereas the output under the line that mentions VM Thread is CPU: 11 PID: 20646 Comm: VM Thread Not tainted 4 19 0-25-amd64 #1 Debian 4 19 289-2, so it's not a thread of the JVM
- Linux machine crashing on a daily basis, what does this kernel . . .
The crash comes in the form of a total hang No more control and screen freezes I grabbed a stacktrace on this machine using: sudo journalctl -f The last messages displayed are: Nov 18 19:42:12 k
|
|
|