<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:14pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear <span>Håkan,</span></p>
<p><span><br>
</span></p>
<p><span>with diff = 1 the DAQ is running as long as only the VULOM4B is readout. Adding a SIS3316 module results in an readout error of that module, followed by a reset of the DAQ.<br>
</span></p>
<p><span><br>
</span></p>
<p><span>Thus, I am currently unable to test <span class="x_gl-new-dropdown-item-content">
<span class="x_gl-new-dropdown-item-text-wrapper">SIS3316_check_hit_reworked_rebased</span></span>. Sorry :-(<br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
</span></p>
<p><span>Best greetings</span></p>
<p><span>Günter<br>
</span></p>
<p><br>
</p>
<p><br>
</p>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T Johansson <f96hajo@chalmers.se><br>
<b>Gesendet:</b> Mittwoch, 17. Juli 2024 17:05:09<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] New warning meassage in R3BFUSER</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Dear Günter,<br>
<br>
We are in Hans' territory here, so I am a bit lost.<br>
<br>
Since g_counter_ms is not used elsewhere, you could try to replace<br>
<br>
diff = crate_counter_get_diff(g_counter_ms);<br>
<br>
with just<br>
<br>
diff = 1;<br>
<br>
and we see if the DAQ is willing to run. It might be that unpacking <br>
fails later with the SIS3316 enabled.<br>
<br>
Assuming this is the same error that hit also when the SIS3316 modules <br>
were enabled, the issue should (now) not be that there are no modules <br>
configured, but something else.<br>
<br>
And, if it runs, you could see if the SIS3316 modules are willing to <br>
start at least with that change.<br>
<br>
Cheers,<br>
Håkan<br>
<br>
<br>
<br>
On Wed, 17 Jul 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Håkan,<br>
> <br>
> <br>
> yes, the pointer g_counter_ms is zero.<br>
> <br>
> <br>
> <br>
> What should I do now?<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Best greetings<br>
> <br>
> Günter<br>
> <br>
> <br>
> <br>
> _________________________________________________________________________________________<br>
> Von: subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T Johansson<br>
> <f96hajo@chalmers.se><br>
> Gesendet: Montag, 15. Juli 2024 17:40:54<br>
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> Betreff: Re: [subexp-daq] New warning meassage in R3BFUSER <br>
> <br>
> Looks like it breaks in crate_counter_get_diff().<br>
> <br>
> Could you print also g_counter_ms before that line is reached.<br>
> <br>
> I'm getting the suspicion that it is NULL.<br>
> <br>
> Since the function is quite small:<br>
> <br>
> uint32_t<br>
> crate_counter_get_diff(struct CrateCounter const *a_counter)<br>
> {<br>
> return COUNTER_DIFF_RAW(a_counter->cur, a_counter->prev);<br>
> }<br>
> <br>
> and<br>
> <br>
> #define COUNTER_DIFF_RAW(c, raw)\<br>
> (((c).value - (raw)) & (c).mask)<br>
> <br>
> Cheers,<br>
> Håkan<br>
> <br>
> <br>
> <br>
> On Mon, 15 Jul 2024, Weber, Guenter Dr. wrote:<br>
> <br>
> ><br>
> > Here is what I did:<br>
> ><br>
> ><br>
> > printf("before block\n"); fflush(stdout);<br>
> ><br>
> > SUBEVENT_BEGIN(0, 0, event_buffer);<br>
> > printf("after SUBEVENT_BEGIN \n"); fflush(stdout);<br>
> > p32 = land_vme = event_buffer.ptr;<br>
> > printf("after p32 = land_vme = event_buffer.ptr -> %u \n", p32); fflush(stdout);<br>
> > *p32++ = LAND_VME_HAS_TIME_STAMP;<br>
> > printf("after *p32++ = LAND_VME_HAS_TIME_STAMP -> %u \n", p32); fflush(stdout);<br>
> > *p32++ = tt;<br>
> > printf("after *p32++ = tt -> %u \n", p32); fflush(stdout);<br>
> > {<br>
> > uint32_t diff;<br>
> ><br>
> > diff = crate_counter_get_diff(g_counter_ms);<br>
> > printf("after diff -> %u \n", diff); fflush(stdout);<br>
> > if (diff > 1 || g_cfg.mevent_flag) {<br>
> > *land_vme |= LAND_VME_MULTI_EVENT;<br>
> > *p32++ = diff;<br>
> > }<br>
> > }<br>
> > EVENT_BUFFER_ADVANCE(event_buffer, p32);<br>
> > printf("after EVENT_BUFFER_ADVANCE -> %u %u \n", event_buffer, p32);<br>
> fflush(stdout);<br>
> > ret |= crate_readout(g_crate, &event_buffer);<br>
> > SUBEVENT_END(event_buffer);<br>
> ><br>
> ><br>
> > And this is what we get:<br>
> ><br>
> ><br>
> > before block<br>
> > after SUBEVENT_BEGIN<br>
> > after p32 = land_vme = event_buffer.ptr -> 805691484<br>
> > after *p32++ = LAND_VME_HAS_TIME_STAMP -> 805691488<br>
> > after *p32++ = tt -> 805691492<br>
> > 1: lwroc_main.c:132: SIGSEGV received.<br>
> > 1: -:0: Backtrace:<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae32c]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ad68c]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae638]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6494]<br>
> > 1: -:0: [0x100344]<br>
> > 1: -:0: /lib/libc.so.6(fflush+0xb4) [0xfbd78bc]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100067a8]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x10073894]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6fb8]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a8058]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a69b0]<br>
> > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a5ee0]<br>
> > 1: -:0: /lib/libc.so.6 [0xfb91260]<br>
> > 1: -:0: /lib/libc.so.6 [0xfb913ec]<br>
> > 1: -:0: Backtrace (again, with addr2line):<br>
> > 1: -:0: lwroc_dump_backtrace/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:9<br>
> 51<br>
> > 1: -:0: lwroc_do_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 590<br>
> > 1: -:0: lwroc_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 692<br>
> > 1: -:0: lwroc_sighandler<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:132<br>
> > 1: -:0: ?? ??:0<br>
> > 1: -:0: ?? ??:0<br>
> > 1: -:0: f_user_readout /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser/f_user.c:987<br>
> > 1: -:0: fud_read_event<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/f_user_daq/f_user_daq.c:607<br>
> > 1: -:0: lwroc_triva_event_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:463<br>
> > 1: -:0: lwroc_triva_readout<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:818<br>
> > 1: -:0: lwroc_main_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_readout.c:153<br>
> > 1: -:0: main<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:712<br>
> > 1: -:0: ?? ??:0<br>
> > 1: -:0: ?? ??:0<br>
> > 1: -:0: BUG or FATAL reported.<br>
> > 1: -:0: Sleeping INDEFINITELY (to allow debugger attachment).<br>
> > 1: -:0: Debug cmd: cd /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/rio4-mcal-1 ;<br>
> gdb ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 25615<br>
> > 1: -:0: Performing hardware cleanup (TRIVA HALT, RESET) in 2 s...<br>
> > 8: lwroc_triva_state.c:1999: Master TRIVA/MI has error (status = 0x410).<br>
> > 8: lwroc_triva_state.c:2708: Issue during test/run (33), tell master and slaves to<br>
> abort.<br>
> > Send slave abort readout. (1)<br>
> > Send master abort (0x200).<br>
> ><br>
> ><br>
> >________________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> ________________<br>
> > Von: subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T Johansson<br>
> <f96hajo@chalmers.se><br>
> > Gesendet: Montag, 15. Juli 2024 16:50:45<br>
> > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> > Betreff: Re: [subexp-daq] New warning meassage in R3BFUSER <br>
> > On Mon, 15 Jul 2024, Weber, Guenter Dr. wrote:<br>
> ><br>
> > > Dear Håkan,<br>
> > ><br>
> > ><br>
> > > my f_user.c has the identical block at the identical position.<br>
> > ><br>
> > ><br>
> > > Removing the STRUCK modules from main.cfg does not change the situation:<br>
> ><br>
> > That at least removes a lot of unknowns from the equation. ;)<br>
> ><br>
> > Could you add a bunch of<br>
> ><br>
> > printf("a...\n"); fflush(stdout);<br>
> ><br>
> > on the lines around that block, se we know better exactly where it<br>
> > crashes? And then if that brings it down, also start to print pointer<br>
> > values (before their use).<br>
> ><br>
> > With the backtrace, it is also a bit unclear if it actually is failing on<br>
> > the line above or below...<br>
> ><br>
> > Cheers,<br>
> > Håkan<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ><br>
> > ><br>
> > > 10: crate/crate.c:1196: crate_init(MCAL) }<br>
> > > 10: ctrl/ctrl.c:1046: Control server online.<br>
> > > Message not logged - thread has no error buffer yet...<br>
> > > 10: f_user.c:559: WR ID=0x200.<br>
> > > 10: f_user.c:565: TS offset unset. Will not modify stamp.<br>
> > > 10: f_user.c:572: TPAT: No.<br>
> > > 10: f_user.c:573: Sync-check: No.<br>
> > > 10: f_user.c:575: Spill triggers: No.<br>
> > > 10: f_user.c:576: LMU: No.<br>
> > > 10: f_user.c:577: Timer latches: No.<br>
> > > 10: f_user.c:578: Spill shape: No.<br>
> > > 10: f_user.c:579: Micro-structure: No.<br>
> > > 10: f_user.c:581: Multi-event flag: No.<br>
> > > 10: f_user.c:586: UDP destination: None.<br>
> > > 1: lwroc_main.c:132: SIGSEGV received.<br>
> > > 1: -:0: Backtrace:<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae20c]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ad56c]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae518]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6374]<br>
> > > 1: -:0: [0x100344]<br>
> > > 1: -:0: [(nil)]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100066c0]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x10073774]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6e98]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a7f38]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6890]<br>
> > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a5dc0]<br>
> > > 1: -:0: /lib/libc.so.6 [0xfb91260]<br>
> > > 1: -:0: /lib/libc.so.6 [0xfb913ec]<br>
> > > 1: -:0: Backtrace (again, with addr2line):<br>
> > > 1: -:0: lwroc_dump_backtrace/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:9<br>
> 51<br>
> > > 1: -:0: lwroc_do_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 590<br>
> > > 1: -:0: lwroc_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 692<br>
> > > 1: -:0: lwroc_sighandler<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:132<br>
> > > 1: -:0: ?? ??:0<br>
> > > sh: -c: line 0: syntax error near unexpected token `('<br>
> > > sh: -c: line 0: `addr2line -a -f -i -C -p (nil) -e<br>
> ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 2> /dev/null'<br>
> > > sh: -c: line 0: syntax error near unexpected token `('<br>
> > > sh: -c: line 0: `addr2line -i -f -C (nil) -e<br>
> ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 2> /dev/null'<br>
> > > 1: -:0: f_user_readout<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser/f_user.c:975<br>
> > > 1: -:0: fud_read_event<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/f_user_daq/f_user_daq.c:607<br>
> > > 1: -:0: lwroc_triva_event_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:463<br>
> > > 1: -:0: lwroc_triva_readout<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:818<br>
> > > 1: -:0: lwroc_main_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_readout.c:153<br>
> > > 1: -:0: main<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:712<br>
> > > 1: -:0: ?? ??:0<br>
> > > 1: -:0: ?? ??:0<br>
> > > 1: -:0: Backtrace (again, addresses):<br>
> > > 1: -:0: 0x0x100ae20c:<br>
> > > 1: -:0: 0x0x100ad56c:<br>
> > > 1: -:0: 0x0x100ae518:<br>
> > > 1: -:0: 0x0x100a6374:<br>
> > > 1: -:0: 0x0x100344:<br>
> > > 1: -:0: 0x(nil):<br>
> > > 1: -:0: 0x0x100066c0:<br>
> > > 1: -:0: 0x0x10073774:<br>
> > > 1: -:0: 0x0x100a6e98:<br>
> > > 1: -:0: 0x0x100a7f38:<br>
> > > 1: -:0: 0x0x100a6890:<br>
> > > 1: -:0: 0x0x100a5dc0:<br>
> > > 1: -:0: 0x0xfb91260:<br>
> > > 1: -:0: 0x0xfb913ec:<br>
> > > 1: -:0: BUG or FATAL reported.<br>
> > > 1: -:0: Sleeping INDEFINITELY (to allow debugger attachment).<br>
> > > 1: -:0: Debug cmd: cd /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/rio4-mcal-1 ;<br>
> gdb ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 25186<br>
> > > 1: -:0: Performing hardware cleanup (TRIVA HALT, RESET) in 2 s...<br>
> > > 8: lwroc_triva_state.c:1999: Master TRIVA/MI has error (status = 0x410).<br>
> > > 8: lwroc_triva_state.c:2708: Issue during test/run (33), tell master and slaves to<br>
> abort.<br>
> > > Send slave abort readout. (1)<br>
> > > Send master abort (0x200).<br>
> > > 10: lwroc_triva_control.c:863: TRIVA control: run abort request received.<br>
> > > 9: lwroc_triva_control.c:1032: TRIVA control: run aborted - waiting for readout...<br>
> > > 8: lwroc_triva_state.c:414: Waited 1 seconds for master/slaves to abort test/readout:<br>
> > > 8: lwroc_triva_state.c:422: [??conn (this)] (state 13)<br>
> > > 1: -:0: Hardware cleanup done.<br>
> > > 8: lwroc_triva_state.c:414: Waited 5 seconds for master/slaves to abort test/readout:<br>
> > > 8: lwroc_triva_state.c:422: [??conn (this)] (state 13)<br>
> > > ^C8: lwroc_main.c:105: SIGINT received.<br>
> > > 10: lwroc_thread_util.c:62: Set terminate first! (main)<br>
> > > ^C8: lwroc_main.c:105: SIGINT received.<br>
> > > ^C5: lwroc_main.c:109: 3rd signal SIGINT received.<br>
> > ><br>
> > > Attached please find the files you asked for.<br>
> > ><br>
> > ><br>
> > ><br>
> > > Would be really great if you could figure out what is happening.<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > Best greetings from Jena<br>
> > ><br>
> > > Günter<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > Looks like the issue might be at:<br>
> > ><br>
> > > 1: -:0: f_user_readout<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser/f_user.c:975<br>
> > ><br>
> > > which for me is:<br>
> > ><br>
> > > p32 = land_vme = event_buffer.ptr;<br>
> > ><br>
> > > part of a block of code:<br>
> > ><br>
> > > SUBEVENT_BEGIN(0, 0, event_buffer);<br>
> > > p32 = land_vme = event_buffer.ptr;<br>
> > > *p32++ = LAND_VME_HAS_TIME_STAMP;<br>
> > > *p32++ = tt;<br>
> > ><br>
> > > or possibly some function that it calls.<br>
> > ><br>
> > > You have the same code at that line?<br>
> > ><br>
> > > Could you also send the daq startup script and the nurdlib<br>
> > > configuration file?<br>
> > ><br>
> > > Cheers,<br>
> > > Håkan<br>
> > ><br>
> > ><br>
> > > On Mon, 15 Jul 2024, Weber, Guenter Dr. wrote:<br>
> > ><br>
> > > ><br>
> > > > Dear friends,<br>
> > > ><br>
> > > ><br>
> > > > unfortunately, the DAQ crashes on startup. Here is the output:<br>
> > > ><br>
> > > ><br>
> > > > 10: lwroc_hostname_util.c:109: Host 'lyserv' known as 192.168.1.1 (port: 56583).<br>
> > > > Message not logged - thread has no error buffer yet...<br>
> > > > CPUS: 1<br>
> > > > delay: 1<br>
> > > > 10: lwroc_hostname_util.c:109: Host 'lyserv' known as 192.168.1.1 (port: 56583).<br>
> > > > Message not logged - thread has no error buffer yet...<br>
> > > > HOST: RIO4-MCAL-1<br>
> > > > Token: d6d68d7b (d6d68d7b:d6d68d7b) [/mbsusr/mbsdaq/.drasi_tokens/mcal]<br>
> > > > 10: lwroc_hostname_util.c:460: Own address: 192.168.1.71/255.255.255.0 (eth1).<br>
> > > > 10: lwroc_data_pipe.c:146: Data buffer READOUT_PIPE, fmt LMD, size 419430400 =<br>
> 0x19000000, 1 consumers.<br>
> > > > 10: lwroc_triva_readout.c:66: Silence TRIVA (HALT)<br>
> > > > 10: lwroc_net_io.c:172: Started server on port 56583 (data port 35797).<br>
> > > > client union size: 244 240 188 508 640 204 204 => 640<br>
> > > > 10: lwroc_udp_awaken_hints.c:159: UDP awaken hints file:<br>
> /tmp/drasi.u1001/drasi.hints.u1001.RIO4-MCAL-1:56583<br>
> > > > 10: lwroc_main.c:704: Log message rate limit in effect.<br>
> > > > 10: lwroc_readout.c:116: call readout_init...<br>
> > > > 10: lwroc_thread_util.c:118: This is the triva control thread!<br>
> > > > 10: lwroc_thread_util.c:118: This is the net io thread!<br>
> > > > 10: lwroc_thread_util.c:118: This is the slow_async thread!<br>
> > > > 10: lwroc_thread_util.c:118: This is the data server thread!<br>
> > > > 8: lwroc_message_wait.c:86: Waited 1 seconds for msg client.<br>
> > > > 8: lwroc_triva_state.c:414: Waited 1 seconds for initial slave and EB<br>
> connection(s):<br>
> > > > 8: lwroc_triva_state.c:422: [EB lyserv] (state 0)<br>
> > > > 10: lwroc_message_internal.c:485: Message client connected!<br>
> > > > 10: lwroc_net_trans.c:1234: [drasi] Transport client connected (data)<br>
> [192.168.1.1].<br>
> > > > 10: lwroc_triva_control.c:370: Setup TRIVA (DISBUS, HALT, MASTER, RESET)<br>
> > > > 10: lwroc_triva_control.c:418: Minimum event time<br>
> ctime(350000)+1*rd(690)+3*wr(633)+fctime(1000)=353589 ns (2.828 kHz)<br>
> > > > 10: lwroc_triva_state.c:1486: (Re)send ident messages...<br>
> > > > 10: lwroc_triva_control.c:495: START TEST ACQ: HALT, CLEAR=RESET, MT=1<br>
> > > > 9: lwroc_triva_control.c:507: TEST: GO<br>
> > > > 10: lwroc_triva_control.c:725: RUN: RESET<br>
> > > > 10: lwroc_triva_control.c:729: RUN: MT=14<br>
> > > > 9: lwroc_triva_control.c:737: GO (1 good test triggers done) (max 2.8 kHz)<br>
> > > > 10: lwroc_triva_readout.c:376: Trigger 14 seen.<br>
> > > > 10: config/config.c:205: Will try default cfg<br>
> path='/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default', can be set<br>
> with NURDLIB_DEF_PATH.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 10: config/parser.c:319: Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/global.cfg' {<br>
> > > > 10: config/parser.c:331: Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/global.cfg' }<br>
> > > > 10: config/parser.c:319: Opened './main.cfg' {<br>
> > > > 10: config/config.c:1388: .Global log level=verbose.<br>
> > > > 10: config/parser.c:319: .Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/crate.cfg' {<br>
> > > > 10: config/parser.c:331: .Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/crate.cfg' }<br>
> > > > 10: config/parser.c:319: .Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/gsi_vulom.cfg' {<br>
> > > > 10: config/parser.c:331: .Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/gsi_vulom.cfg' }<br>
> > > > 10: config/parser.c:319: .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' {<br>
> > > > 10: config/parser.c:331: .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' }<br>
> > > > 10: config/parser.c:319: .Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' {<br>
> > > > 10: config/parser.c:331: .Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' }<br>
> > > > 10: config/parser.c:319: .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' {<br>
> > > > 10: config/parser.c:331: .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' }<br>
> > > > 10: config/parser.c:319: .Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' {<br>
> > > > 10: config/parser.c:331: .Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' }<br>
> > > > 10: config/parser.c:319: .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' {<br>
> > > > 10: config/parser.c:331: .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' }<br>
> > > > 10: config/parser.c:319: .Opened<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' {<br>
> > > > 10: config/parser.c:331: .Closed<br>
> '/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/sis_3316.cfg' }<br>
> > > > 10: config/parser.c:319: .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' {<br>
> > > > 10: config/parser.c:331: .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/nurdlib/cfg/default/module_log_level.<br>
> cfg' }<br>
> > > > 10: config/parser.c:331: Closed './main.cfg' }<br>
> > > > 10: crate/crate.c:373: crate_create {<br>
> > > > 10: crate/crate.c:714: crate_create(MCAL) }<br>
> > > > 10: crate/crate.c:1022: crate_init(MCAL) {<br>
> > > > 10: crate/crate.c:1046: .Slow-init module[0]=GSI_VULOM.<br>
> > > > LOG: TRLO: MD5SUM: 0x1409285e (CT: 63bb1d44 = 2023-01-08 19:45:08 UTC)<br>
> > > > 10: crate/crate.c:1046: .Slow-init module[1]=SIS_3316.<br>
> > > > 10: module/map/map.c:286: ...rd(0x30000000+0x64/32)=532ns<br>
> wr(0x30000000+0x64/32)=356ns.<br>
> > > > 10: module/sis_3316/sis_3316.c:1481: ..Serial number=0x00800178.<br>
> > > > 10: module/sis_3316/sis_3316.c:1488: ..id/firmware=0x3316200e.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[0] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[1] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[2] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[3] firmware=0x0125000c.<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime. <br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 10: crate/crate.c:1046: .Slow-init module[2]=SIS_3316.<br>
> > > > 10: module/map/map.c:286: ...rd(0x31000000+0x64/32)=528ns<br>
> wr(0x31000000+0x64/32)=359ns.<br>
> > > > 10: module/sis_3316/sis_3316.c:1481: ..Serial number=0x008001a7.<br>
> > > > 10: module/sis_3316/sis_3316.c:1488: ..id/firmware=0x33162010.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[0] firmware=0x01250011.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[1] firmware=0x01250011.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[2] firmware=0x01250011.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[3] firmware=0x01250011.<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 10: crate/crate.c:1046: .Slow-init module[3]=SIS_3316.<br>
> > > > 10: module/map/map.c:286: ...rd(0x32000000+0x64/32)=564ns<br>
> wr(0x32000000+0x64/32)=399ns.<br>
> > > > 10: module/sis_3316/sis_3316.c:1481: ..Serial number=0x00800171.<br>
> > > > 10: module/sis_3316/sis_3316.c:1488: ..id/firmware=0x3316200e.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[0] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[1] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[2] firmware=0x0125000c.<br>
> > > > 10: module/sis_3316/sis_3316.c:1491: ..adc[3] firmware=0x0125000c.<br>
> > > > 10: crate/crate.c:1099: .Fast-init module[0]=GSI_VULOM.<br>
> > > > 10: crate/crate.c:1099: .Fast-init module[1]=SIS_3316.<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[0] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[1] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[2] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[3] = 15 mV -> 0x080001f3<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[4] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[5] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[6] = 10 mV -> 0x0800014c<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[7] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[8] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[9] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[10] = 13 mV -> 0x080001b0<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[11] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[12] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[13] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[14] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[15] = 15 mV -> 0x080001f3<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 10: crate/crate.c:1099: .Fast-init module[2]=SIS_3316.<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[0] = 10 mV -> 0x0800014c<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[1] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[2] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[3] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[4] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[5] = 10 mV -> 0x0800014c<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[6] = 13 mV -> 0x080001b0<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[7] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[8] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[9] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[10] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[11] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[12] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[13] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[14] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[15] = 8 mV -> 0x0800010a<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 1<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 10: crate/crate.c:1099: .Fast-init module[3]=SIS_3316.<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[0] = 10 mV -> 0x0800014c<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[1] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[2] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[3] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[4] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[5] = 10 mV -> 0x0800014c<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[6] = 13 mV -> 0x080001b0<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[7] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[8] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[9] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[10] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[11] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[12] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[13] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[14] = 8 mV -> 0x0800010a<br>
> > > > 10: module/sis_3316/sis_3316.c:4380: ...threshold[15] = 8 mV -> 0x0800010a<br>
> > > > 10: crate/crate.c:1131: .Post-init module[1]=SIS_3316.<br>
> > > > 10: crate/crate.c:1131: .Post-init module[2]=SIS_3316.<br>
> > > > 10: crate/crate.c:1131: .Post-init module[3]=SIS_3316.<br>
> > > > 10: crate/crate.c:1196: crate_init(MCAL) }<br>
> > > > 10: ctrl/ctrl.c:1046: Control server online.<br>
> > > > Message not logged - thread has no error buffer yet...<br>
> > > > 10: f_user.c:559: WR ID=0x200.<br>
> > > > 10: f_user.c:565: TS offset unset. Will not modify stamp.<br>
> > > > 10: f_user.c:572: TPAT: No.<br>
> > > > 10: f_user.c:573: Sync-check: No.<br>
> > > > 10: f_user.c:575: Spill triggers: No.<br>
> > > > 10: f_user.c:576: LMU: No.<br>
> > > > 10: f_user.c:577: Timer latches: No.<br>
> > > > 10: f_user.c:578: Spill shape: No.<br>
> > > > 10: f_user.c:579: Micro-structure: No.<br>
> > > > 10: f_user.c:581: Multi-event flag: No.<br>
> > > > 10: f_user.c:586: UDP destination: None.<br>
> > > > 1: lwroc_main.c:132: SIGSEGV received.<br>
> > > > 1: -:0: Backtrace:<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae20c]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ad56c]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100ae518]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6374]<br>
> > > > 1: -:0: [0x100344]<br>
> > > > 1: -:0: [(nil)]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100066c0]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x10073774]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6e98]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a7f38]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a6890]<br>
> > > > 1: -:0: ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi [0x100a5dc0]<br>
> > > > 1: -:0: /lib/libc.so.6 [0xfb91260]<br>
> > > > 1: -:0: /lib/libc.so.6 [0xfb913ec]<br>
> > > > 1: -:0: Backtrace (again, with addr2line):<br>
> > > > 1: -:0: lwroc_dump_backtrace/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:9<br>
> 51<br>
> > > > 1: -:0: lwroc_do_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 590<br>
> > > > 1: -:0: lwroc_message_internal/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_message_internal.c:1<br>
> 692<br>
> > > > 1: -:0: lwroc_sighandler<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:132<br>
> > > > 1: -:0: ?? ??:0<br>
> > > > sh: -c: line 0: syntax error near unexpected token `('<br>
> > > > sh: -c: line 0: `addr2line -a -f -i -C -p (nil) -e<br>
> ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 2> /dev/null'<br>
> > > > sh: -c: line 0: syntax error near unexpected token `('<br>
> > > > sh: -c: line 0: `addr2line -i -f -C (nil) -e<br>
> ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 2> /dev/null'<br>
> > > > 1: -:0: f_user_readout<br>
> /mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/r3bfuser/f_user.c:975<br>
> > > > 1: -:0: fud_read_event<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/f_user_daq/f_user_daq.c:607<br>
> > > > 1: -:0: lwroc_triva_event_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:463<br>
> > > > 8: lwroc_triva_state.c:2028: Master TRIVA/MI no progress last second, and in<br>
> deadtime.<br>
> > > > 8: lwroc_triva_state.c:2399: Master: deadtime: 1. Status: 0x10 (IN_READOUT). EC:<br>
> 2<br>
> > > > 10: lwroc_triva_state.c:2428: [EB lyserv] EB: Status: 0x0.<br>
> > > > 8: lwroc_triva_state.c:2488: Node(s) busy in readout, waiting...<br>
> > > > 1: -:0: lwroc_triva_readout<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_triva_readout.c:818<br>
> > > > 1: -:0: lwroc_main_loop<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_readout.c:153<br>
> > > > 1: -:0: main<br>
> /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/drasi/lwroc/lwroc_main.c:712<br>
> > > > 1: -:0: ?? ??:0<br>
> > > > 1: -:0: ?? ??:0<br>
> > > > 1: -:0: Backtrace (again, addresses):<br>
> > > > 1: -:0: 0x0x100ae20c:<br>
> > > > 1: -:0: 0x0x100ad56c:<br>
> > > > 1: -:0: 0x0x100ae518:<br>
> > > > 1: -:0: 0x0x100a6374:<br>
> > > > 1: -:0: 0x0x100344:<br>
> > > > 1: -:0: 0x(nil):<br>
> > > > 1: -:0: 0x0x100066c0:<br>
> > > > 1: -:0: 0x0x10073774:<br>
> > > > 1: -:0: 0x0x100a6e98:<br>
> > > > 1: -:0: 0x0x100a7f38:<br>
> > > > 1: -:0: 0x0x100a6890:<br>
> > > > 1: -:0: 0x0x100a5dc0:<br>
> > > > 1: -:0: 0x0xfb91260:<br>
> > > > 1: -:0: 0x0xfb913ec:<br>
> > > > 1: -:0: BUG or FATAL reported.<br>
> > > > 1: -:0: Sleeping INDEFINITELY (to allow debugger attachment).<br>
> > > > 1: -:0: Debug cmd: cd /LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2024_mcalstruck/rio4-mcal-1<br>
> ; gdb ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi 19740<br>
> > > > 1: -:0: Performing hardware cleanup (TRIVA HALT, RESET) in 2 s...<br>
> > > > 8: lwroc_triva_state.c:1999: Master TRIVA/MI has error (status = 0x410).<br>
> > > > 8: lwroc_triva_state.c:2708: Issue during test/run (33), tell master and slaves to<br>
> abort.<br>
> > > > Send slave abort readout. (1)<br>
> > > > Send master abort (0x200).<br>
> > > > 10: lwroc_triva_control.c:863: TRIVA control: run abort request received.<br>
> > > > 9: lwroc_triva_control.c:1032: TRIVA control: run aborted - waiting for readout...<br>
> > > > 8: lwroc_triva_state.c:414: Waited 1 seconds for master/slaves to abort<br>
> test/readout:<br>
> > > > 8: lwroc_triva_state.c:422: [??conn (this)] (state 13)<br>
> > > > 1: -:0: Hardware cleanup done.<br>
> > > > 8: lwroc_triva_state.c:414: Waited 5 seconds for master/slaves to abort<br>
> test/readout:<br>
> > > > 8: lwroc_triva_state.c:422: [??conn (this)] (state 13)<br>
> > > > 8: lwroc_triva_state.c:414: Waited 10 seconds for master/slaves to abort<br>
> test/readout:<br>
> > > > 8: lwroc_triva_state.c:422: [??conn (this)] (state 13)<br>
> > > > ^C8: lwroc_main.c:105: SIGINT received.<br>
> > > > 10: lwroc_thread_util.c:62: Set terminate first! (main)<br>
> > > > ^C8: lwroc_main.c:105: SIGINT received.<br>
> > > > ^C5: lwroc_main.c:109: 3rd signal SIGINT received.<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Looks like DRASI still has a problem ??<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Best greetings<br>
> > > ><br>
> > > > Günter<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> >>>______________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> ________________<br>
> > _<br>
> > > _<br>
> > > > Von: subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Weber,<br>
> Guenter Dr. <g.weber@hi-jena.gsi.de><br>
> > > > Gesendet: Montag, 15. Juli 2024 16:02:57<br>
> > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> > > > Betreff: Re: [subexp-daq] New warning meassage in R3BFUSER <br>
> > > ><br>
> > > > Dear Håkan,<br>
> > > ><br>
> > > ><br>
> > > > thank you for the reply.<br>
> > > ><br>
> > > ><br>
> > > > After implementing the suggested changes, I now get the following warning (on PC):<br>
> > > ><br>
> > > ><br>
> > > > (base) mbsdaq@atpnbg011:~/mbsrun/rio4/2024_mcalstruck/r3bfuser$ make fuser_drasi<br>
> > > > NCONF build_cc_x86_64-linux-gnu_7_debug/nconf.args<br>
> > > > For nconf results and logs, see also build_cc_x86_64-linux-gnu_7_debug/nconf*.<br>
> > > > UDP:ARPA_INET_H<br>
> > > > build_cc_x86_64-linux-gnu_7_debug/nconf.args done.<br>
> > > > CC build_cc_x86_64-linux-gnu_7_debug/subevent.drasi.o<br>
> > > > CC build_cc_x86_64-linux-gnu_7_debug/f_user.drasi.o<br>
> > > > f_user.c: In function ‘f_user_init’:<br>
> > > > f_user.c:697:2: warning: null argument where non-null required (argument 3)<br>
> [-Wnonnull]<br>
> > > > crate_dt_release_set_func(g_crate, dt_release, NULL);<br>
> > > > ^~~~~~~~~~~~~~~~~~~~~~~~~<br>
> > > > CC build_cc_x86_64-linux-gnu_7_debug/udp.drasi.o<br>
> > > > LD build_cc_x86_64-linux-gnu_7_debug/m_read_meb.drasi<br>
> > > > build_cc_x86_64-linux-gnu_7_debug: Simon says: Alles wird gut ;o)<br>
> > > ><br>
> > > > On the RIO4 there is no warning:<br>
> > > ><br>
> > > ><br>
> > > > RIO4-MCAL-1 mbsdaq > make fuser_drasi<br>
> > > > NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
> > > > For nconf results and logs, see also build_cc_ppc-linux_4.2.2_debug/nconf*.<br>
> > > > UDP:ARPA_INET_H<br>
> > > > build_cc_ppc-linux_4.2.2_debug/nconf.args done.<br>
> > > > CC build_cc_ppc-linux_4.2.2_debug/f_user.drasi.o<br>
> > > > CC build_cc_ppc-linux_4.2.2_debug/subevent.drasi.o<br>
> > > > CC build_cc_ppc-linux_4.2.2_debug/udp.drasi.o<br>
> > > > LD build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi<br>
> > > > build_cc_ppc-linux_4.2.2_debug: Simon says: Alles wird gut ;o)<br>
> > > ><br>
> > > > In a few minutes I can tell you if the DAQ is running with the new software or not.<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > Best greetings<br>
> > > ><br>
> > > > Günter<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> >>>______________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> _______________________________________________________________________________________<br>
> ________________<br>
> > _<br>
> > > _<br>
> > > > Von: subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T<br>
> Johansson <f96hajo@chalmers.se><br>
> > > > Gesendet: Montag, 15. Juli 2024 15:49:23<br>
> > > > An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
> > > > Betreff: Re: [subexp-daq] New warning meassage in R3BFUSER <br>
> > > ><br>
> > > > Dear Günter,<br>
> > > ><br>
> > > > it looks like with a change of the second parameter of log_callback (both<br>
> > > > in prototype an definition) of r3bfuser/f_user.c from unsigned to int,<br>
> > > > then in compiles.<br>
> > > ><br>
> > > > Likely caused by commit '36772113' in nurdlib that changed line numbers<br>
> > > > from unsigned to int.<br>
> > > ><br>
> > > > Cheers,<br>
> > > > Håkan<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > On Mon, 15 Jul 2024, Weber, Guenter Dr. wrote:<br>
> > > ><br>
> > > > ><br>
> > > > > Dear all,<br>
> > > > ><br>
> > > > ><br>
> > > > > I just set up a new DAQ system (new NURDLIB, TRLOII, DRASI, R3BFUSER, etc.).<br>
> > > > ><br>
> > > > ><br>
> > > > > I followed the 'cooking receipt' that I git from Hakan, as always.<br>
> > > > ><br>
> > > > ><br>
> > > > > When compiling fuser_drasi, the following happens (on PC):<br>
> > > > ><br>
> > > > ><br>
> > > > > (base) mbsdaq@atpnbg011:~/mbsrun/rio4/2024_mcalstruck/r3bfuser$ make<br>
> > > > > fuser_drasi<br>
> > > > > NCONF build_cc_x86_64-linux-gnu_7_debug/nconf.args<br>
> > > > > For nconf results and logs, see also<br>
> > > > > build_cc_x86_64-linux-gnu_7_debug/nconf*.<br>
> > > > > UDP:ARPA_INET_H<br>
> > > > > build_cc_x86_64-linux-gnu_7_debug/nconf.args done.<br>
> > > > > CC build_cc_x86_64-linux-gnu_7_debug/subevent.drasi.o<br>
> > > > > CC build_cc_x86_64-linux-gnu_7_debug/f_user.drasi.o<br>
> > > > > f_user.c: In function ‘f_user_init’:<br>
> > > > > f_user.c:682:26: warning: passing argument 1 of ‘nurdlib_setup’ from<br>
> > > > > incompatible pointer type [-Wincompatible-pointer-types]<br>
> > > > > g_crate = nurdlib_setup(log_callback, path);<br>
> > > > > ^~~~~~~~~~~~<br>
> > > > > In file included from f_user.c:15:0:<br>
> > > > > ../nurdlib/include/nurdlib.h:28:15: note: expected ‘LogCallback {aka void<br>
> > > > > (*)(const char *, int, unsigned int, const char *)}’ but argument is of<br>
> > > > > type ‘void (*)(const char *, unsigned int, unsigned int, const char *)’<br>
> > > > > struct Crate *nurdlib_setup(LogCallback, char const *) FUNC_RETURNS;<br>
> > > > > ^~~~~~~~~~~~~<br>
> > > > > f_user.c:697:2: warning: null argument where non-null required (argument 3)<br>
> > > > > [-Wnonnull]<br>
> > > > > crate_dt_release_set_func(g_crate, dt_release, NULL);<br>
> > > > > ^~~~~~~~~~~~~~~~~~~~~~~~~<br>
> > > > > CC build_cc_x86_64-linux-gnu_7_debug/udp.drasi.o<br>
> > > > > LD build_cc_x86_64-linux-gnu_7_debug/m_read_meb.drasi<br>
> > > > > build_cc_x86_64-linux-gnu_7_debug: Simon says: Alles wird gut ;o)<br>
> > > > ><br>
> > > > ><br>
> > > > > On the RIO4 the warning is a bit less detailed:<br>
> > > > ><br>
> > > > ><br>
> > > > > RIO4-MCAL-1 mbsdaq > make fuser_drasi<br>
> > > > > NCONF build_cc_ppc-linux_4.2.2_debug/nconf.args<br>
> > > > > For nconf results and logs, see also build_cc_ppc-linux_4.2.2_debug/nconf*.<br>
> > > > > UDP:ARPA_INET_H<br>
> > > > > build_cc_ppc-linux_4.2.2_debug/nconf.args done.<br>
> > > > > CC build_cc_ppc-linux_4.2.2_debug/f_user.drasi.o<br>
> > > > > f_user.c: In function 'f_user_init':<br>
> > > > > f_user.c:682: warning: passing argument 1 of 'nurdlib_setup' from<br>
> > > > > incompatible pointer type<br>
> > > > > CC build_cc_ppc-linux_4.2.2_debug/subevent.drasi.o<br>
> > > > > CC build_cc_ppc-linux_4.2.2_debug/udp.drasi.o<br>
> > > > > LD build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi<br>
> > > > > build_cc_ppc-linux_4.2.2_debug: Simon says: Alles wird gut ;o)<br>
> > > > ><br>
> > > > > Any ideas what might have happened here? Or is this normal behaviour?<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > Many thanks!<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > Best greetings<br>
> > > > ><br>
> > > > > Günter<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > ><br>
> > > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
> <br>
></div>
</span></font>
</body>
</html>