What happens to one core of Linux after kernal panic, other cores

In general, when the new kernel does not work properly, you can temporarily boot the system by using the fallback version of the initramfs kernel file, or even directly overwrite the fallback version to roll back the changes.

It's panic, that is, the system is dead, so how can you still read and write the hard disk, these are the normal operations of the system, the serial port is used to locate these problems, because the serial port has been printed on the console, in fact, it is temporarily placed in memory, and cannot be saved on the hard disk. For example, some servers, there is software management software, use tools to simulate the serial port, and then redirect the printed information to a certain computer, if you are using your own computer to install a virtual machine, then you can only rely on screenshots, my job is to specialize in researching these problems, others are sending screenshots to me. If it is a server, directly connect to the virtual serial port or physical serial port and check the error message.

Like panic, it's a very serious mistake, and it's basically not saved.

It is generally believed that your system may not be able to operate the disk correctly after kernel panic, so it is better to print it on the screen to ensure that you can see it.

lz ask for a screenshot to see it, no picture is not good for your diagnosis.

Restart the Linux system, see the picture as shown and press the e key quickly see the interface as shown in the figure press the e key As shown in the picture, use the up and down keys to select the second one in the E button Add enforcing=0 after the last line Press enter to save and exit Press the B key on this page to restart.

Panic means panic in English, Linux Kernel Panic is as its name suggests, Linux Kernel doesn't know how to go, it will try to print out all the information it can get at this time.

There are two main types of kernel panic and panic (i.e., AIEEE information output).

panic (i.e. oops message output).

There are many reasons for kernel panics, and you must have some serious bugs that you didn't follow the manual tutorial or whatever.

Of course, it is not excluded that what you are looking at is itself wrong.

If you want to know what the reason is, you have to post at least the content of the n lines above to analyze. Just talking about kernel panic, then I can only suspect that you don't have embedded development at all or start working on the rest of the ...... before you even get started

I'm guessing it's the root partition mount failed or you didn't do the root filesystem.

Kernel panic? What does that mean? Haven't heard of this term. Is it a typo?

kill -9 to kill the process, or restart.

Rebooting is very simple, the key should be to find out the cause of the deadlock and avoid this kind of error.

1. var log messages: When you're lucky, the entire kernel panic stack trace information can be recorded here.

2. Application Library Logs: You may be able to see what happened before the panic occurred from these log messages.

3. Other information before the panic occurs, or the bad file knows how to reproduce the chaotic state at the moment of panic.

4. Terminal screen dump information, generally after the OS is locked, copying, pasting must be no fun, so this kind of information, you can need to use a digital camera or the original pen and paper tool.

It is caused by the inconsistency of the default startup item kernel of GNU Grub when starting Linux, press F1 when booting, press the up and down arrows on the keyboard to select the appropriate one in the interface, and press Enter. If it can be started successfully, you can delete the others, and only keep the one that can be started, so as not to manually select each startup, as shown in the figure: my machine is the above one by default, and the kernel panic - not syncing:

fatal exception, change to the following to start Linux normally