From: Rob Prowel <rprowel@comcast.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon bogus performance value causing RCU stalls?
Date: Sun, 23 Sep 2018 17:54:22 -0400 [thread overview]
Message-ID: <de33e029-2be3-85de-4777-64dd8803fe1e@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1809232314460.1398@nanos.tec.linutronix.de>
On 09/23/18 17:19, Thomas Gleixner wrote:
>>
>> What is that value for the second Athlon core (seems extremely bogus), and
>> would/could that be the reason for the schedule_timeouts? This bogus value
>> also shows up in the bootup log when the second core is activated. Seems to
>> be AMD specific, as the values are correct on my Xeon machines.
>
> That's a 32bit machine I assume.
No. Actually it is a 64 bit AMD Athlon. Might need to check the math being a
problem in the 64 bit domain as well.
>
> 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.
>
Will check with the newer kernel when it's available but please do double check if this
problem might exist on 64 bit architectures as well...and of course I'm interested to
know whether it is the likely cuprit of my RCU problem.
next prev parent reply other threads:[~2018-09-23 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 20:07 Rob Prowel
2018-09-23 21:19 ` Thomas Gleixner
2018-09-23 21:54 ` Rob Prowel [this message]
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
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=de33e029-2be3-85de-4777-64dd8803fe1e@comcast.net \
--to=rprowel@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®