Re: 2.6.15 and CONFIG_PRINTK_TIME

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • 2.6.15 and CONFIG_PRINTK_TIME
    ... I remember there was some talk about resetting the time on printk during the ... boot to zero... ...
    (Linux-Kernel)
  • RE: SP2 amd AMD boot up failures
    ... it dont even boot up! ... > I do not know the error that makes it reboot. ... >> needs a reboot, and then never boots up again, keeps resetting on a black ... >> usb 2.0 belkin pci card ...
    (microsoft.public.windowsupdate)
  • Re: [patch] Re: 2.6.16-rc4-mm1 (bugs and lockups)
    ... This is enough for printk but not for the boot lockup. ... The attached patch is however enough. ... +static void boot_cpu_init ...
    (Linux-Kernel)
  • Re: Tech: Data East Star Trek 12V
    ... boot up and go into attract mode. ... sometimes it boots up great into attract mode ... at 5.02V whether it's booted and working or resetting. ...
    (rec.games.pinball)
  • Re: oops pauser. / boot_delayer
    ... >>> This one delays each printkduring boot by a variable time ... Another very common situation is a system which fails to boot due to ... failures to find the root filesystem. ... An option to pause briefly after each boot time printk would be very ...
    (Linux-Kernel)