gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

Bug #1828026 reported by Po-Hsu Lin
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Failed on Moonshot nodes.

FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

# TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 -machine gic-version=2 -append 'mmio'
timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.6k28Ehxzim
INFO: gicv2: mmio: number of implemented SPIs: 256
PASS: gicv2: mmio: all 1 CPUs have interrupts
INFO: gicv2: mmio: IIDR: 0x00000000
PASS: gicv2: mmio: GICD_TYPER is read-only
PASS: gicv2: mmio: GICD_IIDR is read-only
PASS: gicv2: mmio: ICPIDR2 is read-only (0x00000004)
PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0xffffffff)
PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
PASS: gicv2: mmio: IPRIORITYR: clearing priorities
PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 00000000)
PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x00000000)
SUMMARY: 17 tests, 2 unexpected failures

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic aarch64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
Date: Tue May 7 11:25:30 2019
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew)
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Can be found on Disco as well.

affects: linux-hwe (Ubuntu) → linux (Ubuntu)
tags: added: disco
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1828026

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-kvm-unit-tests
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Seeing this on Focal/linux 5.8.0-49.55~20.04.1 generic-64k. Both tests gicv2-mmio-3p and gicv2-mmio-up are failing (similar to LP#1802492 which was marked as a duplicate of this bug). These failures look to only be appearing with the host mcdivitt34-kernel

gicv2-mmio-3p output:

03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: bits for 5 non-existent CPUs masked
03/27 17:50:48 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: register content preserved (01030207 => 0103020f)
03/27 17:50:48 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01030207 => 0x02)
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x011f020f)
03/27 17:50:48 DEBUG| utils:0153| [stdout] SUMMARY: 17 tests, 3 unexpected failures
03/27 17:50:48 DEBUG| utils:0153| [stdout] FAIL gicv2-mmio-3p (17 tests, 3 unexpected failures)

gicv2-mmio-up output:

03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 00000000)
03/27 17:50:50 DEBUG| utils:0153| [stdout] PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x00000000)
03/27 17:50:50 DEBUG| utils:0153| [stdout] SUMMARY: 17 tests, 2 unexpected failures
03/27 17:50:50 DEBUG| utils:0153| [stdout] FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

tags: added: 5.8 focal sru-20210315
tags: added: hwe
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

found on bionic 4.15.0-141.145 generic arm64 also on host mcdivitt34-kernel

Failing the same as the focal I reported previously with failures on gicv2-mmio-3p and gicv2-mmio-up

Different for bionic is gicv3-active is failing as well. May be related, though will file a bug for that (not finding one).

Previously bionic 4.15.0-139.143 also had the above three failing with a 4th failing as well: gicv3-ipi

Possibly these tests will intermittently pass/fail?

Revision history for this message
Kelsey Steele (kelsey-steele) wrote :
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

also found on bionic/hwe-5.4 5.4.0-71.79~18.04.1

tags: added: 5.4 bionic hwe-5.4
Stefan Bader (smb)
tags: added: 4.15 sru-20210621
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With kvm-unit-test repo updated to d8a4f9e5 (ci: Update the list of tests that we run in the Fedora Cirrus-CI), this test will be skipped on this moonshot system:

 Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/gicv2-mmio-up'
 BUILD_HEAD=63cdb04b
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host -accel kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel _NO_FILE_4Uhere_ -smp 1 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.fEB6VHLSIv
 qemu-system-aarch64: -accel: invalid option
 SKIP gicv2-mmio-up (qemu-system-aarch64: -accel: invalid option)
GOOD ubuntu_kvm_unit_tests.gicv2-mmio-up ubuntu_kvm_unit_tests.gicv2-mmio-up timestamp=1665027878 localtime=Oct 06 03:44:38 completed successfully

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in ubuntu-kernel-tests:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.