From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <530FA6F4.9020705@xenomai.org> Date: Thu, 27 Feb 2014 21:58:28 +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> <530FA4B1.80305@xenomai.org> In-Reply-To: <530FA4B1.80305@xenomai.org> 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:48 PM, Gilles Chanteperdrix 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. > > __report_bad_irq is called when report_bad_irq has been called 100 > times. Could you put the trace freeze in report_bad_irq instead of > __report_bad_irq ? Sorry, no, that is not how it works. -- Gilles.