If not a reset, then one of the following may have occurred. Length of Logged Manager Information: The mode parameters in effect for this initiator have been restored from non-volatile memory. Alternatively, the installed version of the device driver does not match that of the installed version of HP-UX. Disk Inquiry Vendor ID
In case a different kernel function reports the error, figure out to which kernel subsystem or driver this belongs, and check for any known issue and a fix in a newer version.
How to correct Ultra SCSI Bus Reset EMS errors –
It can be downloaded from software. Disk Inquiry Vendor ID The HP-UX command uptime can be used to check uptime. Yes, that was a very annoying bug in the driver.
Any other event that requires the attention of the initiator. Retrieved from ” http: Command Data Block Contents: Click here to access the technical article at http: Timeout called with negative time.
How to correct Ultra320 SCSI Bus Reset EMS errors
For anyone interested, here was the answer from HP along with all the Example for HP-UX I believe HP had resolved that prior to my version I guess I can check with them. This example shows that a mpt function is called.
The mpt scsiU driver needs to be updated. Alternatively, a removable medium has been loaded or replaced.
In this case the mppt version of mpt driver is older than the one with the fix B. Release notes for the mpt driver version B.
HP-UX: How to get machine information
The fix will be released with Fusion. Offset to Logged Manager Information: Kudos points for any replies The version or level of microcode has been changed.
The fix from JAGag on The mode parameters in effect for this initiator have been changed by another initiator. I believe it does. All forum topics Previous Topic Next Topic. Latest mpt driver can be downloaded by searching scsiU from the follwing website: The device has been reset by a Bus Device Reset message, a hard reset condition, or a power-on reset.
Click here to access the technical article at: Thanks in advance and any response is appreciated.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. Does this ring a bell with anyone?