| Title: | HSJ30/40 Product Conference |
| Moderator: | SSDEVO::EDMONDS |
| Created: | Mon Jul 12 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1264 |
| Total number of notes: | 4958 |
I got the following error . Device HSJ40 Version V25J(25) .
I know that we need to upgrade to the newest version of firmware ,
but site has not wanted to do so .
thank you
Frank Bernal
Last Failure Entry: 3. Flags: 00000002
Template: 1.(01) Description: Last Failure Event
Power on Time 2. Years,349. Days, 7. Hours, 34. Minutes,29. Secinds
Controller Model: HSJ40
Serial Number ZG41404844 Hardware Version: H04(4A)
Controller Identifier:
Unique Device Number: 0000941404844 Model: 40.(28) Class 1.(01)
Firmware Version: V25(25)
Node Name: "HSJ001" Ci node Number 15.(0F)
Instance Code: 0102030A Description
An unrecoverable firmware inconsistency was detected.
Reporting Component: 1.(01) Description
Executive Services
Reporting Component's event number 2.(02)
Event Treshhold: 10.(0a) Classification:
Soft. An unexpected condition detected by a controller firmware component
(e.g., protocol violations,host buffer access errors, internal inconsistencies,
etc.) is indicated .
Last Failure Code: 010D0110 (No Last Failure Parameters)
Last Failure Code: 010D0110 Description:
The System Information Structure within the System Information Page has been
reset to default settings. The only known cause for this event is an
I960 processor hang caused by an unimplemented memory region reference.
When such a hang occurrs,controller modules equipped with inactivity
watchdog timer circuitry will spontaneously reboot after the watchdog timer
expires ( within seconds of the hang ).Controller Modules not equipped will
just hang as indicated by the green LED on the OCP remaining in a steady state.
Reporting Component: 1.(01) Description
Executive Services
Reporting component's event number: 13 (0D)
Restart Type: 1.(01) Description: No restart
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1257.1 | What rev of board do you have? | SSDEVO::RMCLEAN | Wed May 21 1997 11:36 | 15 | |
Yup upgrade might well help but you are also missing a LOT of patches for V2.5 which might help also. My concern here is that you may well have a Rev A of the HSJ and this does not support any later versions of HSOF software. I also believe that Rev A of the board exhibited this crash on rare occasions. The crash says that the FX chip did a compare and found an error. When the software went back to find the mis-compare it couldn't find anything wrong so it crashed to prevent bad data from getting transferred anywhere. This is not a common crash but I believe that it was seen on earlier revs of the board. I think that there is an upgrade policy available for Rev A boards but I don't know what it is. | |||||
| 1257.2 | Only Rev A & C for J's | SSDEVO::RMCLEAN | Thu May 22 1997 12:04 | 7 | |
After more checking there were Rev A and Rev C boards for the HSJ. The release notes are wrong for the HSJ software and both boards are supported but as I said in .-1 I believe that if you are having problems with the FX chip you would be best to change the board to a Rev C board if there is one available. I believe that the FX chip is different onthe Rev C board and this might make this problem go away. It was not a serious problem because the system re-booted to prevent any accidental data loss. | |||||
| 1257.3 | TINCUP::RIDGE | I don't know where I'm at, but I'm nearly there! | Fri May 23 1997 17:41 | 18 | |
First, I believe for clarity we should refer to these boards not as by Rev, but as "model" of HSJ boards,,,, ...but to continue ... Engineering has never told MCS formally (as yet), that 'A' boards have an inherent problem here and that our service strategy should include "C" boards as replacements for "A" variants of the J controllers... Is engineering wanting us to adopt this policy??... cause that could get real expensive to the corporation I know thats not what you meant to define as policy for MCS to follow, .. you are addressing this SPECIFIC and isolated occurrence. generidge mcs.. | |||||
| 1257.4 | Yup I think he may have a board problem and A different alyout might be nice | SSDEVO::RMCLEAN | Tue May 27 1997 10:34 | 7 | |
>>you are addressing this SPECIFIC and isolated occurrence. That is exactly that. I have seen the described problem in a VERY sporatic manner and I hope that a different board and a Cx module in specific which has a different electrical layout will ensure that he does not see the problem. I have asked the engineers to see if there was a different FX chip used in those boards. I know the HSX50's have a different chip for the FX. | |||||