All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Heusel <christian@heusel.eu>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, stable@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: Kernel 6.9 regression: X86: Bogus messages from topology detection
Date: Fri, 31 May 2024 11:11:39 +0200	[thread overview]
Message-ID: <875xuu8hx0.ffs@tglx> (raw)
In-Reply-To: <87cyp28j0b.ffs@tglx>

On Fri, May 31 2024 at 10:48, Thomas Gleixner wrote:

> Christian!
>
> On Fri, May 31 2024 at 10:16, Christian Heusel wrote:
>>> One of the reporters in the Arch Bugtracker with an Intel Core i7-7700k
>>> has tested a modified version of this fix[0] with the static change
>>> reversed on top of the 6.9.2 stable kernel and reports that the patch
>>> does not fix the issue for them. I have attached their output for the
>>> patched (dmesg6.9.2-1.5.log) and nonpatched (dmesg6.9.2-1.log) kernel.
>>> 
>>> Should we also get them to test the mainline version or do you need any
>>> other debug output?
>
> Can I get:
>
>     - dmesg from 6.8.y kernel
>     - output of cpuid -r
>     - content of /sys/kernel/debug/x86/topo/cpus/* (on 6.9.y)
>
> please?

It seems there are two different issues here. The dmesg you provided is
from a i7-1255U, which is a hybrid CPU. The i7-7700k has 4 cores (8
threads) and there is not necessarily the same root cause.

Thanks,

        tglx

  reply	other threads:[~2024-05-31  9:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  7:29 Kernel 6.9 regression: X86: Bogus messages from topology detection Peter Schneider
2024-05-27 13:14 ` Thomas Gleixner
2024-05-27 20:49   ` Thomas Gleixner
2024-05-27 21:06   ` Peter Schneider
2024-05-27 21:15     ` Peter Schneider
2024-05-27 21:34       ` Christian Heusel
2024-05-30  8:30       ` Thomas Gleixner
2024-05-30 10:06         ` Peter Schneider
2024-05-30 13:35           ` Thomas Gleixner
2024-05-30 15:53             ` Thomas Gleixner
2024-05-30 16:24               ` Thomas Gleixner
2024-05-31  6:52                 ` Peter Schneider
2024-05-31  8:33                   ` Thomas Gleixner
2024-05-31  8:42                     ` Thomas Gleixner
2024-05-31  9:41                       ` Peter Schneider
2024-05-31 10:07                         ` Thomas Gleixner
2024-05-31 10:22                           ` Peter Schneider
2024-06-01  7:06                       ` Linux regression tracking (Thorsten Leemhuis)
2024-06-01  7:20                         ` Thomas Gleixner
2024-06-01  7:25                           ` Linux regression tracking (Thorsten Leemhuis)
2024-05-31  8:13                 ` Christian Heusel
2024-05-31  8:16                   ` Christian Heusel
2024-05-31  8:48                     ` Thomas Gleixner
2024-05-31  9:11                       ` Thomas Gleixner [this message]
2024-05-31 13:08                         ` Christian Heusel
2024-05-31 13:42                           ` Thomas Gleixner
2024-05-31 14:29                             ` Christian Heusel
2024-05-31 15:25                               ` Thomas Gleixner
2024-05-31 11:06                     ` Thomas Gleixner
2024-05-31 19:02 ` [tip: x86/urgent] x86/topology/intel: Unlock CPUID before evaluating anything tip-bot2 for 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=875xuu8hx0.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=christian@heusel.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pschneider1968@googlemail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --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.