linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Balakrishnan Balasubramanian <linux-wireless-list@balki.me>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi module crash
Date: Fri, 7 Jun 2019 12:25:41 +0300	[thread overview]
Message-ID: <CANUX_P0=F4-Q5Drhcpk6-y7F7Ub3omQk=Pg6wh3pv=pLc9YHWQ@mail.gmail.com> (raw)
In-Reply-To: <2455026.F8Aexx8IWb@zadesk>

On Fri, Jun 7, 2019 at 5:22 AM Balakrishnan Balasubramanian
<linux-wireless-list@balki.me> wrote:
>
> I am using iwd demon for wifi. Once a while I loose connectivity. Restarting
> the demon does not help. But once I restart the system, it starts working fine.
> Attaching stack trace from journal.

This is because the device is removed from the PCI bus. Nothing from
iwlwifi side can be done.
If that happens upon suspend / resume, I know there are been fixes in
PCI bus driver. If not, check that the device sits correctly in its
socket.

>
> Regards,
> Bala
>
>
> ---------- Forwarded message ----------
> From: Denis Kenzior <denkenz@gmail.com>
> To: Balakrishnan Balasubramanian <iwd-lists@balki.me>, iwd@lists.01.org
> Cc:
> Bcc:
> Date: Thu, 06 Jun 2019 18:07:40 -0500
> Subject: Re: iwd crashes randomly
> Hi Bala,
>
> On 06/06/2019 06:00 PM, Balakrishnan Balasubramanian wrote:
> > Sometimes after a week and sometimes after two days. Once crashed, restarting
> > the service does not help. Had to restart the computer. Attaching stack trace
> > from journal.
>
> That implies that your kernel is crashing, not iwd.  The attached log
> shows a kernel stack trace somewhere inside iwlwifi module.  I would
> post this trace to linux-wireless@vger.kernel.org.
>
> If you have an associated iwd backtrace, then certainly post this here,
> but if the kernel module is crashing, there isn't much we can do.
>
> Regards,
> -Denis

  reply	other threads:[~2019-06-07  9:25 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 [this message]
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
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='CANUX_P0=F4-Q5Drhcpk6-y7F7Ub3omQk=Pg6wh3pv=pLc9YHWQ@mail.gmail.com' \
    --to=egrumbach@gmail.com \
    --cc=linux-wireless-list@balki.me \
    --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).