[lkml]   [2012]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame?
On Tue, 2012-01-17 at 15:27 +0100, Tim Sander wrote:
> Hi
> I have further input to the ksoftirq/0 using as much cpu as available on a
> arm pcm043 platform without load with a 3.0.14-rt31 kernel and some local
> platform adaptions.
> > I was thinking about this ksoftirq0 running on max cpu. The context:
> > > > > and the running wild ksoftirqd0 most probably after the kernel
> > > > > message: "sched: RT throttling activated"

> I think that the message "sched: RT throttling activated" and the ksoftirqd
> running on full cpu are possibly to seperate errors. Btw. is there a way to
> find out which processes where conuming this timeframe. It would be nice to add
> info output which processes caused the throtteling. Is it possible to get this
> information out of the scheduler structure?


This is your territory.

-- Steve

 \ /
  Last update: 2012-01-17 15:45    [W:0.095 / U:41.952 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site