From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 26 Feb 2014 20:29:31 +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 Here is one more ipipe trace with less garbage: http://pastebin.com/WG80f6cx This happened when i plug usb device after boot is complete On 26 February 2014 19:59, Gregory Dymarek wrote: > > Gilles > here is the ipipe trace (see line 112) > http://pastebin.com/EcLn0MxJ > > that corresponds to > http://pastebin.com/vjLJVDGS > > I do not see any call to enable irq, but there are plenty calls for debug. > > > Could you also explain in a few words the previous patch please. > What was wrong with local_fiq_disable() defined as ipipe_stall_root() ? > > Thanks > > > On 25 February 2014 23:51, Gilles Chanteperdrix < > gilles.chanteperdrix@xenomai.org> wrote: > >> On 02/26/2014 12:20 AM, Gregory Dymarek wrote: >> > well, this does not work for me. It boots fine when there is no USB >> device >> > plugged in. >> > However, when my WIFI or bluetooth adapter is plugged in, the boot log >> > shows: http://pastebin.com/vjLJVDGS >> >> Well, it looks like a different issue, which happens when irqs are >> re-enabled by DWC_SPINUNLOCK_IRQRESTORE. So, maybe we have progressed. I >> am cloning the rpi repository, to see what happens at this point. >> >> But you can try and use the I-pipe tracer again, put a trace freeze in >> the "report_bad_irq" function. >> >> -- >> Gilles. >> > > >