Re: memory clobber in rx path, maybe related to ath9k.

[Ben Greear <greearb@candelatech.com>]

On 10/05/2010 10:43 AM, Luis R. Rodriguez wrote:
> On Tue, Oct 5, 2010 at 10:38 AM, Ben Greear<greearb@candelatech.com>  wrote:
>> On 10/05/2010 10:36 AM, Luis R. Rodriguez wrote:
>>>
>>> On Tue, Oct 5, 2010 at 10:24 AM, Ben Greear<greearb@candelatech.com>
>>>   wrote:
>>>>
>>>> On 10/05/2010 10:16 AM, Luis R. Rodriguez wrote:
>>>>>
>>>>> On Tue, Oct 5, 2010 at 10:00 AM, Ben Greear<greearb@candelatech.com>
>>>>>   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.
>>>
>>> OK I just enabled PAGE_ALLOC thingy, it wasn't enabled on my kernel.
>>>
>>>> Please try creating a bunch of stations on one ath9k phy,
>>>
>>> How many?
>>
>> 130 is a nice round number :)
>
> Let me get this straight. You are creating 130 STAs with ath9k using
> iw, then running 150 instances of wpa_supplicant to connect to the
> same AP?

Well, 130 instances, yes :)

>> I'll try with a smaller number and see if I can hit it.
>
> Please do, you can use the log2n approach, should take you 7 tries,
> each by a power of 2, start at the middle of course.

Sure...will be a few minutes.

If it's any sane bug, then hopefully I can hit it with a small
number.

Out of curiosity, is there any particular number of STAs > 1 you guys
test with?

Thanks,
Ben

>
>    Luis


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com