While installing IBM SDD driver crashing system with PANIC?

[rveri]

Hi All,

While installing IBM SDD driver causing system to crash with PANIC. and dumping memory. This is for connecting new IBM storage to the system.

Here is the error message.
----------------------------

Press CTRL-K for keyboard help. │
│Source: ddsapd01:/var/patch/sdd/sdd/IBMsddHP64_050203.depot │
│Target┌ === Install Window (sapsvr01) (3) ┐ │
│ │ │ │
│Only s│ Press 'Products' and/or 'Logfile' for more target information.│ │
│──────│ │───────│
│Top (B│ Target : ddsapd01:/ │elected│
│──────│ Status : Executing configure │───────│
│ Mark│ Percent Complete : 100% │ │
│┌─────│ Kbytes Installed : 5975 of 5975 │─────┐ │
││ Yes │ Time Left (minutes): 0 │ Ve ^ │
││ │ Loading Software : IBMsdd_tag,r=1.6.0.9 │ │
││ │ │ │
││ │ [ Products... ] [ Logfile... ] │ │
************* SYSTEM ALERT **************──────────────────────────────│ │
SYSTEM NAME: dsapd01s [ Help ] │ │
DATE: 11/18/2005 TIME: 19:02:26────────────────────────────────────────┘ │
ALERT LEVEL: 12 = Software failure │
││ v │
REASON FOR ALERT >┘ │
SOURCE: 1 = processor │
SOURCE DETAIL: 1 = processor general SOURCE ID: 0────────────────────────────┘
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
ON FLASH FLASH ON ON
LED State: System Running. Unexpected Reboot. Non-critical Error Detected.
Check Chassis and Console Logs for error messages.

0xF8E010C01100B900 00000000 0000B900 - type 31 = legacy PA HEX chassis-code
0x58E018C01100B900 0000690A 1213021A - type 11 = Timestamp 11/18/2005 19:02:26
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:

-------------------------------------------------------------------------------------------------

SDD driver Link:
http://www-1.ibm.com/support/docview.wss?rs=540&context=ST52G7&uid=ssg1S4000053&loc=en_US&cs=utf-8〈=en+en


Here is the Fiber patch versions available as per recomendation:

PHKL_28984 1.0 Fibre Channel Mass Storage Patch
PHSS_28509 1.0 Tachyon TL Fibre Channel Driver Patch


Any Idea whats wrong. Please suggest.
Thanks

[Duncan Edmonstone]

Have you installed all the patches mentioned on p154 of the install doc?

Is your system 32-bit or 64-bit (I'm assuming its 64?)

Have you made sure you don't have any other multipath software installed already? (like HP's SecurePath?)


IBM's SDD goes on as a Dynamically Loaded Kernel Module, so it looks to me like the system is panicing when the module is being loaded - you could have a hunt around in the depot file and try and locate the command that are being run, that might point you in the right direction...

Otherwise I'm afraid you are completely in the hands of IBM on this one - the best you are likely to get out of HP is 'best effort' support, rather than a fix, as they will (rightly) say - this ones and IBM problem...

HTH

Duncan

[Steven E. Protter]

Shalom rveri,

These kind of problems are almost always corrected by removing conflicting software, installing patches, or a combination of these two recommendations.

I would run

swverify \*

Make sure all patches are installed correctly and nothing is corrupt.

It might not be a bad idea to contact IBM support. Its there product, and though I'm surprised they delivered it in depot form, they may have a newer version if they've encountered this bug before.

SEP

[Raj D.]

Hi ,

Check for minimum patch requirement from IBM site and also do swverify \*
as mentioned above. You can also send the crash dump to HP for furthe analysis.

hth,
Raj

[rveri]

Thanks for replying.

I have installed in one N4000 ,and no Panic, and I am trying to install in another system now , with same version of SDD driver 1.6.0.9 , with same Fibre patch but still panic.

I have compared both the system and found , only firmware level is different.

well after rebooting the server , system again given panic at service startup.

Then I boot in single user and Comment out the S340confserver , that was loading the hd2vp utility [ Converting sdisk to vpath utility ]. Then system cameup properly.

After booting found swlist shows the driver installed properly. # showvpath shows the path.

I ll be updating . thx.

[Steven E. Protter]

Good detective work.

I suggest upgrading that firmware forthwith.

SEP