linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Alexander Wetzel <alexander@wetzel-home.de>,
	kvalo@codeaurora.org, Andy Lavr <andy.lavr@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [REGRESSION] Re: [PATCH 10/12] iwlwifi: remove wide_cmd_header field
Date: Fri, 09 Oct 2020 11:21:05 +0300	[thread overview]
Message-ID: <11996c068501b02797b4cfaeed87953cc9c24dc6.camel@coelho.fi> (raw)
In-Reply-To: <f20c67c4-3b9b-acc7-5e8c-998ddaf6b6ec@wetzel-home.de>

On Wed, 2020-10-07 at 22:23 +0200, Alexander Wetzel wrote:
> Am 28.09.20 um 11:23 schrieb Luca Coelho:
> > From: Mordechay Goodstein <mordechay.goodstein@intel.com>
> > 
> > Driver doesn't support fw without wide_cmd
> > so driver always sets it to true.  instead of setting
> > it always to true just remove the field.
> > 
> 
> I guess that's only true for mvm but not dvm...
> 
> At least this patch kills my wireless using a Ultimate-N 6300.
> Reverting to commit on top of wt-2020-10-06 works.
> 
> Here the last error I got during git bisect:
> 
> 
> [  375.671958] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
> [  375.739218] iwlwifi 0000:03:00.0: Microcode SW error detected. 
> Restarting 0x82000000.
> [  375.739226] iwlwifi 0000:03:00.0: Loaded firmware version: 9.221.4.1 
> build 25532 6000-4.ucode
> [  375.739349] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
> [  375.739353] iwlwifi 0000:03:00.0: Status: 0x00000000, count: 5
> [  375.739357] iwlwifi 0000:03:00.0: 0x00000007 | BAD_COMMAND

Hmmm, this indeed looks wrong.  I'll try to fix it or, in the worst
case, revert this patch.

--
Cheers,
Luca.


  reply	other threads:[~2020-10-09  8:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  9:23 [PATCH 00/12] iwlwifi: updates intended for v5.10 2020-09-28 Luca Coelho
2020-09-28  9:23 ` [PATCH 01/12] iwlwifi: add a common struct for all iwl_tx_power_cmd versions Luca Coelho
2020-10-01 19:00   ` Luca Coelho
2020-09-28  9:23 ` [PATCH 02/12] iwlwifi: acpi: prepare SAR profile selection code for multiple sizes Luca Coelho
2020-09-28  9:23 ` [PATCH 03/12] iwlwifi: support REDUCE_TX_POWER_CMD version 6 Luca Coelho
2020-09-28  9:23 ` [PATCH 04/12] iwlwifi: acpi: rename geo structs to contain versioning Luca Coelho
2020-09-28  9:23 ` [PATCH 05/12] iwlwifi: support version 3 of GEO_TX_POWER_LIMIT Luca Coelho
2020-09-28  9:23 ` [PATCH 06/12] iwlwifi: mvm: support new KEK KCK api Luca Coelho
2020-09-28  9:23 ` [PATCH 07/12] iwlwifi: rs: set RTS protection for all non legacy rates Luca Coelho
2020-09-28  9:23 ` [PATCH 08/12] iwlwifi: acpi: in non acpi compilations remove iwl_sar_geo_init Luca Coelho
2020-09-28  9:23 ` [PATCH 09/12] iwlwifi: fw: add default value for iwl_fw_lookup_cmd_ver Luca Coelho
2020-09-28  9:23 ` [PATCH 10/12] iwlwifi: remove wide_cmd_header field Luca Coelho
2020-10-07 20:23   ` [REGRESSION] " Alexander Wetzel
2020-10-09  8:21     ` Luca Coelho [this message]
2020-09-28  9:23 ` [PATCH 11/12] iwlwifi: mvm: add support for range request command ver 11 Luca Coelho
2020-09-28  9:23 ` [PATCH 12/12] iwlwifi: mvm: add support for responder dynamic config command version 3 Luca Coelho

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=11996c068501b02797b4cfaeed87953cc9c24dc6.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=alexander@wetzel-home.de \
    --cc=andy.lavr@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).