From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Repeated firmware crash when admin down.
Date: Mon, 23 Mar 2015 17:30:35 -0700 [thread overview]
Message-ID: <5510B02B.9030503@candelatech.com> (raw)
In-Reply-To: <CA+BoTQk8Xz_mv=626rHYRT7gaVYCqfwuCP8ZSSx7gUWO898oMw@mail.gmail.com>
The user reports this does indeed fix the problem.
Thanks,
Ben
On 03/22/2015 11:37 PM, Michal Kazior wrote:
> On 20 March 2015 at 22:46, Ben Greear <greearb@candelatech.com> wrote:
>> Someone reported this bug to me. It is repeatable on various firmware,
>> including my own and official QCA firmware.
>>
>> I am not certain of the hardware platform, but I think it might be a Ventana
>> imx6 board.
>>
>> Kernel is based on 3.19-mumble.
>>
>> I cannot reproduce on x86 (but testing on 3.17 kernel and different flavour of
>> Linux, so who knows.)
>>
>> They simply admin-down wlanX, and then the firmware crashes over and over.
>> They cannot get any register dump.
>> When they admin up the interface, the crashes stop and system resumes normally.
>>
>> I had them try it with my firmware and a driver patch
>> which will attempt to do ping-pong register dump
>> over pci register reads in case the firmware's normal PCI messaging transport
>> is down, but the register value always reads as '0xdeadbeef'.
>>
>> Driver patch is linked below, 'val' is 0xdeadbeef after the million read attempts.
>
> If you read MMIO registers while the device sleeps you get 0xdeadbeef.
> I've recently posted a patch which should fix some of these[1].
>
> I'm guessing the imx6 board could be using shared irq and the line is
> shared with some other (active) device(s). This would lead to checking
> registers in ath10k after ath10k_pci_sleep(). In that case my patch
> should be sufficient.
>
> [1]: https://github.com/kvalo/ath/commit/320e14b8db51a2d635897d521db4e5c79c3a8390
>
>
> Michał
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-03-24 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 21:46 Repeated firmware crash when admin down Ben Greear
2015-03-23 6:37 ` Michal Kazior
2015-03-24 0:30 ` Ben Greear [this message]
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=5510B02B.9030503@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.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