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 lists.zx2c4.com (lists.zx2c4.com [165.227.139.114]) (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 F1177EB64DA for ; Sun, 2 Jul 2023 13:50:01 +0000 (UTC) Received: by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTP id ffe02173; Sun, 2 Jul 2023 13:47:14 +0000 (UTC) Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [2607:f8b0:4864:20::630]) by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id 220ed613 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sun, 2 Jul 2023 11:57:23 +0000 (UTC) Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-1b82616c4ecso15419625ad.2 for ; Sun, 02 Jul 2023 04:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688299042; x=1690891042; h=content-transfer-encoding:in-reply-to:references:cc:to:from :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=7qagKLZGa10wVvAq9nJ5ZILI98Y2jy96AWT9f4TfrO8=; b=Lp2sEjNT5bKhVCBgHl3nADK0T6dCzbAGMULQ8a01f0WSYh5V+VyzpqN6nRviRXY14l TuGij9y1QDbB5weNaxnndCHewGgNzjQctmmwA9p10EraO6jqGyd4Y9mSs3iXpc0eMQ0f mhqA80KUShZ6yE+rTLGzQcrp5XD3ZyYA/5W3IASKWR5MxWvgZJCWILuEPI/wtdBUpq7h jS3zBfTPXVGAyWplOa3qj8l5StQhaGEi+dRHM+o80rS8CQdAgMFAIqrr2/dwywj7cf3N /Pwv97UPtiwTZdTWV2IxxVSbbaPt1rPPOzN2PbXcrZd3x7dJK8bFOsbp+3tDdGPiN0XA KVeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688299042; x=1690891042; h=content-transfer-encoding:in-reply-to:references:cc:to:from :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7qagKLZGa10wVvAq9nJ5ZILI98Y2jy96AWT9f4TfrO8=; b=AALBDlcX9E9rzKYra1Ga579GSSWvrZWie0rYSAPi4Dm+l488xFbvbS74rETMH+gfAt O8aQ25sAHglGyG/ShPmpPJbj2pDtMEw1xI+QcRJQO4svD+R1OA+Z16ayTigfb/gHg5/B Cbg/1TepofFZGlTmzeUg9gS8w6C4LdCY0CxsFZTzOgJ9N1QhQRT5ouK+jtEx8ZAMI8O/ vHqyycoaWr300qo5hx2RIYUg3bRlQLZdaCJy3sZb67Q72vAwqcTFCRRnQc2I7LM665w4 7kWlilD7KANIsGdcBv01beizqhtIkY5opCU/Nzhtuwlb+Z9B/Mz5sI0YpeftDRBM5g5E gFTA== X-Gm-Message-State: ABy/qLb6mjqMEzsX62XkbC2no+vyZL6/+w2L3yV/zC2TlOhO4Slw5xpf cqadasrOwdpbneP8s6EOd0s= X-Google-Smtp-Source: APBJJlE4CbVvUaMvQBQttUFOCXJMSfMnxOJ3T5YMiAeUk7XAACrdXab8dfLsDFAcYWm09mkvHX3dOQ== X-Received: by 2002:a17:902:d4c4:b0:1b8:2c6f:3247 with SMTP id o4-20020a170902d4c400b001b82c6f3247mr6252238plg.4.1688299041674; Sun, 02 Jul 2023 04:57:21 -0700 (PDT) Received: from [192.168.0.103] ([103.131.18.64]) by smtp.gmail.com with ESMTPSA id y13-20020a170902ed4d00b001b8932d77d7sm490425plb.279.2023.07.02.04.57.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Jul 2023 04:57:21 -0700 (PDT) Message-ID: <79196679-fb65-e5ad-e836-2c43447cfacd@gmail.com> Date: Sun, 2 Jul 2023 18:57:05 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: Fwd: RCU stalls with wireguard over bonding over igb on Linux 6.3.0+ Content-Language: en-US From: Bagas Sanjaya To: Eric DeVolder , "Borislav Petkov (AMD)" , David R , Boris Ostrovsky , Miguel Luis , "Paul E. McKenney" , Joel Fernandes , Boqun Feng , "Jason A. Donenfeld" , Jay Vosburgh , Andy Gospodarek , "Rafael J. Wysocki" , Len Brown , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Thorsten Leemhuis Cc: Linux Kernel Mailing List , Linux Regressions , Linux RCU , Wireguard Mailing List , Linux Networking , Linux ACPI , Manuel 'satmd' Leiner References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 02 Jul 2023 13:47:11 +0000 X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" [also Cc: original reporter] On 7/2/23 10:31, Bagas Sanjaya wrote: > Hi, > > I notice a regression report on Bugzilla [1]. Quoting from it: > >> I've spent the last week on debugging a problem with my attempt to upgrade my kernel from 6.2.8 to 6.3.8 (now also with 6.4.0 too). >> >> The lenghty and detailed bug reports with all aspects of git bisect are at >> https://bugs.gentoo.org/909066 >> >> A summary: >> - if I do not configure wg0, the kernel does not hang >> - if I use a kernel older than commit fed8d8773b8ea68ad99d9eee8c8343bef9da2c2c, it does not hang >> >> The commit refers to code that seems unrelated to the problem for my naiive eye. >> >> The hardware is a Dell PowerEdge R620 running Gentoo ~amd64. >> >> I have so far excluded: >> - dracut for generating the initramfs is the same version over all kernels >> - linux-firmware has been the same >> - CPU microcode has been the same >> >> It's been a long time since I seriously involved with software development and I have been even less involved with kernel development. >> >> Gentoo maintainers recommended me to open a bug with upstream, so here I am. >> >> I currently have no idea how to make progress, but I'm willing to try things. > > See Bugzilla for the full thread. > > Anyway, I'm adding it to regzbot to make sure it doesn't fall through cracks > unnoticed: > > #regzbot introduced: fed8d8773b8ea6 https://bugzilla.kernel.org/show_bug.cgi?id=217620 > #regzbot title: correcting acpi_is_processor_usable() check causes RCU stalls with wireguard over bonding+igb > #regzbot link: https://bugs.gentoo.org/909066 > satmd: Can you repeat bisection to confirm that fed8d8773b8ea6 is really the culprit? Thorsten: It seems like the reporter concluded bisection to the (possibly) incorrect culprit. What can I do in this case besides asking to repeat bisection? -- An old man doll... just what I always wanted! - Clara