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 in mlme.c, wireless-testing 2.6.39-wl + hacks
Date: Fri, 01 Jul 2011 10:10:46 +0200 [thread overview]
Message-ID: <1309507846.3888.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4E0CECDD.7040409@candelatech.com>
> Very little significant changes in this area, but I've a non-related
> proprietary module loaded, and patches to various other parts of the
> networking code.
>
> The full tree is here if you want to take a look, or I can send
> you a full unified diff:
>
> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux.wireless-testing-ct.ct/.git;a=summary
Fair enough, I don't see anything there that would impact this bug.
> Seems a tricky timing related bug, possibly we're only hitting it because
> we're testing on an older C3 processor system that is significantly slower
> than our normal test systems.
Hm. That seems odd. I didn't see anything that lacked locking either.
I think the detail that we need to investigate is what you said before:
> configured for in-kernel authentication,
> re-configure them for supplicant, let them associate, delete one of
> them.
but I don't see anything there either right now.
johannes
next prev parent reply other threads:[~2011-07-01 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:22 Crash in mlme.c, wireless-testing 2.6.39-wl + hacks Ben Greear
2011-06-30 21:30 ` Johannes Berg
2011-06-30 21:38 ` Ben Greear
2011-07-01 8:10 ` Johannes Berg [this message]
2011-07-01 13:00 ` 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=1309507846.3888.1.camel@jlt3.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 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).