linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: miaoqing@codeaurora.org (miaoqing at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: ath9k ARMv7 OOPS in v4.8.6, v4.2.8
Date: Thu, 24 Nov 2016 14:06:57 +0800	[thread overview]
Message-ID: <7aba95bdf0d562f3c9640d533c33e1ca@codeaurora.org> (raw)
In-Reply-To: <aaba8b1e30dd4c22be52e50befb202b2@aptaiexm02f.ap.qualcomm.com>


>> Okay, so i was 0, so running UP probably isn't going to help.  r7 is
>> also spec_priv->rfs_chan_spec_scan.
>> 
>> So, I think the question is... how is this NULL - and has it always
>> been NULL...
> 
> The problem appears to be that ath_cmn_process_fft() isn't called that
> often.  When it is, it crashes in ath_cmn_is_fft_buf_full() because
> spec_priv->rfs_chan_spec_scan is NULL when ATH9K_DEBUGFS=n. :-(
> 
> I'm running with ATH9K_DEBUGFS=y now.  If it goes a couple of days
> without crashing, I'll gin up a patch.
> 

A similar patch was applied to ath-next branch: 
https://patchwork.kernel.org/patch/9431163/.

--
Miaoqing

  parent reply	other threads:[~2016-11-24  6:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 19:15 ath9k ARMv7 OOPS in v4.8.6, v4.2.8 Jason Cooper
2016-11-23 19:26 ` Kalle Valo
2016-11-23 19:34   ` Jason Cooper
2016-11-23 19:51 ` Russell King - ARM Linux
2016-11-23 20:21   ` Jason Cooper
2016-11-23 20:59   ` Jason Cooper
2016-11-23 21:17     ` Russell King - ARM Linux
2016-11-23 21:40       ` Jason Cooper
     [not found]         ` <aaba8b1e30dd4c22be52e50befb202b2@aptaiexm02f.ap.qualcomm.com>
2016-11-24  6:06           ` miaoqing at codeaurora.org [this message]
2016-11-24 12:28             ` Jason Cooper
2016-11-24 12:33         ` Jason Cooper

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=7aba95bdf0d562f3c9640d533c33e1ca@codeaurora.org \
    --to=miaoqing@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).