* Roman Zippel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Wed, 1 Aug 2007, Ingo Molnar wrote:
>
> > Andi's theory cannot be true either, Roman's debug info also shows this
> > /proc/<PID>/sched data:
> >
> > clock-delta : 95
> >
> > that means that sched_clock() is in high-res mode, the TSC is alive and
> > kicking and a sched_clock() call took 95 nanoseconds.
> >
> > Roman, could you please help us with this mystery?
>
> Actually, Andi is right. What I sent you was generated directly after
> boot, as I had to reboot for the right kernel, so a little later
> appeared this:
>
> Aug 1 14:54:30 spit kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> Aug 1 15:09:56 spit kernel: Clocksource tsc unstable (delta = 656747233 ns)
> Aug 1 15:09:56 spit kernel: Time: pit clocksource has been installed.
just to make sure, how does 'top' output of the l + "lt 3" testcase look
like now on your laptop? Yesterday it was this:
4544 roman 20 0 1796 520 432 S 32.1 0.4 0:21.08 lt
4545 roman 20 0 1796 344 256 R 32.1 0.3 0:21.07 lt
4546 roman 20 0 1796 344 256 R 31.7 0.3 0:21.07 lt
4547 roman 20 0 1532 272 216 R 3.3 0.2 0:01.94 l
and i'm still wondering how that output was possible.
Ingo
-
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/
