From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
Date: Mon, 6 Jan 2025 21:04:53 +0100 [thread overview]
Message-ID: <20250106200453.1546073-1-ojeda@kernel.org> (raw)
In-Reply-To: <20250106151150.585603565@linuxfoundation.org>
On Mon, 06 Jan 2025 16:13:24 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> 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.
>
> Responses should be made by Wed, 08 Jan 2025 15:11:04 +0000.
> Anything received after that time might be too late.
I got (in both the two runs I did):
[ 0.022989] ------------[ cut here ]------------
[ 0.023006] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[ 0.023362] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1325 memblock_set_node+0xcf/0xe0
[ 0.023841] Modules linked in:
[ 0.023988] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.70-rc1-g5652330123c6 #1
[ 0.024062] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
[ 0.024156] RIP: 0010:memblock_set_node+0xcf/0xe0
[ 0.024215] Code: 2c 07 48 83 c0 18 48 ff c9 75 f0 48 89 df e8 78 01 00 00 31 c0 eb a8 c6 05 a7 24 a6 ff 01 48 c7 c7 1e 37 7b a7 e8 71 aa 07 fe <0f> 0b e9 67 ff ff ff e8 75 f3 e3 fe 0f 1f 44 00 00 55 41 57 41 56
[ 0.024361] RSP: 0000:ffffffffa7a03eb0 EFLAGS: 00000046 ORIG_RAX: 0000000000000000
[ 0.024386] RAX: 0000000000000000 RBX: ffffffffa82a2240 RCX: ffffffffa7a52068
[ 0.024397] RDX: ffffffffa7a03daf RSI: 0000000000000082 RDI: ffffffffa7a52060
[ 0.024407] RBP: 0000000000000000 R08: ffffffffa7a52240 R09: 4f4e5f414d554e20
[ 0.024417] R10: 2045444f4e5f4f4e R11: 0a64616574736e69 R12: 0000000000000040
[ 0.024428] R13: 0000000000000000 R14: ffffffffffffffff R15: 0000000000000000
[ 0.024465] FS: 0000000000000000(0000) GS:ffffffffa81a4000(0000) knlGS:0000000000000000
[ 0.024490] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.024502] CR2: ffff8c88c6001000 CR3: 0000000005628000 CR4: 00000000000000b0
[ 0.024585] Call Trace:
[ 0.024778] <TASK>
[ 0.024953] ? __warn+0xc3/0x1c0
[ 0.025012] ? memblock_set_node+0xcf/0xe0
[ 0.025024] ? report_bug+0x144/0x1e0
[ 0.025042] ? early_fixup_exception+0x46/0x90
[ 0.025051] ? early_idt_handler_common+0x2f/0x40
[ 0.025065] ? memblock_set_node+0xcf/0xe0
[ 0.025074] ? acpi_numa_processor_affinity_init+0x80/0x80
[ 0.025084] ? numa_init+0x5e/0x190
[ 0.025091] ? x86_numa_init+0x15/0x40
[ 0.025099] ? setup_arch+0x4a3/0x5a0
[ 0.025105] ? start_kernel+0x5a/0x3a0
[ 0.025115] ? x86_64_start_reservations+0x20/0x20
[ 0.025122] ? x86_64_start_kernel+0xa7/0xb0
[ 0.025128] ? secondary_startup_64_no_verify+0x179/0x17b
[ 0.025156] </TASK>
[ 0.025196] ---[ end trace 0000000000000000 ]---
I hope the helps!
Cheers,
Miguel
next prev parent reply other threads:[~2025-01-06 20:05 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 [this message]
2025-01-06 20:13 ` Florian Fainelli
2025-01-07 0:36 ` Peter Schneider
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=20250106200453.1546073-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--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