* boot kernel panic with QCA6174 and kernel 4.8
@ 2016-12-07 8:40 Alexandre Maloteaux
2016-12-07 12:41 ` Mohammed Shafi Shajakhan
0 siblings, 1 reply; 4+ messages in thread
From: Alexandre Maloteaux @ 2016-12-07 8:40 UTC (permalink / raw)
To: ath10k
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Hi
Since recent kernel upgrade on Arch linux ; im facing boot kernel
panics with the ath10k_pci and QCA6174 802.11ac Wireless Network Adapter
on an Eurocom P5 Pro laptop.
This is the main call stack dump :
ath10k_print_driver_info(ath10k_core)
ath10k_pcl_fw_crashed_dump (ath10k_pci)
ath10k_pcl.tasklet
So far i can circumvent the kernel panic by appending
modprobe.blacklist=ath10k_pci to the kernel command line.
Once the Os is booted i can load the module with modprobe without
triggering the kernel panic.
I also unpacked the initrd and the firmware file are not located in
lib/firmware.
I could not setup kdump so early in the boot process so i have attached
a screenshot of the on screen dump.
lspci :
06:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 20)
uname -r
4.8.11-1-ARCH
Best Regards
[-- Attachment #2: sc panic.jpg --]
[-- Type: image/jpeg, Size: 428995 bytes --]
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boot kernel panic with QCA6174 and kernel 4.8
2016-12-07 8:40 boot kernel panic with QCA6174 and kernel 4.8 Alexandre Maloteaux
@ 2016-12-07 12:41 ` Mohammed Shafi Shajakhan
2016-12-07 12:52 ` Mohammed Shafi Shajakhan
0 siblings, 1 reply; 4+ messages in thread
From: Mohammed Shafi Shajakhan @ 2016-12-07 12:41 UTC (permalink / raw)
To: Alexandre Maloteaux; +Cc: ath10k
Hi,
On Wed, Dec 07, 2016 at 09:40:29AM +0100, Alexandre Maloteaux wrote:
> Hi
> Since recent kernel upgrade on Arch linux ; im facing boot kernel
> panics with the ath10k_pci and QCA6174 802.11ac Wireless Network Adapter
> on an Eurocom P5 Pro laptop.
>
> This is the main call stack dump :
>
> ath10k_print_driver_info(ath10k_core)
> ath10k_pcl_fw_crashed_dump (ath10k_pci)
> ath10k_pcl.tasklet
[shafi] If you have the source of the same and with the help of gdb we
can get the exact line
>
> So far i can circumvent the kernel panic by appending
> modprobe.blacklist=ath10k_pci to the kernel command line.
> Once the Os is booted i can load the module with modprobe without
> triggering the kernel panic.
>
> I also unpacked the initrd and the firmware file are not located in
> lib/firmware.
[shafi] interesting your log (image file) seems to show the firmware is crashed
? if the firmware is missing you can give a try with this
https://patchwork.kernel.org/patch/9412085/ but the call trace looks completely
different, if the f/w is not there
long time back we fixed a race https://patchwork.kernel.org/patch/9167045/ but
it should be available in 4.8.11
>
> I could not setup kdump so early in the boot process so i have attached
> a screenshot of the on screen dump.
>
> lspci :
> 06:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 20)
>
> uname -r
> 4.8.11-1-ARCH
>
> Best Regards
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boot kernel panic with QCA6174 and kernel 4.8
2016-12-07 12:41 ` Mohammed Shafi Shajakhan
@ 2016-12-07 12:52 ` Mohammed Shafi Shajakhan
2016-12-07 20:30 ` Alexandre Maloteaux
0 siblings, 1 reply; 4+ messages in thread
From: Mohammed Shafi Shajakhan @ 2016-12-07 12:52 UTC (permalink / raw)
To: Alexandre Maloteaux; +Cc: ath10k
Hi,
also worth putting a print in 'ath10k_debug_print_board_info'
debug.c
~/ath/drivers/net/wireless/ath/ath10k$ git diff
diff --git a/drivers/net/wireless/ath/ath10k/debug.c
b/drivers/net/wireless/ath/ath10k/debug.c
index bfc0215..89ab4af 100644
--- a/drivers/net/wireless/ath/ath10k/debug.c
+++ b/drivers/net/wireless/ath/ath10k/debug.c
@@ -169,6 +169,12 @@ void ath10k_debug_print_board_info(struct ath10k *ar)
else
scnprintf(boardinfo, sizeof(boardinfo), "N/A");
+ if (IS_ERR_OR_NULL(ar->normal_mode_fw.board)) {
+ printk("\nAvoided oops ?\n");
+ WARN_ON(1);
+ return;
+ }
+
ath10k_info(ar, "board_file api %d bmi_id %s
crc32 %08x",
ar->bd_api,
boardinfo,
Let me know if it helps, or you need a patch format
regards,
shafi
On Wed, Dec 07, 2016 at 06:11:49PM +0530, Mohammed Shafi Shajakhan wrote:
> Hi,
>
> On Wed, Dec 07, 2016 at 09:40:29AM +0100, Alexandre Maloteaux wrote:
> > Hi
> > Since recent kernel upgrade on Arch linux ; im facing boot kernel
> > panics with the ath10k_pci and QCA6174 802.11ac Wireless Network Adapter
> > on an Eurocom P5 Pro laptop.
> >
> > This is the main call stack dump :
> >
> > ath10k_print_driver_info(ath10k_core)
> > ath10k_pcl_fw_crashed_dump (ath10k_pci)
> > ath10k_pcl.tasklet
>
> [shafi] If you have the source of the same and with the help of gdb we
> can get the exact line
>
> >
> > So far i can circumvent the kernel panic by appending
> > modprobe.blacklist=ath10k_pci to the kernel command line.
> > Once the Os is booted i can load the module with modprobe without
> > triggering the kernel panic.
> >
> > I also unpacked the initrd and the firmware file are not located in
> > lib/firmware.
>
> [shafi] interesting your log (image file) seems to show the firmware is crashed
> ? if the firmware is missing you can give a try with this
> https://patchwork.kernel.org/patch/9412085/ but the call trace looks completely
> different, if the f/w is not there
>
> long time back we fixed a race https://patchwork.kernel.org/patch/9167045/ but
> it should be available in 4.8.11
>
> >
> > I could not setup kdump so early in the boot process so i have attached
> > a screenshot of the on screen dump.
> >
> > lspci :
> > 06:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> > Network Adapter (rev 20)
> >
> > uname -r
> > 4.8.11-1-ARCH
> >
> > Best Regards
>
>
> > _______________________________________________
> > ath10k mailing list
> > ath10k@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/ath10k
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: boot kernel panic with QCA6174 and kernel 4.8
2016-12-07 12:52 ` Mohammed Shafi Shajakhan
@ 2016-12-07 20:30 ` Alexandre Maloteaux
0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Maloteaux @ 2016-12-07 20:30 UTC (permalink / raw)
To: Mohammed Shafi Shajakhan; +Cc: ath10k
Hi would like to clarify that i have the bug since 1 week . However the
kernel panic is semi-Random.
If i face the kernel panic ; then i can restart indefinitely and i
always face the crash.
Right now i came back home and the laptop starts correctly. I can
restart it multiple time and it will boot correctly as well.
I m facing this behavior since 1 week and can't find a pattern on how to
crash / success boot.
Best Regards
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-07 20:31 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-07 8:40 boot kernel panic with QCA6174 and kernel 4.8 Alexandre Maloteaux
2016-12-07 12:41 ` Mohammed Shafi Shajakhan
2016-12-07 12:52 ` Mohammed Shafi Shajakhan
2016-12-07 20:30 ` Alexandre Maloteaux
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox