linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@intel.com>
To: Thomas Backlund <tmb@mageia.org>, Roman Gilg <subdiff@gmail.com>,
	Mehmet Akif Tasova <makiftasova@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	Shahar S Matityahu <shahar.s.matityahu@intel.com>,
	Tova Mussai <tova.mussai@intel.com>,
	Ayala Beker <ayala.beker@intel.com>,
	Sara Sharon <sara.sharon@intel.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "iwlwifi: mvm: fix scan config command size"
Date: Mon, 23 Dec 2019 15:52:43 +0200	[thread overview]
Message-ID: <88b9ffdc51ae5e11341332d7f5efed07320251c6.camel@intel.com> (raw)
In-Reply-To: <946da821-9e54-4508-e3ab-f2cdc19c8084@mageia.org>

On Mon, 2019-12-23 at 14:24 +0200, Thomas Backlund wrote:
> Den 18-12-2019 kl. 21:12, skrev Roman Gilg:
> > On Fri, Dec 13, 2019 at 9:36 PM Mehmet Akif Tasova
> > <makiftasova@gmail.com> wrote:
> > > Since Linux 5.4.1 released, iwlwifi could not initialize Intel(R) Dual Band
> > > Wireless AC 9462 firmware, failing with following error in dmesg:
> > > 
> > > iwlwifi 0000:00:14.3: FW error in SYNC CMD SCAN_CFG_CMD
> > > 
> > > whole dmesg output of error can be found at:
> > > https://gist.github.com/makiftasova/354e46439338f4ab3fba0b77ad5c19ec
> > > 
> > > also bug report from ArchLinux bug tracker (contains more info):
> > > https://bugs.archlinux.org/task/64703
> > 
> > Since this bug report is about the Dell XPS 13 2-in1: I tested your
> > revert with this device, but the issue persists at least on this
> > device. So these might be two different issues, one for your device
> > and another one for the XPS.
> 
> Yeah, to get iwlwifi to work somewhat nicely you need this revert

Indeed the revert is correct.  I'm going to apply it in our internal
tree and send it out for v5.5-rc* (with stable in CC so it goes to
v5.4).  Thanks Mehmet!


> [...]and also theese on top of 5.4.6:
> 
>  From db5cce1afc8d2475d2c1c37c2a8267dd0e151526 Mon Sep 17 00:00:00 2001
> From: Anders Kaseorg <andersk@mit.edu>
> Date: Mon, 2 Dec 2019 17:09:20 -0500
> Subject: Revert "iwlwifi: assign directly to iwl_trans->cfg in QuZ 
> detection"
> 
>  From 0df36b90c47d93295b7e393da2d961b2f3b6cde4 Mon Sep 17 00:00:00 2001
> From: Luca Coelho <luciano.coelho@intel.com>
> Date: Thu, 5 Dec 2019 09:03:54 +0200
> Subject: iwlwifi: pcie: move power gating workaround earlier in the flow

The fixes for these two are already in v5.5-rc3, [1] and [2]
respectively.  They are both marked for v5.4, hopefully they'll be
included in v5.4.7.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=db5cce1afc8d2475d2c1c37c2a8267dd0e151526
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0df36b90c47d93295b7e393da2d961b2f3b6cde4


> and atleast v2 of the "iwlwifi: mvm: don't send the 
> IWL_MVM_RXQ_NSSN_SYNC notif to Rx queues" patch that is being debated on 
> this list.

Kalle is on vacation, but when he gets, back we'll decide what to do
with this.  If he really doesn't like our v4, I'll send out a new
version that satisfies him so we can finally fix this bug.


> With theese in place, we seem to have it behaving properly again for 
> Mageia users reporting various problems / firmware crashes / ...

Thanks, Thomas, for the comprehensive list of fixes needed here!


--
Cheers,
Luca.


      reply	other threads:[~2019-12-23 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 20:35 [PATCH] Revert "iwlwifi: mvm: fix scan config command size" Mehmet Akif Tasova
2019-12-18 19:12 ` Roman Gilg
     [not found]   ` <CAP=YcKGLDx_coFsY7ej6BkdBJT+FELGSOMM6YM_r7jgqEsvChw@mail.gmail.com>
2019-12-19 10:15     ` Mehmet Akif Tasova
2019-12-23 12:24   ` Thomas Backlund
2019-12-23 13:52     ` Luciano Coelho [this message]

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=88b9ffdc51ae5e11341332d7f5efed07320251c6.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=ayala.beker@intel.com \
    --cc=davem@davemloft.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=makiftasova@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sara.sharon@intel.com \
    --cc=shahar.s.matityahu@intel.com \
    --cc=subdiff@gmail.com \
    --cc=tmb@mageia.org \
    --cc=tova.mussai@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).