From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
Adrian Chadd <adrian@freebsd.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k driver crashes whenever firmware crashes on ARM SoC
Date: Thu, 13 Mar 2014 07:09:18 +0200 [thread overview]
Message-ID: <87y50ed6rl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-01MAbTh4ekq8+u-uG_cH=o9SCkpC-fWuMfsPDmfAMCow@mail.gmail.com> (Avery Pennarun's message of "Wed, 12 Mar 2014 18:28:17 -0500")
Avery Pennarun <apenwarr@gmail.com> writes:
> On Wed, Mar 12, 2014 at 11:01 AM, Ben Greear <greearb@candelatech.com> wrote:
>> Come to think of it, I'm not sure I've seen a hard lockup of the machine
>> on non CUS223 machines, but I have seen cases where non CUS223 NIC wedges
>> and the existing restart does not recover it.
>>
>> This requires a reboot to recover from.
>
> That's not so surprising; the current driver doesn't do the cold reset
> that is the only thing you can recover from a wedge, I guess because
> of the CUS223 bug.
>
> Stupid question: can I honestly just buy a different module and make
> my PCIe crashiness problems go away?
That's my theory, but I would like to confirm that somehow.
> Is there a reason do prefer the CUS223?
Good question, I haven't figured out that. CUS223 board is physically
larger than XB140, for example, and I would assume there's a reason for
that.
> Another question: is there perhaps anything the firmware can do to eg.
> set a watchdog timer, so that the internal CPU will restart (go back
> to "waiting for firmware" mode) if it doesn't answer for a while? The
> idea would be for the device to un-wedge itself even if there's
> nothing we can do to fix it from outside.
That's something a firmware engineer should comment on, which I'm not.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-03-13 5:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:18 ath10k driver crashes whenever firmware crashes on ARM SoC Avery Pennarun
2014-01-28 18:20 ` Ben Greear
2014-01-28 18:34 ` Avery Pennarun
2014-01-28 19:01 ` Ben Greear
2014-01-28 19:11 ` Avery Pennarun
2014-01-28 20:10 ` Janusz Dziedzic
2014-01-28 20:51 ` Avery Pennarun
2014-01-29 16:44 ` Kalle Valo
[not found] ` <CAJ-VmokorbJ2iU4rGNYdRj+A22NR9cV-5h-tDN0pD2FCurZDpA@mail.gmail.com>
2014-01-28 20:55 ` Avery Pennarun
2014-01-29 16:41 ` Kalle Valo
2014-01-29 18:44 ` Adrian Chadd
2014-01-30 2:41 ` Avery Pennarun
2014-02-09 8:00 ` Avery Pennarun
2014-02-27 15:48 ` Missing memory barriers Kalle Valo
2014-02-28 6:10 ` Avery Pennarun
2014-03-06 13:34 ` Kalle Valo
2014-03-11 7:33 ` ath10k driver crashes whenever firmware crashes on ARM SoC Kalle Valo
2014-03-11 7:40 ` Avery Pennarun
2014-03-11 7:52 ` Adrian Chadd
2014-03-11 7:59 ` Avery Pennarun
2014-03-11 8:13 ` Kalle Valo
2014-03-11 8:37 ` Michal Kazior
2014-03-11 8:10 ` Kalle Valo
2014-03-11 19:01 ` Ben Greear
2014-03-12 8:22 ` Kalle Valo
2014-03-12 16:01 ` Ben Greear
2014-03-12 23:28 ` Avery Pennarun
2014-03-13 5:09 ` Kalle Valo [this message]
2014-03-13 17:34 ` Adrian Chadd
2014-03-13 17:39 ` Kalle Valo
2014-03-13 17:42 ` Ben Greear
2014-03-14 6:26 ` Kalle Valo
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=87y50ed6rl.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=adrian@freebsd.org \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.