can you add more output to rc.sysinit. Especially after start_udev there are:
calls, which do not have any "Starting" - "[OK]" messages. This often confuses admins, and udev gets the bug report, especially if the kernel clutters the console with output from all the devices.
You even might consider adding a kernel command line switch to activate "set -x" in rc.sysinit. That would help with debugging booting issues.
(In reply to Harald Hoyer from comment #1)
> You even might consider adding a kernel command line switch to activate "set
> -x" in rc.sysinit. That would help with debugging booting issues.
Hmmm maybe we could use kernel "debug" option and log the output of all initscripts to kmsg :)
Ok, now seriously. Yes this is a good point and both of these things are easy to implement, so devel_ack+ fo 6.7.
My $0.02... FWIW, I really wish there was a convenient way to log *all* the output of *all* initscripts. Especially on remote systems where I don't have convenient access to the console, and doubly so when modesetting clears the scrollback buffer on the system so I can't see the last bits of output that typically didn't get logged anywhere.
So far, the only reliable solution I have is to use a serial console, and that's very difficult in many places.
So I will go with this patch:
You can now turn the debug output for everything that sources /etc/init.d/functions and the log output will go to kmsg.
I have chosen kmsg, because in early boot we can't write to any file (well maybe we could create a log file in /dev/shm), I don't like logging to stdout and with kmsg we will get a timestamp for free.
And second part https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel6-branch&id=6b8e2996a8eb36aa70873f3d3e1728b57cdae571
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.