From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 warning in 3.9.0+ when unloading ath9k driver.
Date: Wed, 08 May 2013 11:45:32 -0700 [thread overview]
Message-ID: <518A9D4C.10502@candelatech.com> (raw)
In-Reply-To: <1368036259.8279.26.camel@jlt4.sipsolutions.net>
On 05/08/2013 11:04 AM, Johannes Berg wrote:
> On Wed, 2013-05-08 at 10:38 -0700, Ben Greear wrote:
>> I saw the WARN_ON_ONCE hit below on 3.9.0+ (+ hacks)
>> on a system with ath9k and ath9k_htc driver.
>
> Were you using VLANs?
No.
>
>> I'll be happy to add more debugging if someone has suggestions.
>
>> compat = cfg80211_chandef_compatible(
>> &sdata->vif.bss_conf.chandef, compat);
>> if (!compat)
>> break;
>> }
>> rcu_read_unlock();
>>
>> if (WARN_ON_ONCE(!compat))
>> return;
>
> Might be helpful to know whether chandef_compatible() returned NULL, or
> if the loop simply never found an interface with a matching pointer.
Ok, I'll add this.
Probably un-related, but the system usually crashes shortly after. With
memory debugging enabled, it appears to be relayfs and/or ath9k accessing
freed memory.
I'm digging into that one first on an un-hacked kernel..then will
get back to this warning...
Thanks,
Ben
>
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-05-08 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 17:38 mac80211 warning in 3.9.0+ when unloading ath9k driver Ben Greear
2013-05-08 18:04 ` Johannes Berg
2013-05-08 18:45 ` Ben Greear [this message]
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=518A9D4C.10502@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).