From: David R <david@unsolicited.net>
To: "Limonciello, Mario" <mario.limonciello@amd.com>,
Borislav Petkov <bp@alien8.de>,
Gabriel David <ultracoolguy@disroot.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kishon Vijay Abraham I <kvijayab@amd.com>
Subject: Re: Panic starting 6.2.x and later 6.1.x kernels
Date: Wed, 29 Mar 2023 20:03:25 +0100 [thread overview]
Message-ID: <eaa97a25-27b2-187c-1db2-9c56e35d3463@unsolicited.net> (raw)
In-Reply-To: <e8fd7cdf-b6a5-1c7d-bd08-0d60a1c10495@amd.com>
On 29/03/2023 18:51, Limonciello, Mario wrote:
> APIC @ 0x0000000000000000
>> 0000: 41 50 49 43 DE 00 00 00 03 AC 41 4C 41 53 4B 41
>> APIC......ALASKA
>> 0010: 41 20 4D 20 49 20 00 00 09 20 07 01 41 4D 49 20 A M I ...
>> ..AMI
>> 0020: 13 00 01 00 00 00 E0 FE 01 00 00 00 00 08 01 00
>> ................
>> 0030: 01 00 00 00 00 08 02 01 01 00 00 00 00 08 03 02
>> ................
>> 0040: 01 00 00 00 00 08 04 03 01 00 00 00 00 08 05 08
>> ................
>> 0050: 01 00 00 00 00 08 06 09 01 00 00 00 00 08 07 0A
>> ................
>> 0060: 01 00 00 00 00 08 08 0B 01 00 00 00 00 08 09 00
>> ................
>> 0070: 00 00 00 00 00 08 0A 00 00 00 00 00 00 08 0B 00
>> ................
>> 0080: 00 00 00 00 00 08 0C 00 00 00 00 00 00 08 0D 00
>> ................
>> 0090: 00 00 00 00 00 08 0E 00 00 00 00 00 00 08 0F 00
>> ................
>> 00A0: 00 00 00 00 00 08 10 00 00 00 00 00 04 06 FF 05
>> ................
>> 00B0: 00 01 01 0C 09 00 00 00 C0 FE 00 00 00 00 01 0C
>> ................
>> 00C0: 0A 00 00 10 C0 FE 18 00 00 00 02 0A 00 00 02 00
>> ................
>> 00D0: 00 00 00 00 02 0A 00 09 09 00 00 00 0F 00 ..............
>>
>>
>> Cheers
>> David
>>
>
> Can you guys have a try with this patch to see if it helps the situation?
>
> https://lore.kernel.org/linux-pm/20230329174536.6931-1-mario.limonciello@amd.com/T/#u
>
>
> Thanks,
Your patch on top of 6.2.8 brought the crash back I'm afraid.
Cheers
David
next prev parent reply other threads:[~2023-03-29 19:03 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
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 [this message]
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=eaa97a25-27b2-187c-1db2-9c56e35d3463@unsolicited.net \
--to=david@unsolicited.net \
--cc=bp@alien8.de \
--cc=kvijayab@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=tglx@linutronix.de \
--cc=ultracoolguy@disroot.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;
as well as URLs for NNTP newsgroup(s).