On Wed, Dec 14, 2005 at 08:23:29AM +0100, Andi Kleen wrote:
> "Pallipadi, Venkatesh" <[email protected]> writes:
>
> > >[ 0.000000] time.c: Detected 2793.081 MHz processor.
> > >[ 27.449661] Console: colour VGA+ 80x25
> > >[ 28.484309] Dentry cache hash table entries: 131072 (order:
> > >8, 1048576 bytes)
> > >[ 28.506519] Inode-cache hash table entries: 65536 (order:
> > >7, 524288 bytes)
> > >[ 28.539543] Memory: 1014240k/1047080k available (2490k
> > >kernel code, 32456k reserved, 1664k data, 236k init)
> > >
> > >Note the jump in the time value..
> >
> > May be this is just the origin of time as far as kernel is concerned.
> > No?
>
> It is. Before that the timer interrupt doesn't run and jiffies won't
> increase.
Makes sense now. After sleeping on it, I think the stall I see
is caused by framebuffer console. I'll poke some more at it
this evening.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
