From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: hacked 4.4.6+, 10.4.3 firmware, Running out of ring-index for pipe-id 3 (WMI).
Date: Thu, 31 Mar 2016 22:23:03 -0700 [thread overview]
Message-ID: <56FE05B7.80104@candelatech.com> (raw)
In-Reply-To: <CA+BoTQmFhqpyH--ik7YP8rbimVJnw+aC_go3xrPmYhrLTA5KHg@mail.gmail.com>
On 03/31/2016 10:18 PM, Michal Kazior wrote:
> On 31 March 2016 at 18:44, Ben Greear <greearb@candelatech.com> wrote:
>> On 03/30/2016 11:51 PM, Michal Kazior wrote:
>>
>> So, I am using MSI-X, I guess?
>>
>> # dmesg|grep -i msi
>> [65284.853372] ath10k_pci 0000:05:00.0: pci irq msi-x interrupts 13 irq_mode
>> 0 reset_mode 0
>
> Yep. This at least makes it possible for this weird problem to come
> into existance. However I still find it a little hard to believe for
> tasklets to be scheduled this badly. Maybe the device doesn't assert
> interrupts properly as Adrian suggested? Or maybe they are not mapped
> properly? I think you're actually the first one to exercise MSI-range
> support on qca99x0.
I applied Rajkumar's patch to disable msi-x today, so maybe that will be
the end of those problems.
I think upstream might want a warn-on for that wmi issue, even if you don't
add the work-around code though...just to see if someone else hits it.
If you drop the wrong WMI message, often your best hope is that firmware crashes
right away, so we should really be quite loud about not sending a WMI message.
Thanks,
Ben
--
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
next prev parent reply other threads:[~2016-04-01 5:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 19:01 hacked 4.4.6+, 10.4.3 firmware, Running out of ring-index for pipe-id 3 (WMI) Ben Greear
2016-03-29 8:05 ` Michal Kazior
2016-03-29 15:48 ` Ben Greear
[not found] ` <CAJ-Vmo=RzwymMtdWkrKTEnf+FU=Q3MU3QNqFneq74Qcn3BMfyg@mail.gmail.com>
2016-03-29 17:13 ` Ben Greear
2016-03-29 17:45 ` Adrian Chadd
2016-03-30 20:07 ` Ben Greear
2016-03-31 6:51 ` Michal Kazior
2016-03-31 15:51 ` Ben Greear
2016-03-31 16:44 ` Ben Greear
2016-04-01 5:18 ` Michal Kazior
2016-04-01 5:23 ` Ben Greear [this message]
2016-04-01 6:23 ` Michal Kazior
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=56FE05B7.80104@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 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.