From: Jan Kiszka <jan.kiszka@siemens.com>
To: harald.fessl@sigmatek.at, xenomai@xenomai.org
Subject: Re: [Xenomai] Fwd: Re: Problem that the Linux scheduler is not called for some ms
Date: Wed, 23 Sep 2015 12:36:03 +0200 [thread overview]
Message-ID: <56028093.6050805@siemens.com> (raw)
In-Reply-To: <56026810.8040300@sigmatek.at>
On 2015-09-23 10:51, Harald Feßl wrote:
> Hi
>
> The linux tasks are not blocked (not all).
> I think the problem is , that the linux scheduler function in the kernel
> is not called for some ms.
> I have also traced the calls to the scheduler function
> "static int __sched __schedule(void)"
> and sometimes when the decribed problem occur this function is not
> called while no linux task are running.
If no task is runnable, there is also no reason to invoke schedule.
Please post a ftrace log of your system, covering both a working and a
non-working cycle, including cobalt* and at least sched and irq events.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-09-23 10:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5601617F.3080800@sigmatek.at>
2015-09-22 14:13 ` [Xenomai] Problem that the Linux scheduler is not called for some ms Wolfgang Netbal
2015-09-22 18:44 ` Jan Kiszka
[not found] ` <560263A0.4080208@sigmatek.at>
2015-09-23 8:51 ` [Xenomai] Fwd: " Harald Feßl
2015-09-23 10:36 ` Jan Kiszka [this message]
2015-09-24 14:46 ` Harald Feßl
2015-09-25 8:44 ` Harald Feßl
2015-09-29 12:38 ` Johann Obermayr
2015-09-29 15:56 ` Philippe Gerum
[not found] ` <561256C6.4070508@sigmatek.at>
[not found] ` <561264DD.2020803@xenomai.org>
2015-10-07 9:01 ` Johann Obermayr
2015-10-07 9:07 ` Philippe Gerum
2015-10-07 14:23 ` Harald Feßl
2015-10-07 15:27 ` Philippe Gerum
2015-10-08 7:29 ` Harald Feßl
2015-10-14 7:29 ` Harald Feßl
2015-10-14 8:15 ` Philippe Gerum
2015-10-19 9:37 ` Harald Feßl
2015-10-22 13:26 ` Harald Feßl
2015-10-23 8:02 ` Philippe Gerum
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=56028093.6050805@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=harald.fessl@sigmatek.at \
--cc=xenomai@xenomai.org \
/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.