- Asa-dev - op-lists.linaro.org

Re: [Asa-dev] GICv3 ITS code repo for review

by Marcin Juszkiewicz

W dniu 02.03.2021 o 21:07, Shashi Mallela via Asa-dev pisze: > Hi All, > > As discussed in the meeting today,please find my ITS code implementation from linaro git repo below > ssh://git@git.linaro.org/people/shashi.mallela/qemu.git Next time clone upstream, branch, do your job, push. "I wrote QEMU on one day" like commits are very bad signs. > Please provide your review comments. Build on x86-64 failed: $ ./configure --target-list=aarch64-softmmu $ make -j12 FAILED: libcommon.fa.p/hw_intc_arm_gicv3_its.c.o cc -Ilibcommon.fa.p -I. -I.. -I../capstone/include/capstone -I../slirp -I../slirp/src -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -I/usr/include/p11-kit-1 -I/usr/include/libpng16 -I/usr/include/SDL2 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/fribidi -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/at-spi-2.0 -I/usr/include/libusb-1.0 -fdiagnostics-color=auto -pipe -Wall -Winvalid-pch -Werror -std=gnu99 -O2 -g -isystem /home/hrw/devel/linaro/sbsa-qemu/code/qemu/linux-headers -isystem linux-headers -iquote . -iquote /home/hrw/devel/linaro/sbsa-qemu/code/qemu -iquote /home/hrw/devel/linaro/sbsa-qemu/code/qemu/include -iquote /home/hrw/devel/linaro/sbsa-qemu/code/qemu/disas/libvixl -iquote /home/hrw/devel/linaro/sbsa-qemu/code/qemu/tcg/i386 -iquote /home/hrw/devel/linaro/sbsa-qemu/code/qemu/accel/tcg -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIC -DSTRUCT_IOVEC_DEFINED -D_REENTRANT -Wno-undef -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ libcommon.fa.p/hw_intc_arm_gicv3_its.c.o -MF libcommon.fa.p/hw_intc_arm_gicv3_its.c.o.d -o libcommon.fa.p/hw_intc_arm_gicv3_its.c.o -c ../hw/intc/arm_gicv3_its.c ../hw/intc/arm_gicv3_its.c: In function ‘process_int.isra’: ../hw/intc/arm_gicv3_its.c:92:17: error: ‘icid’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 92 | l2t_id = icid / (page_sz / L1TABLE_ENTRY_SIZE); | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../hw/intc/arm_gicv3_its.c:255:11: note: ‘icid’ was declared here 255 | uint16_t icid; | ^~~~ cc1: all warnings being treated as errors

5 years

1
0
0 0

GICv3 ITS code repo for review

by Shashi Mallela

Hi All, As discussed in the meeting today,please find my ITS code implementation from linaro git repo below ssh://git@git.linaro.org/people/shashi.mallela/qemu.git Please provide your review comments. While majority of the functionality is implemented,there are final changes to be done around GITS_TRANSLATER and referencing the ITS device into sbsa-ref which i shall update subsequently. Thanks Shashi

5 years

1
0
0 0

Re: [Asa-dev] Insanely long time for each PE test in sbsa-acs

by Leif Lindholm

On Tue, Mar 02, 2021 at 11:18:31 +0000, Leif Lindholm via Asa-dev wrote: > On Tue, Mar 02, 2021 at 11:02:35 +0000, Marcin Juszkiewicz via Asa-dev wrote: > > I run sbsa-acs in both QEMU and on HoneyComb to check how it goes. > > > > Recently I noticed long times of PE checks. For example "2 : Check for SIMD > > extensions" is running here for over 3 minutes. On machine with 4 emulated > > cpu cores (a72). > > That sounds completely bonkers. > https://github.com/ARM-software/sbsa-acs/blob/master/test_pool/pe/test_c002… > > I mean the actual test here is reading ID_AA64PFR0_EL1 and checking > the value of a field in the result. > > > That's with local git HEAD builds of QEMU, EDK2, Sbsa.efi using Fedora > > 10.2.1 cross compiler. > > > > Any ideas what is going on? > > 1) The test itself is not the problem. > 2) Masahisa has reported other weirdness recently wrt MPIDR values in > ACPI and stuff. > > What do you get reported in the logs for number of PEs in system and > such? We carried the conversation over to IRC, and the investigation resulted in https://edk2.groups.io/g/devel/topic/patch_edk2_platforms_1_1/81024935 / Leif

5 years

1
0
0 0

Re: [Asa-dev] Insanely long time for each PE test in sbsa-acs

by Leif Lindholm

On Tue, Mar 02, 2021 at 11:02:35 +0000, Marcin Juszkiewicz via Asa-dev wrote: > I run sbsa-acs in both QEMU and on HoneyComb to check how it goes. > > Recently I noticed long times of PE checks. For example "2 : Check for SIMD > extensions" is running here for over 3 minutes. On machine with 4 emulated > cpu cores (a72). That sounds completely bonkers. https://github.com/ARM-software/sbsa-acs/blob/master/test_pool/pe/test_c002… I mean the actual test here is reading ID_AA64PFR0_EL1 and checking the value of a field in the result. > That's with local git HEAD builds of QEMU, EDK2, Sbsa.efi using Fedora > 10.2.1 cross compiler. > > Any ideas what is going on? 1) The test itself is not the problem. 2) Masahisa has reported other weirdness recently wrt MPIDR values in ACPI and stuff. What do you get reported in the logs for number of PEs in system and such? / Leif

5 years

1
0
0 0

Insanely long time for each PE test in sbsa-acs

by Marcin Juszkiewicz

I run sbsa-acs in both QEMU and on HoneyComb to check how it goes. Recently I noticed long times of PE checks. For example "2 : Check for SIMD extensions" is running here for over 3 minutes. On machine with 4 emulated cpu cores (a72). That's with local git HEAD builds of QEMU, EDK2, Sbsa.efi using Fedora 10.2.1 cross compiler. Any ideas what is going on?

5 years

1
0
0 0

SynchronousException occurs in secondary core while booting edk2

by Masahisa Kojima

Hi All, Sorry for long email, but I need your advice to debug my current problem. [Issue] SynchronousExceptionSPx() occurs in secondary core while primary core is executing to boot edk2. # I use almost latest TF-A and edk2 source code. # TF-A Includes Graeme's patches to support 512 cores. [Detail] In sbsa-qemu boot flow, primary core starts bl1 -> bl2 -> bl31 -> bl32 -> edk2. My sbsa-qemu enables UEFI secure variables, so edk2 calls MM_COMMUNICATE service and access uefi variables using StandaloneMM variable/flash drivers running in Secure-EL0. For secondary cores, all secondary cores sleep with wfe() in plat/qemu/common/aarch64/plat_helpers.S::plat_secondary_cold_boot_setup() in bl1, until linux kernel calls PSCI(cpu on). The below gdb output is at edk2 boot. At this point, everythig is fine and edk2 <-> StandaloneMM communication works. --- (gdb) info thread Id Target Id Frame * 1 Thread 1.1 (CPU#0 [running]) spm_mm_smc_handler (smc_fid=3288334433, x1=0, x2=0, x3=0, x4=0, cookie=0x0 <bl1_entrypoint>, handle=0x3ff8a010 <sp_ctx+16>, flags=0) at services/std_svc/spm_mm/spm_mm_main.c:280 2 Thread 1.2 (CPU#1 [running]) plat_secondary_cold_boot_setup () at plat/qemu/common/aarch64/plat_helpers.S:84 --- Several MM_COMMUNICATE service call occurs in edk2, suddenly SynchronousExceptionSPx() is invoked in secondary core. (To make issue simple, I start qemu with "-smp 2") # I set breakpoint at SynchronousExceptionSPx() in secondary core. --- (gdb) info thread Id Target Id Frame 1 Thread 1.1 (CPU#0 [running]) 0x0000000020aef988 in ?? () * 2 Thread 1.2 (CPU#1 [running]) SynchronousExceptionSPx () at bl1/aarch64/bl1_exceptions.S:54 --- After that, secondary core goes into panic_handler() and could not boot anymore. EDK2 and standaloneMM runs only on primary core until linux issues PSCI call, so I don't have any idea why SynchronousException(generated by software?) occurs in secondary core. [Observation] 1) Some EL3 registers are as follows when secondary core stops with breakpoint at SynchronousExceptionSPx (). ELR_EL3 0x31c4 ESR_EL3 0x2000000 FAR_EL3 0x0 ELR_EL3 points 0x31c4, it is wfe() at plat_secondary_cold_boot_setup(). Does it mean SynchronousException occurs while secondary core sleep with wfe()? # All register dump and disassembled bl1.elf are attached. 2) PSCI related area "PLAT_QEMU_HOLD_BASE"(starts from bottom of the secure SRAM(0x20000000)) is as expected. Secondary core#1 checks 0x20000010 in poll_mailbox() loop, the value(0) means secondary core shall keep to sleep with wfe(). --- INFO: 0x20000000 3fcee114 INFO: 0x20000008 0 INFO: 0x20000010 0 INFO: 0x20000018 0 --- This log is output in every spm_mm SMC handler of primary core. 3) When I load same TF-A/BL32(StandaloneMM) image and disable UEFI secure boot on edk2, this issue does not occur. It means calling MM_COMMUNICATE service causes this issue. Does anyone have any idea/clue to debug of this issue? Thanks, Masahisa

5 years

2
2
0 0

SMP boot fails

by Masahisa Kojima

Hi All, I just encounter this error, I would like to share the information. SMP boot fails with the latest master branch of edk2/edk2-platforms/tf-a as of today. # I boot sbsa-qemu with "-smp 4". Linux kernel outputs following error. [ 0.000000] duplicate boot CPU MPIDR: 0x0 in MADT [ 0.000000] duplicate boot CPU MPIDR: 0x0 in MADT [ 0.000000] duplicate boot CPU MPIDR: 0x0 in MADT debian@debian:~$ lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: ARM Model: 3 Model name: Cortex-A72 Stepping: r0p3 BogoMIPS: 125.00 L1d cache: 32K L1i cache: 32K L2 cache: 512K NUMA node0 CPU(s): 0 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid Thanks, Masahisa

5 years

1
0
0 0

SBSA level 3,4 cards

by Marcin Juszkiewicz

During today's meeting we agreed on creating Jira cards to track how close we are to SBSA level 3 and 4 compliance when it comes to QEMU SBSA Reference Platform. SBSA level 3 requirements are tracked in card ASA-75. I marked several cards as blockers of it. SBSA level 4 is tracked in ASA-76. It depends on ASA-75 and then has several newer cards added as blockers: ASA-81 Pass "Memory Access to Un-Populated addr" test in SBSA-ACS ASA-80 Pass PCIe tests in SBSA-ACS ASA-79 Pass PCIe MSI/MSI-X test in SBSA-ACS ASA-78 Pass VMID16 test in SBSA-ACS ASA-77 Pass RAS test in SBSA-ACS ASA-74 Add support for newer cpu core than Cortex-A72 ASA-67 Add Virtual Host Extensions (VHE) Each card got failure message from SBSA-ACS as first comment. ASA-74 among with QEMU-414 will bring us Cortex-A76 which will be v8.2 so we should pass most of PE tests. According to SBSA v6.1 specification we will need ARMv8.3 cpu for level 4 (level 3 is fine with v8.0 one). This will be sorted out once we get v8.2 one.

5 years, 1 month

1
0
0 0

Re: [Asa-dev] [CI] SBSA ACS tests

by Marcin Juszkiewicz

W dniu 30.10.2020 o 13:03, Marcin Juszkiewicz via Asa-dev pisze: > I added new CI job: ldcg-sbsa-acs. > > It builds HEAD of qemu and edk2 and then use it to run Arm SBSA ACS > testsuite for SBSA levels 3-6. Some changes done: 1. As SBSA ACS gets new commits I changed CI job to build what's in git HEAD instead of using releases. 2. sbsa-ref is now using Cortex-A72 instead of A57 during run. 3. We have two runs per SBSA level now. One is with default action for watchdog (reset) while other ignores watchdog (action none). Shashi has some ideas why SBSA ACS are failing in watchdog tests and will file an issue. https://snapshots.linaro.org/ldcg/sbsa-acs/9/ should get populated in few minutes with full logs.

5 years, 1 month

1
0
0 0

Build failed in Jenkins: SBSA QEMU firmware test - just SBSA ACS #7

by ci_notify＠linaro.org

See <https://ci.linaro.org/job/ldcg-sbsa-acs/7/display/redirect> Changes: ------------------------------------------ Started by user Marcin Juszkiewicz (marcin.juszkiewicz(a)linaro.org) Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on leg-aarch64-01-e830a7bfee32 (docker-buster-arm64-ldcg) in workspace <https://ci.linaro.org/job/ldcg-sbsa-acs/ws/> [ldcg-sbsa-acs] $ /bin/bash /tmp/jenkins12294656593135610403.sh + rm -rf '<https://ci.linaro.org/job/ldcg-sbsa-acs/ws/*'> + sudo apt update WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Get:2 http://deb.debian.org/debian buster InRelease [121 kB] Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB] Get:4 http://deb.debian.org/debian buster-backports InRelease [46.7 kB] Ign:5 http://obs.linaro.org/linaro-overlay-buster/buster ./ InRelease Get:6 http://obs.linaro.org/linaro-overlay-buster/buster ./ Release [1,016 B] Get:7 http://obs.linaro.org/linaro-overlay-buster/buster ./ Release.gpg [228 B] Get:8 http://security.debian.org/debian-security buster/updates/main arm64 Packages [254 kB] Get:9 http://deb.debian.org/debian buster/main arm64 Packages [7,737 kB] Get:10 http://deb.debian.org/debian buster-updates/main arm64 Packages [7,848 B] Get:11 http://deb.debian.org/debian buster-backports/main arm64 Packages [416 kB] Get:12 http://obs.linaro.org/linaro-overlay-buster/buster ./ Sources [19.2 kB] Get:13 http://obs.linaro.org/linaro-overlay-buster/buster ./ Packages [144 kB] Fetched 8,864 kB in 39s (225 kB/s) Reading package lists... Building dependency tree... Reading state information... 27 packages can be upgraded. Run 'apt list --upgradable' to see them. + sudo apt -y --no-install-recommends install build-essential pkg-config python3 libpixman-1-dev libglib2.0-dev dosfstools ninja-build python WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.6). dosfstools is already the newest version (4.1-2). python is already the newest version (2.7.16-1). python set to manually installed. python3 is already the newest version (3.7.3-1). python3 set to manually installed. The following additional packages will be installed: libblkid-dev libffi-dev libglib2.0-bin libglib2.0-dev-bin libmount-dev libpcre16-3 libpcre3-dev libpcre32-3 libpcrecpp0v5 libpixman-1-0 libselinux1-dev libsepol1-dev zlib1g-dev Suggested packages: libglib2.0-doc libgdk-pixbuf2.0-bin | libgdk-pixbuf2.0-dev libxml2-utils The following NEW packages will be installed: libblkid-dev libffi-dev libglib2.0-bin libglib2.0-dev libglib2.0-dev-bin libmount-dev libpcre16-3 libpcre3-dev libpcre32-3 libpcrecpp0v5 libpixman-1-0 libpixman-1-dev libselinux1-dev libsepol1-dev ninja-build pkg-config zlib1g-dev 0 upgraded, 17 newly installed, 0 to remove and 27 not upgraded. Need to get 5,319 kB of archives. After this operation, 21.6 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian buster/main arm64 libblkid-dev arm64 2.33.1-0.1 [229 kB] Get:2 http://deb.debian.org/debian buster/main arm64 libffi-dev arm64 3.2.1-9 [155 kB] Get:3 http://deb.debian.org/debian buster/main arm64 libglib2.0-bin arm64 2.58.3-2+deb10u2 [122 kB] Get:4 http://deb.debian.org/debian buster/main arm64 libglib2.0-dev-bin arm64 2.58.3-2+deb10u2 [156 kB] Get:5 http://deb.debian.org/debian buster/main arm64 libmount-dev arm64 2.33.1-0.1 [238 kB] Get:6 http://deb.debian.org/debian buster/main arm64 libpcre16-3 arm64 2:8.39-12 [236 kB] Get:7 http://deb.debian.org/debian buster/main arm64 libpcre32-3 arm64 2:8.39-12 [230 kB] Get:8 http://deb.debian.org/debian buster/main arm64 libpcrecpp0v5 arm64 2:8.39-12 [151 kB] Get:9 http://deb.debian.org/debian buster/main arm64 libpcre3-dev arm64 2:8.39-12 [578 kB] Get:10 http://deb.debian.org/debian buster/main arm64 libsepol1-dev arm64 2.8-1 [308 kB] Get:11 http://deb.debian.org/debian buster/main arm64 libselinux1-dev arm64 2.8-1+b1 [163 kB] Get:12 http://deb.debian.org/debian buster/main arm64 pkg-config arm64 0.29-6 [62.2 kB] Get:13 http://deb.debian.org/debian buster/main arm64 zlib1g-dev arm64 1:1.2.11.dfsg-1 [210 kB] Get:14 http://deb.debian.org/debian buster/main arm64 libglib2.0-dev arm64 2.58.3-2+deb10u2 [1,509 kB] Get:15 http://deb.debian.org/debian buster/main arm64 libpixman-1-0 arm64 0.36.0-1 [436 kB] Get:16 http://deb.debian.org/debian buster/main arm64 libpixman-1-dev arm64 0.36.0-1 [453 kB] Get:17 http://deb.debian.org/debian buster/main arm64 ninja-build arm64 1.8.2-1 [82.7 kB] debconf: unable to initialize frontend: Dialog debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype dpkg-preconfigure: unable to re-open stdin: Fetched 5,319 kB in 1s (9,639 kB/s) Selecting previously unselected package libblkid-dev:arm64. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 39577 files and directories currently installed.) Preparing to unpack .../00-libblkid-dev_2.33.1-0.1_arm64.deb ... Unpacking libblkid-dev:arm64 (2.33.1-0.1) ... Selecting previously unselected package libffi-dev:arm64. Preparing to unpack .../01-libffi-dev_3.2.1-9_arm64.deb ... Unpacking libffi-dev:arm64 (3.2.1-9) ... Selecting previously unselected package libglib2.0-bin. Preparing to unpack .../02-libglib2.0-bin_2.58.3-2+deb10u2_arm64.deb ... Unpacking libglib2.0-bin (2.58.3-2+deb10u2) ... Selecting previously unselected package libglib2.0-dev-bin. Preparing to unpack .../03-libglib2.0-dev-bin_2.58.3-2+deb10u2_arm64.deb ... Unpacking libglib2.0-dev-bin (2.58.3-2+deb10u2) ... Selecting previously unselected package libmount-dev:arm64. Preparing to unpack .../04-libmount-dev_2.33.1-0.1_arm64.deb ... Unpacking libmount-dev:arm64 (2.33.1-0.1) ... Selecting previously unselected package libpcre16-3:arm64. Preparing to unpack .../05-libpcre16-3_2%3a8.39-12_arm64.deb ... Unpacking libpcre16-3:arm64 (2:8.39-12) ... Selecting previously unselected package libpcre32-3:arm64. Preparing to unpack .../06-libpcre32-3_2%3a8.39-12_arm64.deb ... Unpacking libpcre32-3:arm64 (2:8.39-12) ... Selecting previously unselected package libpcrecpp0v5:arm64. Preparing to unpack .../07-libpcrecpp0v5_2%3a8.39-12_arm64.deb ... Unpacking libpcrecpp0v5:arm64 (2:8.39-12) ... Selecting previously unselected package libpcre3-dev:arm64. Preparing to unpack .../08-libpcre3-dev_2%3a8.39-12_arm64.deb ... Unpacking libpcre3-dev:arm64 (2:8.39-12) ... Selecting previously unselected package libsepol1-dev:arm64. Preparing to unpack .../09-libsepol1-dev_2.8-1_arm64.deb ... Unpacking libsepol1-dev:arm64 (2.8-1) ... Selecting previously unselected package libselinux1-dev:arm64. Preparing to unpack .../10-libselinux1-dev_2.8-1+b1_arm64.deb ... Unpacking libselinux1-dev:arm64 (2.8-1+b1) ... Selecting previously unselected package pkg-config. Preparing to unpack .../11-pkg-config_0.29-6_arm64.deb ... Unpacking pkg-config (0.29-6) ... Selecting previously unselected package zlib1g-dev:arm64. Preparing to unpack .../12-zlib1g-dev_1%3a1.2.11.dfsg-1_arm64.deb ... Unpacking zlib1g-dev:arm64 (1:1.2.11.dfsg-1) ... Selecting previously unselected package libglib2.0-dev:arm64. Preparing to unpack .../13-libglib2.0-dev_2.58.3-2+deb10u2_arm64.deb ... Unpacking libglib2.0-dev:arm64 (2.58.3-2+deb10u2) ... Selecting previously unselected package libpixman-1-0:arm64. Preparing to unpack .../14-libpixman-1-0_0.36.0-1_arm64.deb ... Unpacking libpixman-1-0:arm64 (0.36.0-1) ... Selecting previously unselected package libpixman-1-dev:arm64. Preparing to unpack .../15-libpixman-1-dev_0.36.0-1_arm64.deb ... Unpacking libpixman-1-dev:arm64 (0.36.0-1) ... Selecting previously unselected package ninja-build. Preparing to unpack .../16-ninja-build_1.8.2-1_arm64.deb ... Unpacking ninja-build (1.8.2-1) ... Setting up libpcrecpp0v5:arm64 (2:8.39-12) ... Setting up libglib2.0-dev-bin (2.58.3-2+deb10u2) ... Setting up libpixman-1-0:arm64 (0.36.0-1) ... Setting up libblkid-dev:arm64 (2.33.1-0.1) ... Setting up libpixman-1-dev:arm64 (0.36.0-1) ... Setting up libpcre16-3:arm64 (2:8.39-12) ... Setting up libsepol1-dev:arm64 (2.8-1) ... Setting up libglib2.0-bin (2.58.3-2+deb10u2) ... Setting up libffi-dev:arm64 (3.2.1-9) ... Setting up ninja-build (1.8.2-1) ... Setting up libpcre32-3:arm64 (2:8.39-12) ... Setting up pkg-config (0.29-6) ... Setting up zlib1g-dev:arm64 (1:1.2.11.dfsg-1) ... Setting up libmount-dev:arm64 (2.33.1-0.1) ... Setting up libpcre3-dev:arm64 (2:8.39-12) ... Setting up libselinux1-dev:arm64 (2.8-1+b1) ... Setting up libglib2.0-dev:arm64 (2.58.3-2+deb10u2) ... Processing triggers for libc-bin (2.28-10) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libglib2.0-0:arm64 (2.58.3-2+deb10u2) ... No schema files found: doing nothing. + fetch_code + git clone --depth 1 https://github.com/qemu/qemu.git Cloning into 'qemu'... fatal: unable to access 'https://github.com/qemu/qemu.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated. Build step 'Execute shell' marked build as failure

5 years, 1 month

1
1
0 0

2026

2025

2024

2023

2022

2021

2020

Asa-dev