From: Johannes Berg <johannes@sipsolutions.net>
To: Kevin Cruz <skate_ops@yahoo.com>
Cc: Intel Wireless <ilw@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: How do I get mac80211 debugfs?
Date: Tue, 02 Oct 2012 13:20:19 +0200 [thread overview]
Message-ID: <1349176819.10698.16.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1349159890.10698.2.camel@jlt4.sipsolutions.net> (sfid-20121002_083802_746542_57596E7B)
On Tue, 2012-10-02 at 08:38 +0200, Johannes Berg wrote:
> Hi Kevin,
>
> > So I tried that but all I got back was:
> >
> > cat: /sys/kernel/debug/ieee80211/phy*/queues: No such file or directory
> >
> > so I'm assuming it's because I must not have mac80211 debugfs. So how
> > do I get it?
>
> First, make sure it's mounted, check "mount" and if not mount it:
>
> sudo mount -t debugfs debugfs /sys/kernel/debug
>
> If that doesn't work you don't have it enabled in the kernel config,
> check for CONFIG_DEBUG_FS. If you do have it, but not mac80211's files,
> check for CONFIG_MAC80211_DEBUGFS.
Oh also, if tracing already works, that'd be sufficient. No need to
enable debugfs just to confirm the issue, tracing would let me confirm
it as well. I just thought debugfs would let me confirm the issue first
before going to the trouble of enabling tracing.
johannes
next prev parent reply other threads:[~2012-10-02 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 20:25 iwlwifi can't connect to router after resuming from suspend Kevin Cruz
2012-09-28 12:19 ` Dan Carpenter
2012-09-28 22:15 ` Kevin Cruz
2012-09-29 7:25 ` Dan Carpenter
2012-10-01 14:44 ` Kevin Cruz
2012-10-01 15:09 ` Dan Carpenter
2012-10-01 16:42 ` Kevin Cruz
2012-10-01 19:31 ` Johannes Berg
2012-10-01 23:06 ` How do I get mac80211 debugfs? Kevin Cruz
2012-10-01 23:15 ` Kevin Cruz
2012-10-02 6:38 ` Johannes Berg
2012-10-02 11:20 ` Johannes Berg [this message]
2012-10-02 6:48 ` Rami Rosen
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=1349176819.10698.16.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=skate_ops@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome