From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754549Ab2AQOmK (ORCPT ); Tue, 17 Jan 2012 09:42:10 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:46658 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753958Ab2AQOmI (ORCPT ); Tue, 17 Jan 2012 09:42:08 -0500 X-Authority-Analysis: v=2.0 cv=SqgSGYy0 c=1 sm=0 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=p-wZvnPcUTwA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=bcbrHNUOv8UQ218sAlwA:9 a=PUjeQqilurYA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Message-ID: <1326811325.17534.48.camel@gandalf.stny.rr.com> Subject: Re: [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? From: Steven Rostedt To: Tim Sander , Peter Zijlstra Cc: Tim Sander , LKML , RT , Thomas Gleixner , Clark Williams , John Kacur Date: Tue, 17 Jan 2012 09:42:05 -0500 In-Reply-To: <201201171527.19165.tstone@iss.tu-darmstadt.de> References: <1324525237.5916.114.camel@gandalf.stny.rr.com> <201201121757.25467.tim.sander@hbm.com> <201201131042.08323.tim.sander@hbm.com> <201201171527.19165.tstone@iss.tu-darmstadt.de> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.2-1 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > > > 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? > Peter, This is your territory. -- Steve