From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jens.axboe@oracle.com>,
prasanna@in.ibm.com, ananth@in.ibm.com,
anil.s.keshavamurthy@intel.com, davem@davemloft.net
Subject: Re: BUG? 2.6.24-rc*[-mm*] - debugfs subdirs missing on x86_64
Date: Fri, 18 Jan 2008 16:13:03 -0500 [thread overview]
Message-ID: <1200690783.8060.18.camel@localhost> (raw)
In-Reply-To: <20080118201926.GA24225@suse.de>
On Fri, 2008-01-18 at 12:19 -0800, Greg KH wrote:
> On Fri, Jan 18, 2008 at 03:12:33PM -0500, Lee Schermerhorn wrote:
> > I searched around the archives and web and didn't find any reports on
> > this [maybe just missed them?], so I MUST be doing something
> > wrong/stupid. My config [included] may be the culprit. Apologies for
> > the long cc list. I'm copying the kprobes and blktrace maintainers
> > [addresses from MAINTAINERS] to verify that they're NOT seeing this
> > problem.
> >
> > Problem: I see no sub-directories below /sys/kernel/debug on x86_64
>
> Have you mounted debugfs on /sys/kernel/debug? Try:
> mount -t debugfs none /sys/kernel/debug
> as root and see if the files are present or not.
D'oh! [or something stronger] I KNEW it was something stupid. I
thought it strange that there were no reports of something this glaring.
That's why I took so long investigating before I finally asked.
I've used debugfs+mmtrace on x86_64 in the past and I've had the debugfs
mount in my test systems' fstab for so long that I don't even think
about it [obviously!]. I moved to a different test system a couple of
months ago and apparently brought over an old fstab patch.
Sorry for the noise [he says sheepishly].
Lee
prev parent reply other threads:[~2008-01-18 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 20:12 BUG? 2.6.24-rc*[-mm*] - debugfs subdirs missing on x86_64 Lee Schermerhorn
2008-01-18 20:19 ` Greg KH
2008-01-18 21:13 ` Lee Schermerhorn [this message]
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=1200690783.8060.18.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.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