From: Robin Jose <ackku.jose@gmail.com>
To: selvakumar nagendran <kernelselva@yahoo.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Printk output on console
Date: Mon, 27 Dec 2004 16:04:50 +0530 [thread overview]
Message-ID: <472a9f230412270234f8eab15@mail.gmail.com> (raw)
In-Reply-To: <20041221063222.26890.qmail@web60605.mail.yahoo.com>
You can refer to Rubini's book "Linux Device Drivers 2nd Edition". See
section "How messages gets logged" in Chapter 4, which explains in
detail how to use printk for debugging.
This book is now available online, under Oreilly's open book project
http://www.xml.com/ldd/chapter/book/ch04.html
Thanks,
Robin
On Mon, 20 Dec 2004 22:32:22 -0800 (PST), selvakumar nagendran
<kernelselva@yahoo.com> wrote:
> How can we see the output of printk calls in kernel
> source files in our console. Is there any special
> command or utility for it?
> How to view the output of printk on our console? What
> is the log level to be set for this?
>
> Thanks,
> selva
>
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-12-27 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 6:32 Printk output on console selvakumar nagendran
2004-12-27 10:34 ` Robin Jose [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-21 9:24 srinivas naga vutukuri
2004-12-21 9:43 ` selvakumar nagendran
2004-12-21 16:19 ` srinivas naga vutukuri
2004-12-23 11:04 ` Luca Falavigna
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=472a9f230412270234f8eab15@mail.gmail.com \
--to=ackku.jose@gmail.com \
--cc=kernelselva@yahoo.com \
--cc=linux-kernel@vger.kernel.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