![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: We are receiving the following errors: %SYSMAN-I-NODERR, error returned from node MPSMA1 "SYSTEM-F-BADPARAM, bad parameter value." from a SYSMAN IO CONNECT call after we upgraded the Alpha firmware from DEC Firmware CD 4.0 to DEC Firmware CD 5.3. When someone try to access the device after the failure the machine BUGCHECKs with code 000001CC, INVEXCEPTN, Exception while above ASTDEL. Firmware CD 4.0 - AlphaBIOS 5.32-0; pfio 3.10; pks0 A10; pks1 A10; pks2 A10; SRMflash 4.9-1 Firmware CD 5.3 - AlphaBIOS 5.67-0; pfio 3.10; pks0 A11; pks1 A11; pks2 A11; SRMflash 5.3-1 The system is a 4 CPU AS4100 running OpenVMS V6.2-1H3. The driver we are trying to load is for a PCI card. Our SYSMAN command is: IO CONNECT TPA0 /ADAPTER=%X0003 /NODE=%X0028 /VECTOR=%X0C40 /CSR=0 /DRIVER_NAME=SDL48DVDRIVER.EXE We have checked and rechecked the parameters by following the proper link lists in the UCB using SYSMAN. When we moved the card to another PCI bus (adapter) on the same machine the driver successfully loaded. We have rerun the test on another machine that is identically configured (same adapter, slot, and IO CONNECT command) we get the same results. We have observed on these machines that the SCSI disk device names are different at the Console Firmware prompt and the VMS Prompt. The chart below lists our devices. The second column is the console device and the third column is the VMS device. I do not know if this has anything to do with it but it seems suspicious. SCSI I/O Board 1 DKB DKE SCSI I/O Board 1 DKC DKD SCSI I/O Board 1 DKD DKC SCSI I/O Board 1 DKE DKB The following chart summarizes our results. Node 1: Adapter 3 CD 4.0 PASS Adapter 3 CD 5.3 FAIL Adapter X CD 4.0 PASS Adapter X CD 5.3 PASS X = do not remember the number of the other adapter but it was not 3 Node 2: Adapter 3 CD 4.0 PASS Adapter 3 CD 5.3 FAIL Adapter X CD 4.0 PASS Adapter X CD 5.3 PASS The Answer is : Please check with the organization supporting the PCI card and the PCI card device driver -- resolution of this problem will involve specific identification of the PCI card involved, as well as assistance from the folks maintaining the associated device driver and (if necessary) then working with a Compaq Customer Support Center or OpenVMS Engineering. You will likely be asked to provide a copy of the crashdump file and potentially the CLUE CRASH output.
|