From: Frank Geurts (geurts_at_rice.edu)
Date: Fri Mar 07 2003 - 16:18:25 EST
-------- Original Message --------
Subject: Re: FYI: L2 latencies
Date: Fri, 7 Mar 2003 14:54:01 -0500
From: "Frank Geurts" <geurts_at_rice.edu>
Reply-To: startrig-hn_at_connery.star.bnl.gov
To: startrig-hn_at_connery.star.bnl.gov
Newsgroups: http://www.star.bnl.gov/HyperNews-star/get/startrig.html
Zoran Milosevich wrote:
> i'm a little confused. this message was sent today, and talks about
runs from
> last night, yet gives log information from the previous night.
no confusion here: the message is sent today, correct. What triggered
going through the det.log files was an alleged tof problem last night
(turned out to be L3) and the excerpt from the log file is from Thursday
March 6 at 8h34 AM and concerns run 4065011 ...
> do you see problems
> after about run 4065050? if so, please let me know which run number.
yes, i can see them for runs after 4065050 as well. Below is a dump of
run 4065052 (the first physics run after pedestal runs 50 and 51). This
remains much like this for all the following runs.
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2209, lost a L2 Accept/Abort
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2210, lost a L2 Accept/Abort
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2211, lost a L2 Accept/Abort
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 1539]: L2
Accept with L0 2212, L2 2209, LAMG 1, buffer 211
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 1539]: L2
Accept with L0 2212, L2 2210, LAMG 1, buffer 212
[tof02 20:10:09] (getdata): WARNING: getdata.cxx [line 1539]: L2
Accept with L0 2212, L2 2211, LAMG 1, buffer 213
[tof01 20:10:09] (main): WARNING: sbMain.C [line 2058]: Release on
error (1) pending - releaseing
[tof01 20:10:09] (main): WARNING: sbMain.C [line 2058]: Release on
error (1) pending - releaseing
[tof01 20:10:09] (main): WARNING: sbMain.C [line 2058]: Release on
error (1) pending - releaseing
[tof01 20:10:10] (main): WARNING: sbMain.C [line 650]: RLS: no token
2209 (task 20) - responding immediatelly
[tof01 20:10:10] (main): WARNING: sbMain.C [line 650]: RLS: no token
2210 (task 20) - responding immediatelly
[tof01 20:10:10] (main): WARNING: sbMain.C [line 650]: RLS: no token
2211 (task 20) - responding immediatelly
[tof02 20:10:11] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2320, lost a L2 Accept/Abort
[tof02 20:10:24] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2863, lost a L2 Accept/Abort
[tof02 20:10:24] (getdata): WARNING: getdata.cxx [line 927]: time-out
for token 2864, lost a L2 Accept/Abort
[tof02 20:10:24] (getdata): WARNING: getdata.cxx [line 1539]: L2
Accept with L0 2865, L2 2863, LAMG 0, buffer 117
[tof02 20:10:24] (getdata): WARNING: getdata.cxx [line 1539]: L2
Accept with L0 2865, L2 2864, LAMG 0, buffer 118
> thanks,
> zoran
>
>
> Jeff Landgraf wrote:
>
>
>>---------- Forwarded message ----------
>>Date: Fri, 07 Mar 2003 11:47:30 -0600
>>From: Frank Geurts <geurts_at_rice.edu>
>>To: Tonko A. Ljubicic <tonko_at_bnl.gov>, Jeff Landgraf <jml_at_bnl.gov>
>>Cc: tofp_at_physics.rice.edu
>>Subject: FYI: L2 latencies
>>
>>Hi guys,
>> after the alleged tof problem this night I looked again through the
>>log files and could still see many, many very late l2 accepts. As you
>>know, TOF typically time-outs an L0 token if an L2-accept/abort has not
>>been received w/i 100ms. I think the following piece of the log file
>>(filtered for TOF only) might give you some better diagnostics.
>>
>> (from the Thursday March 6)
>>
>>[tof02 08:34:27] (getdata): WARNING: getdata.cxx [line 927]: time-out
>>for token 1998, lost a L2 Accept/Abort
>>[tof02 08:34:29] (getdata): WARNING: getdata.cxx [line 927]: time-out
>>for token 2080, lost a L2 Accept/Abort
>>[tof02 08:34:36] (getdata): WARNING: getdata.cxx [line 927]: time-out
>>for token 2348, lost a L2 Accept/Abort
>>[tof02 08:34:39] (getdata): WARNING: getdata.cxx [line 927]: time-out
>>for token 2469, lost a L2 Accept/Abort
>>[tof02 08:34:39] (getdata): WARNING: getdata.cxx [line 927]: time-out
>>for token 2468, lost a L2 Accept/Abort
>>[tof02 08:34:39] (getdata): WARNING: getdata.cxx [line 1539]: L2
>>Accept with L0 2465, L2 2469, LAMG 1, buffer 64
>>[tof02 08:34:39] (getdata): WARNING: getdata.cxx [line 1539]: L2
>>Accept with L0 2465, L2 2468, LAMG 1, buffer 65
>>
>>and there is much more of that ... like two weeks ago you can clearly
>>see the L2 accepts coming in more than 100ms after the L0 while in the
>>mean time more L0s have already entered the system.
>>
>>Tonko, can you remind me again what you do in STAR daq with those
>>events, do you keep 'm or kick 'm out?
>>
>>There is little information in the startrg-hn group except for Hank's
>>trg nts 030306 ... any news on that?
>>
>>
>>>L2: Agree to test write changes, then connection to DAQ for BECM
towers and then
>>>test aborts. ZM will finalize command and interface to daq with TL, then
>>>complete code for testing. ZM will work with JeffL to gresurrect and
clarify
>>>connection to RTS GUI.
>>
>>cheers,
>>-frank
>>
>>-------------------------------------------------------------
>>Visit this STAR HyperNews message (to reply or unsubscribe) at:
>>http://www.star.bnl.gov/HyperNews-star/get/startrig/2127.html
>
>
-------------------------------------------------------------
Visit this STAR HyperNews message (to reply or unsubscribe) at:
http://www.star.bnl.gov/HyperNews-star/get/startrig/2127/1/1.html
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:37 EDT