From: "Robert P. J. Day" <rpjday@mindspring.com>
To: umesh@websurfer.com.np
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel message
Date: Sat, 2 Jun 2007 05:39:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706020538490.7922@localhost.localdomain> (raw)
In-Reply-To: <2631.63.219.2.2.1180775978.squirrel@mail.websurfer.com.np>
On Sat, 2 Jun 2007, umesh@websurfer.com.np wrote:
> Can anyone send me the documentation about dmesg message that how
> can we understand by it. I am searching good document which can
> explain each and every line of dmesg.
>
> umesh
this is really more of a kernel newbie question that belongs on the
newbie list but, if you really want to know the meaning of each line,
you might want to trace the code from kernel startup to see when each
of those lines is printed to see what they represent.
starting in init/main.c, find the routine "start_kernel" around line
500 and several lines in, you'll see:
...
printk(KERN_NOTICE);
printk(linux_banner);
...
(why these two printk's are broken over two lines is a mystery but ...
whatever.)
then if you go to init/version.c, you can verify that linux_banner
does indeed represent the normal first line in /var/log/dmesg, such
as:
Linux version 2.6.20-1.2948.fc6
(brewbuilder@hs20-bc1-7.build.redhat.com) (gcc version 4.1.1 20070105
(Red Hat 4.1.1-51)) #1 SMP Fri Apr 27 19:48:40 EDT 2007
at that point, start following the code to see where each line in
dmesg comes from.
rday
p.s. please use a better subject line than just "Kernel message".
that doesn't tell anyone what you're actually asking about.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
prev parent reply other threads:[~2007-06-02 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 9:19 umesh
2007-06-02 9:39 ` Robert P. J. Day [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=Pine.LNX.4.64.0706020538490.7922@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=umesh@websurfer.com.np \
/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®