From: Ellie Revves <ellierevves@gmail.com>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: Re: ath9k driver may be broken on ARM64 ?
Date: Wed, 24 Oct 2018 15:13:50 -0400 [thread overview]
Message-ID: <6c59ee97-cad9-46bb-be0c-6daa6f614a61@gmail.com> (raw)
In-Reply-To: <caf394ef-dc52-b19b-6b31-77b92158f389@gmail.com>
Hi,
well I enabled CONFIG_ATH_DEBUG and booted this kernel, sorry for the
mess of escape sequence but I captured via serial console:
http://ix.io/1pWI
I don't see anything different even if I cranked up ath9k.debug= to the
*any* value. I guess this thing happens so early at boot that nothing
useful is yet initialized...
Thanks
Ellie Revves a écrit :
> Hi,
> sure, I enabled atheros wireless debugging in my kernel and am
> rebuilding it. After this is done, should I set ath9k.debug= on the
> cmdline ? It is built as module, but my filesystem is read-only so no
> modprobe.d snippet can be added.
> Thanks
>
> Tom Psyborg a écrit :
>> Hi
>>
>> There was similar issue reported in forum recently:
>> https://forum.openwrt.org/t/wireless-card-atheros-ar9565/23608
>>
>> Could you enable ath9k debug and post output?
>
next prev parent reply other threads:[~2018-10-24 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 5:13 ath9k driver may be broken on ARM64 ? Ellie Revves
2018-10-24 12:09 ` Tom Psyborg
2018-10-24 18:39 ` Ellie Revves
2018-10-24 19:13 ` Ellie Revves [this message]
2018-10-24 22:53 ` Tom Psyborg
2018-10-24 23:05 ` Ellie Revves
2018-10-24 23:18 ` Tom Psyborg
2018-10-25 4:26 ` Ellie Revves
2018-10-25 6:27 ` Dominique Martinet
2018-10-26 5:11 ` Dominique Martinet
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=6c59ee97-cad9-46bb-be0c-6daa6f614a61@gmail.com \
--to=ellierevves@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pozega.tomislav@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