On Wed, Jun 02, 2004 at 03:14:08PM +0200, Martin S. Weber wrote:
> On Wed, Jun 02, 2004 at 02:59:22PM +0200, Love wrote:
> > 
> > "Martin S. Weber" <Ephaeton@gmx.net> writes:
> > 
> > > Has anyone else seen this ? Know what it is ? How to stop it ? How to
> > > watch it to gain information helpful to debugging it ? Any hints anyone ?
> > 
> > Yes, I've seen this when playing movies with mplayer on my
> > 
> > $ dmesg | grep 'cpu[0-3]:.*Intel Xeon'
> > cpu0: Intel Xeon (686-class), 2392.40 MHz, id 0xf29
> > cpu1: Intel Xeon (686-class), 2392.30 MHz, id 0xf29
> > cpu2: Intel Xeon (686-class), 2392.29 MHz, id 0xf29
> > cpu3: Intel Xeon (686-class), 2392.29 MHz, id 0xf29
> > 
> > machine, booting a up kernel makes the problem go away.
> 
> up = Uni Processor I assume ? Hmm, kind of a suboptimal solution :)
> 

Argh. Half-optimal solution: Don't run ntpd.

Those thingies still occur without ntpd running, but FAR less
often. Nearly fine.

Regards,

-Martin