RT Throtteling with PREEMT-RT on UBIFS root fs update

RT Throtteling with PREEMT-RT on UBIFS root fs update

[Tim Sander]

Hi

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.

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.

Any ideas whats causing this?
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 fur den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail.

Re: RT Throtteling with PREEMT-RT on UBIFS root fs update

[Tim Sander]

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: RT Throtteling with PREEMT-RT on UBIFS root fs update

[Thomas Gleixner]

On Thu, 17 Nov 2011, Tim Sander wrote:
> 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?

There is no harm, this message is informative and if that behaviour is
directly related to an ubifs update then I'd say we should not worry
too much about it. Though it'd be interesting to poke the UBIFS folks
about it.

Thanks,

	tglx