From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <525E8665.8000705@steinkuehler.net> Date: Wed, 16 Oct 2013 07:28:21 -0500 From: Charles Steinkuehler MIME-Version: 1.0 References: <525DC044.6090201@steinkuehler.net> <525E73FB.4060809@xenomai.org> <525E7ABF.8040403@steinkuehler.net> <525E7D85.9020307@xenomai.org> <525E81CD.6000603@steinkuehler.net> In-Reply-To: <525E81CD.6000603@steinkuehler.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] Hung task on Xenomai patched ARM 3.8.13 BeagleBone Kernel List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org On 10/16/2013 7:08 AM, Charles Steinkuehler wrote: > On 10/16/2013 6:50 AM, Gilles Chanteperdrix wrote: >> Ok, so the MMC irq is a gpio irq. And its counter is 0, which does not >> seem to be normal if the root filesystem in on MMC. Is it 0 too when >> you boot an unpatched kernel? >> >> Do you run a vanilla kernel or a vendor kernel with additional patches >> to drivers/gpio/gpio-omap.c, or maybe a beaglebone specific GPIO >> driver in drivers/gpio ? > = > It's a BeagleBone specific kernel with a list of patches as long as my > arm...and I have pretty long arms! > = > https://github.com/cdsteinkuehler/linux-dev/blob/3.8.13-bone28-xenomai/pa= tch.sh > = > I'm not sure about the GPIO interrupt. I'll see what happens with the > non-xenomai kernel, and review the board setup. Both the BeagleBone and the Xenomai kernels behave the same way. The GPIO mmc interrupt is stuck at zero, and the 80: INTC mmc interrupt count increases on access to the filesystem. -- = Charles Steinkuehler charles@steinkuehler.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 261 bytes Desc: OpenPGP digital signature URL: