1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 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 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | some of my scan tasks are not being processed because of long delays. |
From: | "Thompson, David H." <[email protected]> |
To: | [email protected] |
Date: | Thu, 25 Mar 2004 14:22:14 -0500 |
Has anybody seen this before? The delay on one of my scan tasks is 413.2 days. This happens on different tasks on different reboots. This is the SNS timing system, with hardware time support. The driver does not change the vxWorks clock. TSInit gets called before IOCInit, from inside the driver that supplies the time. This seems to happen right at bootup. It has happened on a development system as well as the production system. I went down a wild goose chase thinking one my drivers was malfunctioning before I noticed that some unrelated PVs were never updating.
0x7ffffffff=2147483647, I think the taskDelay call must have gotten a 0 or a negative number. The IOC has been up about a day.
Epics version R3.14.4 VxWorks T202 – kernel similar to Andrew’s APS version.
NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY ---------- ------------ -------- --- ---------- -------- -------- ------- ----- …. scan0.1 19724e4 15f62c0 133 DELAY 1951c8 15f61e8 0 4 scan0.2 19724e4 15fbae8 134 DELAY 1951c8 15fba10 0 9 cbMedium 19724e4 1713008 135 PEND 1907bc 1712f38 0 0 scan0.5 19724e4 1601310 135 DELAY 1951c8 1601238 0 26 scan1 19724e4 1606b38 136 DELAY 1951c8 1606a60 0 2142158394 scan2 19724e4 160c360 137 DELAY 1951c8 160c288 0 34 scan5 19724e4 1611b88 138 DELAY 1951c8 1611ab0 0 77 scan10 19724e4 16173b0 139 DELAY 1951c8 16172d8 0 22
|