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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DE79CC433EF for ; Fri, 27 May 2022 06:51:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=e1J/GNmxWVOvzywBU2yRZrC5mqea3qNx65pVi3u/r6M=; b=rvsPPcfK7tgZov hpJG9MpnIwJfmzAPZCDKWVduINDaUFxrjyP7oLfao1LB2mJfjzPb5POlZ77Hr/3kpFJCWLHR4/+U7 8a6g43E98bc9PkT/EQ5GQQVFok1I/EfnGAakfTr9XdQ3vstkgJgrhv8cZhXHX/oMHXyckySqmdeVy RQZL7aOvW9aEugGmVpV70YdIF/0ea3NKjaTSikPrdn9NbObKT4JMsKs9iNPyxTh7LthV+PKjT7DEC WxuNhdtxnM0gwAGN9MHUOMh7Jjo6euOVOeJK4f4zJehyuIHRI9kFKKKg4/iQIZ0j0B+Wn2HfjCNy/ w7vxV3/eA4T4Z1mZeoaw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nuTny-00Gn9x-Eb; Fri, 27 May 2022 06:50:38 +0000 Received: from muru.com ([72.249.23.125]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nuTnu-00Gn8d-Uq for linux-arm-kernel@lists.infradead.org; Fri, 27 May 2022 06:50:36 +0000 Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id ADF298109; Fri, 27 May 2022 06:46:24 +0000 (UTC) Date: Fri, 27 May 2022 09:50:29 +0300 From: Tony Lindgren To: Arnd Bergmann Cc: Yegor Yefremov , Ard Biesheuvel , Linux-OMAP , linux-clk , Stephen Boyd , Linux ARM Subject: Re: am335x: 5.18.x: system stalling Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220526_235035_095684_ED8E2C38 X-CRM114-Status: GOOD ( 29.24 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org * Arnd Bergmann [220527 06:35]: > On Fri, May 27, 2022 at 6:44 AM Yegor Yefremov > wrote: > > On Thu, May 26, 2022 at 4:16 PM Arnd Bergmann wrote: > > > > > > On Thu, May 26, 2022 at 2:37 PM Yegor Yefremov > > > wrote: > > > > On Thu, May 26, 2022 at 10:19 AM Ard Biesheuvel wrote: > > > > > > > > > > On Thu, 26 May 2022 at 08:20, Tony Lindgren wrote: > > > > > > > > > > > > * Yegor Yefremov [220526 05:45]: > > > > > > > On Tue, May 24, 2022 at 4:19 PM Tony Lindgren wrote: > > > > > > > > Maybe also try with CONFIG_MUSB_PIO_ONLY=y to see if it makes things > > > > > > > > better or worse :) > > > > > > > > > > > > > > PIO is always the last resort :-) And now it proves it again. With > > > > > > > PIO_ONLY the system doesn't stall. > > > > > > > > > > > > OK great :) So it has something to do with drivers/dma/ti/cppi41.c, or > > > > > > with drivers/usb/musb/cppi_dma.c or whatever the dma for am335x here > > > > > > is. Or maybe there's something using stack for buffers being passed to > > > > > > dma again that breaks with vmap stack. > > > > > > > > > > > > > > > > In order to confirm this theory, could you please try rebuilding your > > > > > kernel with CONFIG_VMAP_STACK disabled, and leave everything else as > > > > > before? > > > > > > > > I have disabled the CONFIG_VMAP_STACK option: > > > > > > > > # zcat /proc/config.gz | grep VMAP_STACK > > > > CONFIG_HAVE_ARCH_VMAP_STACK=y > > > > # CONFIG_VMAP_STACK is not set > > > > > > > > The system stalls. > > > > > > Ok, I guess that means we can stop looking for invalid DMA buffers > > > on stacks. Out of the original commits you listed as possible causes, > > > we can also rule out 23d9a9280efe ("ARM: 9177/1: disable vmap'ed > > > stacks on suspend-capable SMP configs") and cafc0eab1689 > > > ("ARM: v7m: enable support for IRQ stacks"). It could still be > > > 9c46929e7989 ("ARM: implement THREAD_INFO_IN_TASK for > > > uniprocessor systems") and 5fe41793bc78 ("ARM: 9176/1: avoid > > > literal references in inline assembly") or possibly the merge. > > > > > > Can you post the whole .config file somewhere for reference? > > > In particular, do you have CONFIG_SMP, CONFIG_LD_IS_LLD > > > or CURRENT_POINTER_IN_TPIDRURO set? > > > > This is my config [1] and this is the system in question [2]. > > > > [1] https://github.com/visionsystemsgmbh/onrisc_br_bsp/blob/master/board/vscom/baltos/linux-experimental-config > > Thanks! The first thing I noticed in here is that this config enables both > CONFIG_ARCH_MULTI_V6 (for OMAP2) and CONFIG_SMP, which > gets you into a couple of corner cases that nobody else hits in practice. > > Can you still reproduce the problem if you turn off both of these? Based on what we just discussed on #armlinux, testing before and after commit 9c46929e7989 ("ARM: implement THREAD_INFO_IN_TASK for uniprocessor systems") might be a good idea as it enables some config options that did not get enabled earlier. Another thing that might help is to bisect again and ensure vmap stack config option stays disabled so issues related to vmap stack are kept out of the way. Regards, Tony _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel