Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:37023 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751782AbcFJJVA (ORCPT ); Fri, 10 Jun 2016 05:21:00 -0400 Message-ID: <1465550453.2308.0.camel@sipsolutions.net> (sfid-20160610_112104_431024_738C7858) Subject: Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05 From: Johannes Berg To: Michal Kazior , Felix Fietkau Cc: "A. Benz" , linux-wireless Date: Fri, 10 Jun 2016 11:20:53 +0200 In-Reply-To: (sfid-20160610_111051_322091_FF8AB05C) References: (sfid-20160610_111051_322091_FF8AB05C) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, 2016-06-10 at 11:10 +0200, Michal Kazior wrote: >  > Hmm.. could it be related to ath10k not fulfilling (some) NAPI's > locking requirements and thus ending up with, e.g. linked-list > mayhem? > Shoudln't matter since ath10k doesn't actually use rx_napi()? johannes