On Fri, Jul 28, 2023 at 12:23:12PM +0200, Emil Renner Berthing wrote: > On Fri, 28 Jul 2023 at 12:07, Xi Ruoyao <xry111@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > On Fri, 2023-07-28 at 15:40 +0800, Xi Ruoyao wrote: > > > On Fri, 2023-07-28 at 00:04 -0700, Drew Fustini wrote: > > > > It seems like your kernel config is the problem. I used it and I saw > > > > the same result of a panic in riscv_intc_irq: > > > > https://gist.github.com/pdp7/1a26ebe20017a3b90c4e9c005f8178e1 > > > > > > > > This is the config I have been using successfully: > > > > https://gist.github.com/pdp7/ecb34ba1e93fc6cfc4dce66d71e14f82 > > > > > > > > Could you try that config? > > > > > > > > Linux 6.5-rc3 boots okay when built with it: > > > > https://gist.github.com/pdp7/580b072f9a5bf9be87cf88b5f81e50e3 > > > > > > Yes, your configuration works. > > > > > > I'll try to figure out which specific configuration item is problematic > > > in my origin one... > > > > Ah, I found it... If I deselect CONFIG_FRAME_POINTER it will crash. > > > > And I see RISC-V selects ARCH_WANT_FRAME_POINTERS, so it seems frame > > pointer is mandated. But then why I'm able to deselect > > CONFIG_FRAME_POINTER? > > You've probably run into this issue: > https://lore.kernel.org/linux-riscv/20230716001506.3506041-1-guoren@xxxxxxxxxx/ > > Try applying those two patches. > > /Emil Thanks, I think that fixes the issue with CONFIG_FRAME_POINTER=n. I had the same kernel crash [1] when trying the config from Xi [2]. I just did 'b4 shazam 20230716001506.3506041-1-guoren@xxxxxxxxxx' and the riscv_intc_irq panic no longer occurs [3]. I don't have the mmc patches applied on this branch so the boot just hangs at mounting rootfs but I think it is otherwise okay. Drew [1] https://gist.github.com/pdp7/1a26ebe20017a3b90c4e9c005f8178e1 [2] https://gist.github.com/pdp7/c6e358be892d506826be304dcc346a7a [3] https://gist.github.com/pdp7/871ada434febeca4ff93f2381352c038
