From: Peter Schneider <pschneider1968@googlemail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
Date: Tue, 7 Jan 2025 01:36:00 +0100 [thread overview]
Message-ID: <896ab5a8-e86b-4176-812f-9111b44df90a@googlemail.com> (raw)
In-Reply-To: <20250106151150.585603565@linuxfoundation.org>
Am 06.01.2025 um 16:13 schrieb Greg Kroah-Hartman:
> This is the start of the stable review cycle for the 6.6.70 release.
> There are 222 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
6.6.70-rc1 builds, boots and seems to work on my 2-socket Ivy Bridge Xeon E5-2697 v2
server, but I see a scary looking dmesg warning, right after booting. As it is currently
running, I will try building 6.12.9-rc with it, and see how that goes. The dmesg warnings
I see look similar to that already reported by Miguel Ojeda.
[ 0.012910] ACPI: Reserving ERST table memory at [mem 0x7cca41c8-0x7cca43f7]
[ 0.012911] ACPI: Reserving HEST table memory at [mem 0x7cca43f8-0x7cca449f]
[ 0.012912] ACPI: Reserving BERT table memory at [mem 0x7cca44a0-0x7cca44cf]
[ 0.012938] ------------[ cut here ]------------
[ 0.012939] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[ 0.012948] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1324 memblock_set_node+0x10c/0x120
[ 0.012955] Modules linked in:
[ 0.012956] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1+ #1
[ 0.012959] Hardware name: ASUSTeK COMPUTER INC. Z9PE-D16 Series/Z9PE-D16 Series, BIOS
5601 06/11/2015
[ 0.012960] RIP: 0010:memblock_set_node+0x10c/0x120
[ 0.012962] Code: 0f 87 fe c0 ca 00 41 83 e4 01 74 0b 41 bc ff ff ff ff e9 50 ff ff ff
48 c7 c7 d0 28 fa 98 c6 05 58 0a 13 02 01 e8 14 86 ce ff <0f> 0b eb de e8 fb e3 d0 00 66
66 2e 0f 1f 84 00 00 00 00 00 90 90
[ 0.012965] RSP: 0000:ffffffff99803df8 EFLAGS: 00010046 ORIG_RAX: 0000000000000000
[ 0.012967] RAX: 0000000000000000 RBX: ffffffff999fc990 RCX: 0000000000000000
[ 0.012969] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 0.012970] RBP: ffffffff99803e28 R08: 0000000000000000 R09: 0000000000000000
[ 0.012971] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 0.012972] R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000008a000
[ 0.012973] FS: 0000000000000000(0000) GS:ffffffff99bb0000(0000) knlGS:0000000000000000
[ 0.012975] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.012976] CR2: ffff9e62eac01000 CR3: 0000000ae9e36000 CR4: 00000000000200f0
[ 0.012978] Call Trace:
[ 0.012979] <TASK>
[ 0.012981] ? show_regs+0x6d/0x80
[ 0.012987] ? __warn+0x89/0x160
[ 0.012990] ? memblock_set_node+0x10c/0x120
[ 0.012993] ? report_bug+0x17e/0x1b0
[ 0.012996] ? fixup_exception+0x27/0x370
[ 0.013000] ? early_fixup_exception+0x9b/0xf0
[ 0.013004] ? do_early_exception+0x25/0x80
[ 0.013008] ? early_idt_handler_common+0x2f/0x3a
[ 0.013013] ? memblock_set_node+0x10c/0x120
[ 0.013015] ? memblock_set_node+0x10c/0x120
[ 0.013017] ? __pfx_x86_acpi_numa_init+0x10/0x10
[ 0.013021] numa_init+0x82/0x570
[ 0.013025] x86_numa_init+0x1f/0x60
[ 0.013028] initmem_init+0xe/0x20
[ 0.013030] setup_arch+0x98b/0xea0
[ 0.013034] start_kernel+0x6c/0xb00
[ 0.013039] ? load_ucode_intel_bsp+0x3d/0x80
[ 0.013044] x86_64_start_reservations+0x18/0x30
[ 0.013046] x86_64_start_kernel+0xbf/0x110
[ 0.013049] secondary_startup_64_no_verify+0x18f/0x19b
[ 0.013056] </TASK>
[ 0.013057] ---[ end trace 0000000000000000 ]---
[ 0.013063] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[ 0.013065] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[ 0.013066] SRAT: PXM 0 -> APIC 0x02 -> Node 0
[ 0.013066] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
next prev parent reply other threads:[~2025-01-07 0:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:13 [PATCH 6.6 000/222] 6.6.70-rc1 review Greg Kroah-Hartman
2025-01-06 19:00 ` Naresh Kamboju
2025-01-09 11:39 ` Greg Kroah-Hartman
2025-01-06 20:04 ` Miguel Ojeda
2025-01-06 20:13 ` Florian Fainelli
2025-01-07 0:36 ` Peter Schneider [this message]
2025-01-07 1:16 ` Peter Schneider
2025-01-07 0:54 ` SeongJae Park
2025-01-07 7:03 ` Ron Economos
2025-01-07 10:24 ` Naresh Kamboju
2025-01-07 13:01 ` Mike Rapoport
2025-01-09 11:52 ` Greg Kroah-Hartman
2025-01-07 12:33 ` Mark Brown
2025-01-07 12:44 ` Jon Hunter
2025-01-07 21:20 ` [PATCH 6.6] " Hardik Garg
2025-01-07 23:15 ` [PATCH 6.6 000/222] " Shuah Khan
2025-01-08 12:27 ` Muhammad Usama Anjum
2025-01-08 14:12 ` Harshit Mogalapalli
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=896ab5a8-e86b-4176-812f-9111b44df90a@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox