Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp2017860pxm; Fri, 4 Mar 2022 07:56:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJwBTsQnqTseJaPDnoW43jGseAX83uX4z3jP4sO7lsACluhDKOn1EItUDAdyb1+0rIA/Nfn8 X-Received: by 2002:a05:6402:d2:b0:413:2e50:d6fd with SMTP id i18-20020a05640200d200b004132e50d6fdmr40097632edu.171.1646409401630; Fri, 04 Mar 2022 07:56:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646409401; cv=none; d=google.com; s=arc-20160816; b=bOtKpzsK3Ji/b13NAgzVQPV4CBzk6Vex5xz3jqrWfhYOHaeD7d3nRq9UpM8TDmhfAl xYHyRnMC2gJ8mLn0R0YJRpXbLzEpOpyJ/kQ6mr4ViYaIoZNdG1Uh++j+ogxY2dmffPFC TW0qVBjjkPcyOmUVa0rjOi2DlsRh9sjYP8QWF6tWzlGuFHrK2hWcy9n6u8vAvZH0lI02 p19q3WsBEq+VBSf/1MYjS28bAf2yydxV67BXTEXkO0tC6gxIqVLhkAOmdGroFGhlGTyr QIyNTfqdy8TdLMPWLIDI1DJJ44RjuChI39irrEfDEgvW6fitr0Iv9v8w46MumQe1eZml A8jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=W3JUjUY/2pghrZi3FcJ+ewxZF+VyMxMbAEzz0CsmnUE=; b=cSa0D7TzWsBopTxTW5v1RlBowdFsv9HGefwOIQmekp0jKvsmnlusBa1aTi8bdpRgtM I/DbXPz5+GM4tjSB4zXsyrowvZG5T8zxmOlMMEThIQbkSu28GwjoW5UJ6Xz+S0PLXey0 z7++mDpxDEiISL8d5E4onczQqbLtlDBqt07iTsB+bfzhoy8ZIyaYEU//9NhYhMWXBfxY /DZ4JraKWBJb7LEzq99UUni1r2TpjUeOJUL3prLeQrvhHaV1vFeRsQcjrdhQ7FQ9XjZh trWIZjqp3ZHvHLhM345wFs2PwIn3RfYYTg9eKMJetbc4uBAR2FydexoZHp/5ipBoZlLD QDtg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=qY1klgu0; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cr19-20020a170906d55300b006d79f572b5dsi3554879ejc.171.2022.03.04.07.56.20; Fri, 04 Mar 2022 07:56:41 -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=@gmail.com header.s=20210112 header.b=qY1klgu0; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235619AbiCDOqa (ORCPT + 72 others); Fri, 4 Mar 2022 09:46:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230382AbiCDOq3 (ORCPT ); Fri, 4 Mar 2022 09:46:29 -0500 Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE0B248384 for ; Fri, 4 Mar 2022 06:45:40 -0800 (PST) Received: by mail-pg1-x52f.google.com with SMTP id o23so7669996pgk.13 for ; Fri, 04 Mar 2022 06:45:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W3JUjUY/2pghrZi3FcJ+ewxZF+VyMxMbAEzz0CsmnUE=; b=qY1klgu0tw3GfONCW43gFHNTCxpd5NNdMXHgQOYFSFqan/Ctk9aCxStHD5vEH8YWYK m0IGw4Km8IkpOuTbq3KDqSOlOVCwzIa8pdCukIzagRu2+3wrEb28fyRxLtMRVubssc/G kTLcO68YuKlriqDQg5Y7RU+OsbmPz/6+ziSFlvimqftp3vuyC5k4HVR5jNz9/EwomAuo nB9mIEUxQUl6G+aklPXyXhqUB/vFaH4YCyTzpKADV6JSV/XArJ2YXFladSfGWNCkNRnH aEQ0NNenMg9GjVBz9CN/yKPuplWwJ6jaBDopaU8hyxlPUVhqKgLSKDJucq591fKbn6V2 GPpQ== 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=W3JUjUY/2pghrZi3FcJ+ewxZF+VyMxMbAEzz0CsmnUE=; b=8CZgM4wCeAgRHS5woG8WvV7Vl26zg/XN0rRmS4u+/93N0+wy3pgvRjGi7DF6bnTr+T 0kovMc+0dq1NlnG6jgQpxoZ01bbrUq2EhmgrCBUrfylmESori/1Yk4RA9ZXQdup+kWaE 2p0nLN022io6fr7xLwQPlIVFU3UGZwQ3T++xHHvMjObCFn2t4hsyxnaPzY2h2T5JAawx EOzXb1I0A2pUNsqp/m6fY5BaN+eDeqpss6ChBWZbg5C3zNcoANIY2CDBUyUL2kV175MQ 3qVZNO/LRhf9+tgTjO/RLdb55hWP9c9nJZBG2Jd7yMZ+1J++MsSU651FB5bhFzgUt7ZA jdbQ== X-Gm-Message-State: AOAM533G3KvHo5xLwy7Jgg8ohGDAqlCDFbW1Mlr+FwYHZaPtHhZOhXk/ VwozKH8Irewto7VA335LQeIDQwfh3twfQzhyNcr2H0S/580= X-Received: by 2002:a05:6a00:887:b0:4f2:6d3f:5b53 with SMTP id q7-20020a056a00088700b004f26d3f5b53mr44180225pfj.21.1646405140123; Fri, 04 Mar 2022 06:45:40 -0800 (PST) MIME-Version: 1.0 References: <2d1c129b-d473-39e3-69b7-6f36dc1682a6@leemhuis.info> <9312eb18-840f-9a1f-bcb0-8e3a43e45239@leemhuis.info> <236d45a6-8b88-c02e-a61d-ce1773fdb0ef@lwfinger.net> <02ef7552-67f5-dbcf-ece6-87b5b49e1bb5@leemhuis.info> In-Reply-To: <02ef7552-67f5-dbcf-ece6-87b5b49e1bb5@leemhuis.info> From: Nico Sneck Date: Fri, 4 Mar 2022 16:45:28 +0200 Message-ID: Subject: Re: rtw_8822ce wifi regression after kernel update from 5.15 to 5.16 To: Thorsten Leemhuis , Larry Finger Cc: Yan-Hsuan Chuang , "regressions@lists.linux.dev" , linux-wireless@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Hi Larry, Thorsten. Sorry I'm a bit late, been really busy with work lately. Haven't had time to continue bisecting, hopefully I can find some time this sunday. I still think this is a kernel regression - I don't believe I'm using the driver from Larry's repo. This is a stock Fedora 35 installation, I've not installed the driver from Larry's repo, and I don't believe Fedora packages it by default. The reason I used "rtw_8822ce" in the title is because "rtw_8822ce" is printed by my kernel. However, thinking about it a bit, I think that string may not be the driver name, but rather, maybe the device name printed by the kernel? See here: https://github.com/torvalds/linux/blob/38f80f42147ff658aff218edb0a88c37e58bf44f/drivers/net/wireless/realtek/rtw88/mac.c#L968 >rtw_warn(rtwdev, "timed out to flush queue %d\n", prio_queue); It prints the rtwdev variable, which in my case is "rtw_8822ce". And looking some more, I can see this: https://github.com/torvalds/linux/blob/38f80f42147ff658aff218edb0a88c37e58bf44f/drivers/net/wireless/realtek/rtw88/rtw8822ce.c#L24 >.name = "rtw_8822ce", So at least some name inside the driver itself is "rtw_" instead of "rtw88_". Furthermore, here's what lsmod has to say: >[nico@fedora linux]$ lsmod | grep 88 >rtw88_8822ce 16384 0 >rtw88_8822c 487424 1 rtw88_8822ce >rtw88_pci 28672 1 rtw88_8822ce >rtw88_core 167936 2 rtw88_pci,rtw88_8822c >mac80211 1179648 2 rtw88_pci,rtw88_core >kvm 1036288 1 kvm_amd >cfg80211 1024000 2 rtw88_core,mac80211 So I still believe this is a regression somewhere in the net stack - maybe in wireless/ or wireless/rtw88/, but could be elsewhere as well, as there are quite a few moving pieces involved with this machinery. I tried to trace the logic leading to the function "__rtw_mac_flush_prio_queue", but it becomes pretty difficult considering all the places where the struct "ieee80211_ops rtw_ops" member ".flush" in mac80211.c is handled. Add to that my poor understanding of C, and the difficulty of bisecting this, it's not easy to pinpoint where the regression came from. I'll try latest -RC, and if it doesn't work, I'll try bisecting the net merge commits as soon as I have time. p.s. sorry for top posting, writing this in a hurry in gmail web client. On Fri, Mar 4, 2022 at 8:33 AM Thorsten Leemhuis wrote: > > Hi, this is your Linux kernel regression tracker. > > On 28.02.22 23:07, Larry Finger wrote: > > On 2/28/22 08:30, Thorsten Leemhuis wrote: > > [...] > > > > Your use of rtw_8822ce in the title finally registered on me. With that > > driver in use, that means that you are using my GitHub repo; however, > > newer kernels have the driver built in, but with names such as > > rtw88_8822ce. The difference in the name is deliberate. > > Many thx for this, the names already had made me a bit suspicious, but > wasn't aware of this! > > > If you want to > > use the GitHub version, you must blacklist the ones from the kernel. > > > > To check this, run 'lsmod | grep 88'. If you see a mixture of rtw_xxx > > and rtw88_xxx, then this is your problem. > > Nico didn't reply to your mail, so I'll assume for now that this is not > a kernel regression: > > #regzbot invalid: seems it's a regression in a external module of > similar name > > @Yan-Hsuan Chuang: sorry for the noise! > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > P.S.: As the Linux kernel's regression tracker I'm getting a lot of > reports on my table. I can only look briefly into most of them and lack > knowledge about most of the areas they concern. I thus unfortunately > will sometimes get things wrong or miss something important. I hope > that's not the case here; if you think it is, don't hesitate to tell me > in a public reply, it's in everyone's interest to set the public record > straight. > > >