From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Dave Kleikamp <dave.kleikamp@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Harald Arnesen <harald@skogtun.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BISECTED]: Kernel panic (was: Linux 5.7-rc2)
Date: Wed, 22 Apr 2020 16:49:10 +0200 [thread overview]
Message-ID: <1587566950.9537.107.camel@suse.cz> (raw)
In-Reply-To: <5b9531e1-e0ae-cf5d-84f2-6bbb5c2cd089@oracle.com>
On Wed, 2020-04-22 at 09:12 -0500, Dave Kleikamp wrote:
> On 4/22/20 4:02 AM, Giovanni Gherdovich wrote:
> > Linus, Peter:
> >
> > the panic seen by Harald Arnesen (and Dave Kleikamp) is unrelated to
> > virtualization, and happens on all machines that have a CPU with less than 4
> > physical cores. It's a very serious (and very stupid) bug in the original
> > version of my code and is fixed by patch 2/4 "x86, sched: Account for CPUs
> > with less than 4 cores in freq. invariance" in the series
> >
> > https://lore.kernel.org/lkml/20200416054745.740-1-ggherdovich@suse.cz
> >
> > Harald, Dave:
> >
> > for peace of mind, can you please share the output of
> >
> > turbostat --interval 1 sleep 0
>
> This is a Lenovo T410.
>
> turbostat version 20.03.20 - Len Brown <lenb@kernel.org>
> CPUID(0): GenuineIntel 0xb CPUID levels; 0x80000008 xlevels; family:model:stepping 0x6:25:5 (6:37:5)
> [...]
> cpu0: MSR_TURBO_RATIO_LIMIT: 0x00001416
> 20 * 133.3 = 2666.6 MHz max turbo 2 active cores
> 22 * 133.3 = 2933.3 MHz max turbo 1 active cores
2 cores/ 4 threads, reported 4C turbo frequency of zero (i.e. bits 31:24
in MSR_TURBO_RATIO_LIMIT). This is consistent with all other occurrences
of this bug that have been reported.
Thanks Dave for your reply.
Giovanni
next prev parent reply other threads:[~2020-04-22 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 21:58 Linux 5.7-rc2 Linus Torvalds
[not found] ` <428bac87-b6dd-0867-c8f8-622cd606de3e@skogtun.org>
2020-04-21 19:03 ` [BISECTED]: Kernel panic (was: Linux 5.7-rc2) Linus Torvalds
2020-04-21 21:23 ` Peter Zijlstra
2020-04-21 21:30 ` Linus Torvalds
2020-04-21 21:41 ` Peter Zijlstra
2020-04-22 9:02 ` Giovanni Gherdovich
2020-04-22 9:37 ` Harald Arnesen
2020-04-22 10:22 ` Harald Arnesen
2020-04-22 11:01 ` Giovanni Gherdovich
2020-04-22 14:12 ` Dave Kleikamp
2020-04-22 14:49 ` Giovanni Gherdovich [this message]
2020-04-22 9:32 ` Harald Arnesen
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=1587566950.9537.107.camel@suse.cz \
--to=ggherdovich@suse.cz \
--cc=dave.kleikamp@oracle.com \
--cc=harald@skogtun.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.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.