This is an odd one. Below is the results of a ‘sin rtc’ command and it
shows negative timer values. When this happens of course the whole system
goes nuts.
ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 1817.568 0.500
1 25 //204/bin/tinit signal 14 -2142.577 60.000
2 25 //204/bin/tinit sleep -.— -.—
3 57 //204/bin/nameloc signal 6 -.— -.—
4 5 /bin/Fsys.eide proxy 13 1818.747 2.000
5 57 //204/bin/nameloc sleep -2168.182 0.000
6 61 //204//usr/ucb/Socket proxy 62 0.014 0.000
7 81 //204//recorder.proc proxy 84 -.— -.—
9 96 //204/bin/tinit sleep -.— -.—
10 116 //204//bin/Photon proxy 117 3.235 0.000
11 98 //204/bin/cron signal 14 -7.025 0.000
12 96 //204/bin/tinit signal 14 -2128.798 60.000
14 124 //204//chipsbios.ms signal 14 -.— -.—
15 74 //204//usr/ucb/inetd sleep -.— -.—
16 11448 //204/bin/Input sleep -199.975 0.000
17 11451 //204/bin/Input proxy 11453 -.— -.—
24 87 //204//samba/bin/nmbd proxy 88 4.643 0.000
41 9938 //204/*/bin/phrelay proxy 9942 0.599 1.000
These are the versions I am running:
PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25N Sep 24 2001
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys.eide eide 4.25A Feb 09 2000
//204/bin/Dev32 Dev32 4.23G Oct 04 1996
//204/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//204/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//204/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//204/bin/Pipe Pipe 4.23A Feb 26 1996
//204/bin/Net Net 4.25C Aug 30 1999
//204//Net.ether9000 Net.ether900 4.24E Feb 17 2000
//204//usr/ucb/Socket Socket 4.25C Aug 19 1998
//204/bin/Mqueue mqueue 4.24A Aug 30 1999
//204/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//204/bin/cron cron 4.23B Oct 30 1997
//204/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//204//bin/Photon Photon 1.14B Sep 03 1999
//204//bin/phfontpfr Photon Font 1.14H Jan 17 2001
You may notice that we are running Proc32 4.25N. This same results have
happened while running 4.25L.
Anyone have any ideas as to what the cause may be, and what the solution is?
TIA
–
Ivan Bannon
RJG Inc.
This has happened again. We’ve noticed that it is only the “sleep” timers
that are
counting negative. We have an interrupt driven serial driver running at a
higher
proirity that Proc32. Could this be causing the problem? any help is
greatly
appreciated.
“Ivan Bannon” <ivan.bannon@rjginc.com> wrote in message
news:a6qnvh$iip$1@inn.qnx.com…
This is an odd one. Below is the results of a ‘sin rtc’ command and it
shows negative timer values. When this happens of course the whole system
goes nuts.
ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 1817.568 0.500
1 25 //204/bin/tinit signal 14 -2142.577 60.000
2 25 //204/bin/tinit sleep -.— -.—
3 57 //204/bin/nameloc signal 6 -.— -.—
4 5 /bin/Fsys.eide proxy 13 1818.747 2.000
5 57 //204/bin/nameloc sleep -2168.182 0.000
6 61 //204//usr/ucb/Socket proxy 62 0.014 0.000
7 81 //204//recorder.proc proxy 84 -.— -.—
9 96 //204/bin/tinit sleep -.— -.—
10 116 //204//bin/Photon proxy 117 3.235 0.000
11 98 //204/bin/cron signal 14 -7.025 0.000
12 96 //204/bin/tinit signal 14 -2128.798 60.000
14 124 //204//chipsbios.ms signal 14 -.— -.—
15 74 //204//usr/ucb/inetd sleep -.— -.—
16 11448 //204/bin/Input sleep -199.975 0.000
17 11451 //204/bin/Input proxy 11453 -.— -.—
24 87 //204//samba/bin/nmbd proxy 88 4.643 0.000
41 9938 //204/*/bin/phrelay proxy 9942 0.599 1.000
These are the versions I am running:
PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25N Sep 24 2001
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys.eide eide 4.25A Feb 09 2000
//204/bin/Dev32 Dev32 4.23G Oct 04 1996
//204/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//204/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//204/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//204/bin/Pipe Pipe 4.23A Feb 26 1996
//204/bin/Net Net 4.25C Aug 30 1999
//204//Net.ether9000 Net.ether900 4.24E Feb 17 2000
//204//usr/ucb/Socket Socket 4.25C Aug 19 1998
//204/bin/Mqueue mqueue 4.24A Aug 30 1999
//204/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//204/bin/cron cron 4.23B Oct 30 1997
//204/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//204//bin/Photon Photon 1.14B Sep 03 1999
//204//bin/phfontpfr Photon Font 1.14H Jan 17 2001
You may notice that we are running Proc32 4.25N. This same results have
happened while running 4.25L.
Anyone have any ideas as to what the cause may be, and what the solution
is?
TIA
–
Ivan Bannon
RJG Inc.
“Ivan Bannon” <ivan.bannon@rjginc.com> wrote in
news:a6t877$eu2$1@inn.qnx.com:
This has happened again. We’ve noticed that it is only the “sleep”
timers that are
counting negative. We have an interrupt driven serial driver running
at a higher
proirity that Proc32. Could this be causing the problem? any help is
greatly
appreciated.
Why are you running your driver higher than Proc? The kernel(not proc) can
still preempt you for scheduling purposes/exceptions etc. Unless of course
you’ve remapped the PIC, so that Int0 isn’t the highest priority. Does the
problem go away if you run under the priority of proc, but higher than
everyone else?
\
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
By default Int3 is the highest priority. We have switched the driver to run
the same priority
as Proc32 and still see the timer problem. We may have solved the problem
though. (I hope).
After digging into some of the node sync’ing routines we found that the
system was issuing a
“rtc hw” every 4 hours. I guess to adjust for real-time clock drift though
I’m not sure why.
Anyway, the problem appears to happen on those systems that had the biggest
difference
between the BIOS time and the RTC, some up to 23 hours. (the RTC was
correct, the BIOS
was behind). The system was also attempting to sync all the nodes to the
time on the highest
node. This created a “flip flop” situation that appears to be the root
cause of our timer problems.
Though, again I am not sure.
“Adam Mallory” <amallory@qnx.com> wrote in message
news:Xns91D776E1B5799amalloryqnxcom@209.226.137.4…
“Ivan Bannon” <> ivan.bannon@rjginc.com> > wrote in
news:a6t877$eu2$> 1@inn.qnx.com> :
This has happened again. We’ve noticed that it is only the “sleep”
timers that are
counting negative. We have an interrupt driven serial driver running
at a higher
proirity that Proc32. Could this be causing the problem? any help is
greatly
appreciated.
Why are you running your driver higher than Proc? The kernel(not proc)
can
still preempt you for scheduling purposes/exceptions etc. Unless of
course
you’ve remapped the PIC, so that Int0 isn’t the highest priority. Does
the
problem go away if you run under the priority of proc, but higher than
everyone else?
\
Cheers,
Adam
QNX Software Systems Ltd.
[ > amallory@qnx.com > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Where can I get the Proc32 4.25N and what’s new in it?
–
bung’s life…
shane: Ooh, just got a box from Microsoft, 11 DVDs, and a nice carrying case
for them all.
rath : How did you score such a booty?
shane: Tax refund $
rath : …and you bought SOFTWARE???
rain : Yeah well this thread is not a discussion about his intelligence…
“Ivan Bannon” <ivan.bannon@rjginc.com> a écrit dans le message de news:
a6qnvh$iip$1@inn.qnx.com…
This is an odd one. Below is the results of a ‘sin rtc’ command and it
shows negative timer values. When this happens of course the whole system
goes nuts.
ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 1817.568 0.500
1 25 //204/bin/tinit signal 14 -2142.577 60.000
2 25 //204/bin/tinit sleep -.— -.—
3 57 //204/bin/nameloc signal 6 -.— -.—
4 5 /bin/Fsys.eide proxy 13 1818.747 2.000
5 57 //204/bin/nameloc sleep -2168.182 0.000
6 61 //204//usr/ucb/Socket proxy 62 0.014 0.000
7 81 //204//recorder.proc proxy 84 -.— -.—
9 96 //204/bin/tinit sleep -.— -.—
10 116 //204//bin/Photon proxy 117 3.235 0.000
11 98 //204/bin/cron signal 14 -7.025 0.000
12 96 //204/bin/tinit signal 14 -2128.798 60.000
14 124 //204//chipsbios.ms signal 14 -.— -.—
15 74 //204//usr/ucb/inetd sleep -.— -.—
16 11448 //204/bin/Input sleep -199.975 0.000
17 11451 //204/bin/Input proxy 11453 -.— -.—
24 87 //204//samba/bin/nmbd proxy 88 4.643 0.000
41 9938 //204/*/bin/phrelay proxy 9942 0.599 1.000
These are the versions I am running:
PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25N Sep 24 2001
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys.eide eide 4.25A Feb 09 2000
//204/bin/Dev32 Dev32 4.23G Oct 04 1996
//204/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//204/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//204/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//204/bin/Pipe Pipe 4.23A Feb 26 1996
//204/bin/Net Net 4.25C Aug 30 1999
//204//Net.ether9000 Net.ether900 4.24E Feb 17 2000
//204//usr/ucb/Socket Socket 4.25C Aug 19 1998
//204/bin/Mqueue mqueue 4.24A Aug 30 1999
//204/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//204/bin/cron cron 4.23B Oct 30 1997
//204/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//204//bin/Photon Photon 1.14B Sep 03 1999
//204//bin/phfontpfr Photon Font 1.14H Jan 17 2001
You may notice that we are running Proc32 4.25N. This same results have
happened while running 4.25L.
Anyone have any ideas as to what the cause may be, and what the solution
is?
TIA
–
Ivan Bannon
RJG Inc.