linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Gabriel David <ultracoolguy@disroot.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	David R <david@unsolicited.net>,
	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 12:39:43 +0200	[thread overview]
Message-ID: <20230329103943.GAZCQVb1n3tKlGOAWI@fat_crate.local> (raw)
In-Reply-To: <9ed16be4-051d-c20f-0410-b8a973c4c09e@disroot.org>

On Tue, Mar 28, 2023 at 09:26:16PM -0400, Gabriel David wrote:
> 
> On 3/28/23 1:10 PM, 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 have the same problem, and while I haven't tested the commit you mentioned
> earlier, `nointremap` on the failing kernels(6.1.x and 6.2.3) worked.
> 
> So far, apart from this mail thread I've found this reddit thread with the
> issue https://reddit.com/r/archlinux/comments/11ux6uh/stuck_at_loading_initial_ramdisk/
> , and to them updating the BIOS worked. However, to me it didn't. Another
> thing is that David, that person, and me all use 1st gen Ryzen processors(in
> my case, a Ryzen 3 1200).

Yeah, this looks like something's borked with interrupt remapping and
timer interrupt when the code looks at that online capable bit. I guess
interrupt remapping doesn't consider that bit and still remaps to cores
which are now *not* onlined, leading to the panic.

But this is all conjecture of me trying to connect the IO-APIC
observation to this online capable bit.

And, ofcourse, I cannot trigger it:

[    0.000000] Linux version 6.1.21 (root@epic) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC Wed Mar 29 12:00:57 CEST 2023

...

[    0.200425] smpboot: CPU0: AMD EPYC 7251 8-Core Processor (family: 0x17, model: 0x1, stepping: 0x2)

...

[    4.019751] AMD-Vi: Interrupt remapping enabled

So it looks like only some Zen1 client BIOSes are b0rked. Which is
swell, again. ;-\

But let's wait for tglx to look at this first.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2023-03-29 10:39 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 [this message]
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=20230329103943.GAZCQVb1n3tKlGOAWI@fat_crate.local \
    --to=bp@alien8.de \
    --cc=david@unsolicited.net \
    --cc=kvijayab@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).