From: Larry Finger <Larry.Finger@lwfinger.net>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Microcode SW errors for Intel 7260
Date: Sat, 05 Jul 2014 23:29:30 -0500 [thread overview]
Message-ID: <53B8D0AA.7020703@lwfinger.net> (raw)
In-Reply-To: <CANUX_P0wGNT-E0TnuMkrHV+LWyZAJjiaz+hEzYDVO9EWpJYzfA@mail.gmail.com>
On 07/05/2014 01:10 PM, Emmanuel Grumbach wrote:
>
> Please run with trace-cmd:
>
> I need -e iwlwifi -e iwlwifi_msg
>
Emmanuel,
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?
Larry
next prev parent reply other threads:[~2014-07-06 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 1:37 Microcode SW errors for Intel 7260 Larry Finger
2014-07-05 18:10 ` Emmanuel Grumbach
2014-07-06 4:29 ` Larry Finger [this message]
2014-07-06 4:56 ` Emmanuel Grumbach
2014-07-06 16:11 ` Larry Finger
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=53B8D0AA.7020703@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.