From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Andrew Lutomirski <luto@mit.edu>,
Clemens Ladisch <clemens@ladisch.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
x86 <x86@kernel.org>
Subject: Re: [FALSE ALARM] Re: HPET (?) related hangs and breakage in 2.6.35,36
Date: Thu, 11 Nov 2010 12:06:42 +0100 [thread overview]
Message-ID: <20101111110642.GN8917@amd.com> (raw)
In-Reply-To: <20101110185031.GB13539@aftab>
On Wed, Nov 10, 2010 at 01:50:31PM -0500, Borislav Petkov wrote:
> On Wed, Nov 10, 2010 at 01:48:00PM -0500, Andrew Lutomirski wrote:
> > > Clocksource: tsc unstable (delta = -34355296774 ns)
> > > Switching: to clocksource hpet
> >
> > Please disregard -- this is a bug in nouveau (or drm) not hpet. I'll
> > send a bug report to the maintainers.
>
> Interesting! Joerg was complaining about similar symptoms with .36 today
> too.
The issue I have seen was on two boxes with 890FX chipset and Phenom II
X6 CPUs on a recent avi/master which was 2.6.36 + some kvm patches.
The problem was that the box became extremly sluggish and slow. I stated
dstat and it reported a lot of missed ticks. After some time the
clocksource tsc became unstable and the system became responsive again.
I have not yet investigated this further but can do any requested tests.
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2010-11-11 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:46 HPET (?) related hangs and breakage in 2.6.35,36 Andrew Lutomirski
2010-11-09 15:20 ` Clemens Ladisch
2010-11-09 15:38 ` Borislav Petkov
2010-11-09 17:44 ` Andrew Lutomirski
2010-11-09 18:01 ` Borislav Petkov
2010-11-09 21:29 ` Andrew Lutomirski
2010-11-10 18:48 ` [FALSE ALARM] " Andrew Lutomirski
2010-11-10 18:50 ` Borislav Petkov
2010-11-10 19:02 ` Andrew Lutomirski
2010-11-10 20:52 ` Thomas Gleixner
2010-11-10 20:56 ` Andrew Lutomirski
2010-11-10 20:58 ` Thomas Gleixner
2010-11-11 11:06 ` Roedel, Joerg [this message]
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=20101111110642.GN8917@amd.com \
--to=joerg.roedel@amd.com \
--cc=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.