From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "sj-iport-5.cisco.com", Issuer "Cisco SSCA" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 805BBDE090 for ; Wed, 8 Apr 2009 04:29:51 +1000 (EST) Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n37II7JP019568 for ; Tue, 7 Apr 2009 11:18:07 -0700 Received: from sj-webmail-9.cisco.com (sj-webmail-9.cisco.com [171.71.183.158]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n37II7hS013626 for ; Tue, 7 Apr 2009 18:18:07 GMT Received: from sj-webmail-9.cisco.com (localhost.localdomain [127.0.0.1]) by sj-webmail-9.cisco.com (8.13.1/8.13.1) with ESMTP id n37II7Bx003084 for ; Tue, 7 Apr 2009 11:18:07 -0700 Received: from sj-webmail-9 (root@localhost) by sj-webmail-9.cisco.com (8.13.1/8.13.1/Submit) with ESMTP id n37II6L1003082 for ; Tue, 7 Apr 2009 11:18:07 -0700 Date: Tue, 7 Apr 2009 11:18:06 -0700 From: Subodh Nijsure To: Message-ID: <00ba01c9b7ad$32dae000$d151150a@cisco.com> Subject: Printk time stamp seems to be stuck. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BB_01C9B772.867C0800" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_NextPart_000_00BB_01C9B772.867C0800 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline I am running PPC kernel (2.6.26) with .config that contains CONFIG_PRINTK_TIME=y also I am booting kernel with parameter printk.time=1. I am also booting the kernel with option initcall_debug and I see following output after setup_vmstat() the printk timestamp feature stops working. i.e. after call to setup_vmstat all printk messages have same timestamp... [ 4.294855] calling pdflush_init+0x0/0x28() [ 4.294926] initcall pdflush_init+0x0/0x28() returned 0 after 0 msecs [ 4.294931] calling kswapd_init+0x0/0x2c() [ 4.294962] initcall kswapd_init+0x0/0x2c() returned 0 after 0 msecs [ 4.294966] calling setup_vmstat+0x0/0x74() [ 4.294966] initcall setup_vmstat+0x0/0x74() returned 0 after 0 msecs [ 4.294966] calling init_emergency_pool+0x0/0x84() [ 4.294966] highmem bounce pool size: 64 pages Has anybody else seen this or there is something odd with my kernel/board setup. /Subodh Nijsure ------=_NextPart_000_00BB_01C9B772.867C0800 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

I = am running=20 PPC kernel (2.6.26) with .config that contains CONFIG_PRINTK_TIME=3Dy also I a= m booting=20 kernel with parameter printk.time=3D1.

I am al= so booting=20 the kernel with option initcall_debug and I see following output after=20 setup_vmstat() the printk timestamp feature stops working.

i.e. af= ter call to=20 setup_vmstat all printk messages have same timestamp...

[    4.294855] calling&nb= sp;=20 pdflush_init+0x0/0x28()
[    4.294926] initcall=20 pdflush_init+0x0/0x28() returned 0 after 0 msecs
[   =20 4.294931] calling kswapd_init+0x0/0x2c()
[    4.2= 94962]=20 initcall kswapd_init+0x0/0x2c() returned 0 after 0 msecs
[  = =20 4.294966] calling setup_vmstat+0x0/0x74()
[    4.= 294966]=20 initcall setup_vmstat+0x0/0x74() returned 0 after 0 msecs
[  = ; =20 4.294966] calling init_emergency_pool+0x0/0x84()
[  &n= bsp;=20 4.294966] highmem bounce pool size: 64 pages

Has any= body else=20 seen this or there is something odd with my kernel/board=20 setup.

/Subodh= =20 Nijsure

------=_NextPart_000_00BB_01C9B772.867C0800--