VME error observed - after replugging the PU - error so far was not observed.
|
|
29.04.2015 |
Rerun with 300 mio statistics to be sure - no errors were observed. started at 14:30. |
|
|
05.02.2015 |
95 mio events - with dataverify - no errors - move to 48 board. (3 screenshots were made) |
04.02.2015 |
38 mio events - left to get 100 mio events - then try 48 board |
|
|
03.02.2015 |
run 1 mio after long break - no errors |
03.02.2015 |
start injector.sh to check than run works with more then 2 mio events - left over night run |
|
|
|
|
07.05.2014 |
stopped due to 20.2 mio events - no vme errors - vme_poke 0x7000030 0x1 0x4 2 did not help - Olga/DataVerifyFiles/DataVerify_rod190_07052014.err |
|
with no solution I just change the board |
|
|
06.05.2014 |
stop no VME bus errors - restart tdaq with other board - ../Olga/DataVerifyFiles/DataVerify_rod190_06052014.err - over 20mio again with errors - |
|
vme_poke 0x9000030 0x1 0x4 2 does not work |
11:00 |
|
11:30 |
start tdaq after the injector board removing - and sending injectorclockreset - but tdaq produced a lot of errors screenshot in folder 06.05.2014 |
11:44 |
restart tdaq - runs with no data verify errors and with injector clock reset |
17:57 |
10 mio events no VME error and other errors - keep for the night and test of the InjClockReset Screenshot-2.png |
|
|
05.05.2014 |
restart tdaq - 20.2 mio no vme bus error - screenshot and dataverify_rod190_05052014.err saved |
9:30 |
new start |
14:56 |
8 mio events - continue - to see where 16 mio will give errors |
|
|
|
------------------------------------------------------------------------------- |
02.05.2014 |
|
9:37 |
860 mio events with no errors - restart for a few more runs |
12:00 |
switch dataverify back and run over the 4 hours and then leave for a weekend to see if errors appear again. |
15:55 |
4.3 mio events - no errors - restart for the weekend - |
|
|
30.04.2014 |
Stopped tdaq with 250mio events with no data veryfy and no vme bus error - switch to other board and rotating PUs back to see if error is repeatable |
9:27 |
restart tdaq as rod241 did not run |
|
PU mezanine boards from top to down: 20ALLPRP00471 20ALLPRP00092 20ALLPRP00912 20ALLPRP00700 |
11:30 |
restart of TDAq - 50 mio without any error |
12:15 |
22 mio without error - restart tdaq |
14:36 |
63 mio events with no errors - restart tdaq again |
17:45 |
87 mio events with no errors - restart tdaq for the full day |
|
|
29.04.2014 |
stop due to large number of events - 20240879 - preentscreen and copied data verify cp /tmp/DataVerify_2014.err ~/Olga/DataVerifyFiles DataVerify_rod190_29042014.err |
8-30 |
new start of tdaq |
16:00 |
after meeting stop tdaq with no error at 100mio |
|
Fixing run without dataverify --> 6kHz frequency - run up to 18 mio without errors screenshot-1 - restart tdaq for testing |
|
no VME bus error up to 37mio - stop and restart over the night printscreen-2 |
|
|
28.04.2014 |
Swapping PU boards to chech the DSP influence on the board --> by checkking the VME bus error address |
|
PU mezanine boards from top to down: 20ALLPRP00471 20ALLPRP00092 20ALLPRP00912 20ALLPRP00700 |
|
rotate once: 20ALLPRP00092 20ALLPRP00912 20ALLPRP00700 20ALLPRP00471 |
16:42 |
start tdaq with rotated PUs |
17:06 |
stop due to dataverify errors - screenshot in 28.04.2014 ~/Olga/DataVerifyFiles/DataVerify_rod190_28.04.2014.err |
17:08 |
restart tdaq - no errors in dataverify from start |
19:15 |
stopped tdaq with 2.7 Mio without any error |
19:17 |
start tdaq with disabled DataVerify and EventCounterReset - prinscreen-3 - wrong as I did not save setting |
19:25 |
new start with data verify |
|
|
05.02.2014 |
|
9:30 |
errors after restarting and replugging the ROD and TDAQ |
|
11:21:33 WARNING RODC rcc::VmeBusError WARNING - Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000308 - APPLICATION: RODC - DATE: 2014/Feb/05 11:21:33 - PID: 4063 - HOST: largrod3 - QUALIFIERS: RodCrate - PACKAGE_NAME RodCrate APPLICATION_NAME RODC FILE_NAME ../src/monitoring/BusErrorCatcher.cpp FUNCTION_NAME virtual void* BusErrorCatcher::Main() LINE_NUMBER 107 DATE_TIME 1391595693 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 4063 THREAD_ID 4404 HOST_NAME largrod3 address 0x9000308 cycle D32 READ module ROD_05 |
|
|
|
|
04.02.2014 |
|
7:14 |
20240875 events - 3461396 errors - file copied - the scrinshot done |
07:03:59 |
WARNING LARG_RootController rc::ApplicationWarning WARNING - Failed to lookup application TTCC on the host largrod3.unige.ch - APPLICATION: LARG_RootController - DATE: 2014/Feb/04 07:03:59 - PID: 31260 - HOST: largrod4.unige.ch - QUALIFIERS: RunController - PACKAGE_NAME RunController APPLICATION_NAME LARG_RootController FILE_NAME ../src/lib/Application.cc FUNCTION_NAME bool daq::rc::Application::isRunning(bool) LINE_NUMBER 446 DATE_TIME 1391493839 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 31260 THREAD_ID 31833 HOST_NAME largrod4.unige.ch application TTCC reason Failed to lookup application TTCC on the host largrod3.unige.ch |
9:13 |
restart tdaq - new run |
12:24 |
14:15:33 WARNING RODC rcc::VmeBusError WARNING - Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000348 -- 9 similar messages suppressed, last occurrence was at 2014-Feb-04 14:15:30 - APPLICATION: RODC - DATE: 2014/Feb/04 14:15:33 - PID: 1815 - HOST: largrod3 - QUALIFIERS: RodCrate - PACKAGE_NAME RodCrate APPLICATION_NAME RODC FILE_NAME ../src/monitoring/BusErrorCatcher.cpp FUNCTION_NAME virtual void* BusErrorCatcher::Main() LINE_NUMBER 107 DATE_TIME 1391519733 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 1815 THREAD_ID 2161 HOST_NAME largrod3 address 0x9000348 cycle D32 READ module ROD_05 |
|
14:15:12 ERROR RODC rcc::VmeBusError ERROR - Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000348 - APPLICATION: RODC - DATE: 2014/Feb/04 14:15:12 - PID: 1815 - HOST: largrod3 - QUALIFIERS: RodCrate - PACKAGE_NAME RodCrate APPLICATION_NAME RODC FILE_NAME ../src/plugins/BusErrorMonitor.cpp FUNCTION_NAME virtual bool BusErrorMonitor::AdviceAfter(const Larg::aop::OnlineJoinPoint*) LINE_NUMBER 78 DATE_TIME 1391519712 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 1815 THREAD_ID 2149 HOST_NAME largrod3 address 0x9000348 cycle D32 READ module ROD_05 |
|
1819855 - events only - frequency lowered to 0 |
|
/home/rod4/GENEVA/GenevaDAQ/v8r0/database/lar/slink/lar/partitions/Larg.data.xml Checking the consistency of the database ... to long check before starting |
14:01 |
109540 - events and rate decreased to 0 |
|
15:53:51 WARNING RODC rcc::VmeBusError Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000308 -- 10 similar messages suppressed, last occurrence was at 2014-Feb-04 15:53:48 |
|
time in computers is different |
|
restart of TDAQ and the crate |
31.01.2014 |
|
9:46 |
19 mio events build with 2.3 mio errors scrinshot and error files are moved ~/Olga/DataVerifyFiles/DataVerify_rod48_31012014.err |
9:50 |
new run started - no errors so far with VME bus |
18:31 |
15 mio without events without errors run is left |
|
|
30.01.2014 |
|
10:22 |
restart TDAQ |
|
Bring DefaultRootController to RUNNING state... FATAL 2014-Jan-30 10:19:39 [is::repository_var is::server::resolve(...) at is/src/server.cc:31] IS repository 'RunCtrl' does not exist was caused by: ERROR 2014-Jan-30 10:19:39 [CORBA::Object*ipc::util::resolve(...) at ipc/src/util.cc:369] The object "RunCtrl" of the "is/repository" type is not published in the "initial" partition ERROR: Controller for the initial partition did not reach RUNNING state; continuing anyway. |
10:23 |
run started |
12:13 |
observed stop of the work at ~317865 events without errors |
12:17 |
new run - stopped at 2866 events and the same errors |
14:13:58 |
WARNING RODC rcc::VmeBusError WARNING - Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000248 -- 10 similar messages suppressed, last occurrence was at 2014-Jan-30 14:13:55 - APPLICATION: RODC - DATE: 2014/Jan/30 14:13:58 - PID: 2472 - HOST: largrod3 - QUALIFIERS: RodCrate - PACKAGE_NAME RodCrate APPLICATION_NAME RODC FILE_NAME ../src/monitoring/BusErrorCatcher.cpp FUNCTION_NAME virtual void* BusErrorCatcher::Main() LINE_NUMBER 107 DATE_TIME 1391087638 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 2472 THREAD_ID 2816 HOST_NAME largrod3 address 0x9000248 cycle D32 READ module ROD_05 |
12:23 |
stop TDAQ - restart from skratch |
16:44 |
after restarting TDAQ it does not produce so many triggers - to restart once more and crate too - scrinshots done, no errors occured so far. |
16:50 |
restart of tdaq and crate - run started 802135 events build without errors so far and rate is null |
21:28 |
4112265 events without errors but see screenshot |
|
23:19:32 ERROR RODC rcc::VmeBusError ERROR - Receive BUS error, bad VMEbus D32 READ access of module 'ROD_05' at 0x9000308 - APPLICATION: RODC - DATE: 2014/Jan/30 23:19:32 - PID: 1770 - HOST: largrod3 - QUALIFIERS: RodCrate - PACKAGE_NAME RodCrate APPLICATION_NAME RODC FILE_NAME ../src/plugins/BusErrorMonitor.cpp FUNCTION_NAME virtual bool BusErrorMonitor::AdviceAfter(const Larg::aop::OnlineJoinPoint*) LINE_NUMBER 78 DATE_TIME 1391120372 USER_NAME rod4 CURRENT_WORK_DIR /tmp USER_ID 500 PROCESS_ID 1770 THREAD_ID 2101 HOST_NAME largrod3 address 0x9000308 cycle D32 READ module ROD_05 |