[Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c

[mdavidsaver via Core-talk <core-talk at aps.anl.gov>]

Another https://epics.anl.gov/tech-talk/2023/msg01324.php

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/541371

Title:
  assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in
  dbEvent.c

Status in EPICS Base:
  Triaged

Bug description:
  2009-06-04 10:00   iocsrvid2>

  CAS-client: A call to "assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY)" failed in ../dbEvent.c at 683 Current time THU JUN 04 2009 10:08:33.581404952.
  EPICS Release EPICS R3.14.10-asd1 $R3-14-10$ $2008/10/27 19:39:04$.
  Please E-mail this message and the output from "tt (0x13144d0)"
  to the author or to tech-talk at aps.anl.gov Thread CAS-client (0x13144d0) suspended

  causing all the network buffers to get used up and all network-related
  activities to die, e.g:

  callbackRequest: cbHigh ring buffer full
  NTPTimeSync: NTP requests failing - S_sntpcLib_TIMEOUT DB CA Link Exception: "Virtual circuit unresponsive", context "164.54.2.121:5064"
  save_restore:do_seq - '/iocinfo/saverestore/iocsrvid2/ srvid2AutosaveV3.sav' not found.  Writing a new one. [090604-101331]
  ../online_notify.c: CA beacon (send to "164.54.3.255:5065") error was "S_errno_ENOBUFS"

  iocsrvid2> tt 0x13144d0
  133288 vxTaskEntry    +68 : 19290c0 ()
  1929118 epicsThreadOnceOsd+168: camsgtask ()
  1864ab4 camsgtask      +260: camessage ()
  1868ba8 camessage      +2f0: 1867bb8 ()
  1867e3c rsrvFreePutNotify+880: db_post_single_event () 188629c db_post_single_event+38 : 1885f84 () 1886080 db_post_extra_labor+194: epicsAssert ()
  1928234 epicsAssert    +f8 : epicsThreadSuspendSelf ()
  1929274 epicsThreadSuspendSelf+14 : taskSuspend () value = 0 = 0x0

  This is a PowerPC running vxWorks 5.5.2 and Base R3.14.10.  The IOC
  had to be rebooted.  This is the second or third time we've seen
  ENOBUFS recently, although the engineers didn't see (look for)
  assertion failure before this.


  Original Mantis Bug: mantis-342
      http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=342

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/541371/+subscriptions