On 10/05/2010 10:16 AM, Luis R. Rodriguez wrote:
On Tue, Oct 5, 2010 at 10:00 AM, Ben Greear<greearb@xxxxxxxxxxxxxxx> wrote:
I started seeing this very soon after creating interfaces.
Can you be more specific how one can reproduce?
Enable SLUB debugging, DEBUG_PAGEALLOC (Debug page memory allocations),
lockdep, pre-empt.
Please try creating a bunch of stations on one ath9k phy, and
configure them to use WPA (we're using one supplicant per STA).
If you don't hit it within 2 minutes of creating STAs and starting
WPA, do let me know and I'll try to come up with something
more specific. But, at least for us, it seems extremely easy to
hit this issue.
The same kernel boots fine with no such errors on a system with ath5k, btw.
I wish there was a way to get slub debugging to print the backtrace for the
code that deleted the memory, but so far, I haven't found anything.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
