<div dir="ltr"><br><div class="gmail_extra">Hi Mr.Valdis</div><div class="gmail_extra">as you rightly mentioned,cat /proc/kmsg is showing the time stamps, according to that it is 0ms only.</div><div class="gmail_extra" style>
But when you see the same with UART there is 2sec delay in showing the next log. i caught this while i m observing the UART logs with "Terminaliranicca". </div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>
Since i m early in the mm_init, i cant use watchdog to detect it, hrtimers i cant use..i am really thinking how to analyse this delay..</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Thanks</div>
<div class="gmail_extra" style>Sandeep</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 10:40 AM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On Tue, 22 Jan 2013 10:29:05 -0800, sandeep kumar said:<br>
<br>
> I am seeing this problem at the very early in the start_kernel--><br>
> mm_init--> free_highpages, at that time nothing is up and kernel is running<br>
> in single thread.<br>
<br>
</div>If you build a kernel with printk timestamps, you'll see that they all<br>
come out like this:<br>
<br>
[ 0.000000] Initializing cgroup subsys cpuset<br>
[ 0.000000] Initializing cgroup subsys cpu<br>
[ 0.000000] Linux version 3.8.0-rc3-next-20130117-dirty (<a href="mailto:valdis@turing-police.cc.vt.edu">valdis@turing-police.cc.vt.edu</a>) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-9) (GCC) ) #49 SMP PREEMPT Thu Jan 17 13:25:28 EST 2013<br>
[ 0.000000] Command line: ro root=/dev/mapper/vg_blackice-root log_buf_len=2M vga=893 loglevel=4 threadirqs intel_iommu=off LANG=en_US.UTF-8<br>
[ 0.000000] KERNEL supported cpus:<br>
[ 0.000000] Intel GenuineIntel<br>
[ 0.000000] e820: BIOS-provided physical RAM map:<br>
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bbff] usable<br>
[ 0.000000] BIOS-e820: [mem 0x000000000009bc00-0x000000000009ffff] reserved<br>
(100 or so more lines with same timestamp)<br>
(now we finish memory init)<br>
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)<br>
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)<br>
[ 0.000000] __ex_table already sorted, skipping sort<br>
[ 0.000000] xsave: enabled xstate_bv 0x3, cntxt size 0x240<br>
[ 0.000000] Memory: 4015936k/4718592k available (6266k kernel code, 536744k absent, 165912k reserved, 7260k data, 576k init)<br>
(more lines skipped)<br>
[ 0.000000] memory used by lock dependency info: 5855 kB<br>
[ 0.000000] per task-struct memory footprint: 1920 bytes<br>
[ 0.000000] hpet clockevent registered<br>
[ 0.000000] tsc: Fast TSC calibration using PIT<br>
[ 0.000000] tsc: Detected 2527.012 MHz processor<br>
[ 0.001004] Calibrating delay loop (skipped), value calculated using timer frequency.. 5054.02 BogoMIPS (lpj=2527012)<br>
[ 0.001009] pid_max: default: 32768 minimum: 301<br>
[ 0.001100] Security Framework initialized<br>
<br>
It probably simply be that your code is running before the clock is started<br>
by the kernel.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>With regards,<br>Sandeep Kumar Anantapalli,<br>
</div></div>