From: David R <david@unsolicited.net>
To: Thomas Gleixner <tglx@linutronix.de>, Borislav Petkov <bp@alien8.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Panic starting 6.2.x and later 6.1.x kernels
Date: Mon, 27 Mar 2023 17:21:17 +0100 [thread overview]
Message-ID: <24f77ddd-a852-b496-0e2e-b331061bce07@unsolicited.net> (raw)
In-Reply-To: <d18c96d6-d1e2-aaa9-fab5-e6fc8cc0d1f9@unsolicited.net>
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
next prev parent reply other threads:[~2023-03-27 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 6:43 Panic starting 6.2.x and later 6.1.x kernels David R
2023-03-27 7:49 ` Borislav Petkov
2023-03-27 8:13 ` David R
2023-03-27 13:49 ` Thomas Gleixner
2023-03-27 13:51 ` David R
2023-03-27 14:23 ` David R
2023-03-27 15:53 ` David R
2023-03-27 16:21 ` David R [this message]
2023-03-28 11:02 ` David R
2023-03-28 14:20 ` Borislav Petkov
2023-03-28 15:06 ` David R
2023-03-28 17:10 ` Borislav Petkov
2023-03-28 17:32 ` David R
2023-03-28 17:33 ` Borislav Petkov
[not found] ` <9ed16be4-051d-c20f-0410-b8a973c4c09e@disroot.org>
2023-03-29 10:39 ` Borislav Petkov
2023-03-29 16:14 ` Borislav Petkov
2023-03-29 16:20 ` David R
2023-03-29 17:51 ` Limonciello, Mario
2023-03-29 19:03 ` David R
2023-03-29 19:07 ` Limonciello, Mario
[not found] ` <a0ca1e4e-891c-273d-e2d8-eeb9fc4d0c77@unsolicited.net>
2023-03-29 19:17 ` Limonciello, Mario
2023-03-29 19:20 ` David R
2023-03-29 19:24 ` Limonciello, Mario
2023-03-29 19:31 ` David R
2023-03-30 9:33 ` [tip: x86/urgent] x86/ACPI/boot: Use FADT version to check support for online capable tip-bot2 for Mario Limonciello
2023-03-30 20:50 Panic starting 6.2.x and later 6.1.x kernels gabipr2023
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=24f77ddd-a852-b496-0e2e-b331061bce07@unsolicited.net \
--to=david@unsolicited.net \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).