Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933903AbbDJNYg (ORCPT ); Fri, 10 Apr 2015 09:24:36 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:32832 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965231AbbDJNYX (ORCPT ); Fri, 10 Apr 2015 09:24:23 -0400 Date: Fri, 10 Apr 2015 14:23:30 +0100 From: Mark Brown To: Marcel Ziswiler Cc: linux-can@vger.kernel.org, linux-spi@vger.kernel.org, linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, Laxman Dewangan , Oliver Hartkopp , Marc Kleine-Budde , Wolfgang Grandegger , Thierry Reding , Stephen Warren , Alexandre Courbot , Stefan Agner , Himangi Saraogi , Julia Lawall , Stefano Babic , Christian Pellegrin , "DavidS.Miller" , Marc Zyngier , Sascha Hauer Message-ID: <20150410132330.GH6023@sirena.org.uk> References: <1428670853.7008.87.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qrdGlhWsTzJpGMIr" Content-Disposition: inline In-Reply-To: <1428670853.7008.87.camel@localhost.localdomain> X-Cookie: I've been there. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [REGRESSION] commit 0461a41 "spi: Pump transfers inside calling context for spi_sync()" breaks Apalis/Colibri T30 with MCP2515 SPI CAN controller X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1581 Lines: 42 --qrdGlhWsTzJpGMIr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 10, 2015 at 03:00:53PM +0200, Marcel Ziswiler wrote: > Hi there Please try to use somewhat more targetted CC lists... > I also have not yet looked further into what exactly is happening and > whether or not the SPI stack, the Tegra SPI controller driver or the > MCP2515 SPI CAN driver is to blame but rather decided to ask Mr. Brown > and the community first for any insights they might have to share. > Anybody? I'd ask for trace logs but obviously we can't turn them on until boot has finished... Adding some trace in the relevant bits of code to try to see where it's deadlocking is the obvious first step. --qrdGlhWsTzJpGMIr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVJ87SAAoJECTWi3JdVIfQLCQH+gKqUSelufOuwzReQh4vYJls jWECjIWTrJ6iHlOSrP7ryYU42l6FXR7st6zdabpcmlSJUnzNSqJCAn+Fej3xL0hf LTcYWaqCUsWDEbb37S0j42KIJAjNUxrVXd23HrxrySrMnZaUikXmkxviPnJyoevd cieOW7ZeL8B1G9YtJYG/WjjcXNULa707U60GHutRZWsOT6pRD1uhD6+wxTqJBgpz iBJ/Ijnn6jo0XEhvGyM/p02GxWha6RttvMePG7QKc2CjPjXvj85zRBpVzs/mFk3z ZNdhYFnnOaiyjFGxIN+MPee4Y5arHgZopVlMtLS0Ph5+MiLOckqvBOmFmwlGzgY= =ClLh -----END PGP SIGNATURE----- --qrdGlhWsTzJpGMIr-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/