[Kernel-packages] [Bug 1934759] Re: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1934759 Title: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Found this issue while debugging missing tests with bug 1934282. On Bionic there are 3 scripts that are not in the Makefile of the kselftests/net: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib-onlink-tests.sh in_netns.sh msg_zerocopy.sh [Fix] * 830669e691464c selftests/net: enable msg_zerocopy test * 1751eb42ddb56b selftests: net: use TEST_PROGS_EXTENDED * a52b839752aab7 selftests: Add fib-onlink-tests.sh to TEST_PROGS * Set fib-onlink-tests.sh as executable They all need to be backported to Bionic. For the in_netns.sh it's not causing any issue to us when being called by run_afpackettests, but I think it's no harm to fix it to reduce confusions. Commit 1751eb42ddb56b will replace the change in 9faedd64 selftests: net: add in_netns.sh TEST_GEN_PROGS_EXTENDED [1] and 5ff9c1a3 selftests: net: add in_netns.sh to TEST_PROGS [2], and since we need to backport it there is no need to work on these two. [1] https://github.com/torvalds/linux/commit/9faedd643fd9 [2] https://github.com/torvalds/linux/commit/5ff9c1a3dd92 [Test] Run the "net" test suite in the kselftest directory from a patched source tree. fib-onlink-tests.sh and msg_zerocopy.sh tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1934175
Title:
Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
[...]
[537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
[...]
[537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
[537105.11] IP: kernfs_kill_sb+0x31/0x70
[537105.783582] PGD 0 P4D 0
[537105.787844] Oops: 0002 [#1] SMP PTI
[...]
RIP: 0010:kernfs_kill_sb+0x31/0x70
RSP: 0018:b90aec1afd00 EFLAGS: 00010286
RAX: RBX: 9fdbd567d900 RCX: a0143885ae01
RDX: RSI: a0143885ae00 RDI: a2937c40
RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
R13: a01436e43000 R14: R15: 9fdbd567d900
FS: 7fe41a615b80() GS:a01afea4() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
sysfs_kill_sb+0x1f/0x40
deactivate_locked_super+0x48/0x80
kernfs_mount_ns+0x1eb/0x230
sysfs_mount+0x66/0xc0
mount_fs+0x37/0x160
? alloc_vfsmnt+0x1b3/0x230
vfs_kern_mount.part.24+0x5d/0x110
do_mount+0x5ed/0xce0
[...]
* The following detailed call stack plus the disassembly help to
understand the cause of the issue:
mount_fs()
--sysfs_mount()
kernfs_mount_ns()
--deactivate_locked_super()
sysfs_kill_sb()
--kernfs_kill_sb()
The below disassembly of kernfs_kill_sb() clarifies exactly the issue:
812f46e0 :
[ ... prologue ...]
48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info
*info = sb->s_fs_info
49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi =
&kernfs_mutex (global)
812f46f9: R_X86_64_32S kernfs_mutex
e8 ee da 67 00 callq 819721f0 #
mutex_lock(&kernfs_mutex);
[...]
48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0
[info->head.prev]
48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign
next->prev = prev, see __list_del()]
48 89 10mov%rdx,(%rax)
48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next =
LIST_POISON1
[...]
* The fix for this issue comes from upstream commit 82382acec0c9
("kernfs: deal with kernfs_fill_super() failures"); this commit is a
very trivial fix that adds an INIT_LIST_HEAD(&info->node) in
kernfs_mount_ns(), making the list prev/next pointers valid since the
beginning. Unfortunately this commit wasn't CCed to stable email when
sent, so it wasn't automatically picked up by Ubuntu kernel; now it
was properly submitted to stable list [0].
* Along with this fix, we found another commit (7b745a4e4051) which is
a small/simple fix to correlated code, that also should have been sent
to 4.14.y stable branch, but for some reason wasn't. Since both
commits were accepted in linux-stable, we are hereby proposing the
backport for Ubuntu kernel 4.15.
[0]
https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/
[Test Case]
* We don't have a real test case, although low-memory condition or an
artificial kprobe reproducer could easily trigger the issue.
* We booted a qemu virtual machine with a kernel containing both
patches with no issues.
[Where problems could occur]
* The likelihood of issues are low, specially due to the fact both patches
are very simple and they are on upstream kernel for more than 3 years (and were
quickly accepted in 4.14.y stable branch last week).
* With that sad, the second patch could potentially introduce issues
with super_block references - I honestly cannot conceive any issues
potentially caused by patch 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934175/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHe
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] geneve4
[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Triaged => Fix Committed -- 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/1933074 Title: large_dir in ext4 broken Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: == SRU, Bionic, Focal, Groovy, Hirsute, Impish == [Impact] Creating millions of files on ext4 partition with large_dir support by touching them will eventually trip an ext4 leaf node issue in the index hash. This occurs more frequently when also using smaller block sizes and ends up either with a EXIST or EUCLEAN failure. This occurs on the restart condition when performing do_split. [ Fix ] The fix protects do_split() from the restart condition, making it safe from both current and future ordering of goto statements in earlier sections of the code. The fix is from a patch sent upstream and cc'd to Ted Tso but didn't appear on the ext4 mailing list presumably because it got marked as SPAM. [ Test Case ] Without the fix touching tens of thousands of empty files will trip the issue. It seems to occur more frequently with memory pressure and smaller block sizes, e.g.: sudo mkdir -p /mnt/tmpfs /mnt/storage sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 1024 -F sudo mount /mnt/tmpfs/ext4.img /mnt/storage and compile and run the attached C program (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c) that quickly populates /mnt/storage with empty files. Without the fix this will terminate with an -EEXIST or -EUCLEAN error on the file creation after several tens of thousands of files. [Where problems could occur] This changes the behaviour of the directory indexing hashing so there is a regression potential that this may introduce subsequent index hashing issues when needed (or not) to do a split. This patch seems to cover all the necessary cases, so I believe this risk is relatively low. I have also tested this on all the kernel series in the SRU with 21,000,000 files so I am confident we have enough test coverage to show the fix is OK. -- I believe, I found a bug in ext4 in recent kernel versions. I stumbled across this while I was trying to restore a backup to a new VM. How to reproduce this bug: 1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel version 4.15.0-144-generic. 2. add a secondary disk to hold the test files. 3. prepare and mount the filesystem with enabled 'large_dir' flag: mkfs.ext4 -m0 /dev/sdb1; tune2fs -O large_dir /dev/sdb1; mkdir /mnt/storage; mount /dev/sdb1 /mnt/storage; 4. change to directory and create approx. 16 mio files cd /mnt/storage; i=0; while (( $i < 2000 )); do i=$(( $i + 1 )); (( $i % 1000 == 0 )) && echo $i; touch file_$i.dat || break; done Expected behaviour: - 20 mio files shoud be created without error What happened instead: - The loop aborts with an error message: # 16263100 # touch: cannot touch 'file_16263173.dat': Structure needs cleaning - dmesg gives a little more details: # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode #2: block 146221: comm touch: directory leaf block found instead of index block Additional notes: - This occurs on kernel version 4.15.0-144-generic - Not sure, but I believe one test was run on 4.15.0-143-generic and failed too. - Did not check against 4.15.0-142-generic - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected Status in cloud-images: Confirmed Status in curtin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in curtin source package in Focal: New Status in linux source package in Focal: Fix Committed Status in curtin source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Bug description: [Impact (linux)] The only package that currently satisfies the bootloader Recommends relationship on ARM systems is flash-kernel. This ignores EFI-based systems, which will instead require GRUB. Our installers know to install GRUB anyway - but flash-kernel also gets installed. Normally flash-kernel realizes it is not needed and just exits - so the impact is limited to wasting space and CPU cycles on each kernel update. However, there can be cases where calling flash-kernel can cause problems. The original report here describes one where flash-kernel thinks it recognizes the system and tries to run anyway, when in fact GRUB is the correct boot loader. [Test Case (linux)] On an arm64 system, confirm that grub-efi-arm64 is an option in the Recommends field: $ apt show linux-image-unsigned-5.4.0-78-generic | grep Recommends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Recommends: flash-kernel | grub-efi-arm64, initramfs-tools | linux- initramfs-tool [What Could Go Wrong (linux)] First let me describe the mitigations against something going wrong. The proposed patch was already in the hirsute kernel at the time of hirsute GA, so it's had some real world testing, including in our installers. In addition, the patch still leaves flash-kernel as the *default* bootloader Recommends (first in the |'d list) - it only adds grub-efi-arm64 as a secondary option, preventing the installation of flash-kernel if GRUB is already there. So, the only scenario where I can see a problem might be if something depends on flash-kernel getting installed due to a Recommends even though GRUB is already present. = Original Report Follows = I used APM Mustang which flash-kernel supported in u-boot mode. But I used it with UEFI environment. It will cause fatal error when I used ARM64 ubuntu live server ISO to install system. In code[1], this will not install `flash-kernel` for APM Mustang because of UEFI. So that means code[2] will not disable `flash-kernel` in target system, only disable `update-initramfs`. When curtin execute to `install_kernel` stage, code[3,4] will not install `flash-kernel` either. But in code[5], it will install `linux-generic`. `linux-generic` has a long dependency tree and it will get `flash-kernel` in Recommended field. Apt by default will install Recommended package before kernel is installed.[6] So it will still execute `zz-flash-kernel` and `flash-kernel` when installing kernel. But system didn't create any `initrd.img` ever because curtin disable `update-initramfs` in code[2]. This will cause that `flash-kernel` cannot find `initrd.img.` and fail when installing it. This issue didn't effect all ARM64 UEFI platform because `flash-kernel` didn't support them and skip.[7] I'm not sure which is best solution for this. But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and fix curtin process with this patch both. If we only apply PR-27, it should work fine as well because it will be skipped when detecting UEFI and install `flash-kernel` before `disable_update_initranfs` in ARM platform without UEFI.[9] [Patch-1,2,3] might have side effect. Picking one patch for curtin should be enough. But I need your advice for this to determine which one is better for curtin. There are two categories 1. avoid installing flash-kernel if no need, [Patch1,2] 2. always install flash-kernel in arm/arm64 and make sure it be installed before code[2] [Patch3] (I will attach patch in reply.) Thanks a lot Regards, Date [1] https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58 [2] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699 [3] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370 [4] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327 [5] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374 [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132 [7] https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787 [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_re
[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1934282 Title: Some test in kselftest/net on focal source tree were not tested at all Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile Backport needed for Focal as we only have these tests unadded: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more tests for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception
[Kernel-packages] [Bug 1934878] Re: Mute/mic LEDs no function on some HP platfroms
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934864] Re: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934864 Title: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: SRU justification: [Impact] When plugin HDMI cable, no HDMI output, kernel reported error: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port [Fix] Legacy LSPCON chip from MCA and Parade is only used for platforms, Limit the support between GEN9 and GEN10. The commit is already in 5.13, so only SRU for oem-5.10 and hirsute. [Test] Verified on hardware, HDMI output works fine. [Where problems could occur] The HDMI output may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress -- 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/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: I personally tested on a Clevo NV40MB, but generally: Find a PC with a current Intel iGPU, but only a HDMI 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the HDMI port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Prerequisite (included in this email patchset as 1/4): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
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/1934110
Title:
ubuntu-host driver lacks lseek ops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the
procfs esm-token file will jump to a NULL address causing the
following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI: RDI:
9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09:
0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15:
9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4:
00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7:
0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX:
7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI:
0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09:
562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12:
7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15:
01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c
b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could occur ==
This one liner adds the missing proc_lseek op. It is hard to see where
it can cause a regression since it affects the driver no other way. I
doubt any code is relying on the current semantics of lseek not
working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934012] Re: Hirsute update: upstream stable patchset 2021-06-29
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1934012 Title: Hirsute update: upstream stable patchset 2021-06-29 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-29 Ported from the following upstream stable releases: v5.10.44, v5.12.11 from git://git.kernel.org/ proc: Track /proc/$pid/attr/ opener mm_struct ASoC: max98088: fix ni clock divider calculation ASoC: amd: fix for pcm_read() error spi: Fix spi device unregister flow spi: spi-zynq-qspi: Fix stack violation bug bpf: Forbid trampoline attach for functions with variable arguments net/nfc/rawsock.c: fix a permission check bug usb: cdns3: Fix runtime PM imbalance on error ASoC: Intel: bytcr_rt5640: Add quirk for the Glavey TM800A550L tablet ASoC: Intel: bytcr_rt5640: Add quirk for the Lenovo Miix 3-830 tablet vfio-ccw: Reset FSM state to IDLE inside FSM vfio-ccw: Serialize FSM IDLE state with I/O completion ASoC: sti-sas: add missing MODULE_DEVICE_TABLE spi: sprd: Add missing MODULE_DEVICE_TABLE usb: chipidea: udc: assign interrupt number to USB gadget structure isdn: mISDN: netjet: Fix crash in nj_probe: bonding: init notify_work earlier to avoid uninitialized use netlink: disable IRQs for netlink_lock_table() net: mdiobus: get rid of a BUG_ON() cgroup: disable controllers at parse time wq: handle VM suspension in stall detection net/qla3xxx: fix schedule while atomic in ql_sem_spinlock RDS tcp loopback connection can hang net:sfc: fix non-freed irq in legacy irq mode scsi: bnx2fc: Return failure if io_req is already in ABTS processing scsi: vmw_pvscsi: Set correct residual data length scsi: hisi_sas: Drop free_irq() of devm_request_irq() allocated irq scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal net: macb: ensure the device is available before accessing GEMGXL control registers net: appletalk: cops: Fix data race in cops_probe1 net: dsa: microchip: enable phy errata workaround on 9567 nvme-fabrics: decode host pathing error for connect MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER dm verity: fix require_signatures module_param permissions bnx2x: Fix missing error code in bnx2x_iov_init_one() nvme-tcp: remove incorrect Kconfig dep in BLK_DEV_NVME nvmet: fix false keep-alive timeout when a controller is torn down powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers spi: Don't have controller clean up spi device before driver unbind spi: Cleanup on failure of initial setup i2c: mpc: Make use of i2c_recover_bus() i2c: mpc: implement erratum A-004447 workaround ALSA: seq: Fix race of snd_seq_timer_open() ALSA: firewire-lib: fix the context to call snd_pcm_stop_xrun() ALSA: hda/realtek: headphone and mic don't work on an Acer laptop spi: bcm2835: Fix out-of-bounds access with more than 4 slaves Revert "ACPI: sleep: Put the FACS table after using it" drm: Fix use-after-free read in drm_getunique() drm: Lock pointer access in drm_master_release() perf/x86/intel/uncore: Fix M2M event umask for Ice Lake server KVM: X86: MMU: Use the correct inherited permissions to get shadow page kvm: avoid speculation-based attacks from out-of-range memslot accesses staging: rtl8723bs: Fix uninitialized variables async_xor: check src_offs is not NULL before updating it btrfs: return value from btrfs_mark_extent_written() in case of error btrfs: promote debugging asserts to full-fledged checks in validate_super cgroup1: don't allow '\n' in renaming ftrace: Do not blindly read the ip address in ftrace_bug() mmc: renesas_sdhi: abort tuning when timeout detected mmc: renesas_sdhi: Fix HS400 on R-Car M3-W+ USB: f_ncm: ncm_bitrate (speed) is unsigned usb: f_ncm: only first packet of aggregate needs to start timer usb: pd: Set PD_T_SINK_WAIT_CAP to 310ms usb: dwc3-meson-g12a: fix usb2 PHY glue init when phy0 is disabled usb: dwc3: meson-g12a: Disable the regulator in the error handling path of the probe usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL usb: dwc3: ep0: fix NULL pointer
[Kernel-packages] [Bug 1934179] Re: Focal update: v5.4.128 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1934179 Title: Focal update: v5.4.128 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.128 upstream stable release from git://git.kernel.org/ dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM dmaengine: stedma40: add missing iounmap() on error in d40_probe() afs: Fix an IS_ERR() vs NULL check mm/memory-failure: make sure wait for page writeback in memory_failure kvm: LAPIC: Restore guard to prevent illegal APIC register access batman-adv: Avoid WARN_ON timing related checks net: ipv4: fix memory leak in netlbl_cipsov4_add_std vrf: fix maximum MTU net: rds: fix memory leak in rds_recvmsg net: lantiq: disable interrupt before sheduling NAPI udp: fix race between close() and udp_abort() rtnetlink: Fix regression in bridge VLAN configuration net/sched: act_ct: handle DNAT tuple collision net/mlx5e: Remove dependency in IPsec initialization flows net/mlx5e: Fix page reclaim for dead peer hairpin net/mlx5: Consider RoCE cap before init RDMA resources net/mlx5e: allow TSO on VXLAN over VLAN topologies net/mlx5e: Block offload of outer header csum for UDP tunnels netfilter: synproxy: Fix out of bounds when parsing TCP options sch_cake: Fix out of bounds when parsing TCP options and header alx: Fix an error handling path in 'alx_probe()' net: stmmac: dwmac1000: Fix extended MAC address registers definition net: make get_net_ns return error if NET_NS is disabled qlcnic: Fix an error handling path in 'qlcnic_probe()' netxen_nic: Fix an error handling path in 'netxen_nic_probe()' net: qrtr: fix OOB Read in qrtr_endpoint_post ptp: improve max_adj check against unreasonable values net: cdc_ncm: switch to eth%d interface naming lantiq: net: fix duplicated skb in rx descriptor ring net: usb: fix possible use-after-free in smsc75xx_bind net: fec_ptp: fix issue caused by refactor the fec_devtype net: ipv4: fix memory leak in ip_mc_add1_src net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock be2net: Fix an error handling path in 'be_probe()' net: hamradio: fix memory leak in mkiss_close net: cdc_eem: fix tx fixup skb leak cxgb4: fix wrong shift. bnxt_en: Rediscover PHY capabilities after firmware reset bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path icmp: don't send out ICMP messages with a source address of 0.0.0.0 net: ethernet: fix potential use-after-free in ec_bhf_remove regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting ASoC: rt5659: Fix the lost powers for the HDA header spi: stm32-qspi: Always wait BUSY bit to be cleared in stm32_qspi_wait_cmd() pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled radeon: use memcpy_to/fromio for UVD fw upload hwmon: (scpi-hwmon) shows the negative temperature properly can: bcm: fix infoleak in struct bcm_msg_head can: bcm/raw/isotp: use per module netdevice notifier can: j1939: fix Use-after-Free, hold skb ref while in use can: mcba_usb: fix memory leak in mcba_usb usb: core: hub: Disable autosuspend for Cypress CY7C65632 tracing: Do not stop recording cmdlines when tracing is off tracing: Do not stop recording comms if the trace file is being read tracing: Do no increment trace_clock_global() by one PCI: Mark TI C667X to avoid bus reset PCI: Mark some NVIDIA GPUs to avoid bus reset PCI: aardvark: Don't rely on jiffies while holding spinlock PCI: aardvark: Fix kernel panic during PIO transfer PCI: Add ACS quirk for Broadcom BCM57414 NIC PCI: Work around Huawei Intelligent NIC VF FLR erratum KVM: x86: Immediately reset the MMU context when the SMM flag is cleared ARCv2: save ABI registers across signal handling x86/process: Check PF_KTHREAD and not current->mm for kernel threads x86/pkru: Write hardware init value to PKRU when xstate is init x86/fpu: Reset state for all signal restore failures dmaengine: pl330: fix wrong usage of spinlock flags in dma_cyclc cfg80211: make certificate generation more robust cfg80211: avoid double free of PMSR request net: ll_temac: Make sure to free skb when it is completely used net: ll_
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be cherry-picked into all affected kernels. [Test Plan] Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: # selftests: net: devlink_port_split.py # no devlink device was found, test skipped ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
Issue found with bionic/linux-hwe-5.4 5.4.0-79.88~18.04.1. -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4
[Kernel-packages] [Bug 1935017] Re: Possible io_uring regression with QEMU on Ubuntu's kernel
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
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/1935017
Title:
Possible io_uring regression with QEMU on Ubuntu's kernel
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Committed
Bug description:
Hi everyone.
Possible io_uring regression with QEMU on Ubuntu's kernel
With the latest Ubuntu 20.04's HWE kernel 5.8.0-59, I'm noticing some
weirdness when using QEMU/libvirt with the following storage
configuration:
QEMU version is 5.2+dfsg-9ubuntu3 and libvirt version is
7.0.0-2ubuntu2.
The guest VM is unable to handle I/O properly with io_uring, and nuking
io="io_uring" fixes the issue.
On one machine (EPYC 7742), the partition table cannot be read and on another
(Ryzen 9 3950X), ext4 detects weirdness with journaling and ultimately remounts
the guest disk to R/O:
[2.712321] virtio_blk virtio5: [vda] 3906519775 512-byte logical blocks
(2.00 TB/1.82 TiB)
[2.714054] vda: detected capacity change from 0 to 2000138124800
[2.963671] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.964909] Buffer I/O error on dev vda, logical block 0, async page read
[2.966021] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.967177] Buffer I/O error on dev vda, logical block 1, async page read
[2.968330] blk_update_request: I/O error, dev vda, sector 2 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.969504] Buffer I/O error on dev vda, logical block 2, async page read
[2.970767] blk_update_request: I/O error, dev vda, sector 3 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.971624] Buffer I/O error on dev vda, logical block 3, async page read
[2.972170] blk_update_request: I/O error, dev vda, sector 4 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.972728] Buffer I/O error on dev vda, logical block 4, async page read
[2.973308] blk_update_request: I/O error, dev vda, sector 5 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.973920] Buffer I/O error on dev vda, logical block 5, async page read
[2.974496] blk_update_request: I/O error, dev vda, sector 6 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.975093] Buffer I/O error on dev vda, logical block 6, async page read
[2.975685] blk_update_request: I/O error, dev vda, sector 7 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.976295] Buffer I/O error on dev vda, logical block 7, async page read
[2.980074] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.981104] Buffer I/O error on dev vda, logical block 0, async page read
[2.981786] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.982083] ixgbe :06:00.0: Multiqueue Enabled: Rx Queue count = 63,
Tx Queue count = 63 XDP Queue count = 0
[2.982442] Buffer I/O error on dev vda, logical block 1, async page read
[2.983642] ldm_validate_partition_table(): Disk read failed.
Kernel 5.8.0-55 is fine, and the only io_uring-related change between
5.8.0-55 and 5.8.0-59 is the commit 4b982bd0f383 ("io_uring: don't
mark S_ISBLK async work as unbounded").
I'm hesitant to run lspci -vnvn and post other bug reporting logs as the
machine includes some proprietary hardware (quite unrelated to this specific
issue), but this issue is reproducible on multiple machines.
The another machine that I was able to reproduce this is running a production
software that needs to run 24/7, so I'm also hesitant to gather logs there too.
Thanks,
Regards
Update:
It was the commit 87c9cfe0fa1fb ("block: don't ignore REQ_NOWAIT for direct
IO").
(Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5)
I've double checked by resetting the Git to
Ubuntu-hwe-5.8-5.8.0-59.66_20.04.1 and reverting that patch alone.
It fixes the issue.
It seems like this patch was backported to multiple stable trees, so I'm not
exactly sure why only Canonical's 5.8 is affected.
FWIW, 5.8.0-61 is also affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935017/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932166] Re: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I can confirm that openafs-modules-dkms 1.8.4~pre1-1ubuntu2.2 can be built and loaded in focal with both 5.4.0-79-generic and 5.11.0-24-generic kernels. I have also tested starting the openafs- client.service systemd service. autopkgtest has also passed with both kernels: * 5.11.0-24.25~20.04.1 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210709_104205_12531@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210709_104729_14c3f@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_110044_46791@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_110044_46791@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210709_103426_14c3f@/log.gz * 5.4.0-79.88 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210709_103628_491d4@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210709_103919_491d4@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_105409_ddccd@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/o/openafs/20210709_103343_ddccd@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210709_103009_491d4@/log.gz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932166 Title: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in openafs package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: New Status in openafs source package in Focal: Fix Committed Bug description: [Impact] Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11 [Fix] Apply the attached debdiff (that is, in turn, a backport of upstream Linux build fixes), build the debs, install the dkms deb and build it against an installed 5.11 kernel: $ sudo dkms install openafs/1.8.4~pre1-1ubuntu2.1 -k $linux-5.11-version [Regression potential] The previous DKMS didn't build at all against 5.11. -- This is a scripted bug report about ADT failures while running openafs tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
** Tags added: sru-20210621 -- 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/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/ With these patches applied, the test can pass without triggering this warning. <<>> tag
[Kernel-packages] [Bug 1866591] Re: vmx_pending_event_test failed in ubuntu_kvm_unit_tests
** Tags added: sru-20210621 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- 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/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Issue found on bare-metal node r5.metal, i3.metal, c5.metal timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.132aLPLaXz -smp 1 -cpu host,+vmx -append vmx_pending_event_test # -initrd /tmp/tmp.nWvh3t6ooD enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_pending_event_test FAIL: x86/vmx_tests.c:2184: Assertion failed: (expected) == (actual) LHS: 0x0012 - ''''''''''''''0001'0010 - 18 RHS: 00 - ''''''''''''''' - 0 Expected VMX_VMCALL, got VMX_EXC_NMI. STACK: 405e1c 405e46 4060e4 4061a1 401556 4039f1 400312 SUMMARY: 4 tests, 1 unexpected failures FAIL vmx_pending_event_test (4 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935684] [NEW] vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64
Public bug reported: Issue found on node akis, with bionic/linux 4.15.0-150.155. This is not a regression as the failure can be found on previous releases. Error: filter = vmx_init_signal_test, test = vmx_init_signal_test Test suite: vmx_init_signal_test FAIL: INIT signal blocked when CPU in VMX operation filter = vmx_init_signal_test, test = vmx_sipi_signal_test Full log: Running 'kvm-ok' [stdout] INFO: /dev/kvm exists [stdout] KVM acceleration can be used Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_init_signal_test' [stdout] BUILD_HEAD=90a7d30e [stdout] timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.BwMoFCX0Fv -smp 2 -cpu max,+vmx -m 2048 -append vmx_init_signal_test # -initrd /tmp/tmp.9wCF3rz6vO [stdout] enabling apic [stdout] enabling apic [stdout] paging enabled [stdout] cr0 = 80010011 [stdout] cr3 = 107f000 [stdout] cr4 = 20 [stdout] filter = vmx_init_signal_test, test = test_vmx_feature_control [stdout] filter = vmx_init_signal_test, test = test_vmxon [stdout] filter = vmx_init_signal_test, test = test_vmptrld [stdout] filter = vmx_init_signal_test, test = test_vmclear [stdout] filter = vmx_init_signal_test, test = test_vmptrst [stdout] filter = vmx_init_signal_test, test = test_vmwrite_vmread [stdout] filter = vmx_init_signal_test, test = test_vmcs_high [stdout] filter = vmx_init_signal_test, test = test_vmcs_lifecycle [stdout] filter = vmx_init_signal_test, test = test_vmx_caps [stdout] filter = vmx_init_signal_test, test = test_vmread_flags_touch [stdout] filter = vmx_init_signal_test, test = test_vmwrite_flags_touch [stdout] filter = vmx_init_signal_test, test = null [stdout] filter = vmx_init_signal_test, test = vmenter [stdout] filter = vmx_init_signal_test, test = preemption timer [stdout] filter = vmx_init_signal_test, test = control field PAT [stdout] filter = vmx_init_signal_test, test = control field EFER [stdout] filter = vmx_init_signal_test, test = CR shadowing [stdout] filter = vmx_init_signal_test, test = I/O bitmap [stdout] filter = vmx_init_signal_test, test = instruction intercept [stdout] filter = vmx_init_signal_test, test = EPT A/D disabled [stdout] filter = vmx_init_signal_test, test = EPT A/D enabled [stdout] filter = vmx_init_signal_test, test = PML [stdout] filter = vmx_init_signal_test, test = VPID [stdout] filter = vmx_init_signal_test, test = interrupt [stdout] filter = vmx_init_signal_test, test = nmi_hlt [stdout] filter = vmx_init_signal_test, test = debug controls [stdout] filter = vmx_init_signal_test, test = MSR switch [stdout] filter = vmx_init_signal_test, test = vmmcall [stdout] filter = vmx_init_signal_test, test = disable RDTSCP [stdout] filter = vmx_init_signal_test, test = int3 [stdout] filter = vmx_init_signal_test, test = into [stdout] filter = vmx_init_signal_test, test = exit_monitor_from_l2_test [stdout] filter = vmx_init_signal_test, test = invalid_msr [stdout] filter = vmx_init_signal_test, test = v2_null_test [stdout] filter = vmx_init_signal_test, test = v2_multiple_entries_test [stdout] filter = vmx_init_signal_test, test = fixture_test_case1 [stdout] filter = vmx_init_signal_test, test = fixture_test_case2 [stdout] filter = vmx_init_signal_test, test = invvpid_test_v2 [stdout] filter = vmx_init_signal_test, test = vmx_controls_test [stdout] filter = vmx_init_signal_test, test = vmx_host_state_area_test [stdout] filter = vmx_init_signal_test, test = vmx_guest_state_area_test [stdout] filter = vmx_init_signal_test, test = vmentry_movss_shadow_test [stdout] filter = vmx_init_signal_test, test = vmentry_unrestricted_guest_test [stdout] filter = vmx_init_signal_test, test = vmx_eoi_bitmap_ioapic_scan_test [stdout] filter = vmx_init_signal_test, test = vmx_hlt_with_rvi_test [stdout] filter = vmx_init_signal_test, test = apic_reg_virt_test [stdout] filter = vmx_init_signal_test, test = virt_x2apic_mode_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_thread_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_tpr_threshold_test [stdout] filter = vmx_init_signal_test, test = vmx_init_signal_test [stdout] [stdout] Test suite: vmx_init_signal_test [stdout] FAIL: INIT signal blocked when CPU in VMX operation [stdout] filter = vmx_init_signal_test, test = vmx_sipi_signal_test [stdout] filter = vmx_init_signal_test, test = vmx_vmcs_shadow_test [stdout] filter = vmx_init_signal_test, test = vmx_cr_load_test [stdout] filter = vmx_init_signal_test, test = vmx_cr4_osxsave_test [stdout] filter = vmx_init_signal_test, test = vmx_nm_test [stdout] filter = vmx_init_signal_test, test = vmx_db_test [stdout] filter = vmx_init_signal_test, test = vmx_nmi_window_test [stdout] filter = vmx_init_signal_test, test = vmx_intr_w
[Kernel-packages] [Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Tags added: sru-20210621 -- 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/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918692] Re: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure
** Tags added: sru-20210621 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- 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/1918692 Title: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Running the ubuntu_kvm_unit_test/vmx_apic_passthrough_thread subtest on rumford shows the following failure: 14. 03/03 06:44:40 DEBUG| utils:0153| [stdout] Test suite: vmx_apic_passthrough_thread_test 15. 03/03 06:44:40 DEBUG| utils:0153| [stdout] FAIL: x86/vmx_tests.c:7705: Assertion failed: (0) == ((int)ioapic_read_redir(0xf).remote_irr) 16. 03/03 06:44:40 DEBUG| utils:0153| [stdout] LHS: 00 - ''''''''''''''' - 0 17. 03/03 06:44:40 DEBUG| utils:0153| [stdout] RHS: 0x0001 - '''''''''''''''0001 - 1 18. 03/03 06:44:40 DEBUG| utils:0153| [stdout] IOAPIC pass-through: remote_irr=0 after EOI 19. 03/03 06:44:40 DEBUG| utils:0153| [stdout] STACK: 4083de 40841a 40158a 403a60 400312 20. 03/03 06:44:40 DEBUG| utils:0153| [stdout] SUMMARY: 5 tests, 1 unexpected failures This sounds like some hardware related setup issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1918692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
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/1917616
Title:
vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe
flavors.
2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP
at ip 004071a3
2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code=
rflags=00010006 cs=0008
2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078
rcx=0809 rdx= rbx=0009
2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf
rsi=0042568d rdi=0042568d
2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a
r9=03f8 r10=000d r11=
2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12=
r13= r14=00403dcc r15=
2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031
cr2=e000 cr3=00477000 cr4=2020
2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007
2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd
2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx
2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test:
2549. Traceback (most recent call last):
2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
2551. _call_test_function(self.execute, *p_args, **p_dargs)
2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
2553. return func(*args, **dargs)
2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
2555. postprocess_profiled_run, args, dargs)
2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
2557. self.run_once(*args, **dargs)
2558. File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 80, in run_once
2559. raise error.TestError("Test failed for {}".format(test_name))
2560. TestError: Test failed for vmx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934878] Re: Mute/mic LEDs no function on some HP platfroms
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935052] Re: Enable v4l2loopback
** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1935052 Title: Enable v4l2loopback Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: In Progress Bug description: SRU Justification [Impact] v4l2loopback-dkms cannot be installed because CONFIG_MEDIA_CAMERA_SUPPORT is disabled. Amazon would like this feature enabled. It is already enabled in the Groovy and Hirsute AWS kernels. [Fix] CONFIG_MEDIA_CAMERA_SUPPORT=y [Test Case] sudo apt-get install v4l2loopback-dkms [Where problems could occur] Enabling ioctl functionality in the kernel could expose security vulnerabilities. [Other Info] SF: #00309464 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1935052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935584] Re: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1935584 Title: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug(s) When using ovs internal port with tc the redirect rules to internal port is back to ingress instead of egress. When we reinsert the skb we start from chain 0 but it could be ct state already set so matching rules on the internal port queue would miss. * brief explanation of fixes When reinserting skb back to ingress queue to restart tc classification then also reset ct. * How to test The setup was created by using ovn and testing iperf traffic from host container to VF pod. The result was ip set on the ovs bridge netdev (internal port) The rules were from rep to eventually the internal port and internal port to rep. The rules were with ct actions and chains tc-policy was set to skip-hw. Without the commit the traffic doesn’t work when hw-offload was true (offload to tc sw only) but does work with hw-offload false (ovs dp). * What it could break. Traffic not working in some cases using internal ports and CT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1935584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: dahdi-linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: dahdi-linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932166] Re: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Patch added: "openafs_1.8.4~pre1-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1932166/+attachment/5509655/+files/openafs_1.8.4~pre1-1ubuntu2.2.debdiff ** Changed in: openafs (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: openafs (Ubuntu Focal) Assignee: (unassigned) => Paolo Pisati (p-pisati) ** Changed in: openafs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932166 Title: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in openafs package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: New Status in openafs source package in Focal: In Progress Bug description: [Impact] Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11 [Fix] Apply the attached debdiff (that is, in turn, a backport of upstream Linux build fixes), build the debs, install the dkms deb and build it against an installed 5.11 kernel: $ sudo dkms install openafs/1.8.4~pre1-1ubuntu2.1 -k $linux-5.11-version [Regression potential] The previous DKMS didn't build at all against 5.11. -- This is a scripted bug report about ADT failures while running openafs tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] [NEW] zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
Public bug reported: This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz + + This is a similar issue as reported on bug 1885289, which was fixed on + autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests + don't use autotest, the test script run comes from the zfs-linux dkms + source package, debian/tests/kernel-smoke-test-scrub. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: New Bug description: This is a scripted bug report about ADT failures while running zfs- linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [
[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4
Issue found with bionic/linux-hwe-5.4 5.4.0-79.88~18.04.1.
** Tags added: hwe-5.4 sru-20210621
--
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/1896448
Title:
ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
/ B-5.4-azure / B-5.4
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Bug description:
Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted
before fixing the false-negative return value of this rtnetlink.sh
test (bug 1890136)
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6gretap00"
# FAIL: ip6gretap
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# FAIL: erspan
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ re
[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4
I have nominated this bug report against focal/linux as a fix would need
to be applied there and propagated to all backports in bionic.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
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/1896448
Title:
ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
/ B-5.4-azure / B-5.4
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Bug description:
Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted
before fixing the false-negative return value of this rtnetlink.sh
test (bug 1890136)
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6gretap00"
# FAIL: ip6gretap
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# FAIL: erspan
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
My apologies, I failed to apply the second patch (2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing) to Focal and Groovy while applying this patchset from the mailing-list. The verification with the partial fix was successful because on neither of these series we have skipped testcases, however, pmtu.sh is still failing in bionic/linux-hwe-5.4 because some features are not available and some tests are skipped: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l /linux-hwe-5.4/20210703_113537_4ed63@/log.gz I have just applied the second patch to focal/linux and groovy/linux. I'll reset the status for these two kernels. ** Changed in: linux (Ubuntu Focal) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Fix Released => In Progress ** Tags removed: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selft
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
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/1931731
Title:
pmtu.sh from selftests.net in linux ADT test failure with
linux/5.8.0-56.63
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Released
Bug description:
[Impact]
Upstream commit 6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check
skb is large enough for IPv4/IPv6 header"), applied to groovy/linux 5.8.0-56.63
via upstream stable update (bug 1929132) introduced a regression caught by
kernel selftests, pmtu.sh from net testcase:
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link
layer MTU on geneve interface
[Fix]
The issue is fixed by d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve:
modify IP header check in geneve6_xmit_skb and geneve_xmit_skb"), which is
already applied for the next SRU cycle as part of upstream stable update (bug
1930766).
[Tests]
I have applied the fix on top of 5.8.0-56.63 and ran pmtu.sh and the whole
selftests.net suite. The testcase is now completed successfully and no other
regression was found.
[Where problems could occur]
The fix could be a partial fix not covering all corner cases, this could lead
to other failures with geneve tunnels.
[Original Description]
This is a scripted bug report about ADT failures while running linux tests
for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
Looks to be isolated to Groovy and appearing on all arches.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
arm64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz
02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects
[ OK ]
02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
[ OK ]
02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
[ OK ]
02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
[ OK ]
02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
[ OK ]
02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions
[ OK ]
02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions
[ OK ]
02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions
[ OK ]
02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop
objects
[Kernel-packages] [Bug 1846471] Re: pmtu.sh in net from ubuntu_kernel_selftests complains about vxlan command usage on D
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Won't Fix
--
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/1846471
Title:
pmtu.sh in net from ubuntu_kernel_selftests complains about vxlan
command usage on D
Status in ubuntu-kernel-tests:
Won't Fix
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Won't Fix
Bug description:
It's complaining about:
vxlan: unknown command "df"
Full test report:
selftests: net: pmtu.sh
TEST: ipv4: PMTU exceptions [ OK ]
TEST: ipv6: PMTU exceptions [ OK ]
vxlan: unknown command "df"?
Usage: ... vxlan id VNI
[ { group | remote } IP_ADDRESS ]
[ local ADDR ]
[ ttl TTL ]
[ tos TOS ]
[ flowlabel LABEL ]
[ dev PHYS_DEV ]
[ dstport PORT ]
[ srcport MIN MAX ]
[ [no]learning ]
[ [no]proxy ]
[ [no]rsc ]
[ [no]l2miss ]
[ [no]l3miss ]
[ ageing SECONDS ]
[ maxaddress NUMBER ]
[ [no]udpcsum ]
[ [no]udp6zerocsumtx ]
[ [no]udp6zerocsumrx ]
[ [no]remcsumtx ] [ [no]remcsumrx ]
[ [no]external ] [ gbp ] [ gpe ]
Where: VNI := 0-16777215
ADDR := { IP_ADDRESS | any }
TOS := { NUMBER | inherit }
TTL := { 1..255 | auto | inherit }
LABEL := 0-1048575
vxlan4 not supported
TEST: IPv4 over vxlan4: PMTU exceptions [SKIP]
vxlan: unknown command "df"?
Usage: ... vxlan id VNI
[ { group | remote } IP_ADDRESS ]
[ local ADDR ]
[ ttl TTL ]
[ tos TOS ]
[ flowlabel LABEL ]
[ dev PHYS_DEV ]
[ dstport PORT ]
[ srcport MIN MAX ]
[ [no]learning ]
[ [no]proxy ]
[ [no]rsc ]
[ [no]l2miss ]
[ [no]l3miss ]
[ ageing SECONDS ]
[ maxaddress NUMBER ]
[ [no]udpcsum ]
[ [no]udp6zerocsumtx ]
[ [no]udp6zerocsumrx ]
[ [no]remcsumtx ] [ [no]remcsumrx ]
[ [no]external ] [ gbp ] [ gpe ]
Where: VNI := 0-16777215
ADDR := { IP_ADDRESS | any }
TOS := { NUMBER | inherit }
TTL := { 1..255 | auto | inherit }
LABEL := 0-1048575
vxlan4 not supported
TEST: IPv6 over vxlan4: PMTU exceptions [SKIP]
TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
geneve: unknown command "df"?
Usage: ... geneve id VNI
remote ADDR
[ ttl TTL ]
[ tos TOS ]
[ flowlabel LABEL ]
[ dstport PORT ]
[ [no]external ]
[ [no]udpcsum ]
[ [no]udp6zerocsumtx ]
[ [no]udp6zerocsumrx ]
Where: VNI := 0-16777215
ADDR := IP_ADDRESS
TOS := { NUMBER | inherit }
TTL := { 1..255 | inherit }
LABEL := 0-1048575
geneve4 not supported
TEST: IPv4 over geneve4: PMTU exceptions [SKIP]
geneve: unknown command "df"?
Usage: ... geneve id VNI
remote ADDR
[ ttl TTL ]
[ tos TOS ]
[ flowlabel LABEL ]
[ dstport PORT ]
[ [no]external ]
[ [no]udpcsum ]
[ [no]udp6zerocsumtx ]
[ [no]udp6zerocsumrx ]
Where: VNI := 0-16777215
ADDR := IP_ADDRESS
TOS := { NUMBER | inherit }
TTL := { 1..255 | inherit }
LABEL := 0-1048575
geneve4 not supported
TEST: IPv6 over geneve4: PMTU exceptions [SKIP]
TEST: IPv4 over geneve6: PMTU exceptions [ OK ]
TEST: IPv6 over geneve6: PMTU exceptions [ OK ]
TEST: IPv4 over fou4: PMTU exceptions [ OK ]
TEST: IPv6 over fou4: PMTU exceptions [ OK ]
TEST: IPv4 over fou6: PMTU exceptions [ OK ]
TEST: IPv6 over fou6: PMTU exceptions [ OK ]
TEST: IPv4 over gue4: PMTU exceptions [ OK ]
TEST: IPv6 over gue4: PMTU exceptions [ OK ]
TEST: IPv4 over gue6: PMTU exceptions [ OK ]
TEST: IPv6 over gue6: PMTU exceptions [ OK ]
TEST: vti6: PMTU exceptions [ OK ]
TEST: vti4: PMTU exceptions [ OK ]
TEST: vti4: default MTU assignment [ OK ]
TEST: vti6: default MTU assignment [ OK ]
TEST: vti4: MTU setting on link creation [ OK ]
TEST: vti6: MTU setting on link creation [ OK ]
TEST: vti6: MTU changes on link changes [ OK ]
vxlan: unknown command "df"?
Usage: ... vxlan id VNI
[ { group | remote } IP_ADDRESS ]
[ local ADDR ]
[ ttl TTL ]
[ tos TOS ]
[ flowlabel LABEL ]
[ dev PHYS_DEV ]
[ dstport PORT ]
[ srcport MIN MAX ]
[ [no]learning ]
[ [no]proxy ]
[ [no]rsc ]
[ [no]l2miss ]
[ [no]l3miss ]
[ ageing SECONDS ]
[ maxaddress NUMBER ]
[ [no]udpcsum ]
[ [no]udp6zerocsumtx ]
[ [no]udp6zerocsumrx ]
[ [no]remcsumtx ] [ [no]remcsumrx ]
[ [no]external ] [ gbp ] [ gpe ]
Where: VNI := 0-16777215
ADDR := { IP_ADDRESS | any }
TOS := { NUMBER | inherit }
TTL := { 1..255 | auto | inherit }
LABEL := 0-1048575
vxlan4 not supported
TEST: ipv4: cleanup of cached exceptions [SKIP]
TEST: ipv6: cleanup of cached exceptions [ OK ]
ok 1..15 selftests: net: pmtu.sh [PASS]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/
[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM
This is still affecting at least the generic kernels for amd64 and ppc64el arches. ** Changed in: linux (Ubuntu Bionic) Status: Invalid => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Invalid => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: Invalid => Confirmed -- 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/1897764 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on Focal 5.4.0-49.53 zVM kernel04 Test failed with: # selftests: memory-hotplug: mem-on-off-test.sh # Test scope: 2% hotplug memory # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # offline 2% hot-pluggable memory in online state # trying to offline 1 out of 16 memory block(s): # online->offline memory0 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 0: unexpected fail # online->offline memory1 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 1: unexpected fail # online->offline memory10 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 10: unexpected fail # online->offline memory11 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 11: unexpected fail # online->offline memory12 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 12: unexpected fail # online->offline memory13 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 13: unexpected fail # online->offline memory14 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 14: unexpected fail # online->offline memory15 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 15: unexpected fail # online->offline memory2 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 2: unexpected fail # online->offline memory3 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 3: unexpected fail # online->offline memory4 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 4: unexpected fail # online->offline memory5 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 5: unexpected fail # online->offline memory6 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 6: unexpected fail # online->offline memory7 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 7: unexpected fail # online->offline memory8 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 8: unexpected fail # online->offline memory9 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 9: unexpected fail # FAILED - unable to offline some memory blocks, device busy? # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # Test with memory notifier error injection not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1 This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well. Passed with 5.4.0-44.48 Passed with 5.4.0-43.47 Failed with 5.4.0-42.46 Looks like it's not very stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4
** Also affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-hwe source package in Bionic: New Status in linux-hwe-5.4 source package in Bionic: New Bug description: Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with: error: ‘F_SEAL_FUTURE_WRITE’ undeclared Build log: $ sudo make TARGETS=memfd make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ -I../../../../usr/include/memfd_test.c common.o -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test memfd_test.c: In function ‘test_seal_future_write’: memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in this function); did you mean ‘F_SEAL_WRITE’? mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE); ^~~ F_SEAL_WRITE memfd_test.c:749:27: note: each undeclared identifier is reported only once for each function it appears in ../lib.mk:141: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test' failed make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test] Error 1 make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' Makefile:143: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4
** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe source package in Bionic: New Bug description: Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with: error: ‘F_SEAL_FUTURE_WRITE’ undeclared Build log: $ sudo make TARGETS=memfd make --no-builtin-rules ARCH=x86 -C ../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ -I../../../../usr/include/memfd_test.c common.o -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test memfd_test.c: In function ‘test_seal_future_write’: memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in this function); did you mean ‘F_SEAL_WRITE’? mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE); ^~~ F_SEAL_WRITE memfd_test.c:749:27: note: each undeclared identifier is reported only once for each function it appears in ../lib.mk:141: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test' failed make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test] Error 1 make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd' Makefile:143: recipe for target 'all' failed make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
Found with hirsute/linux 5.11.0-24.25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be cherry-picked into all affected kernels. [Test Plan] Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: # selftests: net: devlink_port_split.py # no devlink device was found, test skipped ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
Found with hirsute/linux 5.11.0-24.25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh 00:09:30 DEBUG| [stdout] # 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup ping 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup traceroute 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error route lookup ping 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed [ OK ] 00:09:34 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup ping 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup traceroute 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup ping 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity [FAIL] 00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit [ OK ] 00:09:40 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # ### 00:09:40 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP error route lookup traceroute 00:09:40 DEBUG| [stdout] # ###
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Tags added: sru-20210621 -- 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/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Bug description: Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
Found with hirsute/linux 5.11.0-24.25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL]
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Summary changed: - psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/impish + psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish ** Tags added: sru-20210621 -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # e
[Kernel-packages] [Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
Found with hirsute/linux 5.11.0-24.25. ** Tags added: sru-20210621 -- 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/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz test_zz_cleanup_source_tree (__main__.ApparmorTestsuites) Cleanup downloaded source ... ok == FAIL: test_utils_testsuite (__main__.ApparmorTestsuites) Run utils (make check) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1841, in test_utils_testsuite self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 == FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites) Run utils (make check with python3) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1862, in test_utils_testsuite3 self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 -- Ran 58 tests in 1448.768s FAILED (failures=2) 23:36:54 INFO | END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 14 23:36:54 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Confirmed that oss4 4.2-build2010-5ubuntu6~20.04.3 autopkgtest is successful with focal/linux-hwe-5.11 5.11.0-24-generic: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/amd64/o/oss4/20210705_154753_c0c2e@/log.gz While also still building successfully with focal/linux 5.4.0-79-generic: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/amd64/o/oss4/20210705_154758_18e1c@/log.gz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in oss4 package in Ubuntu: Invalid Status in linux-hwe-5.11 source package in Focal: Invalid Status in oss4 source package in Focal: Fix Committed Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in oss4 package in Ubuntu: Invalid Status in linux-hwe-5.11 source package in Focal: Invalid Status in oss4 source package in Focal: Fix Committed Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932162] Re: dm-writeboost/2.2.9-1ubuntu1.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
*** This bug is a duplicate of bug 1932257 *** https://bugs.launchpad.net/bugs/1932257 ** This bug has been marked a duplicate of bug 1932257 dm-writeboost dkms: build failure with linux-hwe-5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932162 Title: dm-writeboost/2.2.9-1ubuntu1.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dm-writeboost package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dm-writeboost source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running dm- writeboost tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dm-writeboost/20210611_205906_3bedf@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/d/dm-writeboost/20210612_122210_05325@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/d/dm-writeboost/20210611_210008_1bb6f@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/d/dm-writeboost/20210611_205846_7b434@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1932162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
These patches are not needed for focal/linux. They are targeted for focal/linux-hwe-5.11, so having them applied for hirsute/linux first is the correct nomination. ** Changed in: linux (Ubuntu Focal) Status: In Progress => Invalid -- 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/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932170] Re: virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** No longer affects: linux-hwe-5.11 (Ubuntu) ** No longer affects: linux-hwe-5.11 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932170 Title: virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in virtualbox package in Ubuntu: New Status in virtualbox source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running virtualbox tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/v/virtualbox/20210611_210536_dcb86@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1932170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Patch added: "dahdi-linux_2.11.1~dfsg-1ubuntu6.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+attachment/5507902/+files/dahdi-linux_2.11.1~dfsg-1ubuntu6.3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Patch added: "broadcom-sta_6.30.223.271-12.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+attachment/5507901/+files/broadcom-sta_6.30.223.271-12.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932160 Title: broadcom-sta/6.30.223.271-12 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in broadcom-sta package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in broadcom-sta source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Patch added: "bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+attachment/5507898/+files/bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in bcmwl source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933856] Re: gcc version used for kernel configs doesn't match the one used for builds
For the record, this is what's causing the config differences between the gcc versions: With gcc 10.3.0, CC_HAS_KASAN_GENERIC is not available as it depends on the following compiler flag: config CC_HAS_KASAN_GENERIC def_bool $(cc-option, -fsanitize=kernel-address) 'cc-option' will do something similar to the following, which with gcc 10.2.0 riscv64 cross compiler would return success: $ /usr/bin/riscv64-linux-gnu-gcc-10 -Werror -fsanitize=kernel-address -c -x c /dev/null $ echo $? 0 But with 10.3.0 this doesn't seem to be supported anymore as a standalone flag, depending now on '-fasan-shadow-offset=': $ /usr/bin/riscv64-linux-gnu-gcc-10 -Werror -fsanitize=kernel-address -c -x c /dev/null cc1: error: ‘-fsanitize=kernel-address’ with stack protection is not supported without ‘-fasan-shadow-offset=’ for this target [-Werror] And all KASAN options get removed altogether. This doesn't cause any real config change, as we disable CONFIG_KASAN anyway. But for our annotations '-' != 'n', failing the config checks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933856 Title: gcc version used for kernel configs doesn't match the one used for builds Status in linux-riscv-5.8 package in Ubuntu: Invalid Status in linux-riscv-5.8 source package in Focal: Fix Committed Bug description: [Impact] linux-riscv-5.8 needs to be built with gcc-10 in Focal otherwise it won't boot. This was fixed by commit "UBUNTU: [Packaging] Use gcc-10 for riscv 5.8 kernel build", which adds gcc-10 as "Build-Depends-Arch" and sets a variable "gcc" in 'debian/rules', which is passed down to make by 'debian/rules.d/2-binary-arch.mk'. The other gcc version dependency is when we generate locally the kernel configs by running 'make syncconfig', which is called by 'debian/scripts/misc/kernelconfig'. Currently, the syncconfig is called using the chroot default compiler, which in Focal is gcc-9. So far there hasn't been any major differences, however with the update of gcc-10 in Groovy and Focal from 10.2.0 to 10.3.0 some KASAN related config options are not available anymore, causing some changes on the configs generated. The problem with non-matching gcc versions being used, is that there will be a mismatch between the configs being generated during the preparation of the kernel and the ones during the build. [Fix] The proposed fix is to use the same variable defined for the build, passing it down to 'debian/scripts/misc/kernelconfig' and using it to define the correct cross-compiler to be used. [Where problems could occur] If the environment variables are not set correctly the build can break in some environment which was not tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1933856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933856] Re: gcc version used for kernel configs doesn't match the one used for builds
** Changed in: linux-riscv-5.8 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933856 Title: gcc version used for kernel configs doesn't match the one used for builds Status in linux-riscv-5.8 package in Ubuntu: Invalid Status in linux-riscv-5.8 source package in Focal: Fix Committed Bug description: [Impact] linux-riscv-5.8 needs to be built with gcc-10 in Focal otherwise it won't boot. This was fixed by commit "UBUNTU: [Packaging] Use gcc-10 for riscv 5.8 kernel build", which adds gcc-10 as "Build-Depends-Arch" and sets a variable "gcc" in 'debian/rules', which is passed down to make by 'debian/rules.d/2-binary-arch.mk'. The other gcc version dependency is when we generate locally the kernel configs by running 'make syncconfig', which is called by 'debian/scripts/misc/kernelconfig'. Currently, the syncconfig is called using the chroot default compiler, which in Focal is gcc-9. So far there hasn't been any major differences, however with the update of gcc-10 in Groovy and Focal from 10.2.0 to 10.3.0 some KASAN related config options are not available anymore, causing some changes on the configs generated. The problem with non-matching gcc versions being used, is that there will be a mismatch between the configs being generated during the preparation of the kernel and the ones during the build. [Fix] The proposed fix is to use the same variable defined for the build, passing it down to 'debian/scripts/misc/kernelconfig' and using it to define the correct cross-compiler to be used. [Where problems could occur] If the environment variables are not set correctly the build can break in some environment which was not tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1933856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933856] [NEW] gcc version used for kernel configs doesn't match the one used for builds
Public bug reported: [Impact] linux-riscv-5.8 needs to be built with gcc-10 in Focal otherwise it won't boot. This was fixed by commit "UBUNTU: [Packaging] Use gcc-10 for riscv 5.8 kernel build", which adds gcc-10 as "Build-Depends-Arch" and sets a variable "gcc" in 'debian/rules', which is passed down to make by 'debian/rules.d/2-binary-arch.mk'. The other gcc version dependency is when we generate locally the kernel configs by running 'make syncconfig', which is called by 'debian/scripts/misc/kernelconfig'. Currently, the syncconfig is called using the chroot default compiler, which in Focal is gcc-9. So far there hasn't been any major differences, however with the update of gcc-10 in Groovy and Focal from 10.2.0 to 10.3.0 some KASAN related config options are not available anymore, causing some changes on the configs generated. The problem with non-matching gcc versions being used, is that there will be a mismatch between the configs being generated during the preparation of the kernel and the ones during the build. [Fix] The proposed fix is to use the same variable defined for the build, passing it down to 'debian/scripts/misc/kernelconfig' and using it to define the correct cross-compiler to be used. [Where problems could occur] If the environment variables are not set correctly the build can break in some environment which was not tested. ** Affects: linux-riscv-5.8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-riscv-5.8 (Ubuntu Focal) Importance: Undecided Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Also affects: linux-riscv-5.8 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-riscv-5.8 (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933856 Title: gcc version used for kernel configs doesn't match the one used for builds Status in linux-riscv-5.8 package in Ubuntu: New Status in linux-riscv-5.8 source package in Focal: In Progress Bug description: [Impact] linux-riscv-5.8 needs to be built with gcc-10 in Focal otherwise it won't boot. This was fixed by commit "UBUNTU: [Packaging] Use gcc-10 for riscv 5.8 kernel build", which adds gcc-10 as "Build-Depends-Arch" and sets a variable "gcc" in 'debian/rules', which is passed down to make by 'debian/rules.d/2-binary-arch.mk'. The other gcc version dependency is when we generate locally the kernel configs by running 'make syncconfig', which is called by 'debian/scripts/misc/kernelconfig'. Currently, the syncconfig is called using the chroot default compiler, which in Focal is gcc-9. So far there hasn't been any major differences, however with the update of gcc-10 in Groovy and Focal from 10.2.0 to 10.3.0 some KASAN related config options are not available anymore, causing some changes on the configs generated. The problem with non-matching gcc versions being used, is that there will be a mismatch between the configs being generated during the preparation of the kernel and the ones during the build. [Fix] The proposed fix is to use the same variable defined for the build, passing it down to 'debian/scripts/misc/kernelconfig' and using it to define the correct cross-compiler to be used. [Where problems could occur] If the environment variables are not set correctly the build can break in some environment which was not tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1933856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933547] Re: tpm driver causes non-fatal kernel crash on boot
Hello TomaszCiolek, There is a Hirsute 21.04 kernel update in -proposed with some tpm fixes applied. Could you please try kernel version 5.11.0-23.24 to check whether the issue is resolved with this kernel? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New -- 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/1933547 Title: tpm driver causes non-fatal kernel crash on boot Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kernel: [1.138781] bus_for_each_dev+0x7e/0xc0 Jun 24 07:22:45 munin kernel: [1.138785] driver_attach+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138789] bus_add_driver+0x135/0x1f0 Jun 24 07:22:45 munin kernel: [1.138793] driver_register+0x95/0xf0 Jun 24 07:22:45 munin kernel: [1.138798] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138805] __platform_driver_register+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138811] init_tis+0x87/0xdd Jun 24 07:22:45 munin kernel: [1.138817] ? kobject_uevent+0xb/0x10 Jun 24 07:22:45 munin kernel: [1.138823] ? driver_registe
[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Also found with focal/linux-hwe-5.11 5.11.0-20.21~20.04.1. test_pci 476 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '12' ** Tags added: hwe-5.11 -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 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: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Also found with focal/linux-hwe-5.11 5.11.0-20.21~20.04.1. ** Tags added: hwe-5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G
Also found with focal/linux-hwe-5.11 5.11.0-20.21~20.04.1. ** Tags added: hwe-5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G Status in ubuntu-kernel-tests: In Progress Status in linux-azure package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Status in linux-azure source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
Also found with focal/linux-hwe-5.11 5.11.0-20.21~20.04.1. ** Tags added: hwe-5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Confirmed Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: Confirmed Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on G/H
Also found with focal/linux-hwe-5.11 on ADT.
** Tags added: hwe-5.11
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
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/1923683
Title:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on G/H
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Bug description:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on Groovy riscv 5.8.0-21.23
This test was recently added, not considering a regression
Log is getting cut off from regression test report. the below is all
that could be retrieved at the moment:
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C
linux/tools/testing/selftests TARGETS=ftrace run_tests'
04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules
ARCH=riscv -C ../../.. headers_install
04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:14 DEBUG| utils:0153| [stdout] INSTALL ./usr/include
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done
for 'all'.
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale
failed.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check
that your locale settings:
04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and
installed on your system.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to
the standard locale ("C").
04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test
[PASS]
04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing
check[PASS]
04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer
size [PASS]
04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing
setting [PASS]
04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and
trace_marker [PASS]
04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct
functions against tracers [UNRESOLVED]
04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct
functions against kprobes [UNSUPPORTED]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event -
add/remove kprobe events[FAIL]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event -
add/remove synthetic events [UNSUPPORTED]
04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event -
selective clear (compatibility) [UNSUPPORTED]
04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Gene
[Kernel-packages] [Bug 1931733] Re: ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 (Max stack tracer)
Also found with focal/linux-hwe-5.11 5.11.0-20.21~20.04.1 (ppc64el only): https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l /linux-hwe-5.11/20210612_011655_0d30e@/log.gz ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.4 5.8 focal generic hwe-5.11 sru-20210531 ** Summary changed: - ftracetest from selftests in linux ADT test failure with linux/5.4.0-75.84 (Max stack tracer) + ftracetest from selftests in linux ADT test failure with linux/linux-hwe-5.11 (Max stack tracer) -- 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/1931733 Title: ftracetest from selftests in linux ADT test failure with linux/linux- hwe-5.11 (Max stack tracer) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-75.84 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Problem appears to be isolated to Focal. Seeing on Focal/linux and Focal/hwe-5.8. ppc64el only. Failing with: ftrace - Max stack tracer [FAIL] Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20210603_094441_f3830@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable
** Tags added: hwe-5.11 -- 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/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on Bionic 5.3.0-1033.35-aws TAP version 13 1..1 # selftests: memory-hotplug: mem-on-off-test.sh # Warning: file mem-on-off-test.sh is not executable, correct this. not ok 1 selftests: memory-hotplug: mem-on-off-test.sh make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ubuntu_ker:0242| == Summary === ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Tags added: hwe-5.11 -- 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux-kvm (Ubuntu Disco) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux-kvm (Ubuntu Cosmic) ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Focal: New Status in linux-kvm source package in Focal: New Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux source package in Hirsute: New Status in linux-kvm source package in Hirsute: New Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy
** Summary changed: - psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux + psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test d
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
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/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation
Were applied to Groovy with our stable update process (bug 1918516)
User reported that IR Remote key press will be repeated for multiple times
with these patches applied.
Commit 528222d853f92 ("media: rc: harmonize infrared durations to
microseconds") that needs to be fixed by these two does not exist in
5.8 kernel. The patch author Matthias Reichl also state these are for
5.10 and onward.
[Fix]
Revert these two patches for groovy.
[Test]
Test kernels for G-5.8 / F-5.8 can be found here:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
User Ted L confirmed that F-5.8 test kernel can fix the problem.
[Where problems could occur]
The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
[Original Bug Report]
I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
linux-restricted-modules-5.8.0-50-generic N/A
linux-backports-modules-5.8.0-50-generic N/A
linux-firmware1.187.11
RfKill:
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3405
dmi.board.asset.tag: Default string
dmi.board.name: H110T
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
Confirmed that the pmtu.sh testcase completes successfully with
groovy/linux 5.8.0-57.64.
** Tags added: verification-done-groovy
--
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/1931731
Title:
pmtu.sh from selftests.net in linux ADT test failure with
linux/5.8.0-56.63
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
Upstream commit 6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check
skb is large enough for IPv4/IPv6 header"), applied to groovy/linux 5.8.0-56.63
via upstream stable update (bug 1929132) introduced a regression caught by
kernel selftests, pmtu.sh from net testcase:
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link
layer MTU on geneve interface
[Fix]
The issue is fixed by d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve:
modify IP header check in geneve6_xmit_skb and geneve_xmit_skb"), which is
already applied for the next SRU cycle as part of upstream stable update (bug
1930766).
[Tests]
I have applied the fix on top of 5.8.0-56.63 and ran pmtu.sh and the whole
selftests.net suite. The testcase is now completed successfully and no other
regression was found.
[Where problems could occur]
The fix could be a partial fix not covering all corner cases, this could lead
to other failures with geneve tunnels.
[Original Description]
This is a scripted bug report about ADT failures while running linux tests
for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
Looks to be isolated to Groovy and appearing on all arches.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
arm64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz
02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects
[ OK ]
02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
[ OK ]
02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
[ OK ]
02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
[ OK ]
02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
[ OK ]
02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions
[ OK ]
02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions
[ OK ]
02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions
[ OK ]
02:56:51 DEBUG| [stdout] # TEST:
[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Observed with focal/linux: 5.4.0-76.85. -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 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: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
Observed with focal/linux: 5.4.0-76.85. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64
Observed with focal/linux: 5.4.0-76.85 amd64. ** Tags added: sru-20210531 -- 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/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux source package in Focal: Confirmed Bug description: This issue can be found on both ThunderX and Moonshot ARM64 <<>> incrementing stop Name: cpuhotplug04 Date: Thu Jul 11 08:34:50 UTC 2019 Desc: Does it prevent us from offlining the last CPU? sh: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:28:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
bserved with focal/linux: 5.4.0-76.85. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
Seen with focal/linux: 5.4.0-76.85. -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-te
[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1932159/+attachment/5505028/+files/make.log ** Also affects: bcmwl (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in bcmwl source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932159] [NEW] bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Public bug reported: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: bcmwl (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in bcmwl source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
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/1931731
Title:
pmtu.sh from selftests.net in linux ADT test failure with
linux/5.8.0-56.63
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
Upstream commit 6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check
skb is large enough for IPv4/IPv6 header"), applied to groovy/linux 5.8.0-56.63
via upstream stable update (bug 1929132) introduced a regression caught by
kernel selftests, pmtu.sh from net testcase:
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link
layer MTU on geneve interface
[Fix]
The issue is fixed by d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve:
modify IP header check in geneve6_xmit_skb and geneve_xmit_skb"), which is
already applied for the next SRU cycle as part of upstream stable update (bug
1930766).
[Tests]
I have applied the fix on top of 5.8.0-56.63 and ran pmtu.sh and the whole
selftests.net suite. The testcase is now completed successfully and no other
regression was found.
[Where problems could occur]
The fix could be a partial fix not covering all corner cases, this could lead
to other failures with geneve tunnels.
[Original Description]
This is a scripted bug report about ADT failures while running linux tests
for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
Looks to be isolated to Groovy and appearing on all arches.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
arm64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz
02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects
[ OK ]
02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
[ OK ]
02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
[ OK ]
02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
[ OK ]
02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
[ OK ]
02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions
[ OK ]
02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions
[ OK ]
02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions
[ OK ]
02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop
objects [ OK ]
02:56:53 DEBUG|
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
** Description changed:
- This is a scripted bug report about ADT failures while running linux
- tests for linux/5.8.0-56.63 on groovy. Whether this is caused by the
- dep8 tests of the tested source or the kernel has yet to be determined.
+ [Impact]
+ Upstream commit 6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check
skb is large enough for IPv4/IPv6 header"), applied to groovy/linux 5.8.0-56.63
via upstream stable update (bug 1929132) introduced a regression caught by
kernel selftests, net.pmtu.sh testcase:
+ 02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
+ 02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
+ 02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
+ 02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
+
+ [Fix]
+ The issue is fixed by d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve:
modify IP header check in geneve6_xmit_skb and geneve_xmit_skb"), which is
already applied for the next SRU cycle as part of upstream stable update (bug
1930766).
+
+ [Tests]
+ I have applied the fix on top of 5.8.0-56.63 and ran pmtu.sh and the whole
selftests.net suite. The testcase is now completed successfully and no other
regression was found.
+
+ [Where problems could occur]
+ The fix could be a partial fix not covering all corner cases, this could lead
to other failures with geneve tunnels.
+
+ [Original Description]
+ This is a scripted bug report about ADT failures while running linux tests
for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
Looks to be isolated to Groovy and appearing on all arches.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
arm64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz
-
-
02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects
[ OK ]
02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
[ OK ]
02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
[ OK ]
02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
[ OK ]
02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
[ OK ]
02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions
[ OK ]
02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions
[ OK ]
02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions
[ OK ]
02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop
objects [ OK ]
02:56:53 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions
[ OK ]
02:56:54 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions - nexthop
objects [ OK ]
02:56:56
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Groovy) Importance: Critical => High -- 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/1931731 Title: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: In Progress Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.8.0-56.63 on groovy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Looks to be isolated to Groovy and appearing on all arches. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz 02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh 02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [ OK ] 02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects [ OK ] 02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [ OK ] 02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects [ OK ] 02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects [ OK ] 02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects [ OK ] 02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [ OK ] 02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects [ OK ] 02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [ OK ] 02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects [ OK ] 02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [FAIL] 02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link layer MTU on geneve interface 02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects [FAIL] 02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding link layer MTU on geneve interface 02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects [ OK ] 02:56:53 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 02:56:54 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions - nexthop objects [ OK ] 02:56:56 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 02:56:57 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions - nexthop objects [ OK ] 02:56:58 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 02:56:59 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions - nexthop objects [ OK ] 02:57:01 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 02:57:02 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions - nexthop objects [ OK ] 02:57:03 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 02:57:04 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exce
[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Tags added: sru-20210531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Tags added: sru-20210531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
** Tags added: sru-20210531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
** Tags added: sru-20210531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 12 TINFO: Warming up pid: 1948 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 12 TFAIL: Process 1948 exited with 1 after warm up memcg_stat_rss 13 TINFO: Starting test 10 /opt/ltp/testcases/bin/memcg_stat_r
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: sru-20210531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: p
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
** Tags added: sru-20210531 -- 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/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 7 # ./reuseport_bpf_numa: node id/receive socket mismatch not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931731] Re: pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63
The issue was introduced by upstream commit
6628ddfec7580882f11fdc5c194a8ea781fdadfa ("net: geneve: check skb is
large enough for IPv4/IPv6 header") and it's fixed by
d13f048dd40e8577260cd43faea8ec9b77520197 ("net: geneve: modify IP header
check in geneve6_xmit_skb and geneve_xmit_skb"), which is already
applied for the next SRU cycle as part of upstream stable update (bug
1930766).
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: New => Confirmed
--
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/1931731
Title:
pmtu.sh from selftests.net in linux ADT test failure with
linux/5.8.0-56.63
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
Confirmed
Bug description:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.8.0-56.63 on groovy. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Looks to be isolated to Groovy and appearing on all arches.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/amd64/l/linux/20210610_035450_9c9b9@/log.gz
arm64:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/l/linux/20210611_103429_5c4be@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/ppc64el/l/linux/20210611_013418_76b18@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/s390x/l/linux/20210610_030630_fb359@/log.gz
02:56:31 DEBUG| [stdout] # selftests: net: pmtu.sh
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects
[ OK ]
02:56:31 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions
[ OK ]
02:56:32 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects
[ OK ]
02:56:33 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions
[ OK ]
02:56:34 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:35 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions
[ OK ]
02:56:36 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions - nexthop
objects [ OK ]
02:56:38 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions
[ OK ]
02:56:39 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:40 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions
[ OK ]
02:56:41 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions - nexthop
objects [ OK ]
02:56:43 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions
[ OK ]
02:56:44 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:45 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions
[ OK ]
02:56:46 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions - nexthop
objects [ OK ]
02:56:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions
[FAIL]
02:56:48 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:49 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions - nexthop
objects [FAIL]
02:56:49 DEBUG| [stdout] # PMTU exception wasn't created after exceeding
link layer MTU on geneve interface
02:56:50 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions
[ OK ]
02:56:51 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions - nexthop
objects [ OK ]
02:56:53 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions
[ OK ]
02:56:54 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions - nexthop
objects [ OK ]
02:56:56 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions
[ OK ]
02:56:57 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions - nexthop
objects [ OK ]
02:56:58 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions
[ OK ]
02:56:59 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions - nexthop
objects [ OK ]
02:57:01 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions
[ OK ]
02:57:02 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions - nexthop
objects [ OK ]
02:57:03 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions
[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable
** Tags added: sru-20210531 -- 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/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on Bionic 5.3.0-1033.35-aws TAP version 13 1..1 # selftests: memory-hotplug: mem-on-off-test.sh # Warning: file mem-on-off-test.sh is not executable, correct this. not ok 1 selftests: memory-hotplug: mem-on-off-test.sh make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ubuntu_ker:0242| == Summary === ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
Seen with focal/linux 5.4.0-75.84. ** Tags added: sru-20210531 -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bugs.la
[Kernel-packages] [Bug 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
** Changed in: linux-meta-aws (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-aws-5.8 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-azure (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-azure-5.8 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-gcp (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-gcp-5.8 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-meta-aws (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-aws-5.8 (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-azure (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-azure-5.8 (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-gcp-5.8 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: Fix Committed Status in linux-meta-aws-5.8 source package in Focal: Fix Committed Status in linux-meta-azure source package in Focal: Fix Committed Status in linux-meta-azure-5.8 source package in Focal: Fix Committed Status in linux-meta-gcp source package in Focal: Fix Committed Status in linux-meta-gcp-5.8 source package in Focal: Fix Committed Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
** Also affects: linux-meta-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-aws-5.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-gcp-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-gcp (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-gcp-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-gcp-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-aws-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-aws-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-aws (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-aws (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-gcp (Ubuntu Focal) Importance: Undecided => High ** Description changed: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. + The oracle kernels in focal don't need fixing as they do not produce a + linux-modules-extra-* package. + ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: New Status in linux-meta-aws-5.8 source package in Focal: New Status in linux-meta-azure source package in Focal: New Status in linux-meta-azure-5.8 source package in Focal: New Status in linux-meta-gcp source package in Focal: New Status in linux-meta-gcp-5.8 source package in Focal: New Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931576] [NEW] Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
Public bug reported:
[Impact]
ADT sets up the test environment by installing the image and modules-extra
package via the virtual provides
'kernel-testing--linux---full--preferred' and
'kernel-testing--linux---modules-extra--preferred'. If those are
not available, it falls back to using the real meta names as
'linux-image-' and 'linux-modules-extra-'.
The 5.4 cloud kernels in Focal are not providing the virtual packages
for 'kernel-testing--linux---modules-extra--preferred'. When
the tests falls back to 'linux-modules-extra-', the new 5.8
cloud kernels are pulled for the tests as they are now the default
sources.
ADT log:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz
[Fix]
The meta packages need to be fixed to provide the necessary virtual packages
for testing.
[Where problems could occur]
Adding new virtual meta packages could clash with existing names provided by
other sources. However, if they existed ADT would have pulled them.
** Affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-azure (Ubuntu Focal)
Importance: High
Assignee: Kleber Sacilotto de Souza (kleber-souza)
Status: New
** Affects: linux-meta-azure-5.8 (Ubuntu Focal)
Importance: High
Assignee: Kleber Sacilotto de Souza (kleber-souza)
Status: New
** Also affects: linux-meta-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-meta-azure (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-meta-azure (Ubuntu Focal)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
** Summary changed:
- Cloud kernels meta don't provide kernesl-testing--*--modules-extra--preferred
+ Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
** Also affects: linux-meta-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta-azure-5.8 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-meta-azure-5.8 (Ubuntu Focal)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1931576
Title:
Cloud kernels meta don't provide kernel-testing--*--modules-extra--
preferred
Status in linux-meta-azure package in Ubuntu:
New
Status in linux-meta-azure-5.8 package in Ubuntu:
New
Status in linux-meta-azure source package in Focal:
New
Status in linux-meta-azure-5.8 source package in Focal:
New
Bug description:
[Impact]
ADT sets up the test environment by installing the image and modules-extra
package via the virtual provides
'kernel-testing--linux---full--preferred' and
'kernel-testing--linux---modules-extra--preferred'. If those are
not available, it falls back to using the real meta names as
'linux-image-' and 'linux-modules-extra-'.
The 5.4 cloud kernels in Focal are not providing the virtual packages
for 'kernel-testing--linux---modules-extra--preferred'.
When the tests falls back to 'linux-modules-extra-', the
new 5.8 cloud kernels are pulled for the tests as they are now the
default sources.
ADT log:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz
[Fix]
The meta packages need to be fixed to provide the necessary virtual packages
for testing.
[Where problems could occur]
Adding new virtual meta packages could clash with existing names provided by
other sources. However, if they existed ADT would have pulled them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure/+bug/1931576/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: New Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg-tpi/+archive/ubuntu /cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
This patch has been applied to Groovy (20.10) via upstream stable update (bug 1929132). ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed -- 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/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930637] Re: ath11k WIFI not working in proposed kernel 5.11.0-19-generic
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
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/1930637
Title:
ath11k WIFI not working in proposed kernel 5.11.0-19-generic
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Bug 1928857 pulls stable patches from v5.11.20, which contains commit
dc764382762e {"bus: mhi: core: Process execution environment changes
serially") that cause a regression on ath11k cards and fails device
init:
mhi mhi0: MHI did not enter SBL
[Fix]
Upsteram commit 4884362f6977 ("bus: mhi: core: Download AMSS image
from appropriate function"), also landed to v5.12.6 but not v5.11
stable tree, has fixed this.
[Test Case]
Tested on Dell XPS 13 9310. No longer has this regression and both
WiFi/Bluetooth works fine as before.
[Where problems could occur]
The actual firmware downloading process is moved into a state machine
callback that has identical semantics with before. Additions or removals
to this in the future may change the timing of fw being dowloaded.
[Other Info]
While the commit causing this regress is backported to 5.11 onward and
fixed in v5.12 and 5.13, leaving Hirsute is the only victim.
== original bug report ==
See these references for more information:
- https://bugzilla.kernel.org/show_bug.cgi?id=213055
- https://bugs.archlinux.org/task/70849
Can you please prevent this already fixed bug from being introduced any
further into Ubuntu.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930637/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
The fix for this bug has been applied to 18.04 Bionic kernel as part of " Bionic update: upstream stable patchset 2021-05-25" (bug 1929603). ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- 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/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
