Re: [Xenomai-core] preemptive doesn't work
On 03/06/2012 08:55 AM, Roberto Bielli wrote: Hi, it seems that i have a big problem with preemption. (kernel 2.6.31, arm freescale imx25, xenomai 2.5.6 ) I send a simple application that doesn't work. The task with name 'task2ms' has higher priority than 'taskPrintf', but 'taskPrintf' stop the task 'task2ms' until sleeps. I think i have a problem with ipipe porting. Any idea ? Please try getting a trace with the I-pipe tracer. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] preemptive doesn't work
Hi Gilles,
here is the new trace.
Il 06/03/2012 13:09, Gilles Chanteperdrix ha scritto:
On 03/06/2012 11:14 AM, Roberto Bielli wrote:
Hi,
here is the trace.
Please try to capture the xntimer_next_local_shot which happens before
the bug to see if the timer ticks when expected.
Also note that if we are going through __ipipe_preempt_schedule_irq, it
means that the task eating the cpu is running in secondary mode. So, you
should use T_WARNSW to see.
Please keep the discussion on the mailing list.
--
++
Roberto Bielli
Sviluppo Software
Axel S.r.l.
Via Del Cannino, 3
21020 Crosio Della Valle
Varese - Italy
Telefono: +39 0332 949600
Fax: +39 0332 969315
E-mail: roberto.bie...@axelsw.it
Web Site: www.axelsw.it
++
Si precisa che le informazioni contenute in questo messaggio sono riservate e
ad uso esclusivo del destinatario.
Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di
eliminarlo senza copiarlo e di non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie.
Informativa sul trattamento dei dati personali (D. Lgs. 196/2003).
I dati utilizzati per la spedizione del presente messaggio sono utilizzati da
Axel S.r.l., titolare del trattamento,
per l'invio delle comunicazioni dei diversi settori aziendali, non essendo
autorizzata la divulgazione a terzi.
Potrete rivolgere alla seguente mail richieste di verifica, rettifica o
cancellazione dei Vostri dati: i...@axelsw.it
This e-mail and any attachments is confidential and may contain privileged
information
intended for the addressee(s) only. Dissemination, copying, printing or use by
anybody
else is unauthorised. If you are not the intended recipient,
please delete this message and any attachments and advise the sender
by return e-mail.Thank you.
++
I-pipe worst-case tracing service on 2.6.31/ipipe-1.16-02
CPU: 0, Begin: 413559887374 cycles, Trace Points: 27 (-10/+1), Length: 81 us
Calibrated minimum trace-point overhead: 1.029 us
+- Hard IRQs ('|': locked)
|+ unused
||+--- unused
|||+-- Xenomai
+- Linux ('*': domain stalled, '+': current, '#': current+stalled)
|+-- Delay flag ('+': 1 us, '!': 10 us)
||+- NMI noise ('N')
|||
TypeUser Val. TimeDelay Function (Parent)
| +begin 0x8001 -1262.313 __up_read+0x30 (up_read+0x18)
| #end 0x8001 -1241.880 __up_read+0x50 (up_read+0x18)
#func-1221.850 ipipe_check_context+0x10
(__up_read+0x5c)
#func-1201.522 __ipipe_restore_root+0x10
(__up_read+0x130)
#func-1191.149 __ipipe_unstall_root+0x10
(__ipipe_restore_root+0x94)
| #begin 0x8000 -1181.597 __ipipe_unstall_root+0x34
(__ipipe_restore_root+0x94)
| +end 0x8000 -1161.432 __ipipe_unstall_root+0x98
(__ipipe_restore_root+0x94)
+func-1152.970 ipipe_check_context+0x10
(__up_read+0x138)
+func-112 107.507 __ipipe_check_root+0x10
(ret_from_exception+0x4)
| +func -44.656 __ipipe_grab_irq+0x10 (__irq_usr+0x70)
| +begin 0x 0+ 2.462 __ipipe_grab_irq+0x5c (__irq_usr+0x70)
:| +func 2+ 3.626 __ipipe_handle_irq+0x14
(__ipipe_grab_irq+0x68)
:| +func 6+ 2.104 __ipipe_ack_timerirq+0x10
(__ipipe_handle_irq+0x9c)
:| +func 8+ 2.805 __ipipe_ack_level_irq+0x10
(__ipipe_ack_timerirq+0x24)
:| +func 11+ 1.776 mxc_mask_irq+0x10
(__ipipe_ack_level_irq+0x3c)
:| +func 12+ 1.686 mxc_mask_irq+0x10
(__ipipe_ack_level_irq+0x54)
:| +func 14+ 1.507 __ipipe_mach_acktimer+0x10
(__ipipe_ack_timerirq+0x28)
:| +func 15+ 1.611 __ipipe_end_level_irq+0x10
(__ipipe_ack_timerirq+0x38)
:| +func 17+ 2.253 mxc_unmask_irq+0x10
(__ipipe_end_level_irq+0x28)
:| +func 19+ 2.283 __ipipe_dispatch_wired+0x10
Re: [Xenomai-core] preemptive doesn't work
On 03/06/2012 02:00 PM, Roberto Bielli wrote: Hi Gilles, here is the new trace. There is nothing to see on that trace. Please increase the number of trace points, and trigger a trace when you detect a problem., the number of trace points should be sufficient to get the timer programmation which happens before the problem. Also, did you try T_WANRSW ? Please disable the configuration of you mail server which asks me to send a receipt to each every mail you send me. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] preemptive doesn't work
Hi Gilles, i changed the min value of the '__ipipe_mach_set_dec' but the situation is the same. I see with the scope that the task with less priority is not interrupted. It's difficult to see with the ipipe trace the problem so i put the xenomai trace in the application with |xntrace_user_start|/|xntrace_user_stop|. Is the log of xenomai in the same place (/proc/ipipe/trace/max ) of ipipe ? Thanks a lot Il 06/03/2012 14:04, Gilles Chanteperdrix ha scritto: On 03/06/2012 02:00 PM, Roberto Bielli wrote: Hi Gilles, here is the new trace. There is nothing to see on that trace. Please increase the number of trace points, and trigger a trace when you detect a problem., the number of trace points should be sufficient to get the timer programmation which happens before the problem. Also, did you try T_WANRSW ? Please disable the configuration of you mail server which asks me to send a receipt to each every mail you send me. -- ++ Roberto Bielli Sviluppo Software Axel S.r.l. Via Del Cannino, 3 21020 Crosio Della Valle Varese - Italy Telefono: +39 0332 949600 Fax: +39 0332 969315 E-mail: roberto.bie...@axelsw.it Web Site: www.axelsw.it ++ Si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. Informativa sul trattamento dei dati personali (D. Lgs. 196/2003). I dati utilizzati per la spedizione del presente messaggio sono utilizzati da Axel S.r.l., titolare del trattamento, per l'invio delle comunicazioni dei diversi settori aziendali, non essendo autorizzata la divulgazione a terzi. Potrete rivolgere alla seguente mail richieste di verifica, rettifica o cancellazione dei Vostri dati: i...@axelsw.it This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.Thank you. ++ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] preemptive doesn't work
On 03/06/2012 04:14 PM, Roberto Bielli wrote: Hi Gilles, i changed the min value of the '__ipipe_mach_set_dec' but the situation is the same. I see with the scope that the task with less priority is not interrupted. In the trace you sent, we clearly saw that it was interrupted by a timer interrupt. It's difficult to see with the ipipe trace the problem so i put the xenomai trace in the application with |xntrace_user_start|/|xntrace_user_stop|. Is the log of xenomai in the same place (/proc/ipipe/trace/max ) of ipipe ? See the latency test for an example of usage of the I-pipe tracer in user-space. When using latency -f the trace is available in /proc/ipipe/trace/frozen. What about T_WARNSW (it is the third time I ask). Also, it would be nice if you could try a more recent version of Xenomai and of the I-pipe patch, say 2.6.0 with the I-pipe patch for 2.6.38. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] preemptive doesn't work
Hi Gilles, about T_WARNSW i see in the /proc/xenomai/stat that my task hasn't change mode (the value of MSW is 0 ) so, it hasn't changed in secondary mode. Correct ? Il 06/03/2012 16:20, Gilles Chanteperdrix ha scritto: On 03/06/2012 04:14 PM, Roberto Bielli wrote: Hi Gilles, i changed the min value of the '__ipipe_mach_set_dec' but the situation is the same. I see with the scope that the task with less priority is not interrupted. In the trace you sent, we clearly saw that it was interrupted by a timer interrupt. It's difficult to see with the ipipe trace the problem so i put the xenomai trace in the application with |xntrace_user_start|/|xntrace_user_stop|. Is the log of xenomai in the same place (/proc/ipipe/trace/max ) of ipipe ? See the latency test for an example of usage of the I-pipe tracer in user-space. When using latency -f the trace is available in /proc/ipipe/trace/frozen. What about T_WARNSW (it is the third time I ask). Also, it would be nice if you could try a more recent version of Xenomai and of the I-pipe patch, say 2.6.0 with the I-pipe patch for 2.6.38. -- ++ Roberto Bielli Sviluppo Software Axel S.r.l. Via Del Cannino, 3 21020 Crosio Della Valle Varese - Italy Telefono: +39 0332 949600 Fax: +39 0332 969315 E-mail: roberto.bie...@axelsw.it Web Site: www.axelsw.it ++ Si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. Informativa sul trattamento dei dati personali (D. Lgs. 196/2003). I dati utilizzati per la spedizione del presente messaggio sono utilizzati da Axel S.r.l., titolare del trattamento, per l'invio delle comunicazioni dei diversi settori aziendali, non essendo autorizzata la divulgazione a terzi. Potrete rivolgere alla seguente mail richieste di verifica, rettifica o cancellazione dei Vostri dati: i...@axelsw.it This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.Thank you. ++ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] preemptive doesn't work
On 03/06/2012 04:35 PM, Roberto Bielli wrote: Hi Gilles, about T_WARNSW i see in the /proc/xenomai/stat that my task hasn't change mode (the value of MSW is 0 ) so, it hasn't changed in secondary mode. Or maybe it started in secondary mode and never switched mode? -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
