From: Borislav Petkov <petkovbb@googlemail.com>
To: reg@dwf.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to see kernel pr_err error messages.
Date: Sat, 27 Feb 2010 13:06:30 +0100 [thread overview]
Message-ID: <20100227120630.GA18061@a1.tnic> (raw)
In-Reply-To: <201002271011.o1RAB3in007369@deneb.dwf.com>
From: reg@dwf.com
Date: Sat, Feb 27, 2010 at 03:11:03AM -0700
> Im looking at some kernel code, and there are 'pr_err' error messages in
> it that would help me discover my problem.
>
> However I dont see them printing anywhere.
>
> What do I have to do to see these error messages?
Take a look at 'ignore_loglevel' and 'loglevel' kernel parameters in
<Documentation/kernel-parameters.txt> depending on what exactly you want
to achieve.
> A search with GOOGLE and a grep of the code wasnt too useful, but
> it seems possible that I need to set
>
> #define CONFIG_DEBUG
>
> Is that true? I see a lot of <something>_DEBUGs in the .config file
> but no simple CONFIG_DEBUG that is commented out.
I think this is referring to pr_debug() calls. Those get called when you
add
#define DEBUG
to the file containing them. Otherwise they're optimized away.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2010-02-27 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 10:11 reg
2010-02-27 12:06 ` Borislav Petkov [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=20100227120630.GA18061@a1.tnic \
--to=petkovbb@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@dwf.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
all inboxes | Powered by JetHome®