Your message dated Sun, 03 May 2026 20:04:04 +0000
with message-id <[email protected]>
and subject line Bug#1108898: fixed in grub2 2.12-9+deb13u2
has caused the Debian Bug report #1108898,
regarding riscv64: Illegal instruction appears when using rdcycle in grub
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.)


-- 
1108898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108898
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-efi-riscv64-unsigned
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]
X-Debbugs-Cc: [email protected]
Version: 2.12-8
Severity: normal
Tags: upstream

Dear Maintainer,

Illegal instructions will occur when debian riscv64 iso boots to grub.efi.

Because grub uses the rdcycle instruction.

Upstream[1] has fixed this issue and hopes to backport to 2.12.

[1]: 
https://cgit.git.savannah.gnu.org/cgit/grub.git/commit/grub-core/kern/riscv/efi/init.c?id=c5ae124e11f28f637cbd38cb4d6c1b9817baa135

sudo qemu-system-riscv64 --enable-kvm -M virt -cpu host -m 2048 -smp 2
-nographic \
-boot d -cdrom debian-testing-riscv64-netinst.iso \
-device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \
-device virtio-rng-pci \
-kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \
-drive file=debian.qcow2,format=qcow2,if=virtio
U-Boot 2025.01-3 (Apr 08 2025 - 23:07:41 +0000)
CPU: riscv
Model: riscv-virtio,qemu
DRAM: 2 GiB
Core: 28 devices, 13 uclasses, devicetree: board
Flash: 32 MiB
Loading Environment from nowhere... OK
In: serial,usbkbd
Out: serial,vidconsole
Err: serial,vidconsole
No USB controllers found
Net: eth0: virtio-net#0
Working FDT set to feee6c60
Hit any key to stop autoboot: 0
Device 0: unknown device
Device 0: 1af4 VirtIO Block Device
Type: Hard Disk
Capacity: 610.2 MB = 0.5 GB (1249880 x 512)
... is now current device
Scanning virtio 0:2...
Failed to load '/'
Failed to load '/dtb/'
Failed to load EFI variables
Error: writing contents
** Unable to write file ubootefi.var **
Failed to persist EFI variables
Error: writing contents
** Unable to write file ubootefi.var **
Failed to persist EFI variables
Error: writing contents
** Unable to write file ubootefi.var **
Failed to persist EFI variables
Error: writing contents
** Unable to write file ubootefi.var **
Failed to persist EFI variables
Error: writing contents
** Unable to write file ubootefi.var **
Failed to persist EFI variables
Booting: virtio 0
Unhandled exception: Illegal instruction
EPC: 00000000fdc7a0b8 RA: 00000000fdc7a0fa TVAL: 00000000c0002573
EPC: 000000007e7720b8 RA: 000000007e7720fa reloc adjusted
SP: 00000000feee5050 GP: 0000000000000000 TP: 0000000000000000
T0: 00000000000000e0 T1: 00000000fdc6efe8 T2: 00000000000000f0
S0: 00000000feee5160 S1: 00000000feee52b0 A0: 00000000fdc6efa0
A1: 0000000000000000 A2: 00000000fdc6efe8 A3: fffffffffffffff8
A4: ffffffffffffffb8 A5: 0000000000000001 A6: 0000000000000007
A7: 0000000000000000 S2: 00000000fdc7f528 S3: 00000000fdc7f478
S4: 0000000000000000 S5: 00000000ff7f782c S6: 0000000000000000
S7: 00000000fef2fa70 S8: 0000000000000000 S9: 0000000000000001
S10: 0000000000000001 S11: 0000000000000000 T3: 000000000000001f
T4: 0000000000010000 T5: ffffffffffffffff T6: 00000000000000c0
Code: 7d42 7da2 6149 8082 1141 e022 e406 0800 (2573 c000)
UEFI image [0x00000000fdc6f000:0x00000000fdd8efff] pc=0xb0b8
'/\EFI\BOOT\BOOTRISCV64.EFI'

Thanks,
Han

--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.12-9+deb13u2
Done: Aurelien Jarno <[email protected]>

We believe that the bug you reported is fixed in the latest version of
grub2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <[email protected]> (supplier of updated grub2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 30 Apr 2026 21:02:01 +0200
Source: grub2
Architecture: source
Version: 2.12-9+deb13u2
Distribution: trixie
Urgency: medium
Maintainer: GRUB Maintainers <[email protected]>
Changed-By: Aurelien Jarno <[email protected]>
Closes: 1108898
Changes:
 grub2 (2.12-9+deb13u2) trixie; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from upstream to fix an illegal instruction on riscv64 in
     grub.efi (Closes: #1108898)
Checksums-Sha1:
 42518f020da9f9435a7d085035f978c728ee8d30 8103 grub2_2.12-9+deb13u2.dsc
 ad610a474548de8cfb22128cad0ecb6cb5c42d85 1123180 
grub2_2.12-9+deb13u2.debian.tar.xz
 37cc22b24637dbba953854c323693406806e7cc6 14746 
grub2_2.12-9+deb13u2_source.buildinfo
Checksums-Sha256:
 5d1cda92727de39518a94ce23e7e239077acdfa9a4694e71eba736dbd354391a 8103 
grub2_2.12-9+deb13u2.dsc
 4d3c4689ee100466a36b6a5caa2477ef525fbc5b6ec27cb0319c83db7d9faf89 1123180 
grub2_2.12-9+deb13u2.debian.tar.xz
 e0586a23c6d8ef0cd011063f506dc62c065f933029969d02067a533975767169 14746 
grub2_2.12-9+deb13u2_source.buildinfo
Files:
 a29f7e39ec954c392fb90617a0b8d2ac 8103 admin optional grub2_2.12-9+deb13u2.dsc
 cce3fff8f4007e1dc115b413b5289c5c 1123180 admin optional 
grub2_2.12-9+deb13u2.debian.tar.xz
 ad00f2b1a08052d6ef2ba2f343c67442 14746 admin optional 
grub2_2.12-9+deb13u2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmn3ebwACgkQE4jA+Jno
M2v2VRAAjrW2FUupfwcVTeKvsnkOzeo0w8DEV+lOEjbM0YkhcDN28EgwcHdTtRyZ
68iKdW5Myjg8Tqz/N5xO2B4QQQY3N/OXpUP3x7Y+Gw0xUUfQ4xmpsLQJsd+7+ON+
PAx31I8kdvaAE86YN7vE8u2z7s2aBGrGMBwA5Hh+HRDUNTNWoh1pAu9NruLzbaLc
eI6R39cQ9aIMeb43VpTEsvwObaIhZyepByUrMogIje6wfjFQnPyMYDTjgfn3vceY
xi2WtnNMly9ywK2oXoStNzkm7ruGa/xjUgcJGJ+Rf3nBK+yy/MltfKyipvBo3iHE
zqZ2M+cK3yIoaaQWCOgzbGzt20vyA0p/GE+RyxMwIJuLD2ghx8O/zfgzPj2sXmTS
8RhaSNvEYPEZtqb7JuSkTMt0T6c3gtKrZJErnWSgNYnIp3i2RRPtu7pvlbk2jmdl
ClMnkCsa4obA4E1pdpcFeTAgBna9PdvxL//HCqbXbHq0Vj0mTEKXc8vZyEigVaaL
+wcUNcMPIWdiInhh6/n0/NWgkNIxjIkAsgg1NYWJ4JAFjH2YFZ0fCyz7AXtuH0dg
WFPvHC0dTa+S8EScvnimUvbQJHOTc/nW54K9MSxNYi2oK/6F5goGP1yfNnc2ECOM
XrgUZD5mXJy/0okENtlkH85JOg/NBUt+P5i89ZVAGkoWyIO/Ln8=
=bG3n
-----END PGP SIGNATURE-----

Attachment: pgpivHxwgx0O9.pgp
Description: PGP signature


--- End Message ---

Reply via email to