Improper message state for HAI_Complete_HACB

  • 3574329
  • 13-Feb-2007
  • 27-Apr-2012

Situation

Break caused by Abend: NWPA-042: Improper message state for HAI_Complete_HACB

The iscsiham was passing in a HACB to be completed that was not in use at the time. Here's the HACB:
842A7F00 00000000 1B6102EB 896FF580 50DFF3E0
842A7F10 00000000 00000000 00000000 00000400
842A7F20 1822002F 00000000 00000000 00280001
842A7F30 00000001 00001000 29EA9000 29EA9000
842A7F40 00000040 50B9E120 50B9E120 0BAEE7E0
842A7F50 00000000 84ECA798 84ECA798 00000000
842A7F60 00000000 00000000 00000001 44444444
842A7F70 0000002A 00000000 00000000 00000000
842A7F80 00000000 00000000 00000000 00000000
842A7F90 00000000 00000000 00000000 00000000
842A7FA0 00000000 130B0028 0000E704 00000008
842A7FB0 00000000 00000000 00000000 0A000000
842A7FC0 842A6800 00000000 859F97C0 8F018040
842A7FD0 00000000 85A2CFD0 00000000 1823002F
842A7FE0 00000000 00000000 00000000 00000000
842A7FF0 00000000 00000000 00000000 00000111
This is a valid HACB structure but you can see at offset E0 that it's not in use. Therefore the abend occured in HAI_Complete_HACB as this HACB did not need to be completed. This HACB was passed in by the iscsiham.ham and then pulled out of HAI_Complete_HACB's local space. Here's the stack:
Current EIP:84ECA7D9 NWPA.NLM|HAI_Complete_HACB+41
ESP:8F012E2C EIP:8D0AE691 ISCSIHAM.HAM|iscsihamCallBack+1F9
ESP:8F012E58 EIP:8D0E3E0E ISCSINIT.NLM|iscsi_rx_read_scsi_data+1AE
ESP:8F012E7C EIP:8D0E5EE8 ISCSINIT.NLM|process_iscsi_header+190
ESP:8F012E94 EIP:8D0E6165 ISCSINIT.NLM|connection_rx_thread+1C1
ESP:8F01302C EIP:00225338 SERVER.NLM|TcoNewSystemThreadEntryPoint+40

Resolution

This has been fixed in ISCSI code (Version 1.06) Dec 4, 2006 or later. It was not included in NetWare 6.5 SP6. Until this file is fully released, it is available from Novell Tech Support. This is beta code.

Status

Reported to Engineering

Additional Information

It appears to occur if the iSCSI connections are going up and down.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.