linux-kernel - Re: [BUG] iwlwifi: card unusable after firmware crash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANUX_P3S-Dt2homERtXgxQuh+q=xCTDvqx2ZwOXvZfjMrBY-9w@mail.gmail.com>
Date:   Wed, 9 Dec 2020 22:40:10 +0200
From:   Emmanuel Grumbach <egrumbach@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     "Coelho, Luciano" <luciano.coelho@...el.com>,
        Rui Salvaterra <rsalvaterra@...il.com>,
        "Goodstein, Mordechay" <mordechay.goodstein@...el.com>,
        "Berg, Johannes" <johannes.berg@...el.com>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] iwlwifi: card unusable after firmware crash

On Wed, Dec 9, 2020 at 10:32 PM Emmanuel Grumbach <egrumbach@...il.com> wrote:
>
> On Wed, Dec 9, 2020 at 7:19 PM Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > 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@...el.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 :(
>
> Rui, I looked at the register dump and looks like you're using AMT on
> your system?
> Can you confirm?

Besides, don't you get a stack dump in the vicinity of this register
dump? That's be helpful to see.