Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "what oops refers to in linux". In the operation process of actual cases, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

In linux, oops means "surprise," a message that something is running on the system that violates the rules specified by the kernel;oops generates a crash signature that helps kernel developers find errors and improve code quality.

This tutorial operates on Linux 5.9.8 and Dell G3 computers.

The Linux kernel is watching you, and when it detects something running on the system that violates normal kernel behavior, it shuts down the system and issues an "oops"!

If you examine the processes running on your Linux system, you might be curious about a process called "kerneloops." Note that this is "kernel loops" and not "kerne loops."

Frankly,"oops" is a part of the Linux kernel that has deviated behavior. Did you do something wrong? Probably not. But something's not right. The process that did the wrong thing may have been terminated by the CPU. Worst of all, the kernel may report errors and suddenly shut down the system.

Note that "oops" is not an acronym. It doesn't mean anything like "object-oriented programming and systems" or "out of procedural specs." It's literally "oops," like you just dropped a glass of wine or stepped on your cat. Oops! The plural of "oops" is "oops."

Oops means that something is running on the system that violates kernel rules for proper behavior. Maybe the code tried to take an impermissible code path or use an invalid pointer. Whatever it is, the kernel--which is always monitoring processes for bad behavior--is likely to block a particular process and write a message about what it did to the console,/var/log/dmesg, or/var/log/kern.log.

Oops may be caused by the kernel itself, or some process may try to get the kernel to violate what it can do on the system and what it is allowed to do.

Oops generates a crash signature that helps kernel developers find bugs and improve code quality.

The kerneloops process running on the system might look like this:

kernoops 881 1 0 Feb11 ? 00:00:01 /usr/sbin/kerneloops

You may notice that this process is not run by root, but by a user named "kernoops," and that it takes very little time to run. In fact, the only task assigned to this particular user is to run kerneloops.

$ sudo grep kernoops /etc/passwdkernoops:x:113:65534:Kernel Oops Tracking Daemon,,,:/:/bin/false

If your Linux system doesn't come with kerneloops (like Debian), you might consider adding them. Check out this Debian page for more information.

When should I pay attention to oops?

Oops is no big deal. It depends to some extent on the role played by a particular process. It also depends on the category of oops.

Some oops are severe and cause system panic. Technically, system panic is a subset of oops (i.e., the more severe oops). This occurs when the kernel detects a problem that is severe enough that it believes it must stop running immediately to prevent data loss or other damage to the system. Therefore, the system needs to be paused and restarted to prevent any inconsistencies from making it unavailable or unreliable. So system panic is really about protecting yourself from irreparable damage.

All kernel panics are oops, but not all oops are kernel panics.

/var/log/kern.log and related rotation logs (/var/log/kern.log.1,/var/log/kern.log.2, etc.) contain logs generated by the kernel and processed by syslog.

The kerneloops program collects and by default submits error messages to http://oops.kernel.org/, where they are parsed and presented to kernel developers. Configuration details for this process are specified in the/etc/kerneloops.conf file. You can easily view the settings using the following command:

$ sudo cat /etc/kerneloops.conf | grep -v ^# | grep -v ^$[sudo] password for shs:allow-submit = askallow-pass-on = yessubmit-url = http://oops.kernel.org/submitoops.phplog-file = /var/log/kern.logsubmit-pipe = /usr/share/apport/kernel_oops

In the above (default) settings, kernel issues can be submitted, but require permission from the user. If set to allow-submit = always, the user is not asked.

Debugging kernel problems is one of the more advanced techniques for working with Linux systems. Fortunately, most Linux users rarely or never experience oops or kernel panic. However, it's also good to know what processes like kerneloops are doing on the system, what might be reported, and when the system encounters serious kernel conflicts.

"What does oops mean in linux" is introduced here, thank you for reading. If you want to know more about industry-related knowledge, you can pay attention to the website. Xiaobian will output more high-quality practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.