[krasberg on 2007-12-10 17:08:49] : software power down of DOMs does not always reset dor-driver firmware fuse problems about dor-driver

[dglo]

[jacobsen on 2007-12-12 16:06:19]
An example follows. For some reason, powering down the DOMs does not reset the fuse. The other problem is that it is happening at all.

From: 	  [email protected]
Subject: 	DOMHubMonitor reports abnormal configuration for all on Wed Dec 12 09:15:03 2007
Date: 	December 12, 2007 3:15:03 AM CST
To: 	  [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

DOMHubMonitor reports abnormal configuration for all on Wed Dec 12 09:15:03 2007
(abnormal configuration found 21 times in a row)

sps-ichub29 : Card 1 pair 2 pwr check: plugged(ERR_UNPLUGGED) current(ok,ok) voltage(ok,ok)���
sps-ichub29 : Card 1 pair 3 pwr check: plugged(ERR_UNPLUGGED) current(ok,ok) voltage(ok,ok)���
sps-ichub29 : Unexpected # of communicating DOMs: expected 58; found 0.���

DOMHub (v3.62) using command: quicktable
Using entry for all in ~/domhubConfig.dat.
Using hubs: sps-amanda, sps-ichub21, sps-ichub29, sps-ichub30, sps-ichub38, sps-ichub39, sps-ichub40, sps-ichub49, sps-ichub50, sps-ichub59, sps-ichub58, sps-ichub67, sps-ichub66, sps-ichub74, sps-ichub73, sps-ichub65, sps-ichub72, sps-ichub78, sps-ichub48, sps-ichub57, sps-ichub47, sps-ichub46, sps-ichub56, sps-ithub01, sps-ithub02, sps-ithub03, sps-ithub04
Waiting for 27 DOMHubs to finish...
Waiting on 26 DOMHUBs...
Waiting on 8 DOMHUBs...
All DOMHubs have finished.

SUMMARY

HUB: AM 01 02 03 04 21 29 30 38 39 40 46 47 48 49 50 56 57 58 59
COMM: 2 32 32 32 8 60 0 58 60 60 58 54 58 60 60 59 58 60 60 58

---

HUB: 65 66 67 72 73 74 78
COMM: 60 60 60 58 60 59 60

HUBS= 27; COMM= 1346

sps-ichub29 : Card 1 pair 2 pwr check: plugged(ERR_UNPLUGGED) current(ok,ok) voltage(ok,ok)���
sps-ichub29 : Card 1 pair 3 pwr check: plugged(ERR_UNPLUGGED) current(ok,ok) voltage(ok,ok)���
sps-ichub29 : Unexpected # of communicating DOMs: expected 58; found 0.���

[dglo]

[jacobsen on 2007-12-12 16:22:04]
Oops, it looks like the previous problem was an actual physical event (cable falling out). But the signature from domhubmonitor would be the same.