Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 216686 - Boot logging incomplete
Summary: Boot logging incomplete
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2008-04-07 12:06 UTC by Fergus Allan
Modified: 2008-04-08 14:34 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Image of the boot process (modules.png,166.48 KB, image/png)
2008-04-07 21:33 UTC, Fergus Allan
/var/log/messages (bootlog,24.60 KB, text/plain)
2008-04-07 21:43 UTC, Fergus Allan
emerge info (emerge-info,3.35 KB, text/plain)
2008-04-07 21:44 UTC, Fergus Allan
/etc/conf.d/rc (rc,8.52 KB, text/plain)
2008-04-07 21:52 UTC, Fergus Allan

Note You need to log in before you can comment on or make changes to this bug.
Description Fergus Allan 2008-04-07 12:06:47 UTC
The boot process is logged to /var/log/messages

Everything is logged upto the point 

>>loading modules.  The individual modules may log information which is not displayed on the command line, and whilst the modules are listed on the command line, no entry is made in the /var/log/messages that a module has been loaded.

An entry should be made for each module that loading is attempted for.  If that module also logs information, so be it.
Comment 1 SpanKY gentoo-dev 2008-04-07 21:01:14 UTC
you've opted not to post a lot of information that every bug report should have

please consult the documentation:

in particular, you need to include `emerge --info`, and in this case your /etc/rc.conf as well as /etc/conf.d/rc should be posted as attachments
Comment 2 Fergus Allan 2008-04-07 21:33:41 UTC
Created attachment 149047 [details]
Image of the boot process
Comment 3 Fergus Allan 2008-04-07 21:43:28 UTC
Created attachment 149049 [details]

corresponds to the image
Comment 4 Fergus Allan 2008-04-07 21:44:25 UTC
Created attachment 149050 [details]
emerge info
Comment 5 Fergus Allan 2008-04-07 21:52:38 UTC
Created attachment 149052 [details]
Comment 6 SpanKY gentoo-dev 2008-04-07 22:02:48 UTC
ok, you have some misconceptions here that i'll clear up

/var/log/messages is for kernel and system logging only.  it is not for logging of anything that gets sent to the console while booting.

the module output that you've posted in the image is from the initrd, not baselayout or anything else.  it comes from the tiny image that genkernel created before the root filesystem even gets mounted.  we most likely wont be adding logging support for the initrd.  if we do, that is something to take up with the genkernel people, not baselayout.

logging of the console is done via the bootlog option (which ironically you havent turned on in your /etc/conf.d/rc).  but this is only for once the userspace init process has taken over (and thus baselayout/openrc).  those messages are also logged to a different place, not via the standard system log daemons.  there is also the problem that the dev file system and the system logger are not even available at the time things start.
Comment 7 Fergus Allan 2008-04-08 13:57:58 UTC

The initrd is logged in full.  This must be cached until the file system is available, or it has it's own write mechanism.  Either way, the genkernel people log the lot!  Even though the message were produced before system logger was available.

I noticed the /etc/conf.d/rc boot logging option after you requested it.  I havn't changed it so 'No' must be the default.  I'll have a play and turn it on, but I would have thought the default was YES.

'logged to a different place' - where?

Given that the modules that are not being listed are for the disk drives, would this still be in initrd and so this should be assigned to genkernel?

Let me check the boot logging option.  I will reassign accordingly.

Comment 8 SpanKY gentoo-dev 2008-04-08 14:34:20 UTC
the boot logging requires an external package ... that is why it is not enabled by default, nor does it list the filename (as the location is controlled by the other package, not baselayout).  it typically ends up as /var/log/boot.log iirc.

i dont know where the logging is stored as the log file you posted doesnt contain anything from genkernel.