From: Thomas Gleixner <tglx@linutronix.de>
To: "Mehlan, Markus" <Markus.Mehlan@ritter.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: clock_nanosleep: cyclic POSIX thread freezes during time setting
Date: Mon, 5 Oct 2009 20:57:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0910052044410.2646@localhost.localdomain> (raw)
In-Reply-To: <40F775BBD072A346957E787B3D0DBE5F1C97AF@w2k3-46ex01.RITTER.LOCAL>
Markus,
On Mon, 5 Oct 2009, Mehlan, Markus wrote:
> I have the following problem on a MPC5200b customer board,
> tested with linux-2.6.24.7-rt11 and 2.6.26.8-rt16.
>
> I start the test application. Every 200ms I can see a new
> line on the console ("ping"). Then I set the time with "date
> 100509152009" a few times on
> a second console. The effect is that the output on the first console
> freezes and if I check
> the time with "date", the time doesn't progress during the "freeze
> time". After the
> "freeze time" the time makes a jump of several seconds.
>
> In the real application the "ping" should reset the watchdog-timer. The
> freezing causes
> an elapsing of the watchdog-timer and finally a reboot.
>
> Has someone an idea?
Just tested on a MPC5200 board with cyclictest and setting date on a
second console. Unfortunately I cannot reproduce that problem. Can you
try to activate the function tracer and capture what the system is
doing. That might us give some clue about the problem.
Thanks,
tglx
next prev parent reply other threads:[~2009-10-05 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:20 Mehlan, Markus
2009-10-05 18:57 ` Thomas Gleixner [this message]
2009-10-06 9:00 ` AW: " Mehlan, Markus
2009-10-06 9:13 ` Thomas Gleixner
2009-10-06 9:56 ` AW: " Mehlan, Markus
2009-10-06 10:04 ` Thomas Gleixner
2009-10-06 10:09 ` AW: " Mehlan, Markus
2009-10-07 14:13 ` Mehlan, Markus
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=alpine.LFD.2.00.0910052044410.2646@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=Markus.Mehlan@ritter.info \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome