From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"Coelho, Luciano" <luciano.coelho@intel.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: Thu, 10 Dec 2020 20:57:58 +0200 [thread overview]
Message-ID: <CANUX_P2YqrpenS0Ey2vgyB98PixP5JAYk96LABGV3jeMvc_MJQ@mail.gmail.com> (raw)
In-Reply-To: <CALjTZvZybsB3unK8X0WcA7kLF60=36F2senz6fEoJS6VVx6Hwg@mail.gmail.com>
Hi,
> Hi, again,
>
> I haven't tested any patch or bisected, but I have another data point.
> I built and tested Linux 5.8.18, with the same firmware, and it is
> working correctly. I reduced the test case to just rfkilling the
> connection, which showed the register dump immediately (before that I
> was using the airplane toggle on the keyboard, which isn't working
> correctly, it disables and immediately reenables the radio, for some
> unfathomable reason).
> So, now I'm inclined to believe this is some sort of race condition
> between rfkill and pending transactions.
Which also means it's not a regression.
You can add a dump_stack() in the function that dumps the registers to
get a clue.
prev parent reply other threads:[~2020-12-10 19:00 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
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 [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=CANUX_P2YqrpenS0Ey2vgyB98PixP5JAYk96LABGV3jeMvc_MJQ@mail.gmail.com \
--to=egrumbach@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--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).