Problem-fixing method for kernel panic caused by glibc under Linux system

The Linux operating system, a cloning system developed on the basis of UNIX operating systems, has become one of the most widely used UNIX-type operating systems in the world today, with the help of Internet networks and the combined efforts of computer enthusiasts around the world, and the number of users is growing rapidly. Although the user is very popular in the use, but there are some problems, such as: due to glibc caused kernel panic problem. This is an extremely serious mistake. Unless you know the cause of it. It is difficult to solve. Most of them are caused by hardware damage or kernel conflict and high temperature. The following small series for you to introduce Linux due to glibc caused kernel panic problem repair methods.

Specific methods

The following process is much easier when Linux basically simply enters the resume mode via CD or other means.

(If your installation process is not successful, please download the appropriate installation package to install according to the error prompts until the GLIBC installation is successful) in addition, this is for CentOS, Ubuntu can also use this method, just install the package of commands to replace the dpkg.

Install LIBGCC:

RPM-UVH--root=/mnt/sysimage/--force libgcc-4.7.0-1.fc17.x86_64.rpm

Install Glibc-common:

RPM-UVH--root=/mnt/sysimage/--force--nodeps glibc-common-2.15-32.fc17.x86_64.rpm

Install glibc:

RPM-UVH--root=/mnt/sysimage/--force glibc-2.15-32.fc17.x86_64.rpm

After the installation is complete, you can reboot to see if it is back to normal (can enter the system). If there are other issues, you can fix it after you enter the system, depending on your situation.

This is a very difficult problem, generally if we do not know the cause of the error can only reload the system, if the study of the method of small, you do not have to spend energy to reload the system, hurry to learn!