From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Alexey Galakhov <agalakhov@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] mini2440: ipipe kernel stuck in idle loop after xenomai init
Date: Fri, 06 May 2011 11:33:42 +0200 [thread overview]
Message-ID: <4DC3C076.7010203@domain.hid> (raw)
In-Reply-To: <4DC3BF3C.2030405@domain.hid>
On 05/06/2011 11:28 AM, Alexey Galakhov wrote:
> On 05/05/2011 11:26 PM, Gilles Chanteperdrix wrote:
>> Please try and move the cal to ipipe_tsc_update to the acktimer function.
>> Also call printk in the actkimer function, in order to see if the last
>> action is a set_dec, or an acktimer.
> Just tried to add printk (not moved anything). Got:
>
> ipipe_mach_set_dec: 4294967295
> ipipe_mach_set_dec: 4294967295
> ipipe_mach_set_dec: 42186
> Xenomai: scheduling class idle registered.
> Xenomai: scheduling class rt registered.
> acktimer
> acktimer
> acktimer
> acktimer
> acktimer
> Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded.
> ipipe_mach_set_dec: 42187
> Xenomai: starting native API services.
> Xenomai: starting POSIX services.
> Xenomai: starting RTDM services.
> acktimer
> msgmni has been set to 119
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
> io scheduler noop registered (default)
Ok, so there is a timer interrupt which does not result in reprogramming
the timer, all you need to find out is why... Could you print the tsc
value for each of these printks?
Also, have you tried putting the call to the tsc update function in the
acktimer function?
--
Gilles.
next prev parent reply other threads:[~2011-05-06 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 12:20 [Adeos-main] mini2440: ipipe kernel stuck in idle loop after xenomai init Alexey Galakhov
2011-05-05 12:37 ` Gilles Chanteperdrix
2011-05-05 12:58 ` Alexey Galakhov
2011-05-05 13:16 ` Alexey Galakhov
2011-05-05 14:02 ` Gilles Chanteperdrix
2011-05-05 14:12 ` Alexey Galakhov
2011-05-05 14:42 ` Gilles Chanteperdrix
2011-05-05 15:23 ` Alexey Galakhov
2011-05-05 15:36 ` Gilles Chanteperdrix
[not found] ` <4DC2D0C9.3020605@domain.hid>
[not found] ` <4DC2DDC6.8090909@domain.hid>
2011-05-06 9:28 ` Alexey Galakhov
2011-05-06 9:33 ` Gilles Chanteperdrix [this message]
2011-05-11 10:29 ` Alexey Galakhov
2011-05-11 10:50 ` Gilles Chanteperdrix
2011-05-11 12:24 ` Gilles Chanteperdrix
2011-05-11 12:35 ` Alexey Galakhov
2011-05-11 23:51 ` Gilles Chanteperdrix
2011-05-06 9:55 ` Gilles Chanteperdrix
2011-05-06 10:44 ` Alexey Galakhov
2011-05-06 11:02 ` Alexey Galakhov
2011-05-06 9:32 ` Alexey Galakhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC3C076.7010203@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=agalakhov@domain.hid \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.