From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <531075E7.7060107@xenomai.org> 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> <531075E7.7060107@xenomai.org> Date: Sat, 1 Mar 2014 12:27:43 +0000 Message-ID: From: Gregory Dymarek Content-Type: text/plain; charset=ISO-8859-1 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: xenomai@xenomai.org Hi Gilles, Uploaded a new trace in here with them being reduced to 10 and 9 respectively: https://github.com/gregd72002/rpicopter/blob/master/tmp/frozen On 28 February 2014 11:41, Gilles Chanteperdrix < gilles.chanteperdrix@xenomai.org> wrote: > 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. >