From: "Tim Sander" <tim.sander@hbm.com>
To: "linux-rt-users" <linux-rt-users@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: RT Throtteling with PREEMT-RT on UBIFS root fs update
Date: Thu, 17 Nov 2011 14:54:18 +0100 [thread overview]
Message-ID: <201111171454.18742.tim.sander@hbm.com> (raw)
In-Reply-To: <201111111056.53803.tim.sander@hbm.com>
Hi
This is just a followup
> We are having a problem with a slightly patched (some platform patches,
> newest stable ubifs patches) 3.0.7-rt20 kernel after updating the firmware
> on the first boot we get a message:
> sched: RT throttling activated
> and ksoftirqd/0 taking 95% of the cpu time.
RT throtteling is still activate with 3.0.9-rt25 (+ ubifs stable patches) but
now ksoftirqd/0 is not going berserk.
> Interestingly this only happens after the ubifs root has been updated on
> the first boot (and not allways). Subsequent boot problems have not been
> seen.
Ok the only nitpik that is left, that the processor activates rt throtteling
after the first boot with updated ubifs image.
> Any ideas whats causing this?
Well it can be said that it is not ksoftirqd/0 going berserk which is
triggering this. So i guess when this message is printed it just shows that
the cpu had been temporarily overloded with work in interrupt context.
Is there more harm to expect from this message or save to ignore if the
systemload is normal again?
Best regards
Tim
> Sorry for noise below, please ignore:
Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany | www.hbm.com
Registered as GmbH (German limited liability corporation) in the commercial register at the local court of Darmstadt, HRB 1147
Company domiciled in Darmstadt | CEO: Andreas Huellhorst | Chairman of the board: James Charles Webster
Als Gesellschaft mit beschraenkter Haftung eingetragen im Handelsregister des Amtsgerichts Darmstadt unter HRB 1147
Sitz der Gesellschaft: Darmstadt | Geschaeftsfuehrung: Andreas Huellhorst | Aufsichtsratsvorsitzender: James Charles Webster
The information in this email is confidential. It is intended solely for the addressee. If you are not the intended recipient, please let me know and delete this email.
Die in dieser E-Mail enthaltene Information ist vertraulich und lediglich für den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail.
next prev parent reply other threads:[~2011-11-17 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 9:56 RT Throtteling with PREEMT-RT on UBIFS root fs update Tim Sander
2011-11-17 13:54 ` Tim Sander [this message]
2011-11-17 14:15 ` Thomas Gleixner
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=201111171454.18742.tim.sander@hbm.com \
--to=tim.sander@hbm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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