From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1087717BB6; Mon, 27 May 2024 20:49:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716842979; cv=none; b=SKuMjZnj3uUWtPIgRzRo6KPUazTThoAIgzOZn03nbZLd8uEC8zIk17G61cqONvFAI24Dvkqk2FTcQ08tIiyFfqoXsi7zcY2fCY12c+Ys/ecn1MIKmYnK4x8FJ/CWRKfOLSRGn4O8Tl8xjVqIHAer+BwCVU4PEJSv1M+QQPFYbqQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716842979; c=relaxed/simple; bh=1TtjTvNzEXUXPyQiA9CkznwxyYdBavkdx3z+BpYnphk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=akcu/r0GFW8hYwHEHwBD9JxVGeUx0jWr6OM1p0UeX6hvIz2kivtBFGtDz4I9RgYJ9DALVAVcjAmexRnW+cZV1gGw2INMDZPrXqQeo8BVphcE+UtBqjzU5qfPyzVX3J4bGnRRfe2kGmuS5LGybeDyQmrY3A0w5tiqP1cK0AcDfl0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=k1hpGlmK; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=e8UZkJAo; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="k1hpGlmK"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="e8UZkJAo" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1716842976; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=d55mR4mLG4ZKoYbFrQEL2qAY0vQyIJjzMV7kq4W9+pk=; b=k1hpGlmKHicTsuKs9CRBMBCPmwXtEw2+TBhEYTsjHophh4cpDYx66q8raClDrQTDc/JybU vE2fYr3nkCvuJMWOxuo5ldisV4rbUSBlSLUfY6jNJelXW7Wmx/52pxoPte5RN1uw52LpZ1 ZkRUJK90Gg0TKv6X7GeQG6nI3h4IqyvttZs7ERbgJVolPMJtTrKlOMQQ6is+vkfJS7ocjd +uw63dHv53fGej4ZwvrsL9APk+jfIeS6lE7nec0E5CjmgNcUSIOtyXlW8MQmdwJmy+VcRn z47K8VhWLvCCAm325sayi48nXIIVgmC2omCORcAjPiqXoXSOF7FTKCCdd8F+ng== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1716842976; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=d55mR4mLG4ZKoYbFrQEL2qAY0vQyIJjzMV7kq4W9+pk=; b=e8UZkJAoOXa81pKWl4+SgcO6Q+tpFAkUGJatzGo92GnGsqOhHBlswxHHMw8xi8+7wr7+xd a4uwhkujyOF65SCA== To: Peter Schneider Cc: LKML , x86@kernel.org, stable@vger.kernel.org, regressions@lists.linux.dev Subject: Re: Kernel 6.9 regression: X86: Bogus messages from topology detection In-Reply-To: <877cffcs7h.ffs@tglx> References: <877cffcs7h.ffs@tglx> Date: Mon, 27 May 2024 22:49:35 +0200 Message-ID: <87jzjfaskg.ffs@tglx> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Mon, May 27 2024 at 15:14, Thomas Gleixner wrote: > On Mon, May 27 2024 at 09:29, Peter Schneider wrote: >> This is coming from an older server machine: 2-socket Ivy Bridge Xeon E5-2697 v2 (24C/48T) >> in an Asus Z9PE-D16/2L motherboard (Intel C-602A chipset); BIOS patched to the latest >> available from Asus. All memory slots occupied, so 256 GB RAM in total. >> >> From a "good boot", e.g. kernel 6.8.11, dmesg output looks like this: >> >> [ 1.823797] smpboot: x86: Booting SMP configuration: >> [ 1.823799] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 >> [ 1.827514] .... node #1, CPUs: #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23 >> [ 0.011462] smpboot: CPU 12 Converting physical 0 to logical die 1 >> >> [ 1.875532] .... node #0, CPUs: #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 >> [ 1.882453] .... node #1, CPUs: #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 >> [ 1.887532] MDS CPU bug present and SMT on, data leak possible. See >> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. >> [ 1.933640] smp: Brought up 2 nodes, 48 CPUs >> [ 1.933640] smpboot: Max logical packages: 2 >> [ 1.933640] smpboot: Total of 48 processors activated (259199.61 BogoMIPS) >> >> >> From a "bad" boot, e.g. kernel 6.9.2, dmesg output has these messages in it: >> >> [ 1.785937] smpboot: x86: Booting SMP configuration: >> [ 1.785939] .... node #0, CPUs: #4 >> [ 1.786215] .... node #1, CPUs: #12 #16 > > Yuck. That does not make any sense. > >> [ 1.797547] .... node #0, CPUs: #1 #2 #3 #5 #6 #7 #8 #9 #10 #11 >> [ 1.801858] .... node #1, CPUs: #13 #14 #15 #17 #18 #19 #20 #21 #22 #23 >> [ 1.804687] .... node #0, CPUs: #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 >> [ 1.810728] .... node #1, CPUs: #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 > >> However the machine boots, and except from these strange messages, I cannot detect any >> other abnormal behaviour. It is running ~15 QEMU/KVM virtual machines just fine. Because >> these messages look unusual and a bit scary though, I have bisected the issue, to be able >> to report it here. The first bad commit I found is this one: > > Ok. So as the machine is booting, can you please provide the output of: > > cat /sys/kernel/debug/x86/topo/cpus/* > > on the 6.9 kernel and > > cat /proc/cpuinfo > > for both 6.8 and 6.9? And once the output of: cpuid -r no matter on which kernel please? Thanks, tglx