[Bug 1976116] Re: Focal update: v5.4.191 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976116 Title: Focal update: v5.4.191 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
Found on 2022.05.09/bionic/linux-gcp-fips/4.15.0-2035.38/g1-small ** Tags added: sru-20220509 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971479] Re: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)
Since we don't build i386 for lrm, I have released bionic as this issue isn't related to the kernel release. But when testing I did find that this issue can still be reproduced and leads to a build failure. I tested this with 4.15.0-176 in a i386 VM and could reproduce the failure to apply the buildfix which seems to lead to a build failure. ** Attachment added: "nvidia_file_2.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+attachment/5588603/+files/nvidia_file_2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971479 Title: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972006] Re: Bionic update: upstream stable patchset 2022-05-06
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972006 Title: Bionic update: upstream stable patchset 2022-05-06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970479] Re: Bionic update: upstream stable patchset 2022-04-26
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970479 Title: Bionic update: upstream stable patchset 2022-04-26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971480] Re: issuing invalid ioctl to /dev/vsock may spam dmesg
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971480 Title: issuing invalid ioctl to /dev/vsock may spam dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971479] [NEW] ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)
Public bug reported: There is a failure on ADT with nvidia-graphics-drivers-390 package starting when the package was updated to 390.147-0ubuntu0.18.04.1. This is the failure with bionic/linux 4.15.0-177.186 https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/n/nvidia-graphics-drivers-390/20220503_180848_8905f@/log.gz ... Loading new nvidia-390.147 DKMS files... Building for 4.15.0-177-generic Building for architecture i686 Building initial module for 4.15.0-177-generic Error! Application of patch buildfix_kernel_5.17.patch failed. Check /var/lib/dkms/nvidia/390.147/build/ for more information. ... That leads to ... tar: Cowardly refusing to create an empty archive Try 'tar --help' or 'tar --usage' for more information. autopkgtest [18:08:31]: test dkms-autopkgtest: ---] autopkgtest [18:08:32]: test dkms-autopkgtest: - - - - - - - - - - results - - - - - - - - - - dkms-autopkgtest FAIL non-zero exit status 123 autopkgtest [18:08:32]: summary dkms-autopkgtest FAIL non-zero exit status 123 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971479 Title: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
Hi Dries, Please do not feel a rush to validate the fix, I was more asking just to confirm personally that your issue has been resolved :) That message about dropping the fix is more of an empty threat by a bot than anything else.. So feel free at your earliest convenience to update and confirm that the new kernel fixes things for you. Best, - Luke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
Verification of the fix was confirmed by Chris Chiu when testing the patch changes. For now we will flip verification done for bionic and focal 5.4 kernels. We are also still waiting for confirmation from Dries Oeyen and Tilman Schmidt to confirm that they are also seeing their issues fixed. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968774] Re: LRMv6: add multi-architecture support
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968774 Title: LRMv6: add multi-architecture support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968932] Re: Bionic update: upstream stable patchset 2022-04-13
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968932 Title: Bionic update: upstream stable patchset 2022-04-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968751] Re: Devlink wasn't enabled from common config
** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968751 Title: Devlink wasn't enabled from common config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1968751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968751] Re: Devlink wasn't enabled from common config
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968751 Title: Devlink wasn't enabled from common config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1968751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
** Description changed:
- There have been reports by some users using certain intel xHCI
- controllers that their USB devices are not being detected after boot
- again after similar issues were previously found and fixed. This seems
- to be related to both [1][2] with the majority of the discussion on [1]
- about these problems reoccurring. This bug report is being made more for
- documentation of this new regression.
+ [SRU Justification]
+
+ [Impact]
+ There are users with certain intel xHCI controllers that are
+ experiencing problems with USB devices not being detected at boot.
+
+ This is because when the primary roothub is registered, device
+ enumeration happens before xHC is running and leads to devices not being
+ detected. This results in the error that looks something like
+ 'usb usb1-port3: couldn't allocate usb_device'.
+
+ [Fix]
+ Register both root hubs along with the secondary hcd for xhci.
+
+ This original fix was reverted upstream due to regressions that occured due to
+ racing that happened when both roothubs were registered simultaneously.
+ However with those fixes being addressed in commits
+ ("usb: hub: Fix usb enumeration issue due to address0 race")
+ ("usb: hub: Fix locking issues with address0_mutex")
+ the maintainers have stated that they will be reintroducing this commit.
+ So lets reintroduce it here to fix the issues that users are
+ experiencing.
+
+ [Test Case]
+ Confirmed by Chris Chiu that this issue exists on similiar hardware
+ reported by the users and that reverting these reverts fixes the issue
+ showing no signs of 'couldn't allocate usb_device' and with USB devices
+ available after boot.
+
+ [Regression Potential]
+ Should be low now that we carry the fixes that seemed to be caused by
+ this patch series.
+
+
+ There have been reports by some users using certain intel xHCI controllers
that their USB devices are not being detected after boot again after similar
issues were previously found and fixed. This seems to be related to both [1][2]
with the majority of the discussion on [1] about these problems reoccurring.
This bug report is being made more for documentation of this new regression.
These seems to be due to the patchset for [2] being reverted upstream
due to regressions.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968210
Title:
USB devices not detected during boot on USB 3.0 hubs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968210] [NEW] USB devices not detected during boot on USB 3.0 hubs
Public bug reported: There have been reports by some users using certain intel xHCI controllers that their USB devices are not being detected after boot again after similar issues were previously found and fixed. This seems to be related to both [1][2] with the majority of the discussion on [1] about these problems reoccurring. This bug report is being made more for documentation of this new regression. These seems to be due to the patchset for [2] being reverted upstream due to regressions. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Luke Nowakowski-Krijger (lukenow) Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - USB devices not detected during boot on USB 3.0 hubs + USB devices not detected during boot on USB 3.0 hubs ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968210 Title: USB devices not detected during boot on USB 3.0 hubs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Is it possible to test on a machine that is not in a secureboot default environment that experienced these issues? i.e. a non-core device. This would be to just confirm if the fix does anything. If so I put up the kernel .deb files with the possible fix here https://kernel.ubuntu.com/~lukenow/lp1939638/deferred_xhci. If that is possible please let me know if you are still experiencing these issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Hello Dries and Tilman, Thank you for providing the logs and other relevant information. For clarification, when you were testing if the issue still exists, was this from cold boot or warm boot? And if you sometimes see it working from cold boot it indeed seems to be very racey. There now should be a 100ms power-on-to-good delay on all usb 3.0 hubs since 5.4.0-97, which seems like it used to delay whatever race seems to be going on when the roothubs are being registered (as per the discussion here https://bugzilla.kernel.org/show_bug.cgi?id=214021), but maybe that isn't enough to avoid the race in your case? p.s. If you run lsusb -v as root you should be able to see the bPwrOn2PwrGood value of the root hubs as 100ms. Also, the patchset that seemed to directly address this issue got reverted due to regressions and never seemed to be re-addressed upstream... there seem to be a lot of fixes for those introduced problems since then though so maybe it would make sense to reintroduce those patches. I will send an email to the upstream usb mailing list asking about this and see what their thoughts are. Thanks, - Luke ** Bug watch added: Linux Kernel Bug Tracker #214021 https://bugzilla.kernel.org/show_bug.cgi?id=214021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Hi, would it be possible to provide the dmesg output after boot? Could you also provide the output of 'lspci -nn | grep USB' since since a lot of these issues seem to be USB card specific and I am unfamiliar with your hardware. As Jarkko mentioned, in 5.4.0-90 there were some patches that were reverted to do with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211 that might be now affecting your machines. Thanks, - Luke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959762] Re: HID_ASUS should depend on USB_HID in stable v4.15 backports
For Bionic, similar to focal, this was part of stable update (4.15.0-172) which doesn't need verification. The config also was the same after with HID_ASUS and USB_HID set to 'm'. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959762 Title: HID_ASUS should depend on USB_HID in stable v4.15 backports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
2022.02.21/bionic/linux/4.15.0-172.181 on dryden ** Tags added: sru-20220221 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
Found on 2022.01.31/xenial/kvm/4.4.0-1100.109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927533] Re: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig
Found on 2022.01.31/xenial/kvm/4.4.0-1100.109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927533 Title: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958299] Re: Support CIFS for CUDA
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958299 Title: Support CIFS for CUDA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1958299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957807] Re: Fix ct_state nat matching and nat action not being executed
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957807 Title: Fix ct_state nat matching and nat action not being executed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1957807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959119] Re: Fix sprintf usage that may lead to buffer overflow
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959119 Title: Fix sprintf usage that may lead to buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1959119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64
Found on instances akis exotic-skunk starmie-kernel 2022.01.31/bionic/linux/4.15.0-169.177 ** Tags added: sru-20220131 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat - This does not seem like a kernel regression as these errors did not - appear in the previous spin of kernels in the same cycle and seems like - an lxc test build failure of some kind. + These errors did not appear on previous kernels in the same cycle and + are now have a few tests failing on all architectures and systems as of + Feb 4th 2022 it seems. Log with details is attached in the comments. ** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and - are now have a few tests failing on all architectures and systems as of - Feb 4th 2022 it seems. Log with details is attached in the comments. + now have a few tests failing on all architectures and systems as of Feb + 4th 2022 it seems. Log with details is attached in the comments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
** Description changed: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat - This does not seem like a kernel regression as these errors did not appear in the previous spin of kernels in the same cycle and seems like a test build failure corresponding with the lxc/1:4.0.12-0ubuntu1 update. - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-dryden.ppc64el-ubuntu_lxc-log.txt - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-kernel04.s390x.zvm-ubuntu_lxc-log.txt - http://10.246.75.167/2022.01.03/focal/linux/5.4.0-99.112/sru-generic-metal-onibi.amd64-ubuntu_lxc-log.txt + This does not seem like a kernel regression as these errors did not + appear in the previous spin of kernels in the same cycle and seems like + an lxc test build failure of some kind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
My apologies, I looked at the change log from the focal branch of the lxc-pkg-ubuntu repo and pasted the package version I saw in the top commit. I updated the bug description with the package that the regression tests are installing which seems to be 1:4.0.6-0ubuntu1~20.04.1. And yes you're right I should not post internal links, was not thinking Friday evening... I will update the description and remove them. I attached the log, these errors seem to be affecting all of the architectures and systems and failing the same tests across everything. ** Attachment added: "sru-generic-metal-akis.amd64-ubuntu_lxc-log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+attachment/5559424/+files/sru-generic-metal-akis.amd64-ubuntu_lxc-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
** Summary changed: - lxc/1:4.0.12-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal + lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
** Description changed:
- All ftrace tests from selftests are failing with bionic:linux
- 4.15.0-168.176 on s390x:
+ SRU Justification
+
+ [Impact]
+
+ There seems to have been a typo in Commit 85bf17b28f97
+ ("recordmcount.pl: look for jgnop instruction as well as bcrl on s390")
+ that causes errors in finding mcount locations. This seems to cause problems
with ftrace initialization leading to not being able to use ftrace
+ functions.
+
+ [Fix]
+
+ Fix the typo by changing it to the correct instruction.
+
+ [Test Case]
+
+ Ftrace files in /sys/kernel/debug/tracing should be able to be read from
+ and written to with normal functionality. Ftrace selftests should now
+ pass.
+
+ [Where things could go wrong]
+
+ Its a simple typo fix so none really.
+
+ ---
+ All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176
on s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz
==
selftests: ftracetest
=== Ftrace unit tests ===
[1] Basic trace file check[FAIL]
[2] Basic test for tracers[FAIL]
[3] Basic trace clock test[FAIL]
[4] Basic event tracing check [FAIL]
[5] Snapshot and tracing setting [FAIL]
[6] event tracing - enable/disable with event level files [FAIL]
[7] event tracing - restricts events based on pid [FAIL]
[8] event tracing - enable/disable with subsystem level files [FAIL]
[9] event tracing - enable/disable with top level files [FAIL]
[10] ftrace - function graph filters with stack tracer[FAIL]
[11] ftrace - function graph filters [FAIL]
[12] ftrace - function pid filters[FAIL]
[13] ftrace - test for function event triggers[FAIL]
[14] ftrace - function profiler with function tracing [FAIL]
[15] ftrace - test reading of set_ftrace_filter [FAIL]
[16] ftrace - test for function traceon/off triggers [FAIL]
[17] Test creation and deletion of trace instances while setting an event
[FAIL]
[18] Test creation and deletion of trace instances[FAIL]
[19] Kprobe dynamic event - adding and removing [FAIL]
[20] Kprobe dynamic event - busy event check [FAIL]
[21] Kprobe dynamic event with arguments [FAIL]
[22] Kprobe event string type argument[FAIL]
[23] Kprobe event argument syntax [FAIL]
[24] Kprobes event arguments with types [FAIL]
[25] Kprobe event auto/manual naming [FAIL]
[26] Kprobe dynamic event with function tracer[FAIL]
[27] Kretprobe dynamic event with arguments [FAIL]
[28] Kretprobe dynamic event with maxactive [FAIL]
[29] Register/unregister many kprobe events [FAIL]
[30] event trigger - test multiple actions on hist trigger[FAIL]
[31] event trigger - test synthetic_events syntax parser [FAIL]
[32] event trigger - test event enable/disable trigger[FAIL]
[33] event trigger - test trigger filter [FAIL]
[34] event trigger - test histogram modifiers [FAIL]
[35] event trigger - test multiple histogram triggers [FAIL]
[36] event trigger - test snapshot-trigger[FAIL]
[37] event trigger - test stacktrace-trigger [FAIL]
[38] event trigger - test traceon/off trigger [FAIL]
[39] (instance) Basic test for tracers [FAIL]
[40] (instance) Basic trace clock test [FAIL]
[41] (instance) Snapshot and tracing setting [FAIL]
[42] (instance) event tracing - enable/disable with event level files
[FAIL]
[43] (instance) event tracing - restricts events based on pid[FAIL]
[44] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
[45] (instance) ftrace - test for function event triggers[FAIL]
[46] (instance) ftrace - test for function traceon/off triggers [FAIL]
[47] (instance) event trigger - test event enable/disable trigger[FAIL]
[48] (instance) event trigger - test trigger filter [FAIL]
[49] (instance) event trigger - test histogram modifiers [FAIL]
[50] (instance) event trigger - test multiple histogram triggers [FAIL]
# of passed: 0
# of failed: 50
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
not ok 1..1 selftests: ftracetest [FAIL]
==
After some debugging I've found out that the testcases are not actually
run, the failure happens while running
'tools/testing/selftests/ftrace/test.d/functions:initialize_ftrace()',
on the following line:
[ -f set_ftrace_filter ] && echo | tee set_ftrace_*
After a reboot for clean ftrace state, with kernel 4.15.0-168-generic:
root@kleber-bionic:/sys/kernel/debug/tracing# head set_ftrace_*
head: cannot open 'set_ftr
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)
** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942113 Here is a discussion about recent regressions in systemd tests where its stated that the cgroups are set up in "unified" (v2) mode in 248.3-1ubuntu5 systemd package. 248.3-1ubuntu7 became the release package on 2021-09-27 which was around the start of the cycle that we started seeing this issues (did we see this before then?), which means that it could very likely have been this upgrade that caused it. Even if earlier packages were in updates I am pretty sure that the machine needs to be restarted for the systemd changes to take affect, which I am pretty sure our test machines don't restart after updating during deployment. So it would make sense that we are seeing the errors correlating with the new systemd package hitting release. I also re-ran tests on previous kernels which didnt have these issues and they are now reporting all the errors, which also points to this being a problem with the systemd package upgrade. In the meantime, it seems that these tests are broken and we should just hint the whole ubuntu_ltp_controllers test suite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Description changed: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed - From investigation it seems there's an issue with the transition to - cgroup-v2, which on the ltp mailing list has been rumored that one of - these days the tests would break. Its likely this was caused by a - systemd update, switching to cgroup-v2 causing these tests to break due - to different mount and cgroup hierarchy semantics. + From investigation it seems there could be an issue with the transition + to cgroup-v2. There have been rumors on the ltp mailing list that one of + these days the tests could break due to the transition. Switching to + cgroup-v2, likely due to a systemd update, could cause these tests to + break due to different mount and cgroup hierarchy semantics. - After setting systemd.unified_cgroup_hierarchy=0 on the kernel command - line which sets cgroup back to v1, we get the expected failures that we - saw in previous cycles, pointing to this not being a kernel regression. + I could only reproduce a subset of the new failures we are seeing, but + after setting systemd.unified_cgroup_hierarchy=0 on the kernel command + line which sets cgroup back to v1, a lot of the failures I could produce + went away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Tags added: 5.13 hinted linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp- controllers ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] [NEW] ubuntu_ltp_controllers tests failing on Impish
Public bug reported: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13 hinted impish linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp-controllers ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927272] Re: Some kernel selftests fail on linux-kvm
** Tags added: 5.13 impish sru-20211018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944613] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944613 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Description changed: + [Impact] + + Test fails to build in selftests/seccomp/seccomp_bpf.c with + 'error: storage size of ‘md’ isn’t known' due to the type + struct seccomp_metadata not being defined for B/5.4 kernels. + + [Test case] + + Test successfully builds and test cases pass both on Bionic/5.4 and on + Focal + + [Fixes] + + Unconditionally define struct seccomp_metadata. + Remove linux/ptrace.h where a definition of seccomp_metadata is already being + defined in Focal. + + [Potential regression] + + There could be future build failures if glibc headers get updated to + include definitions of struct seccomp_metadata or if linux/ptrace.h gets updated + to include needed definitions. + + --- Issue found on 5.4.0-48.52~18.04.1 Test build failed with: gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘get_metadata’: seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] Makefile:12: recipe for target 'seccomp_bpf' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896420 Title: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944390 Title: Fix ignoring ct state match of OVS offload to TC/HW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1944390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946266] Re: Add psample tunnel support and also two fixes for psample issues.
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946266 Title: Add psample tunnel support and also two fixes for psample issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946393] Re: Fix byte count on fragmented packets in tc ct action
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946393 Title: Fix byte count on fragmented packets in tc ct action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934477] Re: ubuntu_aufs_smoke_test failed on F-OEM-5.13
Spotted on b/linux-gke-5.4 5.4.0-1052.55~18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934477 Title: ubuntu_aufs_smoke_test failed on F-OEM-5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943065] Re: mlxbf_gige: update driver version to 1.25
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942932] Re: oob_net0 up but stops processing Rx packets
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared)
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943484] Re: Focal update: v5.4.141 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943484 Title: Focal update: v5.4.141 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared)
Another build issue affecting B/5.4 kernels with __u64 for reference https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926142 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (error: ‘F_SEAL_FUTURE_WRITE’ undeclared) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1926142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837386] Re: test_maps from ubuntu_bpf failed with "FAIL:failed to create hashmap" on B-hwe i386
Very similar issue found on bionic/gcp-4.15 on 4.15.0-1109.123 only for n1-highcpu-4 instance. 18:45:34 DEBUG| Running './test_maps' 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:45:36 DEBUG| [stdout] Failed to create hashmap 'Cannot allocate memory'! 18:46:06 ERROR| [stderr] test_maps: test_maps.c:967: run_parallel: Assertion `status == 0' failed. With the rest of the threads reporting the same error. This issue also seems to be found in previous cycles on other instances as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837386 Title: test_maps from ubuntu_bpf failed with "FAIL:failed to create hashmap" on B-hwe i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Found on bionic/gcp-4.15 on 4.15.0-1109.123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Observed on F/gcp 5.4.0-1053.57 on e2-standard-2, f1-micro, n1-highcpu-4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821903] Re: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 (tsc_adjust)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821903 Title: svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.15 (tsc_adjust) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910312] Re: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4
Failure found on F/oracle 5.4.0-1055.59 on all instances in sru 2021-09-06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910312 Title: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1910312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943627] [NEW] Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl
Public bug reported: Found on Focal linux-gcp 5.11.0-1019.21 on g1-small instance. The tests are not able to mount on /dev/cpuctl which is causing cpu controller testing, latency tests, and cpuctl_test_fj to fail, seems to be only on g1-small instances. This error has been observed in previous cycles and is not a new regression. 20:09:23 DEBUG| [stdout] startup='Mon Sep 13 20:07:02 2021' 20:09:23 DEBUG| [stdout] TEST 1: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 3: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 4: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 5: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 97: /opt/ltp/output/cpuctl_results_stress-678.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 6: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 7: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 8: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 120: /opt/ltp/output/cpuctl_results_stress-9.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 9: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 127: /opt/ltp/output/cpuctl_results_stress-10.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 10: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 1 20:09:23 DEBUG| [stdout] TINFO The latency check task started 20:09:23 DEBUG| [stdout] FAIL The Latency test 1 failed 20:09:23 DEBUG| [stdout] Max latency observed = 123838 in Iteration 0 20:09:23 DEBUG| [stdout] The results FAIL is just intuitive and not exact failure. Please look at cpuctl_testplan.txt in the test directory. 20:09:23 DEBUG| [stdout] Task 763103 exited abnormally with return value: 1 20:09:23 DEBUG| [stdout] TBROK Test could'nt execute for expected duration 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] Cleanup done for latency test 1 20:09:23 DEBUG| [stdout] 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 2 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] cat: '/dev/cpuctl/group*/tasks': No such file or directory 20:09:23 DEBUG| [stdout] rmdir: failed to remove '/dev/cpuctl/group*': No such file or directory 20:09:23 DEBU
[Bug 1942472] Re: seccomp from ubuntu_kernel_selftests failed to build on B-5.4
*** This bug is a duplicate of bug 1896420 *** https://bugs.launchpad.net/bugs/1896420 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1896420 seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942472] Re: seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Description changed: Test build on B-5.4 (5.4.0-1054.58~18.04.1) failed with: error: storage size of ‘md’ isn’t known Build log: - * Command: - sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests - Exit status: 2 - Duration: 2.12612104416 - - stdout: - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' - 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/seccomp' - gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf - Makefile:12: recipe for target 'seccomp_bpf' failed - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' - Makefile:143: recipe for target 'all' failed - make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' - stderr: - seccomp_bpf.c: In function ‘get_metadata’: - seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known - struct seccomp_metadata md; - ^~ - seccomp_bpf.c:3029:26: warning: unused variable ‘md’ [-Wunused-variable] - make[1]: *** [seccomp_bpf] Error 1 - make: *** [all] Error 2 + * Command: + sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests + Exit status: 2 + Duration: 2.12612104416 + + stdout: + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' + 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/seccomp' + gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf + Makefile:12: recipe for target 'seccomp_bpf' failed + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' + Makefile:143: recipe for target 'all' failed + make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' + stderr: + seccomp_bpf.c: In function get_metadata’: + seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known + struct seccomp_metadata md; + ^~ + seccomp_bpf.c:3029:26: warning: unused variable unused variable ‘md’ [-Wunused-variable] + make[1]: *** [seccomp_bpf] Error 1 + make: *** [all] Error 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942472] [NEW] seccomp from ubuntu_kernel_selftests failed to build on B-5.4
Public bug reported: Test build on B-5.4 (5.4.0-1054.58~18.04.1) failed with: error: storage size of ‘md’ isn’t known Build log: * Command: sudo make -C linux/tools/testing/selftests TARGETS=seccomp run_tests Exit status: 2 Duration: 2.12612104416 stdout: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 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/seccomp' gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf Makefile:12: recipe for target 'seccomp_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp' Makefile:143: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: seccomp_bpf.c: In function get_metadata’: seccomp_bpf.c:3029:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3029:26: warning: unused variable unused variable ‘md’ [-Wunused-variable] make[1]: *** [seccomp_bpf] Error 1 make: *** [all] Error 2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Affects: linux-oracle-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: 5.4 bionic sru-20210816 ubuntu-kernel-selftests ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942472 Title: seccomp from ubuntu_kernel_selftests failed to build on B-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938748] Re: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.4 / H-oracle-5.11 ARM64
Observed on B/oracle 5.4.0-1054.58~18.04.1 with same instance problem on VM.Standard.A1.Flex-4c.8m -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938748 Title: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.4 / H-oracle-5.11 ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1938748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
Found new failures on bionic/linux-oracle/5.4.0-1054.58~18.04.1 on VM.DenseIO2.8 and VM.Standard2.1 2 newly added tests failed 18:12:43 DEBUG| [stdout] FAIL: all counters 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-0 18:12:43 DEBUG| [stdout] PASS: overflow: status-0 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-0 18:12:43 DEBUG| [stdout] PASS: overflow: irq-0 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-1 18:12:43 DEBUG| [stdout] PASS: overflow: status-1 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-1 18:12:43 DEBUG| [stdout] PASS: overflow: irq-1 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-2 18:12:43 DEBUG| [stdout] PASS: overflow: status-2 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-2 18:12:43 DEBUG| [stdout] PASS: overflow: irq-2 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-3 18:12:43 DEBUG| [stdout] PASS: overflow: status-3 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-3 18:12:43 DEBUG| [stdout] PASS: overflow: irq-3 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-4 18:12:43 DEBUG| [stdout] PASS: overflow: status-4 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-4 18:12:43 DEBUG| [stdout] PASS: overflow: irq-4 18:12:43 DEBUG| [stdout] PASS: cmask 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: cntr 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: status 18:12:43 DEBUG| [stdout] Unhandled exception 13 #GP at ip 0040127f 18:12:43 DEBUG| [stdout] error_code= rflags=00010002 cs=0008 18:12:44 DEBUG| [stdout] rax=00619cf5 rcx=0345 rdx=0002 rbx= 18:12:44 DEBUG| [stdout] rbp=00519f30 rsi=00418117 rdi=00619cf5 18:12:44 DEBUG| [stdout] r8= r9=0020 r10=000d r11=2492492492492493 18:12:44 DEBUG| [stdout] r12=07300402 r13=0603 r14= r15= 18:12:44 DEBUG| [stdout] cr0=80010011 cr2= cr3=01007000 cr4=0020 18:12:44 DEBUG| [stdout] cr8= 18:12:44 DEBUG| [stdout]STACK: @40127f 400338 18:12:44 DEBUG| [stdout] FAIL pmu ** Also affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.4 sru-20210816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853797 Title: pmu in ubuntu_kvm_unit_tests fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
