From: Balakrishnan Balasubramanian <linux-wireless-list@balki.me>
To: b.K.il.h.u+tigbuh@gmail.com
Cc: Balakrishnan Balasubramanian <linux-wireless-list@balki.me>,
Emmanuel Grumbach <egrumbach@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi module crash
Date: Mon, 24 Jun 2019 17:36:25 -0400 [thread overview]
Message-ID: <2221997.PNfK1iNeOp@zadesk> (raw)
In-Reply-To: <CAPuHQ=GLgDFQZDhGv34S4yhOXTQL7AkKOywSqqtyPD8Lv6cCPw@mail.gmail.com>
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
next prev parent reply other threads:[~2019-06-24 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 23:44 iwlwifi module crash Balakrishnan Balasubramanian
2019-06-07 9:25 ` Emmanuel Grumbach
2019-06-07 11:41 ` Balakrishnan Balasubramanian
2019-06-10 6:50 ` Emmanuel Grumbach
2019-06-14 1:47 ` Balakrishnan Balasubramanian
[not found] ` <CAPuHQ=Ffq_Gw_KbyjpzR07MWz=+LxmGVEP2-Tn5zDxrUEuxrZQ@mail.gmail.com>
2019-06-23 9:08 ` b.K.il.h.u+tigbuh
2019-06-24 21:36 ` Balakrishnan Balasubramanian [this message]
2019-06-25 22:17 ` b.K.il.h.u+tigbuh
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=2221997.PNfK1iNeOp@zadesk \
--to=linux-wireless-list@balki.me \
--cc=b.K.il.h.u+tigbuh@gmail.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).