[Bug 1861612] Re: callbackRequestDelay not waiting for 1/60 sec on vxWorks

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

As Ralph suggested while having 7.0.3.1 checked out I reverted commit
https://github.com/epics-base/epics-
base/commit/4f2228fb1d7527fb5ebc8b2d747c309f1dd7698d.

That fixed the problem with the scaler record, I can now run at 60 Hz
display rate with no problems.

It did not change the behavior of the bo record HIGH field.  I see the
same as above, with .01 sec it waits till the next clock tick to go low,
with .005 sec it goes low immediately.  I don't understand this
behavior.

-- 
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/1861612

Title:
  callbackRequestDelay not waiting for 1/60 sec on vxWorks

Status in EPICS Base:
  New

Bug description:
  The problem is documented in this tech-talk thread:
  https://epics.anl.gov/tech-talk/2020/msg00308.php

  In 7.0.3.1, but not in 7.0.3, callbackRequestDelay(1/60) results in
  100% CPU time, most of the time in cbHigh.

  This happens on vxWorks 6.9.4.1 and was first seen with the scaler
  record with multiple types of scaler hardware and device support.

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