From: Chr <chunkeey@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Sun, 30 Mar 2008 23:09:52 +0200
User-Agent: KMail/1.9.9
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org,
       Andi Kleen <andi-suse@firstfloor.org>,
       Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>
References: <200803302109.22219.chunkeey@web.de> <200803302218.52549.chunkeey@web.de> <alpine.LFD.1.10.0803302236180.3219@apollo.tec.linutronix.de>
In-Reply-To: <alpine.LFD.1.10.0803302236180.3219@apollo.tec.linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803302309.52493.chunkeey@web.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1149
Lines: 29

On Sunday 30 March 2008 22:37:29 Thomas Gleixner wrote:
> 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.
> > >
> > > 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 ?
The one in the logs... (but it's because of the TSC, right?)

Regards,
	Chr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/