[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8e4e868-aafb-4df1-8d07-62126bfe2982@hardfalcon.net>
Date: Wed, 18 Jun 2025 15:32:03 +0200
From: Pascal Ernster <git@...dfalcon.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ronald Warsow <rwarsow@....de>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, conor@...nel.org, hargar@...rosoft.com,
broonie@...nel.org
Subject: Re: [PATCH 6.15 000/780] 6.15.3-rc1 review
[2025-06-18 07:42] Greg Kroah-Hartman:
> On Tue, Jun 17, 2025 at 08:27:03PM +0200, Ronald Warsow wrote:
>> Hi Greg
>>
>> Kernel panic here on x86_64 (RKL, Intel 11th Gen. CPU)
>>
>> all others kernels were okay. nothing was changed in my compile config.
>>
>> Tested-by: Ronald Warsow <rwarsow@....de>
>
> Any chance you can use 'git bisect' to find the offending commit?
>
> thanks,
>
> greg k-h
Hi, I've just come across the exact same bug on my x86_64 machines, but
unfortunately I won't have the time to start bisecting this before
tonight or tomorrow morning.
In any case, the culprit must be one of these patches:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/queue-6.15?id=9cc80b684b4f77d6c54fc0f1d34ecfe559838702&id2=f724d2960e671efa0e5bcb51327690f791923e4b
I had built a 6.15.2 kernel with the patch queue from tree id
f724d2960e671efa0e5bcb51327690f791923e4b a few days ago and that kernel
works flawlessly.
Today, I built a kernel with the patch queue from tree id
9cc80b684b4f77d6c54fc0f1d34ecfe559838702 and that kernel crashes when
trying to boot on x86_64 with the same error messages that Ronald
reported yesterday.
Regards
Pascal
Powered by blists - more mailing lists