-- RunaBriguglio - 07 Jul 2011

During opt int mat sampling we found (july-september 2010) sudden RIP of the shell somwhere when enabling the disturb and applying modes.

These failures were fixed by introducing some wait,0.1 at after each instructions.

We noe try to identify the exact instruction that gives the error, disabling one by one the wait.

The code used (from i4d_opt_intmat) is /test/test_enable_disturb.pro

Test ID Test configuration # of test iterations Result
1 Original 5 PASSED
2 Removed wait 8-9 12 PASSED
3 Removed wait 7-8 12 PASSED
4 Removed wait 6-7 12 PASSED
5 Removed wait 4-5 12 No RIP but failure on setting the OVS: then set manually to 125Hz see 1
6 Removed wait 3-4 12 PASSED
7 Removed wait 4-5. OVS set initially to 500 Hz 12 same as 5
8 Removed wait 2-3. OVS set initially to 500 Hz 12 RIP: imposs to identify when. 2011-07-07 19:13:01.3
9 Same as 8; load_program first. separate iterations No RIP

1 idlctrl.R |INF| 12030|2011-07-07 18:52:01.507295| MAIN > Setting the OVS to 0; step 6 idlctrl.R |INF| 12031|2011-07-07 18:52:01.507343| MAIN > Done idlctrl.R |INF| 12032|2011-07-07 18:52:01.507391| MAIN > Enabling the disturb; step 7 idlctrl.R |INF| 12033|2011-07-07 18:52:01.507443| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#1 of 10 idlctrl.R |INF| 12034|2011-07-07 18:52:01.507495| MAIN > ARMATEST: Writing check failed. Attempt#1 of 10 idlctrl.R |INF| 12035|2011-07-07 18:52:01.507549| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12036|2011-07-07 18:52:01.507606| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#2 of 10 idlctrl.R |INF| 12037|2011-07-07 18:52:01.507666| MAIN > ARMATEST: Writing check failed. Attempt#2 of 10 idlctrl.R |INF| 12038|2011-07-07 18:52:01.507735| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12039|2011-07-07 18:52:01.507787| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#3 of 10 idlctrl.R |INF| 12040|2011-07-07 18:52:01.507840| MAIN > ARMATEST: Writing check failed. Attempt#3 of 10 idlctrl.R |INF| 12041|2011-07-07 18:52:01.507891| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12042|2011-07-07 18:52:01.507942| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#4 of 10 idlctrl.R |INF| 12043|2011-07-07 18:52:01.507993| MAIN > ARMATEST: Writing check failed. Attempt#4 of 10 idlctrl.R |INF| 12044|2011-07-07 18:52:01.508044| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12045|2011-07-07 18:52:01.508095| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#5 of 10 idlctrl.R |INF| 12046|2011-07-07 18:52:01.508149| MAIN > ARMATEST: Writing check failed. Attempt#5 of 10 idlctrl.R |INF| 12047|2011-07-07 18:52:01.508208| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12048|2011-07-07 18:52:01.508271| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#6 of 10 idlctrl.R |INF| 12049|2011-07-07 18:52:01.508325| MAIN > ARMATEST: Writing check failed. Attempt#6 of 10 idlctrl.R |INF| 12050|2011-07-07 18:52:01.508381| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12051|2011-07-07 18:52:01.508433| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#7 of 10 idlctrl.R |INF| 12052|2011-07-07 18:52:01.508483| MAIN > ARMATEST: Writing check failed. Attempt#7 of 10 idlctrl.R |INF| 12053|2011-07-07 18:52:01.508534| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12054|2011-07-07 18:52:01.508585| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#8 of 10 idlctrl.R |INF| 12055|2011-07-07 18:52:01.508636| MAIN > ARMATEST: Writing check failed. Attempt#8 of 10 idlctrl.R |INF| 12056|2011-07-07 18:52:01.508686| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12057|2011-07-07 18:52:01.508737| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#9 of 10 idlctrl.R |INF| 12058|2011-07-07 18:52:01.508795| MAIN > ARMATEST: Writing check failed. Attempt#9 of 10 idlctrl.R |INF| 12059|2011-07-07 18:52:01.508848| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12060|2011-07-07 18:52:01.508909| MAIN > % WRITE_SAME_DSP: ARMATEST: Writing check failed. Attempt#10 of 10 idlctrl.R |INF| 12061|2011-07-07 18:52:01.508963| MAIN > ARMATEST: Writing check failed. Attempt#10 of 10 idlctrl.R |INF| 12062|2011-07-07 18:52:01.509019| MAIN > Read 4.04471e-41 instead of 3.47074e-41 idlctrl.R |INF| 12063|2011-07-07 18:52:01.509068| MAIN > -10023


08/08/2011 fibra shell set ok test SC mario (prima errore nel set start RTR 500/100 --> ripetizione errore CA ogni ca 50 secondi aggiunto start rtr in coda alle slopes - -> sc non va raramentei in timeout durante l'attacco/stacco (idem il secondario e a volte con crc) (il W1 andava in timeout a 990 con ovs a 860 sempre, mai con ovs a 500)


09/08/2011 maniglia armadio rotta (porta aperta) -> connettori esapodo rotti -> IT test esapodo test CL con switch bcu unita' A. 1/2 ora test apri chiudi senza problemi, OVS a 920 e a 500. 36 timeout di fibra su ~583100 frames sullo sc . testate anche le porte 2 e 3. nessun problema evidente cambio switch bcu con quella dell'unita' B. test porte 1, 2 e 3. tutto ok. Si e' verificato solo un caso ti timeout continuo SC: problema sync logica SC risolto con un reset (ma non spiega che lo fa continuamente con lo SC) update switch bcu spare hw and firmware nella configuratione "default".
Topic revision: r4 - 09 Aug 2011, MarcoXompero
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback