From: Denis Vlasenko <vda@ilport.com.ua>
To: Kalin KOZHUHAROV <kalin@thinrope.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15 and CONFIG_PRINTK_TIME
Date: Wed, 11 Jan 2006 09:01:57 +0200 [thread overview]
Message-ID: <200601110901.57718.vda@ilport.com.ua> (raw)
In-Reply-To: <dq28uj$96q$1@sea.gmane.org>
On Wednesday 11 January 2006 08:34, Kalin KOZHUHAROV wrote:
> I remember there was some talk about resetting the time on printk during the
> boot to zero... Is that gone for 2.6.15?
>
> I recently turned CONFIG_PRINTK_TIME on two machines and they identically
> print things like this:
>
> [17179569.184000] Linux version 2.6.15-K01_PIII_laptop (kalin@ss) (gcc
> version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #2 PREEMPT Wed
> Jan 11 09:56:21 JST 2006
> [17179569.184000] BIOS-provided physical RAM map:
> [17179569.184000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> [17179569.184000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> [17179569.184000] BIOS-e820: 00000000000e0000 - 00000000000eee00 (reserved)
> [17179569.184000] BIOS-e820: 00000000000eee00 - 00000000000ef000 (ACPI NVS)
> [17179569.184000] BIOS-e820: 00000000000ef000 - 0000000000100000 (reserved)
>
> ...
>
> [17179591.768000] ReiserFS: hda5: checking transaction log (hda5)
> [17179591.836000] ReiserFS: hda5: Using r5 hash to sort names
> [17179605.172000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
>
> That is about t0 + 200 days :-) No, the box is not THAT slow :-D
>
> Now, on two different boxen, the initial time is the same: 17179569.184000
>
> What is this number?
I guess time sybsystem is not up until that line.
--
vda
next prev parent reply other threads:[~2006-01-11 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 6:34 2.6.15 and CONFIG_PRINTK_TIME Kalin KOZHUHAROV
2006-01-11 7:01 ` Denis Vlasenko [this message]
2006-01-11 7:21 ` Kalin KOZHUHAROV
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=200601110901.57718.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=kalin@thinrope.net \
--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