From: Grant Likely <grant.likely@secretlab.ca>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>, ppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: verbose kernel debug
Date: Tue, 29 Jul 2008 17:40:12 -0600 [thread overview]
Message-ID: <20080729234012.GA13708@secretlab.ca> (raw)
In-Reply-To: <9e4733910807291612l5e0567d6t376c2f96c5169333@mail.gmail.com>
On Tue, Jul 29, 2008 at 07:12:58PM -0400, Jon Smirl wrote:
> On 7/29/08, Scott Wood <scottwood@freescale.com> wrote:
> > Jon Smirl wrote:
> >
> > > I'm getting a "Badness at c01cc228 [verbose debug info unavailable]"
> > >
> > > How do I turn on verbose debug support? Or is it helpful? I see the
> > > option for x86 but I don't see how to do it for PowerPC.
> > >
> >
> > Under "Kernel Hacking", enable "Kernel debugging". This will expose a
> > "Verbose BUG() reporting" option.
> >
> > IMHO, this option shouldn't be buried in this manner; it's not just for
> > hacking kernels, but also for submitting decent bug reports.
>
> I looked in there. The option is not appearing for my MPC5200.
Hmmm, I can see it right now on a 5200 configured kernel. It's right
before "Compile the kernel with debug info" option.
It also helps to make sure CONFIG_EMBEDDED is disabled, or if it is
enabled that CONFIG_KALLSYMS is enabled.
g.
next prev parent reply other threads:[~2008-07-29 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:47 verbose kernel debug Jon Smirl
2008-07-29 23:05 ` Scott Wood
2008-07-29 23:12 ` Jon Smirl
2008-07-29 23:40 ` Grant Likely [this message]
2008-07-30 0:09 ` Jon Smirl
2008-07-30 0:17 ` Jon Smirl
2008-07-30 0:28 ` Jon Smirl
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=20080729234012.GA13708@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jonsmirl@gmail.com \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).