On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
> I have the following panic after upgrading my kernel. Working version is
> 6.1.10, so something has happened after that. 6.2.x kernels crash in the
> same way. Attached config.
Please send dmesg from 6.1.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
On 27/03/2023 08:49, Borislav Petkov wrote:
> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>> I have the following panic after upgrading my kernel. Working version is
>> 6.1.10, so something has happened after that. 6.2.x kernels crash in the
>> same way. Attached config.
> Please send dmesg from 6.1.
>
> Thx.
>
Of course - attached.
Thanks
David
On Mon, Mar 27 2023 at 09:13, David R. wrote:
> On 27/03/2023 08:49, Borislav Petkov wrote:
>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>> I have the following panic after upgrading my kernel. Working version is
>>> 6.1.10, so something has happened after that.
IIUC 6.1.11 is failing, right?
>>> 6.2.x kernels crash in the same way. Attached config.
>>>
>> Please send dmesg from 6.1.
>>
> Of course - attached.
Thanks for the info.
tglx
On 27/03/2023 14:49, Thomas Gleixner wrote:
> On Mon, Mar 27 2023 at 09:13, David R. wrote:
>> On 27/03/2023 08:49, Borislav Petkov wrote:
>>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>>> I have the following panic after upgrading my kernel. Working version is
>>>> 6.1.10, so something has happened after that.
> IIUC 6.1.11 is failing, right?
>
>>>> 6.2.x kernels crash in the same way. Attached config.
>>>>
>>> Please send dmesg from 6.1.
>>>
>> Of course - attached.
> Thanks for the info.
>
> tglx
Not tried that version. Will build & report back.
On 27/03/2023 14:49, Thomas Gleixner wrote:
> On Mon, Mar 27 2023 at 09:13, David R. wrote:
>> On 27/03/2023 08:49, Borislav Petkov wrote:
>>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>>> I have the following panic after upgrading my kernel. Working version is
>>>> 6.1.10, so something has happened after that.
> IIUC 6.1.11 is failing, right?
>
>>>> 6.2.x kernels crash in the same way. Attached config.
>>>>
>>> Please send dmesg from 6.1.
>>>
>> Of course - attached.
> Thanks for the info.
>
> tglx
6.1.11 is OK -I will 'bisect' by version and find the one that starts
failing.
David
On 27/03/2023 14:49, Thomas Gleixner wrote:
> On Mon, Mar 27 2023 at 09:13, David R. wrote:
>> On 27/03/2023 08:49, Borislav Petkov wrote:
>>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>>> I have the following panic after upgrading my kernel. Working version is
>>>> 6.1.10, so something has happened after that.
> IIUC 6.1.11 is failing, right?
>
>>>> 6.2.x kernels crash in the same way. Attached config.
>>>>
>>> Please send dmesg from 6.1.
>>>
>> Of course - attached.
> Thanks for the info.
>
> tglx
Currently:
6.1.14 good
6.1.16 bad
Currently building 6.1.15 .....
On 27/03/2023 16:53, David R wrote:
> On 27/03/2023 14:49, Thomas Gleixner wrote:
>> On Mon, Mar 27 2023 at 09:13, David R. wrote:
>>> On 27/03/2023 08:49, Borislav Petkov wrote:
>>>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>>>> I have the following panic after upgrading my kernel. Working
>>>>> version is
>>>>> 6.1.10, so something has happened after that.
>> IIUC 6.1.11 is failing, right?
>>
>>>>> 6.2.x kernels crash in the same way. Attached config.
>>>>>
>>>> Please send dmesg from 6.1.
>>>>
>>> Of course - attached.
>> Thanks for the info.
>>
>> tglx
> Currently:
>
> 6.1.14 good
> 6.1.16 bad
>
> Currently building 6.1.15 .....
6.1.15 is good too - so the issue starts at 6.1.16
On 27/03/2023 09:13, David R wrote:
> On 27/03/2023 08:49, Borislav Petkov wrote:
>> On Mon, Mar 27, 2023 at 07:43:52AM +0100, David R wrote:
>>> I have the following panic after upgrading my kernel. Working
>>> version is
>>> 6.1.10, so something has happened after that. 6.2.x kernels crash in
>>> the
>>> same way. Attached config.
>>
After more investigation :
Revert "x86/acpi/boot: Do not register processors that cannot be
onlined for x2APIC"
This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
Corrects the issue for me.
Cheers
David
On Tue, Mar 28, 2023 at 12:02:57PM +0100, David R wrote:
> After more investigation :
>
> Revert "x86/acpi/boot: Do not register processors that cannot be onlined
> for x2APIC"
>
> This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
>
> Corrects the issue for me.
Hmm, weird. That commit came up already yesterday. But in conjunction
with qemu.
Does this fix it per chance?
https://lore.kernel.org/all/[email protected]/
You'd need to revert the revert and apply this one ontop.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
On 28/03/2023 15:20, Borislav Petkov wrote:
> On Tue, Mar 28, 2023 at 12:02:57PM +0100, David R wrote:
>> After more investigation :
>>
>> Revert "x86/acpi/boot: Do not register processors that cannot be onlined
>> for x2APIC"
>>
>> This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
>>
>> Corrects the issue for me.
> Hmm, weird. That commit came up already yesterday. But in conjunction
> with qemu.
>
> Does this fix it per chance?
>
> https://lore.kernel.org/all/[email protected]/
>
> You'd need to revert the revert and apply this one ontop.
>
> Thx.
>
Yes, that patch fixes it also. By all means add my tested by:
Thanks
David
On Tue, Mar 28, 2023 at 04:06:41PM +0100, David R wrote:
> Yes, that patch fixes it also. By all means add my tested by:
Ok, thanks for checking. That issue is still weird, tho, and we don't have
an idea why that happens.
If you could test your original, failing kernel with "nointremap" on the
command line, that would be cool.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
On 28/03/2023 18:10, Borislav Petkov wrote:
> On Tue, Mar 28, 2023 at 04:06:41PM +0100, David R wrote:
>> Yes, that patch fixes it also. By all means add my tested by:
> Ok, thanks for checking. That issue is still weird, tho, and we don't have
> an idea why that happens.
>
> If you could test your original, failing kernel with "nointremap" on the
> command line, that would be cool.
>
> Thx.
>
I can't reboot now 'till Thursday. Will try then and report back.
On Tue, Mar 28, 2023 at 06:32:31PM +0100, David R wrote:
> I can't reboot now 'till Thursday. Will try then and report back.
Appreciated, thanks!
I'll try to repro here in the meantime but I'm afraid I won't be able to
- this looks like a BIOS issue. But we'll see.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette