From: Salvatore Bonaccorso <carnil@debian.org>
To: Pavel Machek <pavel@nabladev.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, 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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 7.2 000/242] 7.2.13-rc1 review
Date: Fri, 23 Oct 2026 23:34:35 +0200 [thread overview]
Message-ID: <atvS68GhCvmAphrQ@eldamar.lan> (raw)
In-Reply-To: <atvHKoRHHjKV4l8A@duo.ucw.cz>
Hi,
On Fri, Oct 23, 2026 at 10:44:26PM +0200, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 7.2.13 release.
> > There are 242 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.
>
> Either something went very wrong with our testing, or this fails on
> all our targets. 6.18.59-rc1 does not seem to have those widespread
> failures.
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2982452623
>
> Example failure is:
>
> I'll look some more to try to figure out what is going on there.
>
> Best regards,
>
> Pavel
>
>
> [ 1.238864] Yama: becoming mindful.
> L426[ 1.238864] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
> L427[ 1.238864] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
> L428[ 1.238864] VFS: Finished mounting rootfs on nullfs
> L431[ 1.238864] BUG: kernel NULL pointer dereference, address: 000000000000002c
> L436[ 1.238864] #PF: supervisor write access in kernel mode
> L437[ 1.238864] #PF: error_code(0x0002) - not-present page
> L438[ 1.238864] PGD 0 P4D 0
> L441[ 1.238864] Oops: Oops: 0002 [#1] SMP PTI
> L446[ 1.238864] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G S 7.2.13-rc1+ #1 PREEMPT(lazy)
> L447[ 1.238864] Tainted: [S]=CPU_OUT_OF_SPEC
> L448[ 1.238864] Hardware name: SIEMENS AG SIMATIC IPC227E/A5E42630598, BIOS V20.01.11 03/15/2018
> L449[ 1.238864] RIP: 0010:rest_init+0x33/0xd0
> L450[ 1.238864] Code: 34 ff ba 00 02 00 00 31 f6 48 c7 c7 70 a2 e6 b2 e8 52 d3 28 ff 89 c3 e8 bb 2d 34 ff 89 df 48 c7 c6 80 db 85 b3 e8 9d d7 2b ff <81> 48 2c 00 00 00 04 65 8b 15 63 6e 45 01 48 89 c7 89 d0 c1 ea 06
> L451[ 1.238864] RSP: 0000:ffffffffb3803ee0 EFLAGS: 00010246
> L452[ 1.238864] RAX: 0000000000000000 RBX: 00000000ffffffea RCX: 0000000000000000
> L453[ 1.238864] RDX: 0000000000000000 RSI: ffffffffffffffea RDI: ffffffffffffffea
> L454[ 1.238864] RBP: ffff8cf23ffed080 R08: ffffffffb385db88 R09: ffffffffb385db80
> L455[ 1.238864] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8cf23ffed0ab
> L456[ 1.238864] R13: 0000000000000000 R14: ffffffffb380c040 R15: 00000000b43e8000
> L457[ 1.238864] FS: 0000000000000000(0000) GS:ffff8cf287953000(0000) knlGS:0000000000000000
> L458[ 1.238864] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> L459[ 1.238864] CR2: 000000000000002c CR3: 000000000d630000 CR4: 00000000001006f0
> L460[ 1.238864] Call Trace:
> L461[ 1.238864] <TASK>
> L462[ 1.238864] start_kernel+0x7a2/0x7b0
> L463[ 1.238864] x86_64_start_reservations+0x24/0x30
> L464[ 1.238864] x86_64_start_kernel+0xcd/0xd0
> L465[ 1.238864] common_startup_64+0x13e/0x158
> L466[ 1.238864] </TASK>
> L467[ 1.238864] Modules linked in:
> L468[ 1.238864] CR2: 000000000000002c
> L469[ 1.238864] ---[ end trace 0000000000000000 ]---
> L470[ 1.238864] RIP: 0010:rest_init+0x33/0xd0
Same here indepently, but not yet bisected.
Regards,
Salvatore
next prev parent reply other threads:[~2026-10-23 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:37 Greg Kroah-Hartman
2026-10-23 20:44 ` Pavel Machek
2026-10-23 21:34 ` Salvatore Bonaccorso [this message]
2026-10-23 22:44 ` Florian Fainelli
2026-10-23 23:42 ` Barry K. Nathan
2026-10-24 1:21 ` Peter Schneider
2026-10-24 5:32 ` 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=atvS68GhCvmAphrQ@eldamar.lan \
--to=carnil@debian.org \
--cc=achill@achill.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@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--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
all inboxes | Powered by JetHome®