Issues with latest kernel versions and Monitor mode

[Amato Carbonara]

I have captured the log file and placed them in Google drive.  Below
is the sharable link:

https://drive.google.com/open?id=0B80gG9wZvGF0OWhkZFYtV1ZxUmc

There are 2 logs

On Fri, Apr 29, 2016 at 1:10 AM, Michal Kazior <michal.kazior at tieto.com> wrote:
> On 28 April 2016 at 17:20, Amato Carbonara <acarbonara13 at gmail.com> wrote:
>> Hi Michal,
>>   Thank you for your help.  I think we are getting closer.  But I am
>> unsure what kernel logs are needed.  I have been referring to the
>> following link for my information:
>>
>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug
>>
>> My procedure:
>> 1. Set the debug mask:
>> echo 0xffffff3f > /sys/module/ath10k_core/parameters/debug_mask
>>
>> 2. Verify if the debug mask was set:
>> cat /sys/module/ath10k_core/parameters/debug_mask
>>
>> Value returned = 4294967103
>>
>> This is expected: 0xffffff3f is 4294967103 in decimal
>>
>>
>> 3. trace all log messages, including debug logs, into trace.dat file:
>> trace-cmd record -e ath10k_log*
>
> This is more generic:
>
> trace-cmd record -e ath10k
>
>
>>
>> 4. To read the trace.dat file:
>> trace-cmd report
>>
>>
>> When I go to sys/log/debug/tracing/events/ath10k, I see a lot of
>> directories and files.
>>
>> Which are needed to provided the required information?
>
> trace-cmd report > log.txt
>
> And then upload log.txt to some website (pastebin, mega.nz or whatever
> you fancy and doesn't require registering)
>
> Oh, and to be on the same page: you should start the trace-cmd record
> command after loading the driver but before you attempt to exercise
> monitor mode. Once the driver stops to respond control-c the trace-cmd
> record and do a report.
>
>
> Michal
>
>
> PS. Re-add the mailing list next time around you reply, please.
>
>
>>
>> On Thu, Apr 28, 2016 at 12:42 AM, Michal Kazior <michal.kazior at tieto.com> wrote:
>>> On 27 April 2016 at 16:12, Amato Carbonara <acarbonara13 at gmail.com> wrote:
>>>> I tried setting the debug_mask, but received the following error:
>>>>
>>>> # modprobe ath10k_core.ko debug_mask=0xffffff3f
>>>> modprobe: FATAL: Module ath10k_core.ko not found.
>>>>
>>>> I do not have the ath10k_core.ko installed.  Is there a way I can
>>>> install it so I can set the debug mode?
>>>
>>> You have to have it installed. Otherwise you wouldn't be able to run
>>> ath10k and I doubt you have it compiled in-kernel.
>>>
>>> modprobe expects module name without the .ko, so you should run:
>>>
>>>   modprobe ath10k_core debug_mask=0xffffff3f
>>>
>>>
>>> Michał