RHEL: Kernel panic after creation of new RAID group with hpacucli

[Christian Otto Stelter]

Hi!

I got a kernel panic after the creation of a new raid group with hpcaucli on a RHEL 4 (kernel 2.6.18-53.1.4.el5) run on a DL365 G1.

The hpacucli returned normally, but after sending an "hpacucli ctrl slot=0 pd all show" the system got panic. (see att.)

I didn't find anything in RH's bugzilla or here or elsewhere.

Has anyone had this problem, too?

Kind regards, cos

[Steven E. Protter]

Shalom,

That is not a stock kernel for Red Hat 4.

The kernel panic is probably caused by the upgraded kernel not liking the relatively old hardware.

SEP

[Christian Otto Stelter]

Hi, Steven!

It is a standard kernel out of the satellite.

[root@lnxp-1722:~]$ rpm -qi kernel-2.6.18-53.1.4.el5
Name : kernel Relocations: (not relocatable)
Version : 2.6.18 Vendor: Red Hat, Inc.
Release : 53.1.4.el5 Build Date: Wed 14 Nov 2007 05:28:32 PM CET
Install Date: Wed 12 Dec 2007 02:43:41 PM CET Build Host: hs20-bc2-3.build.redhat.com

Smells for me of some kind of a race condition - I've never had this problem before.

Kind regards, cos

[Christian Otto Stelter]

Update.

Seems that someone messed around with /etc (rsync). It 's a system which was installed with RHEL 5 - which does not match with /etc/redhat-release - which shows Version 4.

[Steven E. Protter]

Thats a problem Sir.

IS the system RH 4 or 5?

SEP

[Christian Otto Stelter]

It is a RHEL 5 "camouflaged" as RHEL 4 as it seems. At least it was installed as a regular RHEL 5.

rpm -Va shows no serious changes as far as I can see. So it wasn't an rsync-accident or similar.

I'm trying to verify this with my colleagues whether some kind of stupid application insisted on "being a RHEL 4".

[Christian Otto Stelter]

JFTR. Red Hat recommended a kernel updates (5.1 -> 5.2) which includes a new cciss driver.

Will report whether it helped or not.

[Christian Otto Stelter]

hpacucli worked like a charm after the kernel update.

The v4 /etc/redhat-release was copied onto the system by the customer for running a stupid application installer... he didn't changed it back afterwards.

/* no comment */

Thanks for helping Steven!