From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <531075E7.7060107@xenomai.org> Date: Fri, 28 Feb 2014 12:41:27 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <530CFB0D.8040001@xenomai.org> <530CFC27.5050700@xenomai.org> <530D0205.9050406@xenomai.org> <530D0BBD.6070704@xenomai.org> <530D2C92.9010607@xenomai.org> <530E6159.4050204@xenomai.org> <530F17EC.6020204@xenomai.org> <530F9CA2.2040601@xenomai.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] RaspberryPi kernel 3.8 issue List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gregory Dymarek Cc: xenomai@xenomai.org On 02/27/2014 09:33 PM, Gregory Dymarek wrote: > Not sure if I understand this. This is the first call to __report_bad_irq ( > https://github.com/raspberrypi/linux/blob/rpi-3.8.y/kernel/irq/spurious.c ) > > I added the trace on line 192. > > AFAIK this is the first call to the function. the trace freeze i added is > not conditional. I think the issue you observe is that the irqs_unhandled counter goes over 99000, meaning that the driver returns IRQ_NONE and does not acknowledge the interrupt at device level, so that the interrupt triggers again. So, having enough trace points to see what happens before this irq storm will be hard. Could you try reducing the 100000 and 99000 thresholds in kernel/irq/spurious.c, function note_interrupt? -- Gilles.