[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0803302236180.3219@apollo.tec.linutronix.de>
Date: Sun, 30 Mar 2008 22:37:29 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Chr <chunkeey@....de>
cc: "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with
2.6.25-rc7
On Sun, 30 Mar 2008, Chr wrote:
> On Sunday 30 March 2008 21:59:51 Thomas Gleixner wrote:
> > On Sun, 30 Mar 2008, Rafael J. Wysocki wrote:
> > > > So. take a look at stuck_task... that's best backtrace I could get...
> > > > (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> > > > and I hope the _logs_ are already enough.
> > > >
> > > > BTW: I noticed that the clock seems to jump forward and backwards.
> > > > Is this because the CPU-Cores aren't syncronized? (And why are they
> > > > out of sync?)
> >
> > The cores of those AMD beasts are never in sync. That's a chip feature :)
> >
> > Can you please provide the output of:
> > /sys/devices/system/clocksource/clocksource0/current_clocksource
> >
> > for both 2.6.24 and 2.6.25-rc7
> it's "hpet" (in both cases...)
Hmm. That should be stable. Which clock is jumping back and forth ?
The one in the logs or the system clock ?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists