console and dmesg and boot.log?
- From: Tom Horsley <horsley1953@xxxxxxxxx>
- Date: Fri, 23 Dec 2011 08:01:03 -0500
Just for curosity, what the heck determines which dmesg
output shows up on the console during boot and which doesn't?
With rhgb turned off (so I can see what was just happening
if my system should freeze during boot), I see these lines
from dmesg zip past really early in the boot process:
[ 4.033526] sd 6:0:0:0: [sdc] No Caching mode page present
[ 4.033620] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 4.034208] sd 6:0:0:0: [sdc] No Caching mode page present
[ 4.034296] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 4.045027] sd 6:0:0:0: [sdc] No Caching mode page present
[ 4.045112] sd 6:0:0:0: [sdc] Assuming drive cache: write through
There are zillions of other lines of equally obscure dmesg lines
that don't show up on the console, so why these?
Even more annoying, these lines from dmesg don't appear in
the boot.log file, even though all the other lines that show
up on the console are in boot.log, so I guess the other
question is why they didn't make it to boot.log even though
they did appear on the console?
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
- Prev by Date: Re: Clean Installs are Remarkable
- Next by Date: Re: Was Fedora vs openSUSE now -exageration extraordinaire
- Previous by thread: SSH on Fedora 16
- Next by thread: Why updatedb doesn't traverse my external HD?
- Index(es):
Relevant Pages
|
