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