[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLVA1ZQjwEdbX5KGbSyLnMBAzm9PoN_Ta_Z7rBf4w3GOvQ@mail.gmail.com>
Date: Tue, 2 Jun 2020 12:40:29 -0700
From: John Stultz <john.stultz@...aro.org>
To: Brian Norris <briannorris@...omium.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Rakesh Pillai <pillair@....qualcomm.com>,
Govind Singh <govinds@...eaurora.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Niklas Cassel <niklas.cassel@...aro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Amit Pundir <amit.pundir@...aro.org>,
Kalle Valo <kvalo@...eaurora.org>,
ath10k <ath10k@...ts.infradead.org>,
Sibi Sankar <sibis@...eaurora.org>
Subject: Re: [PATCH] wireless: ath10k: Return early in ath10k_qmi_event_server_exit()
to avoid hard crash on reboot
On Tue, Jun 2, 2020 at 12:16 PM Brian Norris <briannorris@...omium.org> wrote:
>
> + Sibi
>
> On Mon, Jun 1, 2020 at 10:25 PM John Stultz <john.stultz@...aro.org> wrote:
> >
> > Ever since 5.7-rc1, if we call
> > ath10k_qmi_remove_msa_permission(), the db845c hard crashes on
> > reboot, resulting in the device getting stuck in the usb crash
> > debug mode and not coming back up wihthout a hard power off.
> >
> > This hack avoids the issue by returning early in
> > ath10k_qmi_event_server_exit().
> >
> > A better solution is very much desired!
>
> Any chance you can bisect what caused this? There are a lot of
> non-ath10k pieces involved in this stuff.
Amit had spent some work on chasing it down to the in kernel qrtr-ns
work, and reported it here:
https://lists.infradead.org/pipermail/ath10k/2020-April/014970.html
But that discussion seemingly stalled out, so I came up with this hack
to workaround it for us.
thanks
-john
Powered by blists - more mailing lists