mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "jeff.chua.linux@gmail.com" <jeff.chua.linux@gmail.com>,
	"bagasdotme@gmail.com" <bagasdotme@gmail.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"Berg, Johannes" <johannes.berg@intel.com>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: iwlwifi broken in post-linux-6.3.0 after April 26
Date: Sun, 30 Apr 2023 18:00:44 +0000	[thread overview]
Message-ID: <0785e432f1776b3531e8e033cb5b48eeb58b12b6.camel@intel.com> (raw)
In-Reply-To: <e9c289bea2c36c496c3425b7dc42c6324d2a43e3.camel@intel.com>

On Sun, 2023-04-30 at 17:06 +0000, Greenman, Gregory wrote:
> On Sun, 2023-04-30 at 18:58 +0800, Jeff Chua wrote:
> > On Sun, Apr 30, 2023 at 2:17 AM Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> > > 
> > > On Sat, Apr 29, 2023 at 10:07 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> > > > 
> > > > On Sat, Apr 29, 2023 at 01:22:03PM +0800, Jeff Chua wrote:
> > > > > Can't start wifi on latest linux git pull ... started happening 3 days ago ...
> > > > 
> > > > Are you testing mainline?
> > > 
> > > I'm pulling from https://github.com/torvalds/linux.git, currently at ...
> > > 
> > > commit 1ae78a14516b9372e4c90a89ac21b259339a3a3a (HEAD -> master,
> > > origin/master, origin/HEAD)
> > > Merge: 4e1c80ae5cf4 74d7970febf7
> > > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > > Date:   Sat Apr 29 11:10:39 2023 -0700
> > > 
> > > > Certainly you should do bisection.
> > > 
> > > ok, will do.
> > 
> > Bisected!
> > 
> > ef3ed33dfc8f0f1c81ca103e6b68b4f77ee0ab65 is the first bad commit
> > commit ef3ed33dfc8f0f1c81ca103e6b68b4f77ee0ab65
> > Author: Gregory Greenman <gregory.greenman@intel.com>
> > Date:   Sun Apr 16 15:47:33 2023 +0300
> > 
> >     wifi: iwlwifi: bump FW API to 77 for AX devices
> > 
> >     Start supporting API version 77 for AX devices.
> > 
> >     Signed-off-by: Gregory Greenman <gregory.greenman@intel.com>
> >     Link: https://lore.kernel.org/r/20230416154301.e522ccefe354.If7628363fafeb7687163103e734206915c445197@changeid
> >     Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > 
> >  drivers/net/wireless/intel/iwlwifi/cfg/22000.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > 
> > I had to downgrade FW API to 75 to make it work again!
> > 
> > --- a/drivers/net/wireless/intel/iwlwifi/cfg/22000.c    2023-04-30
> > 18:27:21.719983505 +0800
> > +++ a/drivers/net/wireless/intel/iwlwifi/cfg/22000.c    2023-04-30
> > 18:27:25.749983446 +0800
> > @@ -10,7 +10,7 @@
> >  #include "fw/api/txq.h"
> > 
> >  /* Highest firmware API version supported */
> > -#define IWL_22000_UCODE_API_MAX        78
> > +#define IWL_22000_UCODE_API_MAX        75
> > 
> >  /* Lowest firmware API version supported */
> >  #define IWL_22000_UCODE_API_MIN        39
> > 
> > 
> > My h/w is Lenovo X1 with ...
> > 
> > 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi
> > WiFi (rev 01)
> > 
> > 
> > I've the following firmware .. I've tried 77, 78, 79, 81 .. .all not working
> > 
> > -rw-r--r-- 1 root root 1560532 Mar 14 08:05 iwlwifi-so-a0-gf-a0-72.ucode
> > -rw-r--r-- 1 root root 1563692 Mar  6 14:07 iwlwifi-so-a0-gf-a0-73.ucode
> > -rw-r--r-- 1 root root 1577460 Mar 14 08:05 iwlwifi-so-a0-gf-a0-74.ucode
> > -rw-r--r-- 1 root root 1641260 Mar  6 14:07 iwlwifi-so-a0-gf-a0-77.ucode
> > -rw-r--r-- 1 root root 1667236 Mar  6 14:07 iwlwifi-so-a0-gf-a0-78.ucode
> > -rw-r--r-- 1 root root 1672988 Mar  6 14:07 iwlwifi-so-a0-gf-a0-79.ucode
> > -rw-r--r-- 1 root root 1682852 Apr  5 08:22 iwlwifi-so-a0-gf-a0-81.ucode
> > 
> > 
> > # working dmesg attached ...
> > cfg80211: Loading compiled-in X.509 certificates for regulatory database
> > Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> > iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
> > iwlwifi 0000:00:14.3: Direct firmware load for
> > iwlwifi-so-a0-gf-a0-75.ucode failed with error -2
> > iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
> > thermal thermal_zone1: failed to read out thermal zone (-61)
> > iwlwifi 0000:00:14.3: Sorry - debug buffer is only 4096K while you
> > requested 65536K
> 
> Strangely, I couldn't reproduce it on my system. But, anyway this feature
> better be disabled for a while. I'll send a patch with a fix shortly.
May I ask you to try this fix in [1] (also cc-ed you on the patch itself)?

[1] https://lore.kernel.org/linux-wireless/20230430201830.2f8f88fe49f6.I2f0076ef1d1cbe5d10010549c875b7038ec4c365@changeid/

  reply	other threads:[~2023-04-30 18:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230429020951.082353595@lindbergh.monkeyblade.net>
2023-04-29  5:22 ` Jeff Chua
2023-04-29 14:07   ` Bagas Sanjaya
2023-04-29 18:17     ` Jeff Chua
2023-04-30 10:58       ` Jeff Chua
2023-04-30 17:06         ` Greenman, Gregory
2023-04-30 18:00           ` Greenman, Gregory [this message]
2023-04-30 23:57             ` Jeff Chua
2023-05-01  4:46     ` Bagas Sanjaya
2023-07-05  7:24       ` Linux-6.5 iwlwifi crash Jeff Chua
2023-07-05  8:37         ` Linux regression tracking (Thorsten Leemhuis)
2023-07-05 11:56           ` Jeff Chua
2023-07-05 18:11             ` Larry Finger
2023-07-07  1:56               ` Jeff Chua
2023-07-07  8:43                 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07  9:48                   ` Thorsten Leemhuis
2023-07-07 18:07                   ` Larry Finger
2023-07-09  0:00                     ` Jeff Chua

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0785e432f1776b3531e8e033cb5b48eeb58b12b6.camel@intel.com \
    --to=gregory.greenman@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®