From: Kalle Valo <kvalo@codeaurora.org>
To: Justin Capella <justincapella@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ACS scans not returning noise floor
Date: Tue, 26 Feb 2019 14:05:19 +0200 [thread overview]
Message-ID: <87k1hmlpq8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAMrEMU-++j02+sMwMKFS5SSsEzXbu7Sb7WceheKvVPoMUmyi1Q@mail.gmail.com> (Justin Capella's message of "Thu, 21 Feb 2019 16:58:02 -0800")
Justin Capella <justincapella@gmail.com> writes:
> My apologies,
> I left out the important bit of the debug logs
> [ 1265.917324] ath10k_warn: 61 callbacks suppressed
> [ 1265.917330] ath10k_pci 0000:01:00.0: failed to parse chan info event: -71
>
> Possibly also relevant, i'm using country "US" I am aware that the fcc
> crda/regdom wasn't supported, but without the 802.11h option
> condigured in hostapd it had been working with older firmware.
>
> 7ce94a62264be94dc1c41ff5d0c8a19c7f0d3143 is the head of the master
> branch I'm using
What hardware and firmware version? That's very important. Preferably
copy the ath10k driver initialisation messages which contain all that.
Is this is regression, for example did an old firmware work? If yes,
which one did not have this problem?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-02-26 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 0:39 ACS scans not returning noise floor Justin Capella
2019-02-22 0:58 ` Justin Capella
2019-02-26 12:05 ` Kalle Valo [this message]
2019-03-01 9:55 ` Justin Capella
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=87k1hmlpq8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=justincapella@gmail.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