Skip to contentSkip to conversation

Something about timers

DISCUSSION jarmo 2 participants 2 messages Sep 9, 2005

lore
Share & tools
lore

jarmo

author
#0 lore raw

Hi

Just noticed, that if you compile kernel without looking, Prosessor type and features -> Timer frequency, default is 250ms, you get quite suprising behaviour with your ax25 stuff, especially 6pack :)
I'd say quite quick actions and in server case crashes :(. That mean you have both fbb and cluster running in same computer with 5 user ports.

So when taking forinstance kernel 2.6.13 in use, select timer as 1000ms, then your normal ax25 timers should work.

Jarmo

Signature · 3 lines
Linux is the answer.
What was your question?
(Brian Lane)
#1 lore raw
Quoted 10 lines · jarmo

Just noticed, that if you compile kernel without looking, Prosessor type and features -> Timer frequency, default is 250ms, you get quite suprising behaviour with your ax25 stuff, especially 6pack :)
I'd say quite quick actions and in server case crashes :(. That mean you have both fbb and cluster running in same computer with 5 user ports.

So when taking forinstance kernel 2.6.13 in use, select timer as 1000ms, then your normal ax25 timers should work.

Time in AX.25, NET/ROM and ROSE is still being meassured in units of timer ticks which has not only changed going from 2.4 to 2.6; it's also differing between architectures. I've recently sent out a set of three patches to standardize that on ms. That's probably a too small unit so I think I'm going to change that again before submitting to upstream.

Any crashes you may see are certainly unrelated to this.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21