Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp10383633rwl; Mon, 2 Jan 2023 01:22:35 -0800 (PST) X-Google-Smtp-Source: AMrXdXvHbNGjBI7FNZ6Nj08LWgon0Ice5FzQdUmEiwcOcGUqLumURk6gBTnKHLAl2or5n1txqe1B X-Received: by 2002:a17:906:434f:b0:7fc:4242:fa1d with SMTP id z15-20020a170906434f00b007fc4242fa1dmr42416698ejm.54.1672651354839; Mon, 02 Jan 2023 01:22:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672651354; cv=none; d=google.com; s=arc-20160816; b=Co0MN3CztM/SE/UzQpfjY0iYeFyl/PLHNiM8N9ZBZGP4Cea0zJot9Xl6OLI3XsG3Rw IyZxgobLIRFgNUYVblWkp3UvByEXsfS6KzdBWlTaU5XoJfPM0ugvsvs9gEt0HJLywSyS GcLp89HkdrbYYMXuhr8bTXPbxx9POmYXeKlXxvCBciOe5v3/k8ASctTwD45BT5g63Ga3 NwR1v2N/2gZjFeQxTa6E0qLT06DdBfoUsA7NEQH2SPsZ/aMCFWA57KK2Bfwh/LDX2L6Z ULn/gAKd0U1ko2cjPvC6rd5OImBlOu5RerBYcgyAuWP4O6HBxx51l7t7FeQCZHkas+wF O3fw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=tZ3NpLMqcovVZwS0oWf1CXTBaT4YkGn91vDMSBIgkl4=; b=uL8hI6Y3FcbJoZ6F6da42ouigdwozHQ8Qav7uZtz9u7xfzlGYo+k0WN2Dq0duB8grK 8boIMXZI20C4ECc1U/cEUuJVsqGrurlnpXF4WuV1ROA3QiXnXMjCuXfIgIKRRfr5ktCn aZOt95wtRArQsxmIJbQirYd4+Nf3xPZ9nKl6y00VVYVcU01/gcu6CQKJ0JofLBum5Cke XfSH4PG0pLyPGdBCtGXAPXUnXBObrORnI8k3UC+h4/qqCnIwSgHPiZlz6k3Vv+DB7sfF pAD19pgyo8d0mUYkKayETNCZ1DYOYZxevVgfjaAAf0N3eirwrHQEXAzwlrckZcuDdaXT dcuA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b="XWmiE17/"; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cb23-20020a0564020b7700b004798880a0adsi23798145edb.596.2023.01.02.01.22.14; Mon, 02 Jan 2023 01:22:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b="XWmiE17/"; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231808AbjABJNu (ORCPT + 66 others); Mon, 2 Jan 2023 04:13:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37322 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231736AbjABJNt (ORCPT ); Mon, 2 Jan 2023 04:13:49 -0500 Received: from mail.marcansoft.com (marcansoft.com [212.63.210.85]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7012810E5; Mon, 2 Jan 2023 01:13:48 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: marcan@marcan.st) by mail.marcansoft.com (Postfix) with ESMTPSA id 1A1B6447D7; Mon, 2 Jan 2023 09:13:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=marcan.st; s=default; t=1672650826; bh=xIaXBSD0dTetSbOrE8dXjuCDx2D5IOPDOUqyMzdMeFg=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=XWmiE17/tSVdKW7wQc9fHMbyDOTsUmiJVvTIUCTEMVB8m6WSQXrOWkfE6skNxit0f pjRoL/6iOascSh+HrVG/oo/ybSHmYF9Dvj6u5q/V/guBUkk49Pv356UwFKg7fQ7yjQ wnXHP71J+s2WQW/Q40kpbfusrDHAi2iW2+qoHhim5tXtzfoBtPRa9T3WflkmzgKEG5 //oAKEvx3xo15T1nQvzvabolFh1fb64uZuYTTSpH34UH7vaED3htW/0ph6yreFG+GK uyZbCGJxzDdvWGrHZIhUfoUTgQDcHqWqolInVkqy0l7k8r5gWdyBUhcs0K1+Y964X9 iYcST9lbCZhNQ== Message-ID: Date: Mon, 2 Jan 2023 18:13:41 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel 6.1 Content-Language: en-US To: Aditya Garg Cc: "linux-wireless@vger.kernel.org" , "brcm80211-dev-list.pdl@broadcom.com" , "linux-kernel@vger.kernel.org" , Orlando Chamberlain , "arend.vanspriel@broadcom.com" , "aspriel@gmail.com" , "hante.meuleman@broadcom.com" , "kvalo@kernel.org" , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "lina@asahilina.net" References: From: Hector Martin In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2023/01/02 17:57, Aditya Garg wrote: > >> You are using a downstream patched tree, specifically one with further >> Broadcom patches not yet upstream from my Asahi Linux tree and probably >> others. >> >> Please do not spam upstream developers with issues from downstream >> trees. If you have an issue with my tree, you can report it on GitHub. >> If you are using another tree, report it to its maintainer. If you can >> reproduce this with *vanilla* 6.1 then you can report it upstream. >> >> - Hector > > I am sorry for the same Hector, but I sent that cause bcm4364 wifi chip is already supported upstream. If I ain't wrong, don't the Asahi Linux patches provide OTP support only for these chips? There are a pile of Broadcom patches in our tree and there is no way to eliminate them as the cause a priori. If you think this regressed upstream, then test it with upstream Linux 6.1 and find out. As I mentioned to you on Discord previously, please bisect this to a specific commit so we can do something about it. I don't have the hardware and there's nothing I can do with a "the firmware is crashing now" report until you at least tell me what commit caused the problem so I can take a stab at identifying the root cause. - Hector