| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
I have a customer with a locked hub900 console port. The unit is
running v5.0, all network modules are running but he has this in the
lcd:
vo=0c, sr=2708, pc=006029d0 failed
Is this likely to be a problem with the mam?
Thanks
Paul.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4413.1 | NETCAD::MILLBRANDT | answer mam | Wed May 14 1997 20:49 | 24 | |
Hi - It's an address exception (there's no memory to access at 6029D0) at IPL 7. This is most likely a MAM firmware error. Could also be a firmware crash caused by a module with bent pins or other problem. Please give us lots more information: - What version of MCM are you running? (**Must be at least V6.0 of MCM to operate with MAM V5.0.) - When MAM resets, does it get through self-test to where the LCD says "Starting Main Firmware"? Does it get through decompression to "Initializing..."? - What is the complete contents of the Error Log? - What is the name and version level of each module in the hub? - What is your LAN Interconnect configuration? - Is a user doing anything specific when it crashes? Dotsie | |||||
| 4413.2 | NETCAD::DOODY | Michael Doody | Thu May 15 1997 10:04 | 4 | |
I suspect that the "Failed" means that it failed diagnostics and
it means a bad MAM board.
-Mike
| |||||