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: Mon, 27 Nov 2017 06:21:47 +0000 [thread overview]
Message-ID: <87h8tg6y2t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGT1WQO9y89Wz250zZs2qqGv7rut5C82Ncd4=XOKCLthnYrC3w@mail.gmail.com> (Konstantin Bogomolov's message of "Thu, 23 Nov 2017 11:41:54 -0500")
Konstantin Bogomolov <konstantin.bogomolov@dejero.com> writes:
> Hello Kalle,
>
> The panic happens after hostapd outputs "ACS-STARTED". Usually, the
> first attempt for me to start hostapd fails to create the AP (I think
> this is a separate issue with the 5Ghz AP), but the second attempt
> always initiates a panic on Debian 4.9 drivers.
>
> I don't think this is a regression, because I saw the same behaviour
> on a custom 4.1 kernel. I have also tried using backported drivers
> from 4.12.0 to both 4.1 and 4.9, where the panic was also reproducible
> on the second hostapd attempt, but didn't happen every time as it does
> on Debian 4.9. So the AP did work on some occasions using the
> backports, but the panic still happened very frequently. Sadly I don't
> have logs at this time using those backports.
>
> I'll try and reproduce this using a recent kernel and let you know the results.
Also try without ACS (meaning specify a channel mannually hostapd config
file) just to see if the crash is ACS related.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-11-27 6:22 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
2017-11-23 16:41 ` Konstantin Bogomolov
2017-11-27 6:21 ` Kalle Valo [this message]
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=87h8tg6y2t.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