M. Koehrer wrote:
> O.k,
>
> I tried once more with the NMI watchdog stuff.
> However, it looks as if I do not understand the NMI watchdog correctly...
> I passed nmi_watchdog=1 as kernel parameter.
> Now, the NMI watchdog seems to be o.k.
> I have set the kernel parameter "NMI watchdog latency threshold (us)" to
> 1000000 (1 second).
> Now I do a modprobe xeno_nucleus.
> This is o.k.
> Then I do a modprobe xeno_native.
> This leads to a watchdog NMI on the console after 1s.
> "NMI watchdog detected timer latency above 100000us"
> CPU 1
> EIP is at mwait_idle 0x23/0x37
>
> When I compile the Xenomai functionality directly into the kernel (no
> modules), I never reach
> the login prompt at my PC as the NMI watchdog from above came first...
>
> Well, somehow the NMI stuff seems to work. However, I am not able to start my
> application
> as my systems gets the NMI before I have the chance to start the
> application...
> What is wrong here? I think, I miss one piece in the puzzle...
>
> Thanks for any support on that strange behaviour.
1 second is probably way to much and overflow a 32 bits value when
converted to a processor ticks count. The defaults of 100 us is more
reasonable.
--
Gilles Chanteperdrix
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
