Paul Gevers
2025-Dec-06 15:54 UTC
[Pkg-xen-devel] Bug#1122070: xen: FTBFS on arm64: unknown or missing system register name at operand 1 -- `msr TEECR32_EL1, x0'
Source: xen
Version: 4.20.2+7-g1badcf5035-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: debian-arm at lists.debian.org
User: debian-arm at lists.debian.org
Usertags: arm64
Hi,
A recent upload of xen FTBFS on arm64.
https://buildd.debian.org/status/fetch.php?pkg=xen&arch=arm64&ver=4.20.2%2B7-g1badcf5035-1&stamp=1764415132&raw=0
/usr/bin/make -f ./Rules.mk obj=arch/arm/efi need-builtin=1
aarch64-linux-gnu-gcc -MMD -MP -MF xsm/flask/ss/.conditional.o.d
-DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2
-fomit-frame-pointer -nostdinc -fno-builtin -fno-common
-fzero-init-padding-bits=all -Werror -Wredundant-decls -Wwrite-strings
-Wno-pointer-arith -Wdeclaration-after-statement -Wuninitialized -Wvla
-Wflex-array-member-not-at-end -Winit-self -pipe -D__XEN__ -include
./include/xen/config.h -Wa,--strip-local-absolute -mcpu=generic
-mgeneral-regs-only -mno-outline-atomics
-ffile-prefix-map=/build/reproducible-path/xen-4.20.2+7-g1badcf5035=.
-fdebug-prefix-map=/build/reproducible-path/xen-4.20.2+7-g1badcf5035=.
-I./include -I./arch/arm/include -I./arch/arm/include/generated -fno-pie
-fno-stack-protector -fno-exceptions -fno-asynchronous-unwind-tables
-Wnested-externs -iquote ./xsm/flask/include -I./xsm/flask/include -c
xsm/flask/ss/conditional.c -o xsm/flask/ss/conditional.o
Assembler messages:
{standard input}:474: Error: unknown or missing system register name at
operand 1 -- `msr TEECR32_EL1,x0'
{standard input}:480: Error: unknown or missing system register name at
operand 1 -- `msr TEEHBR32_EL1,x0'
{standard input}:488: Error: unknown or missing system register name at
operand 2 -- `mrs x0,TEECR32_EL1'
{standard input}:494: Error: unknown or missing system register name at
operand 2 -- `mrs x0,TEEHBR32_EL1'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20251206/0799f417/attachment.sig>
Debian Bug Tracking System
2025-Dec-08 11:51 UTC
[Pkg-xen-devel] Bug#1122070: marked as done (xen: FTBFS on arm64: unknown or missing system register name at operand 1 -- `msr TEECR32_EL1, x0')
Your message dated Mon, 08 Dec 2025 11:49:25 +0000 with message-id <E1vSZk5-00FgLR-1I at fasolo.debian.org> and subject line Bug#1122070: fixed in xen 4.20.2+7-g1badcf5035-2 has caused the Debian Bug report #1122070, regarding xen: FTBFS on arm64: unknown or missing system register name at operand 1 -- `msr TEECR32_EL1,x0' 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 owner at bugs.debian.org immediately.) -- 1122070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122070 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Paul Gevers <elbrus at debian.org> Subject: xen: FTBFS on arm64: unknown or missing system register name at operand 1 -- `msr TEECR32_EL1,x0' Date: Sat, 6 Dec 2025 16:54:47 +0100 Size: 8466 URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20251208/289d3b7e/attachment-0002.eml> -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters <ftpmaster at ftp-master.debian.org> Subject: Bug#1122070: fixed in xen 4.20.2+7-g1badcf5035-2 Date: Mon, 08 Dec 2025 11:49:25 +0000 Size: 6564 URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20251208/289d3b7e/attachment-0003.eml>