From: Kalle Valo <kvalo@codeaurora.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath11k: fix rmmod failure if qmi sequence fails
Date: Wed, 25 Nov 2020 16:03:33 +0200 [thread overview]
Message-ID: <87mtz5pm8a.fsf@codeaurora.org> (raw)
In-Reply-To: <1605076699-21924-1-git-send-email-akolli@codeaurora.org> (Anilkumar Kolli's message of "Wed, 11 Nov 2020 12:08:19 +0530")
Anilkumar Kolli <akolli@codeaurora.org> writes:
> QMI sequence fails if caldata file is not available.
> It is observed that 'rmmod ath11k' fails if qmi message fails.
> With this patch rmmod/insmod is working.
>
> Logs:
> Direct firmware load for IPQ8074/caldata.bin failed with error -2
> Falling back to user helper
> qmi failed to load CAL: IPQ8074/caldata.bin
> qmi failed to load board data file:-11
>
> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1-00009-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
With this patch reloading ath11k (which has worked fine before) crashes
the kernel on QCA6390 hw2.0:
Nov 25 16:00:52 nuc1 [ 393.188277] BUG: unable to handle page fault for address: ffffffffc05b8e38
Nov 25 16:00:52 nuc1 [ 393.188300] #PF: supervisor read access in kernel mode
Nov 25 16:00:52 nuc1 [ 393.188312] #PF: error_code(0x0000) - not-present page
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-25 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 6:38 [PATCH v2] ath11k: fix rmmod failure if qmi sequence fails Anilkumar Kolli
2020-11-25 14:03 ` Kalle Valo [this message]
2020-11-30 13:55 ` akolli
2020-11-30 16:27 ` Kalle Valo
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=87mtz5pm8a.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--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).