From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1161013AbWAKHDD@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1161013AbWAKHDD (ORCPT <rfc822;willy@w.ods.org>);
	Wed, 11 Jan 2006 02:03:03 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161004AbWAKHDD
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 11 Jan 2006 02:03:03 -0500
Received: from 167.imtp.Ilyichevsk.Odessa.UA ([195.66.192.167]:49121 "HELO
	ilport.com.ua") by vger.kernel.org with SMTP id S1161055AbWAKHDA
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 11 Jan 2006 02:03:00 -0500
From: Denis Vlasenko <vda@ilport.com.ua>
To: Kalin KOZHUHAROV <kalin@thinrope.net>
Subject: Re: 2.6.15 and CONFIG_PRINTK_TIME
Date: Wed, 11 Jan 2006 09:01:57 +0200
User-Agent: KMail/1.8.2
Cc: linux-kernel@vger.kernel.org
References: <dq28uj$96q$1@sea.gmane.org>
In-Reply-To: <dq28uj$96q$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200601110901.57718.vda@ilport.com.ua>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.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