Proliant DL385 G2 + Rhel 5.5 + acpi=off Kernel Panic

[damaris]

Hi. I've tried to deactivate ACPI but when the system boots, kernel panic appears.

Aparently the system array does not have support or has a conflict when acpi is disabled, because the system does not recognized it.

I need to deactivate the acpi, because the server has an overruns problem over a sangoma card, and the sangoma support team needs to try the system without acpi.

Rhel 5.5
Kernel 2.6.18-164.el5
Proliant DL385 G2
cpq_cciss-3.6.26-5
UUID: 414109USE739N4PH
Server Serial Number / Product ID: USE739N4PH / 414109-B21
System ROM: A09 07/11/2009;
backup system ROM: 04/07/2007
Power Regulator for Proliant: OS Control mode

[Matti_Kurkela]

Use the boot options to direct the kernel output to a serial port (either a real serial port or iLO's virtual serial port), and use that to capture the panic message.

If you choose to use a real serial port, connect another computer with a terminal emulator program to it: for example, a laptop running Hyperterminal on Windows, or Minicom on Linux. Set it to capture all incoming data to a file.

If you use iLO's virtual serial port, connect to it using a SSH or telnet client of your choice, and make sure it has a nice, long scroll-back buffer configured. Then just copy&paste the boot messages.

To send the kernel messages to a serial port, add this to the boot options:

console=ttyS0,9600 console=tty0

This will use the COM1 (= ttyS0 in Linux) serial port with 9600 bps communication speed. If you use the iLO serial port (typically COM2 = ttyS1), you can easily use faster speeds, e.g. 115200 bps. The second "console=" option will ensure the normal KVM console remains functional.

The last "console" option on the line will determine the "true" system console, although the kernel messages will be output to all consoles listed.

Good luck trying to run a modern server without ACPI: many features on modern server hardware depend on it.

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=622018
https://bugzilla.redhat.com/show_bug.cgi?id=622021
https://bugzilla.redhat.com/show_bug.cgi?id=576480

MK