From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759629AbYEHJBm (ORCPT ); Thu, 8 May 2008 05:01:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755065AbYEHJBc (ORCPT ); Thu, 8 May 2008 05:01:32 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:55188 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754845AbYEHJBb (ORCPT ); Thu, 8 May 2008 05:01:31 -0400 Date: Thu, 08 May 2008 02:01:24 -0700 (PDT) Message-Id: <20080508.020124.232275605.davem@davemloft.net> To: hinko.kocevar@cetrtapot.si Cc: linux-kernel@vger.kernel.org Subject: Re: time stamped printks From: David Miller In-Reply-To: <4822B919.5070707@cetrtapot.si> References: <4822B919.5070707@cetrtapot.si> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha.home.local id m48927EB025686 From: Hinko Kočevar 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. {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I