From: Kalle Valo <kvalo@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: IPQ8074 firmware crash with testing version 2.7.0.1-01701
Date: Mon, 18 Jul 2022 13:17:13 +0300 [thread overview]
Message-ID: <87fsiysp1y.fsf@kernel.org> (raw)
In-Reply-To: <62be1f6d.1c69fb81.647ef.1d86@mx.google.com> (Christian Marangi's message of "Fri, 1 Jul 2022 00:10:53 +0200")
Christian Marangi <ansuelsmth@gmail.com> writes:
> testing this latest firmware on my ipq8074 based router result in a
> firmware crash. The firmware seems to crash on loading.
>
> The router is a Xiaomi Ax3600
> Firmware: WLAN.HK.2.7.0.1-01701-QCAHKSWPL_SILICONZ-1
>
> This is the crashlog
> [ 17.277607] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
> [ 17.277607] QC Image Version:
> QC_IMAGE_VERSION_STRING=WLAN.HK.2.7.0.1-01701-QCAHKSWPL_SILICONZ-1
> [ 17.277607] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
> [ 17.277607]
> [ 17.277607] :Excep :0 Exception detectedparam0 :zero, param1 :zero,
> param2 :zero.
> [ 17.277607] Thread ID : 0x00000069 Thread name : WLAN RT0 Process ID
> : 0
> [ 17.277607] Register:
> [ 17.277607] SP : 0x4bfacdc0
> [ 17.277607] FP : 0x4bfacdd8
> [ 17.277607] PC : 0x4b18d338
> [ 17.277607] SSR : 0x00000001
> [ 17.277607] BADVA : 0x0028d127
> [ 17.277607] LR : 0x4b18d2b8
> [ 17.277607]
> [ 17.277607] Stack Dump
> [ 17.277607] from : 0x4bfacdc0
> [ 17.277607] to : 0x4bfad400
> [ 17.277607]
> [ 17.324231] remoteproc remoteproc0: crash detected in
> cd00000.q6v5_wcss: type fatal error
> [ 17.346841] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
> [ 17.354631] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
> [ 17.387472] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
>
> Firmware WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1 works correctly so
> this is clrearly a regression.
>
> I know that the crashlog is probably uselss so feel free to tell me how
> to provide additional data.
Bugzilla makes it so much easier to track issues and get them fixed, so
can you please file it there:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
Also remember to include all relevant information, especially the kernel
version and any extra patches you might have.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2022-07-18 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 22:10 IPQ8074 firmware crash with testing version 2.7.0.1-01701 Christian Marangi
2022-07-18 10:17 ` Kalle Valo [this message]
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=87fsiysp1y.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=ath11k@lists.infradead.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