From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "Goodstein, Mordechay" <mordechay.goodstein@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"rsalvaterra@gmail.com" <rsalvaterra@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [BUG] iwlwifi: card unusable after firmware crash
Date: Tue, 8 Dec 2020 16:27:46 +0000 [thread overview]
Message-ID: <4eb99a1da6342999c4dca355533a0847d0e942a5.camel@intel.com> (raw)
In-Reply-To: <CALjTZvZZZVqnoV4YFTDHogVHv77=dKfcSSBGj1zC83zpUid9+g@mail.gmail.com>
On Tue, 2020-12-08 at 11:27 +0000, Rui Salvaterra wrote:
> Hi, everyone,
>
> I'm running Linux 5.10-rc7 with this firmware/hardware:
>
> [ 1.431878] iwlwifi 0000:02:00.0: loaded firmware version
> 29.198743027.0 7265D-29.ucode op_mode iwlmvm
> [ 1.431899] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band
> Wireless AC 3165, REV=0x210
>
> Most of the time, after disabling/enabling Wi-Fi (or, say, rebooting
> the router), the card dies and only comes back after reboot. This is
> the relevant dmesg output:
>
> [ 3174.003910] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> [ 3174.003913] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
It looks like your machine is reporting RF-Kill to the WiFi device.
There seems to be some sort of race there that is causing us to still
try to communicate with the device (and thus you see the transaction
failed dump), but that will obviously fail when RF-Kill is enabled.
--
Luca.
next prev parent reply other threads:[~2020-12-08 16:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:27 Rui Salvaterra
2020-12-08 16:05 ` Jakub Kicinski
2020-12-08 23:09 ` Rui Salvaterra
2020-12-08 16:27 ` Coelho, Luciano [this message]
2020-12-08 23:17 ` Rui Salvaterra
2020-12-09 17:13 ` Jakub Kicinski
2020-12-09 20:02 ` Coelho, Luciano
2020-12-09 20:14 ` Rui Salvaterra
2020-12-09 20:32 ` Emmanuel Grumbach
2020-12-09 20:40 ` Emmanuel Grumbach
2020-12-09 20:41 ` Rui Salvaterra
2020-12-09 20:40 ` Rui Salvaterra
2020-12-09 20:47 ` Emmanuel Grumbach
2020-12-09 21:07 ` Emmanuel Grumbach
2020-12-09 21:16 ` Rui Salvaterra
2020-12-10 16:21 ` Rui Salvaterra
2020-12-10 18:57 ` Emmanuel Grumbach
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=4eb99a1da6342999c4dca355533a0847d0e942a5.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mordechay.goodstein@intel.com \
--cc=rsalvaterra@gmail.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
all inboxes | Powered by JetHome®