All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Rob Prowel <rprowel@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon bogus performance value causing RCU stalls?
Date: Thu, 27 Sep 2018 17:04:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1809271703530.8118@nanos.tec.linutronix.de> (raw)
In-Reply-To: <38932eb1-921f-55f7-10c8-358f9aae32b2@comcast.net>

On Wed, 26 Sep 2018, Rob Prowel wrote:
> On 09/23/18 17:19, Thomas Gleixner wrote:
> > > 
> > > Other than RTFM, or please build a bunch of kernels from source on your
> > > slow
> > > machine, using differing config options to help track down the cause of
> > > this...any thoughts about a solution?
> > 
> > Yes. This was decoded recently as an issue on 32bit due to a calculation
> > which is based on 'unsigned long' but requires to be 64bit wide.
> > 
> > It's in the 4.18.8 stable kernel, which should be available from your
> > fedora repo anytime soon.
> 
> OK.  Followup on AMD performance counter problem in 4.18.7
> 
> The Dell machine I was experiencing the problem on had a lot of ACPI
> issues.  One of the invalid ACPI entries was for a system timer.
> dmesg suggests that the broken timer was used in calculating the
> Athlon performance value.  So no, 32/64 bit math was not the issue.

Uff.

> ACPI=off in the kernel boot line fixed the issue completely. Machine
> still functions well as a file/web/postgresql dev server so it's all
> good.

Thanks for letting me know. I was about to dust of that old X2 I have
somewhere.

Thanks,

	tglx

      reply	other threads:[~2018-09-27 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-23 20:07 AMD Athlon bogus performance value causing RCU stalls? Rob Prowel
2018-09-23 21:19 ` Thomas Gleixner
2018-09-23 21:54   ` Rob Prowel
2018-09-24  6:23     ` Thomas Gleixner
2018-09-24 14:01       ` Rob Prowel
2018-09-26 23:38   ` Rob Prowel
2018-09-27 15:04     ` Thomas Gleixner [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=alpine.DEB.2.21.1809271703530.8118@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rprowel@comcast.net \
    /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.