Re: [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame?
From: Steven Rostedt <rostedt@goodmis.org>
Date: 2012-01-17 14:42:10
Also in:
lkml
From: Steven Rostedt <rostedt@goodmis.org>
Date: 2012-01-17 14:42:10
Also in:
lkml
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 i.mx pcm043 platform without load with a 3.0.14-rt31 kernel and some local platform adaptions.quoted
I was thinking about this ksoftirq0 running on max cpu. The context:quoted
quoted
quoted
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?
Peter, This is your territory. -- Steve