Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp21170859rwd; Thu, 29 Jun 2023 12:01:00 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ606BAwqmrd7PQk+e+QQ8m3MmWHAsq4u48WLp0qRIlQuBioNICYw3kncfOYW6gqtVnnXvW+ X-Received: by 2002:a05:6a20:4408:b0:121:7454:be2a with SMTP id ce8-20020a056a20440800b001217454be2amr600893pzb.45.1688065259994; Thu, 29 Jun 2023 12:00:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688065259; cv=none; d=google.com; s=arc-20160816; b=0otuMKokLGzu9nH7a997x5CrUroQTsnHOaYUZPraG3AQTqJZgDSyJ7ClZZXDtRBWfa zD2z9dg/cjrTr4UsCgj4m7XCGdeoqTd2hMVz6zYfP+iP1E/ggedG64mQUi/DmWrNEh1R b7Z3TowFNpeFbDk7ReFyBCNA70j5j+3RfCZM12Q/2wFeDhWf3Y952wj1o3S//n0GcF9a ooJQXAST2jfS0zYvPFgDjDpmZPrYHIfiIRGbC4MNX1RLs9pTgQ1mZwaRCklum+Mctee6 0MDLLNcbDo6RMZWIe3MP3zRcJX7r+WqBvOSrWd9s2ETuUEJR7fBTqMBM63lGniLxFz6H z7xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=seVl7DqCmL7QKGLLl3/DwBPqokV+xG9U/eV9CD76Rfw=; fh=cPvJ1AqhBSRnAeu1Xx1rijhNOA6/kD+J9tYbJU+nCEw=; b=k7WjogjZ0IGo49fH384RPT8ELhGQ+8A1e2KU/YbxR7xBoxaGobxZUAiSEwye6WPOH5 l7O/2NpXEr98UJMbvLh0v/ARKNhAlde+VyRrJkpQQXoL+T3dRRMgm/oqTD0l7/Ma70xV k6RNig/isgX39os1TKGGOBqvDrRpkP4YlfIA+rVHAART0tzHkF3ntKEP7hj5Yf67wIlU 4aX5jcN8jJnHA7eGV8/7MjmIVmPcwx+jX+Ewsb7uQhH+qnvdwHP+ZaS3NElatlaigz/V 5yo/D6PpZ4kfjuvzp3FTOY9SVCNv1wkacj2VngEOwkqaDU/XpZpDhtPeTEKJH7OJDZ6v Y9dQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=onV24YGD; 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=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bo3-20020a056a000e8300b0068208d19b23si1914259pfb.311.2023.06.29.12.00.47; Thu, 29 Jun 2023 12:00:59 -0700 (PDT) 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=@linuxfoundation.org header.s=korg header.b=onV24YGD; 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=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231996AbjF2TAp (ORCPT + 60 others); Thu, 29 Jun 2023 15:00:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36628 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231950AbjF2TAk (ORCPT ); Thu, 29 Jun 2023 15:00:40 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0DB4AE4B for ; Thu, 29 Jun 2023 12:00:38 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 80A89615D8 for ; Thu, 29 Jun 2023 19:00:38 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94108C433CC; Thu, 29 Jun 2023 19:00:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1688065237; bh=ah18Kry4o3bgB4ytnNxb5ap/lUEyJSBIYP8vjiTTeH8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=onV24YGDOrrpro8Dkjuy1ct5GMeNyJZC4XmIbakU2L/yuxtva75CgDktcrXqXS0JQ dpyM215GukmXDh95AbHzxPxfqz28hkY9US23+hy1yuit3dj6wswt65dz1uOQbMeJPO uDR4+8vlT/gB3w8ZJT1Xm5f1hLh2IpGAm1RC5qDE= Date: Thu, 29 Jun 2023 20:46:36 +0200 From: Greg KH To: =?utf-8?Q?Barnab=C3=A1s_P=C5=91cze?= Cc: Linux regressions mailing list , Gregory Greenman , linux-wireless , Bagas Sanjaya Subject: Re: iwlwifi: AX201 misdetected as AX101 Message-ID: <2023062914-upcoming-turmoil-a443@gregkh> References: <3270268e-c926-01e6-65e1-02aa6abfd0db@leemhuis.info> <0d3db91c-f071-009a-952a-bd109b16a352@leemhuis.info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, 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 On Thu, Jun 29, 2023 at 05:30:34PM +0000, Barnabás Pőcze wrote: > Hi > > > 2023. június 29., csütörtök 18:50 keltezéssel, Linux regression tracking (Thorsten Leemhuis) írta: > > > On 29.06.23 17:28, Barnabás Pőcze wrote: > > > 2023. június 29., csütörtök 13:31 keltezéssel, Thorsten Leemhuis írta: > > >> On 27.06.23 23:55, Barnabás Pőcze wrote: > > >>> 2023. május 26., péntek 19:55 keltezéssel, Barnabás Pőcze írta: > > >>>> I have an Acer Aspire A315-58 laptop[0], which, according to lspci has the following intel wireless chip: > > >>>> > > >>>> Device: 00:14.3 > > >>>> Class: Network controller [0280] > > >>>> Vendor: Intel Corporation [8086] > > >>>> Device: Wi-Fi 6 AX201 [a0f0] > > >>>> SVendor: Intel Corporation [8086] > > >>>> SDevice: Wi-Fi 6 AX201 [0244] > > >>>> Rev: 20 > > >>>> ProgIf: 00 > > >>>> Driver: iwlwifi > > >>>> Module: iwlwifi > > >>>> > > >>>> However, in the kernel message buffer, the following message is written: > > >>>> > > >>>> [ 3.633490] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x351 > > > > Gregory who is CCed since the start of the thread might care to look > > into this. According to a quick search lspci is right, but this needs > > expects. Maybe it's just a cosmetic problem. > > > > >>> [...] > > >>> For the record, I have done a git-bisect[1], and that turned up > > >>> d2ccc5c1526396aef5196e4dd2ec8538994e5072 > > >>> > > >>> as the first good commit[0]. > > >>> > > >>> Sadly, that patch (or even the series) does not appear to be easily backportable, > > >>> so it seems likely that current stable kernels won't be able to support this device. > > >> > > >> Thx for bisecting. > > >> > > >> Thing is: 6.3 will be EOL in about two or three weeks anyway. And Arch > > >> will likely switch to 6.4 (which works -- or did I get this wrong?) > > >> within a week or two. Makes be wonder if it's the best solution for > > >> everyone involved to not resolve this and move on. > > > > > > Yes, 6.4 seems to work. > > > > #regzbot inconclusive: unlikely to be fixed in 6.3 before EOL, but 6.4 works > > > > > I mainly meant LTS releases. Nonetheless, lspci > > > and iwlwifi still disagree on what device it actually is. > > > > Not sure if I properly understand this. > > > > Is this broken in 6.1.y as well, but working in earlier kernels? Then it > > needs a separate report. > > There are two issues: > > * lspci and iwlwifi disagreeing about the device (AX201 vs AX101), and > * the device not working until the aforementioned commit. > > This email was originally intended to be about the first one since the device > does work with 6.4. > > But out of curiosity I wanted to find the commit that made the device work to > see if maybe it could be easily backported to 6.3, 6.1, etc. > > In conclusion: > > device does not work device is misdetected > 6.1 present present > 6.3 present present > 6.4 fixed present > > Since the commits that fixed it don't appear to be easily backportable, > the only thing remains to be seen is why lspci and iwlwifi disagree about the > name of the device. That issue is still present in 6.4. This isn't a regression then, it's never worked, but now it works in 6.4, so yeah! And we don't generally backport new hardware enablement to stable kernels unless it's a simple device id table update. As for naming, realize that iwlwifi and lspci get the names of the device from different places, so perhaps those userspace databases just are not in sync yet? thanks, greg k-h