Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <2455026.F8Aexx8IWb@zadesk> <CAPuHQ=Ffq_Gw_KbyjpzR07MWz=+LxmGVEP2-Tn5zDxrUEuxrZQ@mail.gmail.com>
 <CAPuHQ=GLgDFQZDhGv34S4yhOXTQL7AkKOywSqqtyPD8Lv6cCPw@mail.gmail.com> <2221997.PNfK1iNeOp@zadesk>
In-Reply-To: <2221997.PNfK1iNeOp@zadesk>
From:   b.K.il.h.u+tigbuh@gmail.com
Date:   Wed, 26 Jun 2019 00:17:28 +0200
Message-ID: <CAPuHQ=FiVABk2U+L_XXwKe7NH0NpCf7gz0O_XY6xrC3MSDm3Nw@mail.gmail.com>
Subject: Re: iwlwifi module crash
To:     Balakrishnan Balasubramanian <linux-wireless-list@balki.me>
Cc:     Emmanuel Grumbach <egrumbach@gmail.com>,
        linux-wireless <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Maybe we don't have the same issue, but today this one solved it for
me: `rmmod iwlmvm; rmmod iwlwifi; modprobe iwlwifi`. Well, kind of. It
couldn't really connect to any network afterwards, but after another
such dance it was finally back to normal.

The device disappears from iwconfig for me when this happens, so it is
easy to detect and correct with few lines of shell. It can also be
gone from lspci as well. Another alternative would be to set up a
syslog-ng program destination triggered by a patterndb sample matching
the noted failures among the kernel messages.

If it gets stuck without a visible sign, you could watch Inactive time
and tx failures in `iw dev wlan0 station dump` increase sharply in
case of issues. If you need a bit more reliability, it is easy to ping
the AP or gateway every second and refresh the connection in case of
too many consecutive missing replies.

On Mon, Jun 24, 2019 at 11:36 PM Balakrishnan Balasubramanian
<linux-wireless-list@balki.me> wrote:
>
> Thanks for the tip. In my system the path to remove was below:
>
> /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/remove
> Also symlinked here:
> /sys/module/iwlwifi/drivers/pci:iwlwifi/0000:02:00.0/remove
>
> I am now able to restore internet without system restart. Now I need to find a
> way to do this automatically whenever internet goes down.
>
> Thanks,
> Bala
>
> On Sunday, June 23, 2019 5:08:32 AM EDT b.K.il.h.u+tigbuh@gmail.com wrote:
> > devices/ is probably just a symlink. Try to find it manually:
> > find /sys -iname remove
> > lspci
> >
> > The interesting thing is that my iwlwifi card started to do the same
> > thing just recently (some weeks ago). However, I do suspend a lot and
> > it only happens after resuming, but not after every resume (maybe
> > 5-10%). It always came back after restarting except on one day when it
> > needed three restarts, so maybe mine would be more about needing to
> > reseat the card.
> >
> > > On Fri, Jun 14, 2019 at 4:54 AM Balakrishnan Balasubramanian <linux-
> wireless-list@balki.me> wrote:
> > >> The issue occured again today. I tried to restart the module
> > >>
> > >> > echo 1 > /sys/module/iwlwifi/devices/0000\:02\:00.0/remove
> > >>
> > >> There is no folder 'devices'
> > >>
> > >> zadesk% ls /sys/module/iwlwifi
> > >> coresize  drivers  holders  initsize  initstate  notes  parameters
> > >> refcnt
> > >> sections  srcversion  taint  uevent
> > >>
> > >> > echo 1 > /sys/bus/pci/rescan
> > >>
> > >> Attached the error when trying to rescan.
> > >>
> > >> Thanks,
> > >> Bala
>
>
>
>