Re: Microcode SW errors for Intel 7260

[Larry Finger <Larry.Finger@lwfinger.net>]

On 07/05/2014 11:56 PM, Emmanuel Grumbach wrote:
> Hi Larry,
>
>> I am obviously missing something. Neither iwlwifi nor iwlwifi_msg are listed
>> in /sys/kernel/debug/tracing/available_events/, thus trace-cmd cannot enable
>> logging those events. The output is as follows:
>>
>> finger@linux-rcu3:~/wireless-testing> sudo trace-cmd record -e iwlwifi -e
>> iwlwifi_msg
>> /sys/kernel/debug/tracing/events/iwlwifi_msg/filter
>> /sys/kernel/debug/tracing/events/*/iwlwifi_msg/filter
>> trace-cmd: No such file or directory
>>    No events enabled with iwlwifi_msg
>> finger@linux-rcu3:~/wireless-testing>
>>
>>
>> I compared my .config with one for the openSUSE kernel 3.11.10, and the
>> kernel hacking section has the same settings.
>>
>> Do you have any suggestions?
>>
>
> Do you have CONFIG_IWLWIFI_DEVICE_TRACING enabled?
> If not, please enable it.
> Note that I don't really need iwlwifi_msg. iwlwifi should be enough.
>
> If you have CONFIG_IWLWIFI_DEBUG, then running with debug=0x00000800
> as a module parameter should be enough if that can save you a kernel
> compilation.

Apparently, I was caught by a bug in the kernel configuration system. Using 
'make xconfig', none of the entries under 'menu "Debugging Options"' in 
drivers/net/wireless/iwlwifi/Kconfig appear. Using 'make menuconfig' reveals 
them. I will report the problem to the appropriate persons - it does not seem to 
be a wireless bug.

The rebuilt kernel is running with the appropriate trace turned on. Now it only 
takes a retriggering of the original problem. I just hope that having debugging 
enabled does not affect the timing enough to prevent the errors. :)

Thanks,

Larry