Your message dated Thu, 3 Sep 2026 00:01:18 +0200 with message-id <s5yxohy6kij2uzu2m37ahqfct2t55jafgi7sp3xycuepzrizfh@dxwpmthicgct> and subject line Re: Bug#1145677: riscv64: Boot failure due to "linux,uefi-secure-boot not found" has caused the Debian Bug report #1145677, regarding riscv64: Boot failure due to incorrect memory map to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1145677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1145677 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: linux Version: 7.1.7+deb13-riscv64 Severity: important X-Debbugs-Cc: [email protected], [email protected] User: [email protected] Usertags: riscv64 Dear Maintainer, The RISC-V kernel has also encountered an issue similar to bug #963033. The boot process consists of coreboot(ACPI)/LinuxBoot kexec loading the Debian kernel. Thanks, Han [ 0.000000] Booting Linux on hartid 0 [ 0.000000] Linux version 7.1.7+deb13-riscv64 ([email protected]) (riscv64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT Debian 7.1.7-1~bpo13+1 (2026-08-10) [ 0.000000] random: crng init done [ 0.000000] SBI specification v2.0 detected [ 0.000000] SBI implementation ID=0x1 Version=0x10006 [ 0.000000] SBI TIME extension detected [ 0.000000] SBI IPI extension detected [ 0.000000] SBI RFENCE extension detected [ 0.000000] SBI SRST extension detected [ 0.000000] SBI DBCN extension detected [ 0.000000] earlycon: uart8250 at MMIO32 0x0000000008181900 (options '') [ 0.000000] printk: legacy bootconsole [uart8250] enabled [ 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 [ 0.000000] efi: Can't find property 'linux,uefi-secure-boot' in DT! [ 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 [ 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] [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 7.1.7+deb13-riscv64 #1 PREEMPTLAZY Debian 7.1.7-1~bpo13+1 [ 0.000000] epc : paging_init+0x400/0x6d0 [ 0.000000] ra : paging_init+0x3fc/0x6d0 [ 0.000000] epc : ffffffff80e08af0 ra : ffffffff80e08aec sp : ffffffff82003d90 [ 0.000000] gp : ffffffff822bffd0 tp : ffffffff82010b00 t0 : 5f00000000000000 [ 0.000000] t1 : 000000000000006d t2 : 5f6b636f6c626d65 s0 : ffffffff82003e00 [ 0.000000] s1 : ffffffff81713b18 a0 : 0000000000000000 a1 : ffffffff81234cc8 [ 0.000000] a2 : 0000000000000000 a3 : ffffffff82135940 a4 : 0000000000000000 [ 0.000000] a5 : 0000000000000000 a6 : ffffffff82003c88 a7 : 0000000000000000 [ 0.000000] s2 : 0000000085400000 s3 : 0000000084200000 s4 : 0000000000000000 [ 0.000000] s5 : 0000000000e00000 s6 : 0000000001000000 s7 : 0000000000000000 [ 0.000000] s8 : 0000000000000000 s9 : 0000000000000000 s10: 0000000000000000 [ 0.000000] s11: 0000000000000000 t3 : ffffffff822fe717 t4 : ffffffff822fe717 [ 0.000000] t5 : ffffffff822fe718 t6 : ffffffff82003b88 ssp : 0000000000000000 [ 0.000000] status: 0000000200000100 badaddr: ffffffff80e08af0 cause: 0000000000000003 [ 0.000000] [<ffffffff80e08af0>] paging_init+0x400/0x6d0 [ 0.000000] [<ffffffff80e053c0>] setup_arch+0xe8/0x6f0 [ 0.000000] [<ffffffff80e00bc8>] start_kernel+0x88/0xac8 [ 0.000000] Code: 4601 6585 0537 0020 e097 0001 80e7 05c0 8a2a e111 (9002) 05b7 [ 0.000000] ---[ end trace 0000000000000000 ]--- [ 0.000000] Kernel panic - not syncing: Fatal exception in interrupt [ 0.000000] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
--- End Message ---
--- Begin Message ---On Wed, Sep 02, 2026 at 10:46:46PM +0200, Bastian Blank wrote: > Yes. We need to establish that this piece of hardware is actually > supported by upstream. And given the error messages we saw already, I > doubt that, or at least the combination with linuxboot. Submitter confirmed that he can not disclose this information, so nothing we can do here. Closing. Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5
--- End Message ---
