Linux crashes the problem of processing

Will Linux crash? I can say with certainty, will! how is it? Very simple,

My previous post

introduced a method ~ to make Linux crash is easy, but it is difficult to safely let him get rid of the crash state after the crash .

There are many situations in which Linux crashes. The most common one is caused by excessive system load. This is the principle of the fork bomb introduced as described above. In addition, you can run programs that consume a lot of memory (such as virtual machines) and quickly increase the system load. Due to the system load is too high, the card is dead, it must be solved as soon as possible! It must be remembered at this point that you can no longer try to rely on anything from the graphical interface, such as Gnome's system monitor (this is my ignorance habit from Windows … …), which will only continue to aggravate this card death. Situation. What should I do?

No

I'm afraid, Linux doesn't need a graphical interface at first, because there is a very powerful text interface. Press Ctrl-Alt-F1 (F1-F6

is generally fine), then wait a while, then switch to

tty, the so-called text interface. This time you need to log in with your username and password. Note that keyboard input may be slower, but it should still be tolerable. Next, type

at the prompt and press Enter. You will see a dynamic table listing the processes that consume the most resources. Observe that it is refreshed once or twice, press q to exit, then enter kill , where you can see the PID in the top. This time should be a lot faster, if you find that it did not end successfully, then enter kill -KILL, this time basically no problem.

In addition to the above, some bugs in the underlying software can also cause some strange crashes. One of my classmates recently forced the restart of the ext4

partition because of an inexplicable crash. (The last is sysreccd

fixed, it seems that the partition table is partially damaged.) According to it, the crash is no response. In general, the crash caused by high system load will also be reflected in the terrible keyboard. Some people say that if the crash to the keyboard is not responding, the load

is infinitely large, and some people say that this may be X. Server and driver have problems with the problem. But let's consider what to do if we encounter this situation?

OK, this is the method I learned today, called reisub, which can safely restart the computer in various situations. Everyone on the keyboard can find a key called "Sys

Rq”, which is usually shared with Prt Sc on the keyboard of the desktop, and may be in other locations in the notebook, such as Delete. In the case of a desktop machine, to use this method, you need to hold down Alt-Print (Sys Rq), then press the reisub keys in sequence, and press b to restart the system.

Let's explain this method: In fact, Sys Rq is a kind of system request. When you hold Alt-Print, it is equivalent to holding down the Sys Rq

key. Everything is handled directly by the Linux kernel, which can do many low-level operations. At this time, each letter in reisub

is an independent operation, they respectively represent:

unRaw grabs keyboard control from X Server

tErminate to all processes Send SIGTERM signals, let them solve the problem themselves

kIll Send SIGKILL signals to all processes, force them to close immediately

Sync synchronize all data to disk

Unmount all partitions Mount as read-only mode

reBoot Restart

The order of the 6 letters is not correct. How do you remember that? Here is a way that personally thinks it's better: the word busier (busy's comparative, busier) is the reverse.

Basically, Linux crashes are rare, and now you can safely solve them, how good~