From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Konstantin Bogomolov <konstantin.bogomolov@dejero.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Kernel panic hosting 5Ghz AP
Date: Thu, 23 Nov 2017 06:41:08 +0000 [thread overview]
Message-ID: <87zi7da458.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGT1WQM6uiP6GHW9ukNUPf+JcZckENz514gg0DiR7CCO=5K+Fg@mail.gmail.com> (Konstantin Bogomolov's message of "Wed, 22 Nov 2017 14:22:43 -0500")
Konstantin Bogomolov <konstantin.bogomolov@dejero.com> writes:
> I have an issue where I get a kernel panic upon hosting the following
> AP with hostapd version 2.4 :
>
> # cat hostapd1.conf
> interface=hotspot0
> driver=nl80211
> hw_mode=a
> channel=0
> ieee80211d=1
> country_code=CA
> ieee80211ac=1
> ssid=test5
> auth_algs=1
> wpa=2
> wpa_key_mgmt=WPA-PSK
> rsn_pairwise=CCMP
> wpa_passphrase=testtest
>
> I am using a stock Debian Stretch 4.9 kernel, with the latest ath10k
> firmware. The card I am using is:
>
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 32)
> Subsystem: AzureWave QCA6174 802.11ac Wireless Network Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 326
> Memory at df000000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
> Capabilities: [70] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [148] Virtual Channel
> Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
> Capabilities: [178] Latency Tolerance Reporting
> Capabilities: [180] L1 PM Substates
> Kernel driver in use: ath10k_pci
> Kernel modules: ath10k_pci
>
>
> I get the following dmesg logs from the panic:
>
> [ 84.211731] IPv6: ADDRCONF(NETDEV_UP): hotspot0: link is not ready
> [ 84.212359] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000020
> [ 84.212410] IP: [<ffffffffaa8ed9ed>] skb_release_data+0x8d/0x110
Did you see this once or multiple times? Are you able to reproduce the
crash? Is this a regression (in other words did it work ok before)? At
what stage exactly does it crash, do you need to do something special to
make it crash?
Trying out a recent vanilla kernel.org release would be helpful to
pinpoint the problem as the Debian kernel might have custom patches
causing problems.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-11-23 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 19:22 Kernel panic hosting 5Ghz AP Konstantin Bogomolov
2017-11-23 6:41 ` Kalle Valo [this message]
2017-11-23 16:41 ` Konstantin Bogomolov
2017-11-27 6:21 ` Kalle Valo
2017-11-28 19:52 ` Ryan Hsu
2017-11-29 16:56 ` Konstantin Bogomolov
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=87zi7da458.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=konstantin.bogomolov@dejero.com \
/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