From: Ellie Revves <ellierevves@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: ath9k driver may be broken on ARM64 ?
Date: Wed, 24 Oct 2018 01:13:05 -0400 [thread overview]
Message-ID: <ecb743be-ec4f-0f80-c598-c71826492b30@gmail.com> (raw)
Hi,
for the context part:
I've got a marvell espressobin board, to which I attached a mini-PCIE
wireless card, atheros AR9565 aka. QCB335. I am using both archlinux-arm
and a custom OS made with buildroot, and both have this problem.
Problem:
When the system boots up, the kernel recognizes the card, and then the
ath9k driver gets loaded. From what someone on the irc channel of
#linux-wireless determined, the driver ends up doing a sigbus while
attempting to read from a specific address in memory, which of course
makes it crash. We did check the page tables, and the memory seems to be
mapped fine. So we're still clueless as to why it is not possible to
read from that particular memory address, and why the driver would do
so. Here I attach the kernel page tables, along with the dmesg output.
The problematic line in the trace is x19.
I'd appreciate any help in fixing this issue which I think might be
related to ARM64.
Note that I am no programmer, all the info I gathered so far were with
someone else's help. But if you need some more debug output, files or
anything else, just let me know. I can also apply patches to test
things, or modify the code if I know exactly in what way, i.e: what to
copy and past.
Dmesg:
http://ix.io/1pTK
kernel page tables -- from a later kernel build, but do notice that the
memory is still mapped correctly even if the register changed:
http://ix.io/1pQh
Thanks a lot :)
next reply other threads:[~2018-10-24 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 5:13 Ellie Revves [this message]
2018-10-24 12:09 ` ath9k driver may be broken on ARM64 ? Tom Psyborg
2018-10-24 18:39 ` Ellie Revves
2018-10-24 19:13 ` Ellie Revves
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=ecb743be-ec4f-0f80-c598-c71826492b30@gmail.com \
--to=ellierevves@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
/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