Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #93902

Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found"

Cross-posted to 2 groups.

Show all headers | View raw

Control: retitle -1 riscv64: Boot failure due to incorrect memory map
Control: tags -1 moreinfo

On Wed, Aug 26, 2026 at 11:30:00PM +0800, Han Gao wrote:
>     The RISC-V kernel has also encountered an issue similar to bug #963033.

Similar, yes, but not related to what you claim.

>     The boot process consists of coreboot(ACPI)/LinuxBoot kexec loading the Debian kernel.

As I don't know which package provides linuxboot and no such package
exists in Debian: please re-assign this bug yourself.

> [    0.000000] efi: Getting UEFI parameters from /chosen in DT:
> [    0.000000] efi:   System Table         : 0x00000000900108a8
> [    0.000000] efi:   MemMap Address       : 0x000000008cb3f068
> [    0.000000] efi:   MemMap Size          : 0x0000000000000370
> [    0.000000] efi:   MemMap Desc. Size    : 0x0000000000000028
> [    0.000000] efi:   MemMap Desc. Version : 0x0000000000000001

You claim you boot via coreboot(ACPI) and linuxboot/kexec.  But the
kernel finds a device tree, and a populated one.  But this device tree
includes EFI information, but at least incomplete EFI information.

> [    0.000000] efi: Can't find property 'linux,uefi-secure-boot' in DT!

This line means that the EFI stub did not run.  So you boot with EFI and
without EFI at the same time.

> [    0.000000] __memblock_reserve: [0x0000000084200000-0x00000000865fffff] nid=-1 flags=0 paging_init+0xf8/0x6d0
> [    0.000000] INITRD: 0x1ff6d9f000+0x009a1000 is not a memory region - disabling initrd

Even your initrd is located in memory that does not exist in the
provided memory map in the device tree.

> [    0.000000] __memblock_reserve: [0x0000001ff6d9f000-0x0000001ff773f79e] nid=-1 flags=0 early_init_fdt_scan_reserved_mem+0xe0/0x110
> [    0.000000] __memblock_reserve: [0x000000207dd5b000-0x000000207dd5b37d] nid=-1 flags=0 paging_init+0x23c/0x6d0
> [    0.000000] cma: Size (0x0000000006000000) of region at 0x0000000000000000 exceeds limit (0x0000000000000000)
> [    0.000000] cma: Failed to reserve 96 MiB
> [    0.000000] memblock_phys_alloc_range: 2097152 bytes align=0x1000 from=0x0000000000000000 max_addr=0x0000000000000000 paging_init+0x3fc/0x6d0
> [    0.000000] ------------[ cut here ]------------
> [    0.000000] kernel BUG at arch/riscv/mm/init.c:1224!
> [    0.000000] Kernel BUG [#1]

And here we failed two times (first CMA, then kfence) to get any usable
memory.

I don't see where this is a problem in the kernel.  The boot loader
needs to provide memory information and fails.

Bastian

-- 
The sooner our happiness together begins, the longer it will last.
		-- Miramanee, "The Paradise Syndrome", stardate 4842.6

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" Han Gao <rabenda.cn@gmail.com> - 2026-08-26 17:40 +0200
  Processed: Re: Bug#1145677: riscv64: Boot failure due to  "linux,uefi-secure-boot not found" "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-08-28 15:10 +0200
  Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" Bastian Blank <waldi@debian.org> - 2026-08-28 15:10 +0200
    Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" Bastian Blank <waldi@debian.org> - 2026-08-28 15:30 +0200
      Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" Bastian Blank <waldi@debian.org> - 2026-09-02 22:00 +0200
  Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" Bastian Blank <waldi@debian.org> - 2026-09-02 22:50 +0200
  Bug#1145677: marked as done (riscv64: Boot failure due to  incorrect memory map) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-09-03 00:10 +0200

csiph-web