EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Inter-IOC link problems
From: "Shepherd, EL (Emma)" <[email protected]>
To: <[email protected]>
Date: Thu, 12 Mar 2009 13:25:24 -0000
Hi all,

I decided to wake up this thread as my problem has occurred again
(record with CP link to a PV on another IOC in 'LINK' status and failing
to update).

I loaded a standalone CA client into vxWorks as Jeff suggested and it
works fine, so it doesn't appear to be a global CA issue.  I've also
attached the output of dbcar and some other commands to this message.

I need to reboot this IOC first thing on Monday morning but have until
then to do some more debugging!!  Any ideas what I could try next?

Thanks,

Emma

> -----Original Message-----
> From: Jeff Hill [mailto:[email protected]] 
> Sent: 20 October 2008 17:24
> To: Shepherd, EL (Emma); [email protected]
> Subject: RE: Inter-IOC link problems
> 
> 
> Presumably, the IP stack on this IOC is operating correctly 
> when this happens - as verified by {telnet, ping, ifShow, ...}?
> 
> When this occurs, you might try running a small standalone CA 
> client that you have dynamically loaded into vxWorks. Its 
> best to spawn this type of client so that a CA context will 
> not end up getting attached to the vxWorks shell. The intent 
> of course would be to isolate between a global CA issue, and 
> one that is isolated to the CA client / DB CA Link code combination. 
> 
> I would also look very closely at the output from dbcar at 
> higher interest levels. As the interest level increases you 
> should be able to see if CA thinks that the channel is 
> connected or not (the output from void nciu::show ()). Of 
> particular interest would be any situations where CA thinks 
> the channel is connected, but the DB CA link code does not. 
> Also look for situations where the DB CA Link code thinks 
> that it's a CA link, but the CA channel hasn't been created (yet).
> 
> Also, do a "tt" on the DBCA Link thread, and the satellite 
> threads for its CA context. Look for any situations where 
> threads are hanging around in unusual places which might 
> indicate some form of deadlock. If you see anything out of 
> the ordinary please send the tt output and I will have a 
> look. In lightly loaded situations, "out of the ordinary" 
> usually means a thread that isn't parked in the normal place 
> (as seen by snapshots with tt) for an extended length of 
> time. One of course needs to compare tt output from when the 
> IOC is normal to tt output from when the IOC is misbehaving. 
> Needless to say, a CPU starvation situation on this IOC would 
> also cause issues (could be the cause of your issue).
> 
> In the past, quite some years back actually, I have seen UDP 
> issues if there were too many machines on a network with the 
> wrong subnet mask configuration. I think that there used to 
> be some issues in particular with HP workstations because 
> they would reply with "ICMP network unreachable" if their 
> network mask was set incorrectly and this could cause the 
> IOC's search response to be discarded off the end of the 
> finite length UDP input queue (depending on which response 
> got there first and how many bogus ICMP messages are sent in 
> response to each search request). ICMP traffic can be seen 
> with Ethernet snoopers like wireshark or tcpdump. However, on 
> modern switched networks, it may be best to be on the same 
> hub (not a switch) with the IOC so that you can see unicast 
> traffic that the switch sends only between the IOC and its 
> message peers. Admittedly, this is perhaps contraindicated 
> based on your not seeing any search traffic from the IOC in 
> casnooper. 
> 
> You might have a look at the output from utpStatShow 
> (presuming that something is wrong with UDP and not IP). 
> Also, have a look at ifShow and verify that the broadcast 
> address remains correctly configured, and that there are not 
> high error rates.
> 
> Jeff
> 
> > -----Original Message-----
> > From: [email protected] 
> > [mailto:[email protected]]
> > On Behalf Of Shepherd, EL (Emma)
> > Sent: Friday, October 17, 2008 9:12 AM
> > To: [email protected]
> > Subject: RE: Inter-IOC link problems
> > 
> > I've done a little more investigation and I think that in this case 
> > the gateway is not to blame.  It seems that other CA links 
> on this IOC 
> > are also not working, and they are not all going through 
> the gateway 
> > (some are on other IOCs on the same network).
> > 
> > I setup caSnooper to monitor connection requests on one of 
> the PVs my 
> > IOC is failing to link to.  When I change the link to a 
> constant and 
> > change it back again, caSnooper does not report any new 
> requests for 
> > the PV.  However when I do the same on a 'healthy' IOC which has 
> > working links, I see the new request on caSnooper when I 
> put the link 
> > back.
> > 
> > I'm not sure what that tells me except that it looks like 
> the IOC has 
> > somehow stopped broadcasting search requests..?
> > 
> > Emma
> > 
> > > -----Original Message-----
> > > From: [email protected] 
> > > [mailto:[email protected]] On Behalf Of Shepherd, EL 
> > > (Emma)
> > > Sent: 17 October 2008 12:28
> > > To: Ralph Lange
> > > Cc: [email protected]
> > > Subject: RE: Inter-IOC link problems
> > >
> > >
> > > Hi there,
> > >
> > > Thanks for the replies, it seems that the 'undefined' entry might 
> > > have been a red herring.
> > >
> > > The IOC I am looking at is the client of the PV 
> connection, and the 
> > > IP address listed is the server side of the CA gateway.  
> There are 
> > > in fact two gateways on this machine - one for each 
> direction as you 
> > > suggested. The configuration is really very simple, it is 
> setup to 
> > > allow read access for all PVs.  Do you need to know anything more 
> > > specific?
> > >
> > > Cheers,
> > >
> > > Emma
> > >
> > > > -----Original Message-----
> > > > From: Ralph Lange [mailto:[email protected]]
> > > > Sent: 17 October 2008 08:52
> > > > To: Shepherd, EL (Emma)
> > > > Cc: [email protected]
> > > > Subject: Re: Inter-IOC link problems
> > > >
> > > >
> > > > Hi Emma,
> > > >
> > > > I would need a bit more information about your setup to 
> be able to 
> > > > fully understand your report.
> > > >
> > > > You are looking at the CA client side of an IOC. When you are 
> > > > losing connections between IOCs, is the IOC you're 
> looking at the 
> > > > server or the client of that PV connection?
> > > > It seems there are no beacons coming from the CA Gateway
> > > > (172.23.106.35). Is that the client side or the server side
> > > of the CA
> > > > Gateway? Are two (or more) Gateway processes running on
> > > that machine
> > > > (i.e. one for each direction)? What is the CA configuration for 
> > > > the
> > > > Gateway(s) on that machine?
> > > >
> > > > CA configuration of a Gateway is difficult and subtle. 
> There are a 
> > > > lot of environment variables for CA server and client (see the
> > > CA Manual)
> > > > which influence the behaviour of a CA application. Some
> > > variables are
> > > > using other variables' values as default, which simplifies 
> > > > configuration of pure CA client or server apps, but may lead to 
> > > > unwanted behaviour for
> > > > a CA Gateway (whis is one of the few apps that is as well CA
> > > > server and
> > > > client). E.g, it is quite easy to create a setup where the
> > > Gateway is
> > > > sending out beacons on the wrong (i.e. client) side.
> > > >
> > > > Cheers,
> > > > Ralph
> > > >
> > > >
> > > > Shepherd, EL (Emma) wrote:
> > > > > Hi all,
> > > > >
> > > > > We still seem to suffer quite a bit from problems with
> > > > database links
> > > > > between IOCs, particularly when a gateway is 
> involved.  For some 
> > > > > reason the links can become disconnected and a reboot 
> is usually 
> > > > > necessary to get them working again.  I have just had an
> > > > opportunity
> > > > > to do some diagnosis on one such problem and found a clue
> > > in the CA
> > > > > beacon hashtable part of the dbcar report.  The entry for
> > > > the gateway
> > > > > (172.23.106.35) is 'undefined', although the gateway itself
> > > > seems to
> > > > > be working just fine and I can use caget through the 
> gateway as 
> > > > > normal.
> > > > >
> > > > > Any ideas what could cause this to happen, or how to fix
> > > it when it
> > > > > does?  None of the tasks are suspended, CPU usage is low and 
> > > > > everything else looks fine.
> > > > >
> > > > > CA beacon hash entry for 172.23.106.32:5064 with 
> period estimate 
> > > > > 15.000521
> > > > >         beacon number 168436, on THU OCT 16 2008 14:27:46 CA 
> > > > > beacon hash entry for 172.23.106.35:5064 <no period estimate>
> > > > >         beacon number 0, on <undefined>
> > > > > CA beacon hash entry for 172.23.106.97:5064 with 
> period estimate 
> > > > > 14.988265
> > > > >         beacon number 76356, on THU OCT 16 2008 14:27:52 CA 
> > > > > beacon hash entry for 172.23.106.96:5064 with period estimate 
> > > > > 14.988637
> > > > >         beacon number 39491, on THU OCT 16 2008 14:27:53 CA 
> > > > > beacon hash entry for 172.23.106.98:5064 with period estimate 
> > > > > 14.980477
> > > > >         beacon number 58989, on THU OCT 16 2008 14:27:47 CA 
> > > > > beacon hash entry for 172.23.106.102:5064 with period 
> estimate 
> > > > > 14.990867
> > > > >         beacon number 39993, on THU OCT 16 2008 14:27:53 CA 
> > > > > beacon hash entry for 172.23.106.32:5064 with period estimate 
> > > > > 15.000521
> > > > >         beacon number 168436, on THU OCT 16 2008 14:27:46 CA 
> > > > > beacon hash entry for 172.23.106.35:5064 <no period estimate>
> > > > >         beacon number 0, on <undefined>
> > > > > CA beacon hash entry for 172.23.106.97:5064 with 
> period estimate 
> > > > > 14.988265
> > > > >         beacon number 76356, on THU OCT 16 2008 14:27:52 CA 
> > > > > beacon hash entry for 172.23.106.96:5064 with period estimate 
> > > > > 14.988637
> > > > >         beacon number 39491, on THU OCT 16 2008 14:27:53 CA 
> > > > > beacon hash entry for 172.23.106.98:5064 with period estimate 
> > > > > 14.980477
> > > > >         beacon number 58989, on THU OCT 16 2008 14:27:47 CA 
> > > > > beacon hash entry for 172.23.106.102:5064 with period 
> estimate 
> > > > > 14.990867
> > > > >         beacon number 39993, on THU OCT 16 2008 14:27:53
> > > > entries per
> > > > > bucket: mean = 0.011719 std dev = 0.107617 max = 1
> > > > >
> > > > >
> > > > > Thanks in advance....
> > > > >
> > > > > Emma
> > > > >
> > > >
> > > <DIV><FONT size="1" color="gray">This e-mail and any 
> attachments may 
> > > contain confidential, copyright and or privileged 
> material, and are 
> > > for the use of the intended addressee only. If you are not the 
> > > intended addressee or an authorised recipient of the addressee 
> > > please notify us of receipt by returning the e-mail and 
> do not use, 
> > > copy, retain, distribute or disclose the information in 
> or attached 
> > > to the e-mail. Any opinions expressed within this e-mail are those
> > > of the individual and not necessarily of Diamond Light Source Ltd.
> > > Diamond Light Source Ltd. cannot guarantee that this e-mail
> > > or any attachments are free from viruses and we cannot accept
> > > liability for any damage which you may sustain as a result of
> > > software viruses which may be transmitted in or with the
> > > message. Diamond Light Source Limited (company no. 4375679).
> > > Registered in England and Wales with its registered office at
> > > Diamond House, Harwell Science and Innovation Campus, Didcot,
> > > Oxfordshire, OX11 0DE, United Kingdom </FONT></DIV>
> > >
> > >
> > <DIV><FONT size="1" color="gray">This e-mail and any 
> attachments may 
> > contain confidential, copyright and or privileged material, and are 
> > for
> the
> > use of the intended addressee only. If you are not the intended 
> > addressee or an authorised recipient of the addressee 
> please notify us 
> > of receipt by returning the e-mail and do not use, copy, retain, 
> > distribute or disclose the information in or attached to 
> the e-mail. 
> > Any opinions expressed within this e-mail are those of the 
> individual 
> > and not necessarily of Diamond Light Source Ltd. Diamond 
> Light Source 
> > Ltd. cannot guarantee that this e-mail or any attachments are free 
> > from viruses and we cannot accept liability for any damage 
> which you 
> > may sustain as a result of software viruses which may be 
> transmitted 
> > in or with the message. Diamond Light Source Limited (company no. 
> > 4375679). Registered in England and Wales with its 
> registered office 
> > at Diamond House, Harwell Science and Innovation Campus, Didcot, 
> > Oxfordshire, OX11 0DE, United Kingdom </FONT></DIV>
> 
> 
<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV> 

-- 

Scanned by iCritical.
BL06I-DI-IOC-01 -> ifShow
gei (unit number 0):
     Flags: (0x8063) UP BROADCAST MULTICAST ARP RUNNING
     Type: ETHERNET_CSMACD
     Internet address: 172.23.106.101
     Broadcast address: 172.23.106.255
     Netmask 0xffff0000 Subnetmask 0xffffff00
     Ethernet address is 00:01:af:15:40:4b
     Metric is 0
     Maximum Transfer Unit size is 1500
     0 octets received
     0 octets sent
     0 unicast packets received
     0 unicast packets sent
     0 non-unicast packets received
     0 non-unicast packets sent
     0 multicast packets received
     0 multicast packets sent
     0 broadcast packets received
     0 broadcast packets sent
     0 incoming packets discarded
     0 outgoing packets discarded
     0 incoming errors
     0 outgoing errors
     124 unknown protos
     0 collisions; 0 dropped
lo (unit number 0):
     Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING
     Type: SOFTWARE_LOOPBACK
     Internet address: 127.0.0.1
     Netmask 0xff000000 Subnetmask 0xff000000
     Metric is 0
     Maximum Transfer Unit size is 32768
     2472868 packets received; 2472868 packets sent
     0 multicast packets received
     0 multicast packets sent
     0 input errors; 0 output errors
     0 collisions; 0 dropped
value = 29 = 0x1d
BL06I-DI-IOC-01 ->

BL06I-DI-IOC-01 ->  dbcar "BL06I-DI-BEAM-01:CLC1",8
not_connected BL06I-DI-BEAM-01:CLC1.INPB FE06I-PS-SHTR-02:STA
not_connected BL06I-DI-BEAM-01:CLC1.INPE FE06I-RS-ABSB-02:STA
ncalinks 2 not connected 2 no_read_access 0 no_write_access 0
 nDisconnect 0 nNoWrite 0
ca_client_context at 0x1ecb7730 pndRecvCnt=0 ioSeqNo=0
dbContext at 0x1edecd00
        event call back cache location 0x1d8c6880, and its size 24
dbContextReadNotifyCache
dbContextReadNotifyCacheAlocator
        count 1 and size 88
epicsMutexId 0x1ecb76c0 source ../../../src/libCom/osi/epicsMutex.cpp line 197

Semaphore Id        : 0x1ecb76f0
Semaphore Type      : MUTEX
Task Queuing        : PRIORITY
Pended Tasks        : 0
Owner               : 0x1d7d7a50   (tShell)
Options             : 0xd       SEM_Q_PRIORITY
                                SEM_DELETE_SAFE
                                SEM_INVERSION_SAFE

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

Channel Access Client Context at 0x1d9126d0 for user anonymous
        revision "@(#) EPICS 3.14.8.2, CA Client Library Oct 20 2006"
Hash table with 512 buckets and 0 items of type 6tcpiiu installed
entries per bucket: mean = 0.000000 std dev = 0.000000 max = 0
        connection time out watchdog period 30.000000
Datagram IO circuit (and disconnected channel repository)
        repeater port 5065
        default server port 5064
Channel Access Address List
172.23.106.255:5064
        socket identifier 14
        bytes in xmit buffer 16
        shut down command bool 0
        recv thread exit signal:
repeater subscribe timer: attempts=2 registered=1 once=0
disconnect governor timer:
Channel "FE06I-PS-SHTR-02:STA" is disconnected
Channel "BL06I-DI-PHDGN-01:STA" is disconnected
Channel "BL06I-DI-PHDGN-99:STA" is disconnected
Channel "BL06I-DI-PHDGN-02:STA" is disconnected
Channel "BL06J-PS-SHTR-01:STA" is disconnected
Channel "BL06I-PS-SHTR-01:STA" is disconnected
Channel "BL06I-DI-PHDGN-04:STA" is disconnected
Program begin time:
epicsTime: WED DEC 10 2008 12:43:50.099847050
epicsTime: revision "@(#) EPICS 3.14.8.2, Common Utilities Library Oct 20 2006"
Channel identifier hash table:
Hash table with 512 buckets and 8 items of type 4nciu installed
Channel "FE06I-PS-SHTR-02:STA" is disconnected
Channel "BL06I-DI-PHDGN-01:STA" is disconnected
Channel "BL06I-DI-PHDGN-99:STA" is disconnected
Channel "BL06I-DI-PHDGN-02:STA" is disconnected
Channel "BL06J-PS-SHTR-01:STA" is disconnected
Channel "BL06I-PS-SHTR-01:STA" is disconnected
Channel "BL06I-DI-PHDGN-04:STA" is disconnected
Channel "FE06I-RS-ABSB-02:STA" is disconnected
entries per bucket: mean = 0.015625 std dev = 0.124020 max = 1
IO identifier hash table:
Hash table with 512 buckets and 7 items of type 8baseNMIU installed
event subscription IO at 0x1d7f4c00, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4c58, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4c84, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4cb0, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4cdc, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4d08, type DBF_invalid, element count 1, mask 5
event subscription IO at 0x1d7f4d34, type DBF_invalid, element count 1, mask 5
entries per bucket: mean = 0.013672 std dev = 0.116125 max = 1
Beacon source identifier hash table:
Hash table with 512 buckets and 22 items of type 3bhe installed
CA beacon hash entry for 172.23.106.32:42482 with period estimate 0.905827
CA beacon hash entry for 172.23.106.32:42487 with period estimate 0.907350
CA beacon hash entry for 172.23.106.32:42495 with period estimate 0.907248
CA beacon hash entry for 172.23.106.32:42477 with period estimate 0.909130
CA beacon hash entry for 172.23.106.32:5064 with period estimate 15.003105
CA beacon hash entry for 172.23.106.35:5064 <no period estimate>
CA beacon hash entry for 172.23.106.65:5064 with period estimate 3.219199
CA beacon hash entry for 172.23.106.64:5064 with period estimate 3410.477203
CA beacon hash entry for 172.23.106.97:5064 with period estimate 15.000170
CA beacon hash entry for 172.23.106.96:5064 with period estimate 15.000160
CA beacon hash entry for 172.23.106.98:5064 with period estimate 15.000170
CA beacon hash entry for 172.23.106.102:5064 with period estimate 15.000145
CA beacon hash entry for 172.23.106.32:42659 with period estimate 0.907363
CA beacon hash entry for 172.23.106.32:42661 with period estimate 0.906909
CA beacon hash entry for 172.23.106.32:42644 with period estimate 0.905845
CA beacon hash entry for 172.23.106.32:42638 with period estimate 0.908983
CA beacon hash entry for 172.23.106.32:42621 with period estimate 0.906114
CA beacon hash entry for 172.23.106.32:42620 with period estimate 0.223765
CA beacon hash entry for 172.23.106.32:42622 with period estimate 0.907566
CA beacon hash entry for 172.23.106.32:42606 with period estimate 11.962235
CA beacon hash entry for 172.23.106.32:42543 with period estimate 0.907013
CA beacon hash entry for 172.23.106.32:42500 with period estimate 0.905827
entries per bucket: mean = 0.042969 std dev = 0.202787 max = 1
Timer queue:
EPICS threaded timer queue at 0x1d90fc60
epicsTimerQueue with 14 items pending
11searchTimer, state = pending, delay = -7698880.104460
11searchTimer, state = pending, delay = -7698880.073793
11searchTimer, state = pending, delay = -7698880.056460
11searchTimer, state = pending, delay = -7698880.079126
11searchTimer, state = pending, delay = -7698879.894460
11searchTimer, state = pending, delay = -7698879.920459
11searchTimer, state = pending, delay = -7698879.889126
11searchTimer, state = pending, delay = -7698876.167753
11searchTimer, state = pending, delay = -7698876.067125
11searchTimer, state = pending, delay = -7698874.584459
11searchTimer, state = pending, delay = -7698872.693126
23disconnectGovernorTimer, state = pending, delay = -7698870.835126
11searchTimer, state = pending, delay = -7698811.065086
11searchTimer, state = pending, delay = -7698811.033507
reschedule event

Semaphore Id        : 0x1d90fa90
Semaphore Type      : BINARY
Task Queuing        : FIFO
Pended Tasks        : 0
State               : EMPTY
Options             : 0x0       SEM_Q_FIFO

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

exit event

Semaphore Id        : 0x1d90fa50
Semaphore Type      : BINARY
Task Queuing        : FIFO
Pended Tasks        : 0
State               : EMPTY
Options             : 0x0       SEM_Q_FIFO

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

exitFlag = F, terminateFlag = F
IP address to name conversion engine:
ipAddrToAsciiEngine at 0x1d9120d0 with 0 requests pending
mutex:
epicsMutexId 0x1d912060 source ../../../src/libCom/osi/epicsMutex.cpp line 197
laborEvent:

Semaphore Id        : 0x1d912020
Semaphore Type      : BINARY
Task Queuing        : FIFO
Pended Tasks        : 1
State               : EMPTY
Options             : 0x0       SEM_Q_FIFO

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

exitFlag  boolean = 0
exit event:
Default mutex:
epicsMutexId 0x1ecb76c0 source ../../../src/libCom/osi/epicsMutex.cpp line 197

Semaphore Id        : 0x1ecb76f0
Semaphore Type      : MUTEX
Task Queuing        : PRIORITY
Pended Tasks        : 1
Owner               : 0x1d7d7a50   (tShell)
Options             : 0xd       SEM_Q_PRIORITY
                                SEM_DELETE_SAFE
                                SEM_INVERSION_SAFE

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

mutex:
epicsMutexId 0x1ecb76c0 source ../../../src/libCom/osi/epicsMutex.cpp line 197

Semaphore Id        : 0x1ecb76f0
Semaphore Type      : MUTEX
Task Queuing        : PRIORITY
Pended Tasks        : 1
Owner               : 0x1d7d7a50   (tShell)
Options             : 0xd       SEM_Q_PRIORITY
                                SEM_DELETE_SAFE
                                SEM_INVERSION_SAFE

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

        preemptive callback is enabled
        there are 0 unsatisfied IO operations blocking ca_pend_io()
        the current io sequence number is 0
IO done event:

Semaphore Id        : 0x1ecb7610
Semaphore Type      : BINARY
Task Queuing        : FIFO
Pended Tasks        : 0
State               : EMPTY
Options             : 0x0       SEM_Q_FIFO

VxWorks Events
--------------
Registered Task     : NONE
Event(s) to Send    : N/A
Options             : N/A

Synchronous group identifier hash table:
Hash table with 0 buckets and 0 items of type 4CASG installed
value = 0 = 0x0
BL06I-DI-IOC-01 ->



BL06I-DI-IOC-01 -> dbpr "BL06I-DI-BEAM-01:CLC1",4
A: 0                ACKS: INVALID       ACKT: YES           ADEL: 0
ALST: 0             ASG:                ASP: 0x00000000     B: 1
BKPT: 0x00          C: 0                CALC: (A=C)&&(B=D)&&(E=D)?(A+1):A
CLCV: 0             D: 1                DESC:               DISA: 0
DISP: 0             DISS: NO_ALARM      DISV: 1             DLYA: 0
DOPT: Use CALC      DPVT: 0x00000000    DSET: 0x1ead1b78    DTYP: Soft Channel
E: 3                EGU:                EVNT: 0             F: 0
FLNK:CONSTANT 0     G: 0                H: 0                HHSV: NO_ALARM
HIGH: 0             HIHI: 0             HOPR: 0             HSV: NO_ALARM
HYST: 0             I: 0                INAV: Constant      INBV: Ext PV NC
INCV: Constant      INDV: Constant      INEV: Ext PV NC     INFV: Constant
INGV: Constant      INHV: Constant      INIV: Constant      INJV: Constant
INKV: Constant      INLV: Constant      INPA:CONSTANT 0
INPB:CA_LINK FE06I-PS-SHTR-02:STA CP NMS                    INPC:CONSTANT 0
INPD:CONSTANT 1     INPE:CA_LINK FE06I-RS-ABSB-02:STA CP NMS
INPF:CONSTANT       INPG:CONSTANT       INPH:CONSTANT       INPI:CONSTANT
INPJ:CONSTANT       INPK:CONSTANT       INPL:CONSTANT
IVOA: Continue normally                 IVOV: 0             J: 0
K: 0                L: 0                LA: 0               LALM: 0
LB: 1               LC: 0               LCNT: 0             LD: 1
LE: 3               LF: 0               LG: 0               LH: 0
LI: 0               LJ: 0               LK: 0               LL: 0
LLSV: NO_ALARM      LOLO: 0             LOPR: 0             LOW: 0
LSET: 0x1d95bbf0    LSV: NO_ALARM       MDEL: 0
MLIS: 0x1d8c7b701d8c84d000000006        MLOK: 0x1ecb6c30    MLST: 0
NAME: BL06I-DI-BEAM-01:CLC1             NSEV: NO_ALARM      NSTA: NO_ALARM
OCAL:               OCLV: 0             ODLY: 0             OEVT: 0
OOPT: Every Time    ORPC: 0x7f00000000000000000000000000000000000000
OUT:DB_LINK BL06I-DI-BEAM-01:CLC2.A PP NMS                  OUTV: Local PV
OVAL: 0             PACT: 0             PHAS: 0             PINI: NO
POVL: 0             PPN: 0x00000000     PPNR: 0x00000000    PREC: 0
PRIO: LOW           PROC: 1             PUTF: 0             PVAL: 0
RDES: 0x1ec931f0    RPCL: 0x01033d02043d3f05043d3f4601483ff000000000
RPRO: 0             RPVT: 0x1ecb6bf0    RSET: 0x1ead13f8    SCAN: Passive
SDIS:CONSTANT       SEVR: INVALID       SPVT: 0x00000000    STAT: LINK
TIME: 0x24167f621949f50a                TPRO: 0             TSE: 0
TSEL:CONSTANT       UDF: 0              VAL: 0              VERS: 1
value = 0 = 0x0
BL06I-DI-IOC-01 ->

BL06I-DI-IOC-01 -> i

  NAME        ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
tExcTask   excTask      1effd920   0 PEND         233934 1effd800   3006b     0
tLogTask   logTask      1effad60   0 PEND         233934 1effac50       0     0
tShell     shell        1d7d7a50   1 READY        22d260 1d7d7630   c0002     0
tRlogind   rlogind      1ee4cf60   2 PEND         227904 1ee4cb00       0     0
tWdbTask   wdbTask      1ee3ffe0   3 PEND         227904 1ee3feb0       0     0
tillRdb    1182d4       1ee3a280  10 PEND         227904 1ee39e20  3d0002     0
t1394ohci  1ed1ff34     1ecc3c00  40 PEND         227904 1ecc3b30       0     0
t1394stack 1ed55600     1ecb5370  45 PEND         228130 1ecb5280  160068     0
t1394iidc  1ed55600     1ecb9510  45 DELAY        22cb84 1ecb9190  3d0002     1
tAioIoTask1aioIoTask    1efed5d0  50 PEND         228130 1efed4d0       0     0
tAioIoTask0aioIoTask    1efe6330  50 PEND         228130 1efe6230       0     0
tNetTask   netTask      1eed9130  50 PEND         227904 1eed9040       0     0
tAioWait   aioWaitTask  1eff4870  51 PEND         227904 1eff4700  3d0002     0
tPortmapd  portmapd     1ee489b0  54 PEND         227904 1ee48750  3d0002     0
tTelnetd   telnetd      1ee4ab90  55 PEND         227904 1ee4aa20       0     0
syncNTP    1eaa1ae8     1edae180 109 DELAY        22cb84 1edae020  3d0002   266
cbHigh     1eaa1ae8     1ee10cc0 128 PEND         227904 1ee10ba0       0     0
timerQueue 1eaa1ae8     1ee29390 129 PEND+T       227904 1ee28e00  3d0004     7
scanOnce   1eaa1ae8     1d94d480 129 PEND         227904 1d94d370       0     0
scan0.1    1eaa1ae8     1d926020 133 DELAY        22cb84 1d925ee0       0     6
scan0.2    1eaa1ae8     1d92b8b0 134 DELAY        22cb84 1d92b770       0    11
cbMedium   1eaa1ae8     1ee18430 135 PEND         227904 1ee18310       0     0
scan0.5    1eaa1ae8     1d931140 135 DELAY        22cb84 1d931000       0     5
scan1      1eaa1ae8     1d9369d0 136 DELAY        22cb84 1d936890       0    52
scan2      1eaa1ae8     1d93c260 137 DELAY        22cb84 1d93c120  3d0002    84
scan5      1eaa1ae8     1d941af0 138 DELAY        22cb84 1d9419b0       0   141
scan10     1eaa1ae8     1d947380 139 DELAY        22cb84 1d947240       0   368
cbLow      1eaa1ae8     1ee1fba0 140 PEND         227904 1ee1fa80       0     0
CAC-UDP    1eaa1ae8     1d8fbe00 147 PEND         227904 1d8fb6c0       0     0
timerQueue 1eaa1ae8     1d90f740 148 SUSPEND      22bbf4 1d90f2a0  3d0004     0
CAC-event  1eaa1ae8     1d8cefc0 148 PEND         227904 1d8ceeb0       0     0
dbCaLink   1eaa1ae8     1ed09a30 149 PEND         227904 1ed09910       0     0
poolPoll   1eaa1ae8     1d7edbe0 149 DELAY        22cb84 1d7edaf0       0    41
CAS-client 1eaa1ae8     1cd8a6e0 163 PEND         227904 1cd8a410       0     0
CAS-client 1eaa1ae8     1cd9ca60 163 PEND         227904 1cd9c790       0     0
CAS-event  1eaa1ae8     1cd95400 164 PEND         227904 1cd952f0       0     0
CAS-event  1eaa1ae8     1cd9fbe0 164 PEND         227904 1cd9fad0       0     0
CAS-client 1eaa1ae8     1d599410 179 PEND         227904 1d599140       0     0
CAS-client 1eaa1ae8     1cf63430 179 PEND         227904 1cf63160       0     0
CAS-client 1eaa1ae8     1d766dc0 179 PEND         227904 1d766af0       0     0
CAS-client 1eaa1ae8     1d2ef700 179 PEND         227904 1d2ef430       0     0
CAS-client 1eaa1ae8     1d814820 179 PEND         227904 1d814550       0     0
CAS-client 1eaa1ae8     1d2f85d0 179 PEND         227904 1d2f8300       0     0
CAS-client 1eaa1ae8     1cd8fef0 179 PEND         227904 1cd8fc20       0     0
CAS-client 1eaa1ae8     1cd84ed0 179 PEND         227904 1cd84c00       0     0
CAS-client 1eaa1ae8     1cd7f6c0 179 PEND         227904 1cd7f3f0       0     0
CAS-client 1eaa1ae8     1d129130 179 PEND         227904 1d128e60       0     0
CAS-client 1eaa1ae8     1d123920 179 PEND         227904 1d123650       0     0
CAS-event  1eaa1ae8     1d59c510 180 PEND         227904 1d59c400       0     0
CAS-event  1eaa1ae8     1d76a080 180 PEND         227904 1d769f70       0     0
CAS-event  1eaa1ae8     1cda35e0 180 PEND         227904 1cda34d0       0     0
CAS-event  1eaa1ae8     1d80eea0 180 PEND         227904 1d80ed90       0     0
CAS-event  1eaa1ae8     1d76d7b0 180 PEND         227904 1d76d6a0       0     0
CAS-event  1eaa1ae8     1d2fb6d0 180 PEND         227904 1d2fb5c0       0     0
CAS-event  1eaa1ae8     1d775f80 180 PEND         227904 1d775e70       0     0
CAS-event  1eaa1ae8     1d78d1f0 180 PEND         227904 1d78d0e0       0     0
CAS-event  1eaa1ae8     1d792700 180 PEND         227904 1d7925f0       0     0
CAS-event  1eaa1ae8     1d8a7280 180 PEND         227904 1d8a7170       0     0
CAS-event  1eaa1ae8     1d772ce0 180 PEND         227904 1d772bd0       0     0
CAS-TCP    1eaa1ae8     1d7f3e60 181 PEND         227904 1d7f3bc0       0     0
CAS-beacon 1eaa1ae8     1ee3d640 182 DELAY        22cb84 1ee3d330       0   523
CAS-UDP    1eaa1ae8     1d7f0ce0 183 PEND         227904 1d7f0950       0     0
logRestart 1eaa1ae8     1ecf7200 189 PEND+T       227904 1ecf70b0  3d0004   125
errlog     1eaa1ae8     1ecf4850 189 PEND         227904 1ecf4720  3d0002     0
taskwd     1eaa1ae8     1ee2b860 189 DELAY        22cb84 1ee2b6c0       0   295
ipToAsciiPr1eaa1ae8     1d911cd0 189 PEND         227904 1d9116f0       0     0
CAC-repeate1eaa1ae8     1d8f7400 189 PEND         227904 1d8f7070      30     0
DS1621     117594       1edeca00 199 DELAY        22cb84 1edec960   c0002   264
cpuUsageTas1e9876a0     1eded180 255 PEND         227904 1eded070       0     0
value = 0 = 0x0
BL06I-DI-IOC-01 -> tt 0x1ed09a30
231ff8 vxTaskEntry    +68 : 1eaa1ae8 ()
1eaa1b58 epicsThreadPrivateGet+f8 : dbCaTask ()
1e9ec83c dbCaTask       +190: semTake ()
2285d4 semTake        +13c: semBTake ()
value = 0 = 0x0


Navigate by Date:
Prev: Re: epics for stanford amp or Iseg supply Dennis Armstrong
Next: Scitec 500MC LockIn Peter . Mueller
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Prosilica cameras and bug in EPICS signal handlers Mark Rivers
Next: RE: Inter-IOC link problems Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·