From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Paul Adrian Glaubitz Date: Wed, 15 Jul 2020 06:39:34 +0000 Subject: Re: ioremap and dma cleanups and fixes for superh (2nd resend) Message-Id: List-Id: References: <20200714121856.955680-1-hch@lst.de> <20200714155914.GA24404@brightrain.aerifal.cx> <8cbf2963-d0e4-0ca8-4ffe-c2057694447f@physik.fu-berlin.de> <011f29e6-ad71-366e-dbff-bc8471f3da60@physik.fu-berlin.de> <20200715031210.GD14669@brightrain.aerifal.cx> In-Reply-To: <20200715031210.GD14669@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rich Felker Cc: Christoph Hellwig , Yoshinori Sato , linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org On 7/15/20 5:12 AM, Rich Felker wrote: >> See the traces below and let me know what you think. > > I've got a slightly earlier version (my for-next) built for qemu r2d > board, and don't get any such messages. Do you have a lock-debugging > option enabled that's catching a problem, perhaps? Which kernel option would be that? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913