mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chr <chunkeey@web.de>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Sun, 30 Mar 2008 21:59:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0803302156210.3219@apollo.tec.linutronix.de> (raw)
In-Reply-To: <200803302125.10817.rjw@sisk.pl>

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

Thanks,
	tglx

  reply	other threads:[~2008-03-30 20:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 19:09 Chr
2008-03-30 19:25 ` Rafael J. Wysocki
2008-03-30 19:59   ` Thomas Gleixner [this message]
2008-03-30 20:18     ` Chr
2008-03-30 20:37       ` Thomas Gleixner
2008-03-30 21:09         ` Chr
2008-03-30 21:36           ` Thomas Gleixner
2008-03-30 22:19             ` Chr
2008-03-31 12:56             ` Adrian Bunk
2008-03-31 13:23               ` Chr
2008-03-31 22:01             ` Chr
2008-03-31 23:14               ` Rafael J. Wysocki
2008-03-31 23:30                 ` Chr
2008-04-01 21:16                   ` Rafael J. Wysocki
2008-04-01 22:27                     ` Chr
2008-04-02 12:45                     ` Chr
2008-04-01 16:27               ` Thomas Gleixner
2008-04-01 18:57                 ` Chr
2008-04-01 22:29                 ` Chr
2008-04-02  7:08                   ` Thomas Gleixner
2008-04-02  9:34                     ` Chr
2008-03-31  7:10 ` Andi Kleen
2008-03-31 12:51   ` Chr
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-04  1:49   ` Chr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.10.0803302156210.3219@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=chunkeey@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome