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 3C771C3271E for ; Mon, 8 Jul 2024 10:36:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: Message-ID:In-Reply-To:Date:References:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=tCEBtnHrXN3WZScqh4+AHCjQtHylOyQeuXCIvEWhTL0=; b=Yg29PNObczi6d/Ab0ZeFXFSVTV IrnhaNdIXiu6TvtL+idyv8nFnm6GecxVPvRljz55GXR3NR5nU7i1R4mwPP2P2wikqHzjmGquMEvDn L73S5juGUhaJnLovWaE4ylcPT1urUeIxCBkmHbRjQxUJifhOeLbFz4fBnTCaY3RZcx0jMM2NEFMr+ IL3RZ0XYaOGn35sAFVthJBm9NcO1AU8uIT/JdT4DkFSAnpYhkIDUomEzRDccALHN8rYTSOETWIWEo j33eIBnx/kSKi1Tmm4koC/LTV1SJZCFbHJUYFAEU8ABp/id4pD0ycraUKm5TA9POkRxpC9O7PqKVB ju6+a9Pw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sQljn-00000003T8H-1TL2; Mon, 08 Jul 2024 10:36:51 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sQljj-00000003T7H-3VPr for ath10k@lists.infradead.org; Mon, 08 Jul 2024 10:36:49 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id B4ACC60ACE; Mon, 8 Jul 2024 10:36:46 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D3DEAC116B1; Mon, 8 Jul 2024 10:36:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1720435006; bh=3Nxqm3JLpo/2FtZzwnd9TEiW+RAk0KUEjOFh9w97bxg=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=bqHtdiKcDbR5oKuI2SUSQjjlOJ3EOawsksDOjfas2zNslxhQPIxVFzo36sLkheSPF qetIqmyf7fwnH6jDdn2Ok6U+ZmEyJR7fT2PAXFXtmnGijNwHiMcuP4jaBhGvRk8rhb 3UC8PQ7mEDM9Z40FhIZdH/D/JqB3bFmPMhahOwH8mLeinP+B0c2Qxyo4ZlMVHukkor 9JlTXPYzwo0zzK7vottWFfSqfNZ1HTjxrdHJGSQRbHTG9PoE9TfkRtqJpuAw+AEKB6 WnlIGujYVoTo/GKpvRo7kKf3lMBozTEn7n7YQAha72BYAb9HWmE7RiCWNZuRKfRLIo vAvaOJs5EMrSQ== From: Kalle Valo To: Baochen Qiang Cc: Paul Menzel , James Prestwood , , , LKML , Chun Wu Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9 References: <1faa7eee-ed1e-477b-940d-a5cf4478cf73@gmail.com> <87iky7mvxt.fsf@kernel.org> <37ba6cb0-d887-4fcf-b7dc-c93a5fc5900f@gmail.com> <875xu6mtgh.fsf@kernel.org> <082024ce-fdd4-4fb1-8055-6d25f7d2e524@molgen.mpg.de> <462c97dc-f366-4f75-9327-04d9424b819a@quicinc.com> <82e10a1a-ed23-4d5c-b691-02e39296a91e@quicinc.com> Date: Mon, 08 Jul 2024 13:36:42 +0300 In-Reply-To: <82e10a1a-ed23-4d5c-b691-02e39296a91e@quicinc.com> (Baochen Qiang's message of "Mon, 8 Jul 2024 09:53:08 +0800") Message-ID: <87o778cgqt.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240708_033647_944988_5697C8F9 X-CRM114-Status: GOOD ( 11.48 ) X-BeenThere: ath10k@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "ath10k" Errors-To: ath10k-bounces+ath10k=archiver.kernel.org@lists.infradead.org Baochen Qiang writes: >>> Checked with firmware team and just know that, the TX rate info is >>> generated by firmware directly but for RX rate it is from phy side. >>> From firmware TX rate generation code seems NSS 3 is an impossible >>> value, so it might be an RX rate generated by phy side. But I could >>> not tell for now since the log is not complete. Paul, could you >>> enable full ath10k log and try to reproduce? With full log we can >>> check whether it is a RX rate issue, >> >> Please tell me how I enable full logging. > > once boot, first unload ath10k modules by > > sudo modprobe -r ath10k_pci > > then load ath10k modules with > > sudo modprobe ath10k_core debug_mask=0xffffffff > sudo modprobe ath10k_pci > > you should see lots of prints now BTW the extensive debug messages can slow down the system so there's also the option of using tracing which is a lot faster: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug#tracing Though I have not tested that for a long time but I hope it still works. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches