Tamas Szklenar wrote:
> Tick Device: mode: 0
> Broadcast device
> Clock Event Device: pit
> mode: 2
>
>
> Tick Device: mode: 0
> Clock Event Device: lapic
> mode: 1
>
> Tick Device: mode: 0
> Clock Event Device: lapic
> mode: 1
>
> Tick Device: mode: 0
> Clock Event Device: lapic
> mode: 1
>
> Tick Device: mode: 0
> Clock Event Device: lapic
> mode: 1
The pit is in broadcast mode and the lapic timers are in "shutdown"
state, which means that Linux is using the PIT, and Xenomai fails to
start because it tries to use the lapic.
That is probably related to the following messages in the kernel logs:
Jan 3 13:12:01 cfhat12 kernel: [ 0.016000] System has AMD C1E enabled
Jan 3 13:12:01 cfhat12 kernel: [ 0.160009] Switch to broadcast mode on CPU1
Jan 3 13:12:01 cfhat12 kernel: [ 0.160090] #2
Jan 3 13:12:01 cfhat12 kernel: [ 0.252008] Switch to broadcast mode on CPU2
Jan 3 13:12:01 cfhat12 kernel: [ 0.252052] #3
Jan 3 13:12:01 cfhat12 kernel: [ 0.016000] Switch to broadcast mode on CPU3
Jan 3 13:12:01 cfhat12 kernel: [ 0.344033] Brought up 4 CPUs
Jan 3 13:12:01 cfhat12 kernel: [ 0.344037] Total of 4 processors activated
(27322.12 BogoMIPS).
Jan 3 13:12:01 cfhat12 kernel: [ 0.345670] Switch to broadcast mode on CPU0
And explains the patch Philippe sent in the mean-time...
--
Gilles.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
