From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
x86@kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.13.6
Date: Sat, 8 Mar 2025 17:03:08 +0100 [thread overview]
Message-ID: <1b3ea3ce-7754-494c-a87b-0b70b2d25f99@web.de> (raw)
In-Reply-To: <2025030751-mongrel-unplug-83d8@gregkh>
Greg Kroah-Hartman wrote on 07/03/2025 18:52:
> I'm announcing the release of the 6.13.6 kernel.
>
> All users of the 6.13 kernel series must upgrade.
>
Thank you all for the new stable kernel. Unfortunately, the following messages
appear in dmesg on my system:
[ 0.000000] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.000000] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.000000] Linux version 6.13.6 (root@uruz) (gcc (Debian 14.2.0-17) 14.2.0,
GNU ld (GNU Binutils for Debian) 2.44) #1 SMP Fri Mar 7 19:40:58 CET 2025
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz root=PARTUUID=cb5df131-01
random.trust_cpu=on amd_pstate=active spec_rstack_overflow=off
...
[ 0.295153] smpboot: CPU0: AMD Ryzen 7 5700G with Radeon Graphics (family:
0x19, model: 0x50, stepping: 0x0)
[ 0.295308] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
[ 0.295386] ... version: 0
[ 0.295442] ... bit width: 48
[ 0.295499] ... generic registers: 6
[ 0.295555] ... value mask: 0000ffffffffffff
[ 0.295617] ... max period: 00007fffffffffff
[ 0.295678] ... fixed-purpose events: 0
[ 0.295735] ... event mask: 000000000000003f
[ 0.295838] signal: max sigframe size: 2976
[ 0.295921] rcu: Hierarchical SRCU implementation.
[ 0.295981] rcu: Max phase no-delay instances is 1000.
[ 0.296062] Timer migration: 2 hierarchy levels; 8 children per group; 2
crossnode level
[ 0.296192] smp: Bringing up secondary CPUs ...
[ 0.296286] smpboot: x86: Booting SMP configuration:
[ 0.296346] .... node #0, CPUs: #1 #2 #3 #4
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.296783] #5
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.296817] #6
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.296817] #7
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.310182] #8
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.310682] #9
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.310978] #10
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.311265] #11
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.311553] #12
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.311842] #13
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.312134] #14
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.312424] #15
[ 0.015631] microcode: You should not be seeing this. Please send the
following couple of lines to x86-<at>-kernel.org
[ 0.015631] microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011
[ 0.313521] Spectre V2 : Update user space SMT mitigation: STIBP always-on
[ 0.328817] smp: Brought up 1 node, 16 CPUs
[ 0.330152] smpboot: Total of 16 processors activated (121422.53 BogoMIPS)
[ 0.331117] Memory: 61612104K/62798720K available (10240K kernel code, 922K
rwdata, 2264K rodata, 1248K init, 1564K bss, 1173300K reserved, 0K cma-reserved)
Before this, I used stable kernel 6.13.4 which didn't show these lines.
Regards,
Jörg.
next prev parent reply other threads:[~2025-03-08 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 17:52 Linux 6.13.6 Greg Kroah-Hartman
2025-03-07 17:52 ` Greg Kroah-Hartman
2025-03-08 16:03 ` Jörg-Volker Peetz [this message]
2025-03-08 16:30 ` Borislav Petkov
2025-03-09 9:22 ` Greg Kroah-Hartman
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=1b3ea3ce-7754-494c-a87b-0b70b2d25f99@web.de \
--to=jvpeetz@web.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox