From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Crash related to scanning in 'ath' tree (3.12.0-rc5 + minor patches)
Date: Wed, 06 Nov 2013 20:03:44 +0100 [thread overview]
Message-ID: <1383764624.14307.46.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <527A9124.5000306@candelatech.com> (sfid-20131106_195744_890692_15B02E5D)
On Wed, 2013-11-06 at 10:57 -0800, Ben Greear wrote:
> This is from the 'ath' tree, which is 3.12.0-rc5. There are just a few printk patches
> to mac80211, and some moderate amount of patches to ath10k. I left the ath10k logs in
> this crash in case it provides some clue, but I think it may not be an ath10k problem
> as I have seen what I think is the same crash a few times before in 3.11+ with ath9k.
You couldn't have seen the same crash with ath9k - it's in
ieee80211_prep_hw_scan() which doesn't get called in that case.
johannes
next prev parent reply other threads:[~2013-11-06 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:57 Crash related to scanning in 'ath' tree (3.12.0-rc5 + minor patches) Ben Greear
2013-11-06 19:03 ` Johannes Berg [this message]
2013-11-06 19:09 ` Ben Greear
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=1383764624.14307.46.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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 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.