linux-kernel - Re: time stamped printks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 08 May 2008 02:01:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hinko.kocevar@...rtapot.si
Cc:	linux-kernel@...r.kernel.org
Subject: Re: time stamped printks

From: Hinko Kočevar <hinko.kocevar@...rtapot.si>
Date: Thu, 08 May 2008 10:26:01 +0200

> Hi all,
> 
> I'm building latest GIT tree kernel for CRIS architecture. Right now I'm seeing 
> some strange values with printk stamps - at the start they are initialized to 0, 
> but quickly change to 42949372 - 0x028F5AFC.
> 
> Any thoughts to where to look for fix?

Very early in the boot, the timestamp counter fetching infrastructure
isn't setup yet.  So zero is reported for the timestamp.

So early on in the boot, it is often not even possible to setup
such things yet.  Because infrastructure they need for probing
etc. isn't even available yet.

This happens on basically every single Linux platform, there
isn't really anything to fix.