From: Jakub Kicinski <kuba@kernel.org>
To: "Coelho, Luciano" <luciano.coelho@intel.com>
Cc: Rui Salvaterra <rsalvaterra@gmail.com>,
"Goodstein, Mordechay" <mordechay.goodstein@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] iwlwifi: card unusable after firmware crash
Date: Wed, 9 Dec 2020 09:13:15 -0800 [thread overview]
Message-ID: <20201209091315.2c55e1c6@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com> (raw)
In-Reply-To: <CALjTZvYwccfOVTTGNo1=oLnwXG2b9Vz1nVZuvLKFV94+3fQ6EQ@mail.gmail.com>
On Tue, 8 Dec 2020 23:17:48 +0000 Rui Salvaterra wrote:
> Hi, Luca,
>
> On Tue, 8 Dec 2020 at 16:27, Coelho, Luciano <luciano.coelho@intel.com> wrote:
> > On Tue, 2020-12-08 at 11:27 +0000, Rui Salvaterra wrote:
> > >
> > > [ 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.
>
> Yes, that's an artifact of how I tested: I rebooted the router, the
> Wi-Fi interface disassociated and the dmesg was clean. However, after
> the router came up, the laptop didn't reconnect (and the connection
> had completely disappeared from nmtui). Afterwards, I did the rfkill
> cycle you see, and only then I got the register dump.
>
> > 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.
>
> I'm not sure about that, the card was already dead before the rfkill cycle.
Any luck figuring this out, Luca? If this is a 5.10 regression we need
to let Linus know tomorrow, so the time is ticking :(
next prev parent reply other threads:[~2020-12-09 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:27 [BUG] iwlwifi: card unusable after firmware crash Rui Salvaterra
2020-12-08 16:05 ` Jakub Kicinski
2020-12-08 23:09 ` Rui Salvaterra
2020-12-08 16:27 ` Coelho, Luciano
2020-12-08 23:17 ` Rui Salvaterra
2020-12-09 17:13 ` Jakub Kicinski [this message]
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=20201209091315.2c55e1c6@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com \
--to=kuba@kernel.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).