From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B59B5C433E0 for ; Wed, 15 Jul 2020 03:12:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9B13420663 for ; Wed, 15 Jul 2020 03:12:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727990AbgGODMN (ORCPT ); Tue, 14 Jul 2020 23:12:13 -0400 Received: from brightrain.aerifal.cx ([216.12.86.13]:60896 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726852AbgGODMN (ORCPT ); Tue, 14 Jul 2020 23:12:13 -0400 Date: Tue, 14 Jul 2020 23:12:11 -0400 From: Rich Felker To: John Paul Adrian Glaubitz Cc: Christoph Hellwig , Yoshinori Sato , linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: ioremap and dma cleanups and fixes for superh (2nd resend) Message-ID: <20200715031210.GD14669@brightrain.aerifal.cx> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011f29e6-ad71-366e-dbff-bc8471f3da60@physik.fu-berlin.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 15, 2020 at 01:12:33AM +0200, John Paul Adrian Glaubitz wrote: > Hello! > > I have applied Christoph's full series on top of Linus' tree and I can confirm that > the kernel boots fine on my SH-7785LCR board. > > Thus, for the whole series of patches: > > Tested-by: John Paul Adrian Glaubitz > > However, independent of Christoph's series, the kernels throws two backtraces during > boot which I think should require a git bisect (unless I missed a configuration option > as I trimmed down the kernel a bit to make sure it's not too big). > > 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? Rich