** Description changed:
Found on 2025.01.13/bionic/linux-hwe-5.4/5.4.0-208.228~18.04.1
- (openstack/s390x-vm)
+ (openstack/s390x-vm). Seems to be flaky.
17:53:34 DEBUG| [stdout]
- 17:53:34 DEBUG| [stdout]
+
Public bug reported:
Found on 2025.01.13/bionic/linux-hwe-5.4/5.4.0-208.228~18.04.1
(openstack/s390x-vm)
17:53:34 DEBUG| [stdout]
17:53:34 DEBUG| [stdout]
17:53:34 DEBUG| [stdout]
Thank you. I will notify you if any unexpected issues arise with the
updated version during the next cycle.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2097248
Title:
t
** Summary changed:
- test-aa-notify.py (test_*_since_login) from ubuntu_qrt_apparmor
ApparmorTestsuites.test_utils_testsuite(|3) fail on Oracular
+ test-aa-notify.py (test_*_since_login) from ubuntu_qrt_apparmor
ApparmorTestsuites.test_utils_testsuite(|3) fail with "AppArmor denials: 0" on
Ora
util-linux stopped installing last(1) since version 2.40.1-3, and 'wtmpdb last'
(aliased to 'last') is now recommended. Even if errors are due to the missing
last(1), it might be the case that we can't simply replace it with wtmpdb's one
because its output might differ slightly from that of util
Public bug reported:
Found on 2025.01.13/oracular/linux/6.11.0-17.17
Raw log:
=== test-aa-notify.py ===
.F.FFF.F.FFF.FF..
==
FAIL: test_denied_regex_since_login
(__main__.AANotifyDeniedFilterTest.test_
Public bug reported:
Found on 2025.01.13/oracular/linux-lowlatency/6.11.0-1009.10 (metal
riccioli).
Raw log output:
8<
17:26:51 INFO | START
ubuntu_qrt_apparmor.ApparmorTestsuites.test_regression_mqueue_abi
ubuntu_qrt_apparmor.ApparmorTestsuites.test_regression_
Public bug reported:
Found on 2025.01.13/oracular/linux-lowlatency/6.11.0-1009.10 (metal
riccioli).
Raw log output:
8<
18:43:56 INFO | START ubuntu_stress_smoke_test.env
ubuntu_stress_smoke_test.envtimeout=2100timestamp=1737830636
localtime=Jan 25 18:43:
Public bug reported:
Found on Oracular 6.11.0-17.17.
Log output:
# selftests: net: rtnetlink.sh
# PASS: policy routing
---(snip)---
# FAIL: ip netconf show neta
---(snip)---
# FAIL: ip netconf show test-br0
# FAIL: ip netconf show testbr-vlan1
# FAIL: ip netconf s
>From the patch series "[PATCHv2 net-next 0/3] netdevsim: better ipsec
output format"
(https://lore.kernel.org/all/20241010040027.21440-1-liuhang...@gmail.com/),
only "netdevsim: copy addresses for both in and out paths" made it into
the stable branches. The stable upstream update from v6.11.11
(LP
Public bug reported:
Found on Oracular 6.11.0-17.17 and should be found on its derivatives /
backports.
Log output:
# selftests: net: rtnetlink.sh
# PASS: policy routing
---(snip)---
# PASS: ip
Found on focal:linux-ibm-5.15 5.15.0-1070.73~20.04.1 during 2025.01.13.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2096880
Title:
lttng-modules DKMS failed to build wi
Found on:
SRU Cycle: 2025.01.13
Series: focal
Package: linux-ibm-5.15
Version: 5.15.0-1070.73~20.04.1
Cloud: metal
Instance: fili
Region: kernel
Operation: sru
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubu
Found on 2025.01.13/focal/linux-ibm-5.15/5.15.0-1070.73~20.04.1 on
openstack amd64-vm.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2074132
Title:
gre_gso.sh from ubuntu
Public bug reported:
Found on 2025.01.13/oracular/linux-lowlatency/6.11.0-1009.10 on metal
(riccioli).
Log output:
16:59:47 DEBUG| [stdout] Running tests...
16:59:47 DEBUG| [stdout] zram01 1 TINFO: Running: zram01.sh
---(snip)---
16:59:47 DEBUG| [stdout] zram01 6 TINFO: moun
Found on 2025.01.13/oracular/linux-lowlatency/6.11.0-1009.10 on metal
(riccioli).
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2016859
Title:
net:so_txtime.sh in ubuntu_
Found on 2025.01.13/oracular/linux-lowlatency/6.11.0-1009.10 on metal
(riccioli).
N.B. all other "FAIL" besides bridge_parent_id occurred in exactly the
same way as shown in the bug description.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which i
** Summary changed:
- move_page04 from ubuntu_ltp_syscalls starts to fail (properly) on O/N/J/F/B/X
+ move_pages04 from ubuntu_ltp_syscalls starts to fail (properly) on O/N/J/F/B/X
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed t
Public bug reported:
Upstream LTP has fixed move_pages04 [1], and the commits are already
included in sru/sru-xenial as of today. Therefore, move_pages04 should
start to fail on all older kernels except Plucky, unless an unlikely
tricky backport happens in the future. This bug is opened for hintin
Note: vm-scalability.throughput 78.3% improvement
https://lore.kernel.org/linux-mm/202412271037.59a4097d-...@intel.com/
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2089768
Found on s2024.12.02/bionic/linux-hwe-5.4/5.4.0-205.225~18.04.1 on tf
amd-server
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1878877
Title:
fs_fill in fs from ubuntu_lt
Possibly the same issue observed on s2024.12.02/bionic/linux-
hwe-5.4/5.4.0-205.225~18.04.1 on tf amd-server.
The old console output from 2024.01.08 (see bug description) seems no
longer accesible, so I cannot confirm if it's exactly the same. Below is
the output from s2024.12.02 linux-hwe-5.4 on
Similar issue found on J-hwe-6.8-6.8.0-50.51~22.04.1 (2024.10.28).
Note that the test code has been modified a lot (e.g. 6469b66e3f5a ("selftests:
improve vm.memfd_noexec sysctl tests"))
03:53:48 DEBUG| [stdout] # selftests: memfd: memfd_test
03:53:48 DEBUG| [stdout] # memfd: CREATE
03:53:48 DEB
Public bug reported:
Issue found on Oracular amd64 linux-lowlatency (6.11.0-1007.7)
Test log
stdout:
INFO: /dev/kvm exists
KVM acceleration can be used
Generating public/private rsa key pair.
Your identification has been saved in /home/ubuntu/.ssh/id_rsa
Your public key has been saved
Public bug reported:
Issue found on Oracular amd64
* oracular:linux (6.11.0-13.14)
* oracular:linux-lowlatency (6.11.0-1007.7)
* oracular:linux-realtime (6.11.0-1003.3)
In contrast to LP: #2081798, this test failure indicates an unexpected
success under unprivileged_userns, rather than an unexpec
aio_dio_bugs/src/aio-dio-extend-stat.c is not maintained for about 17
years. It incorrectly defines __USE_GNU (instead of _GNU_SOURCE) at the
top and sets O_DIRECT as 04 even on arm64. I believe this is not
worth fixing; it existed for verifying a fix for an ancient bug. Should
we just drop aio
Patch sent to ML: https://lists.ubuntu.com/archives/kernel-
team/2024-December/155919.html
SRU Justification:
[Impact]
Since upstream commit 003af997c8a9 ("hugetlb: force allocating surplus
hugepages on mempolicy allowed nodes"), the LTP hugetlb test case
'hugemmap10' has started failing frequen
It landed in 6.8.y (v6.8.12) and Noble has no longer been affected since
6.8.0-40.40.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2067291
Title:
ftrace:test.d--dynevent
As of 2024/12/11, fresh EC2 instances of the above-mentioned types still
exhibit the issue, so I sent patch to ML:
https://lists.ubuntu.com/archives/kernel-team/2024-December/155888.html
SRU Justification:
[Impact]
On AWS EC2 a1.metal and c6g.8xlarge instances, issues caused by unexpected
discre
https://bugs.launchpad.net/bugs/2087985 is now extended and covers
"ubuntu-kernel-tests" as well, so this LP is duplicate. For ease of
searching, I just leave a comment here for now.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed
This failure is expected if the tree includes upstream commit
003af997c8a9 ("hugetlb: force allocating surplus hugepages on mempolicy
allowed nodes"). Relevant kernels include:
* O:linux (Ubuntu-6.11.0-8.8 or later)
* O:linux-lowlatency (Ubuntu-lowlatency-6.11.0-1003.3 or later)
* N:linux-hwe-6.11
Public bug reported:
Found on testflinger recht with N-lowlatency-6.8.0-50.51.1.
---
07:17:09 INFO | START ubuntu_ltp.mm:min_free_kbytes
ubuntu_ltp.mm:min_free_kbytes timeout=6300timestamp=1732691829
localtime=Nov 27 07:17:09
07:17:09 DEBUG| Persistent state client._record_
Public bug reported:
Found on testflinger recht with N-lowlatency-6.8.0-50.51.1.
---
00:40:34 INFO | START ubuntu_ltp_controllers.cpuset_load_balance
ubuntu_ltp_controllers.cpuset_load_balance timeout=4500
timestamp=1732668034localtime=Nov 27 00:40:34
00:40:34 DEBUG|
** Description changed:
Test hugemmap10 of ubuntu_ltp_stable.hugetlb was observed to fail:
- * N-lowlatency-6.8.0-50.51.1 (drapion, amd64)
- * N-nvidia-lowlatency-6.8.0-1019.21.1 (bunsen, amd64)
+ * N-lowlatency-6.8.0-50.51.1 (drapion, amd64)
+ * N-nvidia-lowlatency-6.8.0-1019.21.1 (buns
Public bug reported:
Test hugemmap10 of ubuntu_ltp_stable.hugetlb was observed to fail:
* N-lowlatency-6.8.0-50.51.1 (drapion, amd64)
* N-nvidia-lowlatency-6.8.0-1019.21.1 (bunsen, amd64)
07:35:55 DEBUG| [stdout] startup='Tue Nov 26 07:35:38 2024'
07:35:55 DEBUG| [stdout] tst_hugepage.c:
"Unhandled exception 6 #UD" issue which Mehmet had written in comment#4
was also seen in 2024.10.28/noble/linux-lowlatency/6.8.0-50.51.1 on
testflinger amd64 node bomberto.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-
Public bug reported:
Flaky timeout failure was observed on builder-cpu2-ram4-disk20.
mem-on-off-test from memory-hotplug fails with timeout (without blocked task
(ref. LP: #1923113) and any other relevant kernel messages).
---
10:59:54 DEBUG| [stdout] # timeout set to 600
10:59:5
Observed in 2024.10.28/noble/linux-lowlatency/6.8.0-50.51.1 on aws
c3.xlarge
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2071813
Title:
ovl-idmapped-mount.sh in ubuntu_
Found on O-6.11 generic: egede
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2086505
Title:
cpuhotplug04 in cpuhotplug from ubuntu_ltp cause crash on some
instances
S
Aside from a1.metal and c6g.8xlarge, no other instance types appear to
be affected at the moment (note: other instance sizes for c6g are
untested). The following issues emphasize the need for resolution,
particularly the second point:
* WARN messages and kernel taint.
* Fewer usable CPUs than expe
** Patch added: "0001-UBUNTU-SAUCE-arm64-Kconfig-Disable-ACPI_HOTPLUG_CPU.patch"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2088047/+attachment/5840165/+files/0001-UBUNTU-SAUCE-arm64-Kconfig-Disable-ACPI_HOTPLUG_CPU.patch
--
You received this bug notification because you are a member
** Description changed:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
Also observed on c6g.8xlarge (generic-64k).
Although the WARN message is almost identical to that on a1.metal (see
description), this time the MADT/DSDT discrepancy appears differently:
MADT lists 32 processors, while DSDT contains 16 processor devices. It
looks like that CPU#16-31 are possible/on
It appears that the following log lines were emitted for all failed test
machines:
...
[stdout] checking for struct landlock_ruleset_attr.handled_access_net... no
[stdout] checking for struct landlock_ruleset_attr... no
...
This indicates that the test fell back to LTP's copied definition
Thanks for the comment.
I tested only on my local VM (Oracular,Noble,Jammy,Focal,Bionic,Xenial
all amd64).
I think it was just an initial observation. My guess is that it was just
because systemd was upgraded to 256 only on the ARM64 test machine back then.
@cypressyew, if you have any idea, pl
It appears to be almost the same issue as LP: #2083819 i.e. I think this is not
a regression.
The failure should be resolvable by a similar approach to LP: #2083819
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-
Oracular ships systemd 256 and /tmp/ is now by default a tmpfs. [1]
On Oracular:
$ findmnt --target /tmp/
TARGET SOURCE FSTYPE OPTIONS
/tmp tmpfs tmpfs rw,nosuid,nodev,size=6123876k,nr_inodes=1048576,inode64
On Noble:
$ findmnt --target /tmp
TARGET
SOURCEFSTYP
Oracular ships systemd 256 and /tmp/ is now by default a tmpfs. [1]
On Oracular:
$ findmnt --target /tmp/
TARGET SOURCE FSTYPE OPTIONS
/tmp tmpfs tmpfs rw,nosuid,nodev,size=6123876k,nr_inodes=1048576,inode64
On Noble:
$ findmnt --target /tmp
TARGET
SOURCEFSTYP
** Description changed:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
** Description changed:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
** Description changed:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
** Patch added:
"0001-UBUNTU-SAUCE-ACPI-processor-Amazon-Graviton-add-work.patch"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2088047/+attachment/5836833/+files/0001-UBUNTU-SAUCE-ACPI-processor-Amazon-Graviton-add-work.patch
** Description changed:
Found on Oracular/6.11.0-11.11 bo
Public bug reported:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
06:55:12 INFO |
** Description changed:
Found on Oracular/6.11.0-11.11 boot testing on AWS a1.metal instance.
The relevant console log excerpts:
-(snip)-
06:55:12 INFO | 2024-11-09T06:51:17.584884+00:00 ip-172-31-6-235 kernel:
cpuinfo: failed to register hotplug callbacks.
-(snip)-
** Tags added: focal
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2085493
Title:
futex_wait_bitset01, memfd_create0[1-4], copy_file_range0[1-3],
statx[01-12], membarri
** Description changed:
Occasionally, multiple test cases from ubuntu_ltp_syscalls fail on
b:aws-5.4 with the same pettern. The following is futex_wait_bitset01
failure log as an example.
17:15:00 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/
** Description changed:
Occasionally, multiple test cases from ubuntu_ltp_syscalls fail on
- b:linux-aws-5.4 with the same pettern. The following is
- futex_wait_bitset01 failure log as an example.
+ b:aws-5.4 with the same pettern. The following is futex_wait_bitset01
+ failure log as an exampl
** Description changed:
Occasionally, multiple test cases from ubuntu_ltp_syscalls fail on
b:aws-5.4 with the same pettern. The following is futex_wait_bitset01
failure log as an example.
17:15:00 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/
Public bug reported:
Occasionally, multiple test cases from ubuntu_ltp_syscalls fail on
b:linux-aws-5.4 with the same pettern. The following is
futex_wait_bitset01 failure log as an example.
17:15:00 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/auto
For {b,f,j}:kvm, CONFIG_COMPACTION is not set.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2083687
Title:
cachestat03 from ubuntu_ltp_syscalls failed on B-KVM
Status i
"raw gso min size" is failing due to an incorrect checking added in the
upstream commit e269d79c7d35 ("net: missing check virtio") [1], which
was fixed in the upstream commit 89add40066f9 ("net: drop bad gso
csum_start and offset in virtio_net_hdr") [2]. The former was pulled in
via v5.15.165 upstr
61 matches
Mail list logo
