From: Ben Gamari <bgamari.foss@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Another AR5008 hang
Date: Tue, 30 Mar 2010 06:14:40 -0700 (PDT) [thread overview]
Message-ID: <4bb1f940.47c2f10a.3469.609b@mx.google.com> (raw)
In-Reply-To: <1269928986.3927.5.camel@jlt3.sipsolutions.net>
On Tue, 30 Mar 2010 08:03:06 +0200, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Mon, 2010-03-29 at 10:26 -0700, Ben Gamari wrote:
> > New (2.6.33 and greater) kernels seem to result in a selective hang on my
> > machine directly only seconds after association with an 802.11N access point
> > (hosted with hostapd and another ar5008). I've included dmesg output for a
> > failure event, including back traces of hung processes. What ath9k.debug flags
> > would be most helpful for tracing this further?
>
> None, I would think, this seems to be a lockup between
> modprobe/stop_machine and some rtnl things, but I have no idea why that
> would happen. Do you have lockdep enabled? And if you do, please disable
> RCU lockdep as it typically gives you a warning and then turns off
> lockdep...
>
Thank you very much for your response. I do not currently have lockdep enabled,
but I'm building a new kernel as we speak. Thanks again,
- Ben
next prev parent reply other threads:[~2010-03-30 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 17:26 Another AR5008 hang Ben Gamari
2010-03-30 6:03 ` Johannes Berg
2010-03-30 13:14 ` Ben Gamari [this message]
2010-03-30 17:33 ` Ben Gamari
2010-04-06 18:08 ` Lockup inside of stop_machine() during modprobe aes (was Re: Another AR5008 hang) Ben Gamari
2010-04-06 18:08 ` Ben Gamari
2010-04-07 16:00 ` [ath9k-devel] [REGRESSION, 2.6.34-rc1] " Ben Gamari
2010-04-11 16:47 ` [REGRESSION] " Ben Gamari
2010-04-11 16:47 ` Ben Gamari
2010-04-15 21:22 ` Andrew Morton
2010-04-16 1:15 ` Ben Gamari
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=4bb1f940.47c2f10a.3469.609b@mx.google.com \
--to=bgamari.foss@gmail.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 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.