kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: listmail368@gmail.com (Orion Agali)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Displaying debug level printk messages in systemd
Date: Sun, 12 Jul 2015 01:42:50 +1000	[thread overview]
Message-ID: <55A1397A.1080809@gmail.com> (raw)
In-Reply-To: <20150711143619.GA3754@kroah.com>

On 07/12/2015 12:36 AM, Greg KH wrote:
> On Sat, Jul 11, 2015 at 11:06:30PM +1000, Orion Agali wrote:
>> I'm using Arch and I cannot figure out how to get printk debug messages to
>> display in journalctl.
>>
>> I tried the following:
>>   * Set LogLevel=debug in /etc/systemd/systemd.conf
>>   * Add kernel parameter 'debug' on boot
>>   * Setting loglevel=8 in /proc/sys/kernel/printk
>>   * dmsg -n 8
>>
>> Consider the following module:
>>
>> ----------
>> #include <linux/module.h>
>> #include <linux/kernel.h>
>> #include <linux/init.h>
>> static int __init task1_init(void)
>> {
>>     pr_notice("I am at level notice");
>>     pr_debug("I am at level debug.");
>>     return 0;
>> }
>> static void __exit task1_exit(void){}
>> module_init(task1_init);
>> module_exit(task1_exit);
>> ------------
>>
>> The notice level is printed but the debug level is not.
>> The debug message is not in dmesg or /dev/kmsg either
>>
>> The answer is probably straight forward, but I've hit a wall so I'm hoping
>> somebody here will be able to point me in the right direction
> Take a look at Documentation/dynamic-debug-howto.txt for how to get
> pr_debug() working properly for your module.
>
Great reference!

After reading and testing I realize I can
  * activate at compile time using -DDEBUG
  * use dyndbg in the module paramaters
  * add queries to <debugfs>/dynamic_debug/control
  * use dyndbg in the boot string

Thank you.

      reply	other threads:[~2015-07-11 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 13:06 Displaying debug level printk messages in systemd Orion Agali
2015-07-11 14:36 ` Greg KH
2015-07-11 15:42   ` Orion Agali [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=55A1397A.1080809@gmail.com \
    --to=listmail368@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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).