All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Kazior <michal.kazior@tieto.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: "A. Benz" <ash.benz@bk.ru>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05
Date: Fri, 10 Jun 2016 11:10:43 +0200	[thread overview]
Message-ID: <CA+BoTQ=xWetiO9GK_staz=M=rAT4_tA5khedqn206mjyRHsmQg@mail.gmail.com> (raw)
In-Reply-To: <d836933e-ddbb-d10c-0715-6bce4396fd41@nbd.name>

On 10 June 2016 at 10:55, Felix Fietkau <nbd@nbd.name> wrote:
> On 2016-06-10 10:50, Michal Kazior wrote:
>> On 9 June 2016 at 09:46, A. Benz <ash.benz@bk.ru> wrote:
>>> Dear All,
>>>
>>> I am using LEDE on my IPQ806x (QCA9980) system (Archer C2600).
>>> With compat-wireless-2016-05-12, I observed traces attached below.
>>> The router is unstable and eventually reboots by itself (randomly).
>>>
>>> Upon reverting to compat-wireless-2016-01, the issue disappears. Nothing
>>> else is changed (software-wise or hardware).
>>> This was confirmed with other users.
>>>
>>> A new compile with the fixes below:
>>> https://git.lede-project.org/?p=lede/nbd/staging.git;a=commit;h=858e26f3c0fc11231f25497cbb2ddca1e5f101e0
>>>
>>> Did not solve the problem.
>>>
>>> Please let me know if I need to provide any further information.
>>>
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 0 PID: 558 at
>>> compat-wireless-2016-05-12/net/mac80211/rx.c:4068
>>> ieee80211_rx_napi+0x8c/0x8a4 [mac80211]()
>>
>> Can you post what is at rx.c line 4068 (and +/- 3 lines), please?
> It's early in ieee80211_rx_napi:
>
>     sband = local->hw.wiphy->bands[status->band];
>     if (WARN_ON(!sband))
>         goto drop;

Thanks.


> I could not easily find a scenario under which status->band would not be
> set properly by the driver, so my guess is there is some nasty memory
> corruption going on.

Hmm.. could it be related to ath10k not fulfilling (some) NAPI's
locking requirements and thus ending up with, e.g. linked-list mayhem?


Michał

  reply	other threads:[~2016-06-10  9:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  7:46 ath10k/QCA9980 - Issues introduced in wireless testing 2016-05 A. Benz
2016-06-10  8:50 ` Michal Kazior
2016-06-10  8:55   ` Felix Fietkau
2016-06-10  9:10     ` Michal Kazior [this message]
2016-06-10  9:20       ` Johannes Berg
2016-06-10 12:22     ` Kalle Valo
2016-06-10 12:22       ` Kalle Valo
2016-06-10 12:52       ` Ben Greear
2016-06-10 12:52         ` Ben Greear
2016-06-10 12:57         ` Felix Fietkau
2016-06-10 12:57           ` Felix Fietkau
2016-06-10 13:16           ` Ben Greear
2016-06-10 13:16             ` Ben Greear
2016-07-15 11:49             ` Nagarajan, Ashok Raj
2016-07-15 11:49               ` Nagarajan, Ashok Raj

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='CA+BoTQ=xWetiO9GK_staz=M=rAT4_tA5khedqn206mjyRHsmQg@mail.gmail.com' \
    --to=michal.kazior@tieto.com \
    --cc=ash.benz@bk.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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.