What can noapic and acpi = off do for me?

What can noapic and acpioff help me do? Linux general technology-Linux technology and application information. The following is a detailed description. In January, I wrote a post about acpi and apic. At that time, I wrote this post for two reasons: first, I encountered a lot of obfuscation of the difference between apic and acpi. No wonder they both look too similar. Second, because the two core parameters (noapic, acpi = off) related to the time helped me solve a problem that I thought was incredible at the time, so I felt it was necessary to record it.

Later, I wrote another post about the problem of using these two parameters to solve the problem.

I didn't think that, since then, I have encountered many strange problems. Basically, when you think something is wrong, you can use these two parameters as soon as possible. Today, I have encountered the problem solved using these two parameters, so I want to record the problems I have encountered so far.

It should be the CALIAS project at the earliest, and DC4.1 is installed on IBM X346 (now X3650. With a Qlogic Optical Fiber card, the single core starts everything OK, with multiple cores, the optical fiber card looks like the drive is normal, that is, it cannot access the array cabinet.

Later, I took the machine to the company. After the R & D tips, I got it done. From that time on, I knew that there was such a parameter. The same machine and configuration have also encountered this situation in another project, but it is worse, kernel panic. After these two parameters are added, the problem is solved.

If you remember correctly, HP ML570 machine, install X86-64 version DC5, to unzip the kernel, don't move, press the keyboard no response. After the restart, add these two parameters.

The IBM R52 notebook is installed with the red-flag desktop 4.1 plus. The installation is normal. When the ACPI is started, it will not go down after the ACPI appears. After the apci = off, the problem is solved.

There are also a number of times when the general X86 pc server is installed, there is a kernel error, add these two parameters after starting to complete.

Ordinary desktop, non-integrated RTL-8100B/8139D Nic, install DC5, Nic can drive, that is, ping can not get through the network, dmesg can see

Netdev watchdog: eth0: transmit timed out
Eth0: Transmit timeout, status 0c 0005 c07f media 00.
Eth0: Tx queue start entry 4 dirty entry 0.
Eth0: Tx descriptor 0 is 0008a03c. (queue head)
Eth0: Tx descriptor 1 is 0008a03c.
Eth0: Tx descriptor 2 is 0008a03c.
Eth0: Tx descriptor 3 is 0008a03c.
Eth0: link up, 100 Mbps, full-duplex, lpa 0xC5E1
Netdev watchdog: eth0: transmit timed out

At first, I thought the driver version was too low, but I thought about how standard the NIC is for linux. I was puzzled by the two parameters and the problem was solved.

In short: If you encounter an incredible problem, you can give priority to adding the core parameters of acpi = off noapic. Maybe it is so easy to solve the problem.

Method:
/Boot/grub/menu. lst file, and add
Acpi = off noapic