* Printk time stamp seems to be stuck.
@ 2009-04-07 18:18 Subodh Nijsure
0 siblings, 0 replies; only message in thread
From: Subodh Nijsure @ 2009-04-07 18:18 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2237 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-04-07 18:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-07 18:18 Printk time stamp seems to be stuck Subodh Nijsure
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).