* How to use pr_debug
@ 2014-02-26 19:35 m silverstri
2014-02-26 19:47 ` John de la Garza
2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
0 siblings, 2 replies; 5+ messages in thread
From: m silverstri @ 2014-02-26 19:35 UTC (permalink / raw)
To: kernelnewbies
I am using 'pr_debug()' to print debug statements. But I don't see
anything in my serial console. But when I use pr_info(), I see the
debug statements.
Do I need to do anything to see pr_debug()?
Thank you.
^ permalink raw reply [flat|nested] 5+ messages in thread
* How to use pr_debug
2014-02-26 19:35 How to use pr_debug m silverstri
@ 2014-02-26 19:47 ` John de la Garza
2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
1 sibling, 0 replies; 5+ messages in thread
From: John de la Garza @ 2014-02-26 19:47 UTC (permalink / raw)
To: kernelnewbies
On Wed, Feb 26, 2014 at 11:35:23AM -0800, m silverstri wrote:
> I am using 'pr_debug()' to print debug statements. But I don't see
> anything in my serial console. But when I use pr_info(), I see the
> debug statements.
> Do I need to do anything to see pr_debug()?
add this to the top of the file (before the includes)
#define DEBUG
on my system the output goes to /var/log/debug
^ permalink raw reply [flat|nested] 5+ messages in thread
* How to use pr_debug
2014-02-26 19:35 How to use pr_debug m silverstri
2014-02-26 19:47 ` John de la Garza
@ 2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
2014-02-27 0:28 ` 회신: " 김찬
2014-02-27 0:36 ` Kim Chan
1 sibling, 2 replies; 5+ messages in thread
From: Valdis.Kletnieks at vt.edu @ 2014-02-26 22:28 UTC (permalink / raw)
To: kernelnewbies
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
> I am using 'pr_debug()' to print debug statements. But I don't see
> anything in my serial console. But when I use pr_info(), I see the
> debug statements.
> Do I need to do anything to see pr_debug()?
You probably need a #define DEBUG. Also, check your console logging
level, make sure it's set to output debug-level to the console.
/proc/sys/kernel/printk and 'dmesg --console-level' are your friends.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140226/86818c70/attachment.bin
^ permalink raw reply [flat|nested] 5+ messages in thread
* 회신: How to use pr_debug
2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
@ 2014-02-27 0:28 ` 김찬
2014-02-27 0:36 ` Kim Chan
1 sibling, 0 replies; 5+ messages in thread
From: 김찬 @ 2014-02-27 0:28 UTC (permalink / raw)
To: kernelnewbies
Yes, if you add line below,
console_loglevel = 8; // 8 is debug level
The debug messages will also be printed to your console (serial port).
maybe you could revert it back after use.
Chan
________________________________
>From : "Valdis.Kletnieks at vt.edu" <Valdis.Kletnieks@vt.edu>
Sent : 2014-02-27 07:31:25 ( +09:00 )
To : m silverstri <michael.j.silverstri@gmail.com>
Cc : kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject : Re: How to use pr_debug
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
> I am using 'pr_debug()' to print debug statements. But I don't see
> anything in my serial console. But when I use pr_info(), I see the
> debug statements.
> Do I need to do anything to see pr_debug()?
You probably need a #define DEBUG. Also, check your console logging
level, make sure it's set to output debug-level to the console.
/proc/sys/kernel/printk and 'dmesg --console-level' are your friends.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140227/750df755/attachment.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* How to use pr_debug
2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
2014-02-27 0:28 ` 회신: " 김찬
@ 2014-02-27 0:36 ` Kim Chan
1 sibling, 0 replies; 5+ messages in thread
From: Kim Chan @ 2014-02-27 0:36 UTC (permalink / raw)
To: kernelnewbies
Yes, if you add a line below,
console_loglevel = 8; // 8 is debug level
The debug messages will also be printed to your console (serial port).
(Maybe this also goes to /var/log/debug ?)
you could revert it back after use.
Chan
________________________________
>From : "Valdis.Kletnieks at vt.edu" <Valdis.Kletnieks@vt.edu>
Sent : 2014-02-27 07:31:25 ( +09:00 )
To : m silverstri <michael.j.silverstri@gmail.com>
Cc : kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject : Re: How to use pr_debug
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
> I am using 'pr_debug()' to print debug statements. But I don't see
> anything in my serial console. But when I use pr_info(), I see the
> debug statements.
> Do I need to do anything to see pr_debug()?
You probably need a #define DEBUG. Also, check your console logging
level, make sure it's set to output debug-level to the console.
/proc/sys/kernel/printk and 'dmesg --console-level' are your friends.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140227/d47e7b63/attachment.html
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-02-27 0:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-26 19:35 How to use pr_debug m silverstri
2014-02-26 19:47 ` John de la Garza
2014-02-26 22:28 ` Valdis.Kletnieks at vt.edu
2014-02-27 0:28 ` 회신: " 김찬
2014-02-27 0:36 ` Kim Chan
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).