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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3F04AC433F5 for ; Fri, 27 May 2022 09:50:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349440AbiE0Juz (ORCPT ); Fri, 27 May 2022 05:50:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350691AbiE0Juy (ORCPT ); Fri, 27 May 2022 05:50:54 -0400 Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49C6F106572; Fri, 27 May 2022 02:50:52 -0700 (PDT) Received: by mail-yb1-xb36.google.com with SMTP id v26so7104738ybd.2; Fri, 27 May 2022 02:50:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TrHpRv64c+YoK1HzOlrj1Q63oDbBkz6zw8zaaBGCR1k=; b=PZXsgFa+uHGoFqbkla1Fz2CNNzBPa1A2c8IO59HnUNeOUgZvG4ETvXJlXAkCKN+L/d 9Uda1N8PjUxI/Xe9KktOJvYvUMaW/QvYsuiAKSySxIFFNyoAQRYuaw15ronQp2rMecoY IIXrDFwRPZWqF+r9TQEl3NgpTLL90Tj6eyWjMM8xI4bosHWiU37t7qv0NDc/HBZOOMMg SLvzGHQn0Tb0DNpYVu0nL59cOQWypn+bgnsvk3U9tQV9ySY2WAW4uBcNUm8ono04qOk+ tBontVujuWGzexNUPEBDPg8W1zj6Oa6vpd4yZm5Of5d/G7gQSN6J07X3ctsD+kDZTeuC 3ZvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TrHpRv64c+YoK1HzOlrj1Q63oDbBkz6zw8zaaBGCR1k=; b=jQdQEy9PZ8yEDqMFn576VKhGFiTMZ60zdanvcCk314wPiZhZQVMvo234JWnOW50XU/ mD+vw784WXKoyCNBDQHfZKi61iJaVddL8Tr91TGzXZ5DAyK2cjzUH300w3RWuXUBnXx+ H4pnaFJR9z4XdBSt8kH1tjNblaceqK8lAOcpAF5K2pF3YHMN9IaEpRWtC6EAn5XPDXE6 tYOIJ3f1ixjcDqh/9z4xuppkIO/HlOMQ0BX8KOuBWg1VMNGqVwHD9/l1yI3/H92CnBuS DZI3WBJ4tHL+5fxQt94JWVOtRIKWHoQhrysmDPUBuaDv7JTC3sbpJtL3BQM/no1QTTb+ /RDA== X-Gm-Message-State: AOAM530gHg26rJb2zB8QgvzcVUmZAqzsfqAmPZG5R7KFKN/yW3+YImTV oTrXFEUR7sbO2xcOKv5rQfEhSCRybeoOgvCwzEh1PTES X-Google-Smtp-Source: ABdhPJzqL9ND6IPUcs+accWbxqFltjmOUNQB478M6BZsPPyV0GWJU3nx5NkHM9RjxbvbR6/Vb4sHdJfj4nqnLAhQT3A= X-Received: by 2002:a25:1c84:0:b0:64f:6ecc:8fa7 with SMTP id c126-20020a251c84000000b0064f6ecc8fa7mr32131205ybc.432.1653645051230; Fri, 27 May 2022 02:50:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yegor Yefremov Date: Fri, 27 May 2022 11:50:40 +0200 Message-ID: Subject: Re: am335x: 5.18.x: system stalling To: Arnd Bergmann Cc: Tony Lindgren , Ard Biesheuvel , Linux-OMAP , linux-clk , Stephen Boyd , Linux ARM Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On Fri, May 27, 2022 at 10:39 AM Arnd Bergmann wrote: > > On Fri, May 27, 2022 at 10:17 AM Yegor Yefremov > wrote: > > On Fri, May 27, 2022 at 8:57 AM Arnd Bergmann wrote: > > > > > > On Fri, May 27, 2022 at 8:50 AM Tony Lindgren wrote: > > > > * 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: > > > > > > > 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. > > > > > > Unfortunately the commits around 9c46929e7989 are the ones that failed > > > to build according to the original report. But it's possible that the > > > problem has something to do with > > > CONFIG_CURRENT_POINTER_IN_TPIDRURO, which is disabled > > > in the V6+SMP config, and which in turn is required for > > > THREAD_INFO_IN_TASK, IRQSTACKS and STACKPROTECTOR_PER_TASK. > > > > > > If any of the four are the cause of the stall, then turning off ARCH_OMAP2 and > > > CONFIG_CPU_V6 should show the same bug in older commits as well. > > > > Both config options disabled: > > > > # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP' > > # CONFIG_ARCH_MULTI_V6 is not set > > CONFIG_ARCH_MULTI_V6_V7=y > > # CONFIG_SMP is not set > > > > This helped - no stalls. > > Ok, that does point back to a recent regression then, rather than something > that was already broken and just uncovered by the changed behavior. > > Can you try the other combinations as well? OMAP2=y with SMP=n > and OMAP2=n with SMP=y? Hopefully that narrows it down enough that > we can look at which code paths actually changed. # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP' # CONFIG_ARCH_MULTI_V6 is not set CONFIG_ARCH_MULTI_V6_V7=y CONFIG_SMP=y CONFIG_SMP_ON_UP=y No stalls. # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP\|ARCH_OMAP2' CONFIG_ARCH_MULTI_V6=y CONFIG_ARCH_MULTI_V6_V7=y CONFIG_ARCH_OMAP2=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_ARCH_OMAP2PLUS_TYPICAL=y No stalls. As soon as I enable both SMP and OMAP2 options the system stalls. Yegor # CONFIG_SMP is not set 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 316A3C433EF for ; Fri, 27 May 2022 09:52:03 +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:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=HuhquB3Tl49eMitq2LqQOsqykRIJRYtBdfUt9kHls/Y=; b=x+gjbOvQ0WgG64 RuXRplS7DZfPzD6HRQkFY0NTGKs61eQJtTySbT0uvYgvOgd/jDGIQCjckQ8xj7cKOi/GeM9lvurxt R6HxxBfH4hpUjUbDRMjYOU6yUY/ciZgWFKbTtkdJz+3d5dTKhmWeCQsh6U1d4Ptpx1pl+22baBApi BmnJFCbZBpx7Exs8lagS7k0vmkVuCqD2memWiDUcODeozDMSREUfiJQr/oaw4F0NejC73wW4Z1Tqv lIwRgmhwLFaRLEygmRAuZ55h4GbovslP6UYaErWtlsZ1yEPv0CKy/0uCw256ky5JGKspaNUHY/M4y mBtW3gnBK8eb6e/gNJ3g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nuWcS-00HG3E-6H; Fri, 27 May 2022 09:50:56 +0000 Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nuWcP-00HG1p-1T for linux-arm-kernel@lists.infradead.org; Fri, 27 May 2022 09:50:54 +0000 Received: by mail-yb1-xb35.google.com with SMTP id y141so6998663ybe.13 for ; Fri, 27 May 2022 02:50:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TrHpRv64c+YoK1HzOlrj1Q63oDbBkz6zw8zaaBGCR1k=; b=PZXsgFa+uHGoFqbkla1Fz2CNNzBPa1A2c8IO59HnUNeOUgZvG4ETvXJlXAkCKN+L/d 9Uda1N8PjUxI/Xe9KktOJvYvUMaW/QvYsuiAKSySxIFFNyoAQRYuaw15ronQp2rMecoY IIXrDFwRPZWqF+r9TQEl3NgpTLL90Tj6eyWjMM8xI4bosHWiU37t7qv0NDc/HBZOOMMg SLvzGHQn0Tb0DNpYVu0nL59cOQWypn+bgnsvk3U9tQV9ySY2WAW4uBcNUm8ono04qOk+ tBontVujuWGzexNUPEBDPg8W1zj6Oa6vpd4yZm5Of5d/G7gQSN6J07X3ctsD+kDZTeuC 3ZvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TrHpRv64c+YoK1HzOlrj1Q63oDbBkz6zw8zaaBGCR1k=; b=v3ROD5bK7T+m7H+yRDq0T/cC4cYyuL993QP7J3tl3GGgb07dH4tnBBedGVBRinxZn7 qM+thyv4F4o8dE0f3/Hrsrjn8+UyRFOUaK69rwH5S8YqVFgrjhbKQ9wn8QOdCwDrEWd/ MpOrJAdN8DNGlNkWVQ78mjphWjW2CVD4/WQ6OIg4TlyUx63wQsdHaGRet0pQy8nV/l1J zSDsv9Db69ZRwXiEv/r2vw5Vx4HxEDT5uSO9HvQuV6V4Hkw9gVOf0P94dwVkFZ2R9mcI TDm0pGyNbG57lnJsyzrp2anOJYOvkKUcN0bY5k2+dydu6Tjq6Gp8vH7pwG+tbD7mzjBk vusw== X-Gm-Message-State: AOAM532BQSjayt44oXQuvOzhBx5zRjmfl6KWw2+yicTrpe/yoAn5ZDa/ x3j9vByQxB+nhX2VyNc/12iF4wL9oIUSSqvrDm4= X-Google-Smtp-Source: ABdhPJzqL9ND6IPUcs+accWbxqFltjmOUNQB478M6BZsPPyV0GWJU3nx5NkHM9RjxbvbR6/Vb4sHdJfj4nqnLAhQT3A= X-Received: by 2002:a25:1c84:0:b0:64f:6ecc:8fa7 with SMTP id c126-20020a251c84000000b0064f6ecc8fa7mr32131205ybc.432.1653645051230; Fri, 27 May 2022 02:50:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yegor Yefremov Date: Fri, 27 May 2022 11:50:40 +0200 Message-ID: Subject: Re: am335x: 5.18.x: system stalling To: Arnd Bergmann Cc: Tony Lindgren , Ard Biesheuvel , Linux-OMAP , linux-clk , Stephen Boyd , Linux ARM X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220527_025053_140925_E6DFFE9E X-CRM114-Status: GOOD ( 27.92 ) 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 On Fri, May 27, 2022 at 10:39 AM Arnd Bergmann wrote: > > On Fri, May 27, 2022 at 10:17 AM Yegor Yefremov > wrote: > > On Fri, May 27, 2022 at 8:57 AM Arnd Bergmann wrote: > > > > > > On Fri, May 27, 2022 at 8:50 AM Tony Lindgren wrote: > > > > * 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: > > > > > > > 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. > > > > > > Unfortunately the commits around 9c46929e7989 are the ones that failed > > > to build according to the original report. But it's possible that the > > > problem has something to do with > > > CONFIG_CURRENT_POINTER_IN_TPIDRURO, which is disabled > > > in the V6+SMP config, and which in turn is required for > > > THREAD_INFO_IN_TASK, IRQSTACKS and STACKPROTECTOR_PER_TASK. > > > > > > If any of the four are the cause of the stall, then turning off ARCH_OMAP2 and > > > CONFIG_CPU_V6 should show the same bug in older commits as well. > > > > Both config options disabled: > > > > # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP' > > # CONFIG_ARCH_MULTI_V6 is not set > > CONFIG_ARCH_MULTI_V6_V7=y > > # CONFIG_SMP is not set > > > > This helped - no stalls. > > Ok, that does point back to a recent regression then, rather than something > that was already broken and just uncovered by the changed behavior. > > Can you try the other combinations as well? OMAP2=y with SMP=n > and OMAP2=n with SMP=y? Hopefully that narrows it down enough that > we can look at which code paths actually changed. # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP' # CONFIG_ARCH_MULTI_V6 is not set CONFIG_ARCH_MULTI_V6_V7=y CONFIG_SMP=y CONFIG_SMP_ON_UP=y No stalls. # zcat /proc/config.gz | grep 'CONFIG_ARCH_MULTI_V6\|CONFIG_SMP\|ARCH_OMAP2' CONFIG_ARCH_MULTI_V6=y CONFIG_ARCH_MULTI_V6_V7=y CONFIG_ARCH_OMAP2=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_ARCH_OMAP2PLUS_TYPICAL=y No stalls. As soon as I enable both SMP and OMAP2 options the system stalls. Yegor # CONFIG_SMP is not set _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel