gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot

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

Bug Description

This test passed with X-HWE on ARM64 Moonshot:
    TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio'
    PASS gicv2-mmio (17 tests, 1 skipped)

So this feels like a kernel issue to me.

# MAX_SMP=8
# TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -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 8 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.OlzPYOZSZn
INFO: gicv2: mmio: number of implemented SPIs: 256
PASS: gicv2: mmio: all 8 CPUs have interrupts
INFO: gicv2: mmio: IIDR: 0x4b00043b
PASS: gicv2: mmio: GICD_TYPER is read-only
PASS: gicv2: mmio: GICD_IIDR is read-only
PASS: gicv2: mmio: ICPIDR2 is read-only (0x00000000)
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)
SKIP: gicv2: mmio: ITARGETSR: CPU masking (all CPUs implemented)
PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
FAIL: gicv2: mmio: ITARGETSR: register content preserved (0103020f => 01010201)
PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x0103020f => 0x02)
FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x01010201)
SUMMARY: 17 tests, 2 unexpected failures, 1 skipped

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-146-generic 4.4.0-146.172
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic aarch64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 8 02:17 seq
 crw-rw---- 1 root audio 116, 33 May 8 02:17 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Wed May 8 06:36:49 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB:

ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-146-generic N/A
 linux-backports-modules-4.4.0-146-generic N/A
 linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-kvm-unit-tests
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: New → Triaged
tags: added: sru-20191111
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: Triaged → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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