From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:44402 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932989AbcFJMWt (ORCPT ); Fri, 10 Jun 2016 08:22:49 -0400 From: Kalle Valo To: Felix Fietkau Cc: Michal Kazior , "A. Benz" , linux-wireless , ath10k@lists.infradead.org Subject: Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05 References: Date: Fri, 10 Jun 2016 15:22:42 +0300 In-Reply-To: (Felix Fietkau's message of "Fri, 10 Jun 2016 10:55:36 +0200") Message-ID: <877fdxfd2l.fsf@kamboji.qca.qualcomm.com> (sfid-20160610_142330_525694_5EE6EC6C) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: Felix Fietkau writes: > On 2016-06-10 10:50, Michal Kazior wrote: >> On 9 June 2016 at 09:46, A. Benz 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; > > 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. > > FWIW, I've received several reports like this from different people on > different devices. They're also confirming that reverting to the > snapshot from January makes things stable again. Adding ath10k list to the loop. -- Kalle Valo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1bBLSv-0003F3-E1 for ath10k@lists.infradead.org; Fri, 10 Jun 2016 12:23:10 +0000 From: Kalle Valo Subject: Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05 References: Date: Fri, 10 Jun 2016 15:22:42 +0300 In-Reply-To: (Felix Fietkau's message of "Fri, 10 Jun 2016 10:55:36 +0200") Message-ID: <877fdxfd2l.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Felix Fietkau Cc: linux-wireless , Michal Kazior , ath10k@lists.infradead.org, "A. Benz" Felix Fietkau writes: > On 2016-06-10 10:50, Michal Kazior wrote: >> On 9 June 2016 at 09:46, A. Benz 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; > > 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. > > FWIW, I've received several reports like this from different people on > different devices. They're also confirming that reverting to the > snapshot from January makes things stable again. Adding ath10k list to the loop. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k