** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801052
Title:
arm64 kvm-unit-tests timer test failing on 18.04
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
kvm-unit-tests performs 12 timer tests in the latest version, one of them
failing with the latest Ubuntu LTS kernel. This issue has been fixed in
mainline commits 7afc4ddbf299a13aaf28406783d141a34c6b4f5a and
245715cbe83ca934af5d20e078fd85175c62995e (part of 4.19.0 release), which are
tagged with "Cc: Stable # 4.15+" and "Fixes: ...".
Could you please backport them to your tree? "patch" applies them with some
fuzz only (no additional fixing needed).
Here is what I did:
- Boot 4.15.0-38-generic on an ARM Juno r1 board (but every arm64 h/w would
do).
- Run kvm-unit-tests:
$ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
$ cd kvm-unit-tests
$ ./configure && make
$ ./run_tests.sh
This will mark the timer test as failed:
FAIL timer (12 tests, 1 unexpected failures)
A more detailed log can be get by:
$ arm/run arm/timer.flat
I then fetched the official Ubuntu kernel (apt-get source), applied the two
patches mentioned above and rebuilt the kernel (with the .config from /boot).
This will report the timer as pass:
PASS timer (12 tests)
So could you please backport those two patches to make kvm-unit-tests
(and its users) happy?
Btw: I was wondering whether you have some process to find those
stable fixes, even with the 4.15 base kernel being EOL for quite a
while now. Please bear with me if you do and I was just too impatient
;-)
Thanks!
Andre
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jan 28 2018 seq
crw-rw---- 1 root audio 116, 33 Jan 28 2018 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-38-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser':
'fuser'
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=vt220
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyAMA0,115200n8 root=/dev/sda3 rw rootwait
earlycon=pl011,0x7ff80000 debug
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-38-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
