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>
In-Reply-To: <2455026.F8Aexx8IWb@zadesk>
From:   Emmanuel Grumbach <egrumbach@gmail.com>
Date:   Fri, 7 Jun 2019 12:25:41 +0300
Message-ID: <CANUX_P0=F4-Q5Drhcpk6-y7F7Ub3omQk=Pg6wh3pv=pLc9YHWQ@mail.gmail.com>
Subject: Re: iwlwifi module crash
To:     Balakrishnan Balasubramanian <linux-wireless-list@balki.me>
Cc:     linux-wireless <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

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