[Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4
Hello Anderson, Thank you for reporting the issue. We have a new kernel for 22.04 (version 5.15.0-102.112) that is about to be released in the next few days. Could you please test it again with this kernel and report the results? You can either enable -proposed in your system and update the kernel, or wait until it gets promoted to -updates and a simple dist- upgrate will update the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057960 Title: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter
** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058485 Title: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056354] Re: qat: Improve error recovery flows
This patchset was included in noble/linux 6.8.0-16.16 which has not been promoted to the -release pocket yet: linux | 6.8.0-11.11 | noble| source linux | 6.8.0-20.20 | noble-proposed | source Therefore I'm resetting the status to fix committed. ** Changed in: linux (Ubuntu Noble) 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/2056354 Title: qat: Improve error recovery flows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
Patch applied to noble/linux master-next branch: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next=158ef97059945d5a7ba3942d88fa691adb46d465 ** Changed in: linux (Ubuntu) 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/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
** Changed in: linux (Ubuntu Jammy) 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/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
** Changed in: linux (Ubuntu Jammy) 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/1975804 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1974017 Title: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974433] Re: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1974433 Title: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1968096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** Changed in: linux (Ubuntu Jammy) 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/1971417 Title: Fix REG_WAIT timeout for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
** Changed in: linux (Ubuntu Jammy) 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/1969326 Title: Enable hotspot feature for Realtek 8821CE To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
** Changed in: linux (Ubuntu Jammy) 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/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974111] Re: Mute/mic LEDs no function on Elitebook 630
** Changed in: linux (Ubuntu Jammy) 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/1974111 Title: Mute/mic LEDs no function on Elitebook 630 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972899] Re: [Regression] Real-time Kernel Build Failure
** Changed in: linux (Ubuntu Jammy) 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/1972899 Title: [Regression] Real-time Kernel Build Failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Changed in: linux-meta (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973831] Re: Bionic update: upstream stable patchset 2022-05-17
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) 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/1973831 Title: Bionic update: upstream stable patchset 2022-05-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972905] Re: Jammy update: v5.15.36 upstream stable release
Skipped b3745c947129 net/sched: cls_u32: fix netns refcount changes in u32_change() as it has already been applied as a fix for CVE-2022-29581. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-29581 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972905 Title: Jammy update: v5.15.36 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973085] Re: Focal update: v5.4.190 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/1973085 Title: Focal update: v5.4.190 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
** Changed in: linux (Ubuntu Jammy) 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot
** Changed in: linux (Ubuntu Jammy) 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/1958006 Title: multiple UBSAN warnings in Intel IPU6 camera driver at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964983] Re: IPU6 camera has no function on Andrews MLK
** Changed in: linux (Ubuntu Jammy) 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/1964983 Title: IPU6 camera has no function on Andrews MLK To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+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 Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942624] Re: NVMe devices fail to probe due to ACPI power state change
Tagging as verification-done-impish based on comment #12. Thank you! ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942624 Title: NVMe devices fail to probe due to ACPI power state change To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) 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/1837040 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952222] Re: io_uring regression - lost write request
Hello @metze, The Impish kernel with the patches for this issue is currently in -proposed. Could you please test this kernel to check whether it's fixed? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
Thadeu's patch "3c42e9542050 selftests/powerpc/spectre_v2: Return skip code when miss_percent is high" was merged on mainline for v5.17-rc1 and applied via upstream stable to jammy/linux for Ubuntu-5.15.0-19.19 and to impish/linux for Ubuntu-5.13.0-40.45. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
Manually marking focal/linux as 'Fix Released' as the fix was released under bug 1964634. ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967069] Re: Enable headset mic on Lenovo P360
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967069 Title: Enable headset mic on Lenovo P360 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942624] Re: NVMe devices fail to probe due to ACPI power state change
** Changed in: linux (Ubuntu Impish) 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/1942624 Title: NVMe devices fail to probe due to ACPI power state change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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 Impish) 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 1966188] Re: lxc: lxc-test-parse-config-file failure on Jammy (retrieved value "" for config key "lxc.selinux.context")
I can still see the issue from bug 1943441 with impish:linux. However,
with one of the s390x systems (s2lp4 which is a lpar), I only get the
second error reported on this bug:
STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1649849603timeout=1200
localtime=Apr 13 11:33:23
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
Waiting for pid 62280 for 1200 seconds
System python is too old, crash handling disabled
Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
[stderr] parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
[stderr]
[stderr] parse_config_file.c: 580: main: lxc.seccomp.profile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966188
Title:
lxc: lxc-test-parse-config-file failure on Jammy (retrieved value ""
for config key "lxc.selinux.context")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1966188/+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
This bug is awaiting verification that the linux/5.4.0-109.123 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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 1966499] Re: Recent 5.13 kernel has broken KVM support
** Changed in: linux (Ubuntu Impish) 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/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952222] Re: io_uring regression - lost write request
** Changed in: linux (Ubuntu Impish) Status: Confirmed => 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/195 Title: io_uring regression - lost write request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943441] Re: lxc: lxc-test-parse-config-file failure
The issue is still reproducible in Impish (lxc 1:4.0.12-0ubuntu1~21.10.1) ** Also affects: lxc (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Impish) 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/1943441 Title: lxc: lxc-test-parse-config-file failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 Tilman, The fix for this bug report was already released in the past and marked as "Fix Released". In this case the regression is handled by a new bug report and we usually keep the original one without duplicating it. -- 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 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/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
** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress -- 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
Hi, We have identified a fix for this issue and opened a new bug report for it: bug 1968210. Please use this bug from now on for updates and feedback about this regression. Thank you. -- 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 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
Hello John, Thank you for verifying the fix. The verification-needed tag was not added automatically for Focal because the commit contains only the link to the upstream stable update https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964634. I'll add the tag manually to flag that it has been verified. Thank you! ** 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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967892] Re: Fix flow table lookup failure with no originating ifindex
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** 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/1967892 Title: Fix flow table lookup failure with no originating ifindex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1967892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
For Impish, I have cherry-picked the fix from the pull-request for bug 1966021 and applied to the master-next branch and it will be included in the current kernel SRU cycle re-spin. Note that for Focal the patch was already applied for a re-spin and I wasn't able to include the additional BugLink to the commit message, therefore this bug report won't receive automatic updates about the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965160] Re: linux: Fix failure in ubuntu_boot:log_check test
** Changed in: linux (Ubuntu Xenial) 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/1965160 Title: linux: Fix failure in ubuntu_boot:log_check test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42
** Summary changed: - systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42 + systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42
** Description changed: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. 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-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz + + The "tests-in-lxd" testcase is failing with all kernels in Impish: + + test_no_failed (__main__.ServicesTest) + No failed units ... journal for failed service snap-lxd-22662.mount --- + -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for lxd, revision 22662... + Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: mount failed: Operation not permitted. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Mount process exited, code=exited, status=1/FAILURE + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Failed with result 'exit-code'. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for lxd, revision 22662. + journal for failed service snap-snapd-15177.mount --- + -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for snapd, revision 15177... + Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: mount failed: Operation not permitted. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Mount process exited, code=exited, status=1/FAILURE + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Failed with result 'exit-code'. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for snapd, revision 15177. + FAIL + [...] + == + FAIL: test_no_failed (__main__.ServicesTest) + No failed units + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed + self.assertEqual(failed, []) + AssertionError: Lists differ: ['snap-lxd-22662.mount loaded failed fai[119 chars]177'] != [] + + First list contains 2 additional elements. + First extra element 0: + 'snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision 22662' + + + [] + - ['snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision ' + - '22662', + - 'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, revision ' + - '15177'] + + + This testcase started to fail with the latest re-spin of the kernels (uploaded on mar-16), however the only patch applied between the previous kernels and the current ones is a CVE fix which is unlikely to be causing this failure: + + "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()" + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965293] [NEW] systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. 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-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (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/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Adding verification-done-impish based on comment #14. Thank you for the verification. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
The log_check WARNINGs with the 4.4 kernels is being addressed by bug
1965160 with commit 036e9ef8becd ("dmaengine: Replace WARN_TAINT_ONCE()
with pr_warn_once()").
This commit has been applied upstream for v4.13-rc1, so from bionic+ we
should have only the kernel tainted failure. However, that commit keeps
the TAINT_FIRMWARE_WORKAROUND taint flag and this is still true for
mainline, so probably this bug can't be fixed as this is a hardware
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912316
Title:
log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud
node grumman (failed with flag 2048)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965160] Re: linux: Fix failure in ubuntu_boot:log_check test
** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965160 Title: linux: Fix failure in ubuntu_boot:log_check test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963948] Re: Fix flow table lookup after ct clear or switching zones
** 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) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963948 Title: Fix flow table lookup after ct clear or switching zones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1963948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Patch sent upstream: https://marc.info/?l=linux- netdev=164674758624957=2 ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958973] Re: impish:linux: icmp.sh from selftests.net fails
This seems to be a flaky test, it has also failed with impish:linux 5.13.0-32.35 after completing successfully during the previous test run. ** Summary changed: - impish:linux-riscv: icmp.sh from selftests.net fails + impish:linux: icmp.sh from selftests.net fails -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958973 Title: impish:linux: icmp.sh from selftests.net fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
** Tags added: 5.13 impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H/I
** Changed in: linux (Ubuntu Impish) 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/1923683 Title: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H/I To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960430] Re: IPsec tunnel mode fix inner_ipproto setting in sec_path
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960430 Title: IPsec tunnel mode fix inner_ipproto setting in sec_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
This is clearly an endianness issue. I'll investigate whether the testcase needs to adapt to it or the sysfs interface of the netdevsim device needs to follow a pattern no matter what the system's endianness. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
This is also affecting jammy/linux 5.15.0-22.22. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Also found with impish/linux 5.13.0-32.35. ** Tags added: 5.13 impish 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 found with impish/linux 5.13.0-32.35. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** 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/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]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
** Changed in: linux-oem-5.10 (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948724] Re: udpgro_fwd from selftests/net fails ADT test failure with impish
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Tags added: 5.13 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/1948724 Title: udpgro_fwd from selftests/net fails ADT test failure with impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
Confirmed that impish/linux 5.13.0-32.35 and focal/linux 5.4.0-102.115 are not failing to boot on any AWS instance. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961968 Title: Broken network on some AWS instances with focal/impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956780] Re: 5.15 stuck at boot on c4.large
The same issue is also affecting focal and impish kernels (bug 1961968). The same solution is being applied to those kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956780 Title: 5.15 stuck at boot on c4.large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1961968 Title: Broken network on some AWS instances with focal/impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
This was already fixed in Jammy/linux by reverting the same patch. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961968 Title: Broken network on some AWS instances with focal/impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels
SRU requested: https://lists.ubuntu.com/archives/kernel-team/2022-February/128266.html ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961968 Title: Broken network on some AWS instances with focal/impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961968] [NEW] Broken network on some AWS instances with focal/impish kernels
Public bug reported: [Impact] With the latest focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances fail to boot. This impacts mostly the instance types: c4.large, c3.xlarge and x1e.xlarge. However, not all instances deployed on those types will fail. This is affecting mostly c4.large which fails about 80-90% of all deployments. This was traced to be caused by the network interface failing to come up. The following console log snippets from 5.4.0-101-generic on a c4.large show some hints of what's going on: [...] [3.990368] unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x8ea733c8 (native_read_msr+0x8/0x40) [3.998463] Call Trace: [4.001164] ? set_rdt_options+0x91/0x91 [4.004864] resctrl_late_init+0x592/0x63c [4.008711] ? set_rdt_options+0x91/0x91 [4.012452] do_one_initcall+0x4a/0x200 [4.016115] kernel_init_freeable+0x1c0/0x263 [4.020402] ? rest_init+0xb0/0xb0 [4.024889] kernel_init+0xe/0x110 [4.029245] ret_from_fork+0x35/0x40 [...] [7.718268] ena: The ena device sent a completion but the driver didn't receive a MSI-X interrupt (cmd 8), autopolling mode is OFF [7.727036] ena: Failed to submit get_feature command 12 error: -62 [7.731691] ena :00:03.0: Cannot init indirect table [7.735636] ena :00:03.0: Cannot init RSS rc: -62 [7.740700] ena: probe of :00:03.0 failed with error -62 [...] [Fix] Reverting the following upstream stable commit fixes the issue: 83dbf898a2d4 PCI/MSI: Mask MSI-X vectors only on success [Test Case] Boot an affected AWS instance type with focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels with the mentioned patch reverted. Then boot with the original kernels. It should boot successfully with the reverted patch but fail with the original kernels. [Regression Potential] The patch description mentions fixing a MSI-X issue with a Marvell NVME device, which doesn't seem to be following the PCI-E specification. Reverting this commit will keep the issue on systems with that particular NVME device unfixed. As of now there is no follow-up fix for this commit upstream, we might need to keep an eye on any change and re-apply it in case a fix is found. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Description changed: [Impact] - - With the latest focal/linux (5.4.0-101.114) and impish/linux - (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances - fail to boot. This impacts mostly the instance types: c4.large, - c3.xlarge and x1e.xlarge. However, not all instances deployed on those - types will fail. This is affecting mostly c4.large which fails about - 80-90% of all deployments. + With the latest focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances fail to boot. This impacts mostly the instance types: c4.large, c3.xlarge and x1e.xlarge. However, not all instances deployed on those types will fail. This is affecting mostly c4.large which fails about 80-90% of all deployments. This was traced to be caused by the network interface failing to come up. The following console log snippets from 5.4.0-101-generic on a c4.large show some hints of what's going on: [...] [3.990368] unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x8ea733c8 (native_read_msr+0x8/0x40) [3.998463] Call Trace: [4.001164] ? set_rdt_options+0x91/0x91 [4.004864] resctrl_late_init+0x592/0x63c [4.008711] ? set_rdt_options+0x91/0x91 [4.012452] do_one_initcall+0x4a/0x200 [4.016115] kernel_init_freeable+0x1c0/0x263 [4.020402] ? rest_init+0xb0/0xb0 [4.024889] kernel_init+0xe/0x110 [4.029245] ret_from_fork+0x35/0x40 [...] [7.718268] ena: The ena device sent a completion but the driver didn't receive a MSI-X interrupt (cmd 8), autopolling mode is OFF [7.727036] ena: Failed to submit get_feature command 12 error: -62 [7.731691] ena :00:03.0: Cannot init indirect table [7.735636] ena :00:03.0: Cannot init RSS rc: -62 [7.740700] ena: probe of :00:03.0 failed with error -62 [...] [Fix] Reverting the following upstream stable commit fixes the issue: 83dbf898a2d4 PCI/MSI: Mask MSI-X vectors only on success [Test Case] Boot an affected AWS instance type with focal/linux (5.4.0-101.114) and
[Bug 1953689] Re: smartpqi: Update 20.04.4 to latest kernel.org patch level
Confirmed the driver to be updated on impish/linux and focal/linux- hwe-5.13: * Impish $ uname -a Linux autopkgtest 5.13.0-30-generic #33-Ubuntu SMP Fri Feb 4 17:03:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ modinfo smartpqi | grep "^version:" version:2.1.12-055 * Focal $ uname -a Linux autopkgtest-focal 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ modinfo smartpqi | grep "^version:" version:2.1.12-055 ** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953689 Title: smartpqi: Update 20.04.4 to latest kernel.org patch level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941829] Re: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
Issues not detected on impish/linux 5.13.0-30.33. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960427] Re: Add inner_ipproto into sec_path
** 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/1960427 Title: Add inner_ipproto into sec_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Changed in: linux (Ubuntu Impish) 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/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Changed in: linux (Ubuntu Impish) 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/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
** 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/1961076 Title: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux- hwe-5.4/5.4.0-100.113~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1961076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
** Description changed: - This is a scripted bug report about ADT failures while running linux- - hwe-5.4 tests for linux-hwe-5.4/5.4.0-100.113~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. + The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4 + 5.4.0-100.113~18.04.1 on ADT, only on ppc64el. Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz - - The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4 - 5.4.0-100.113~18.04.1 on ADT, only on ppc64el. 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] stress-ng 0.13.11 g48be8ff4ffc4 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] system: Linux autopkgtest 5.4.0-100-generic #113~18.04.1-Ubuntu SMP Mon Feb 7 15:02:55 UTC 2022 ppc64le 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] RAM total: 7.9G, RAM free: 3.3G, swap free: 1023.9M 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 processors online, 4 processors configured 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] setting to a 5 second run per stressor 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] dispatching hogs: 4 dev-shm 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: using cache maximum level L1 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: shared cache buffer size: 32K 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] starting stressors 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: started [26899] (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: started [26900] (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: started [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: started [26902] (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 stressors started 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) was possibly killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: exited [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26901] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] terminated 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] successful run completed in 5.06s 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 corrupted bogo-ops counter, 14 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 hash error in bogo-ops counter and run flag, 2146579844 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] metrics-check: stressor metrics corrupted, data is compromised - 11:35:08 DEBUG| [stdout] + 11:35:08 DEBUG| [stdout] 11:35:08 DEBUG| [stdout] [ 3840.094607] stress-ng invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=1000 11:35:08 DEBUG| [stdout] [ 3840.094611] CPU: 2 PID:
[Bug 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
** Description changed: This is a scripted bug report about ADT failures while running linux- hwe-5.4 tests for linux-hwe-5.4/5.4.0-100.113~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: - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz + + The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4 + 5.4.0-100.113~18.04.1 on ADT, only on ppc64el. + + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] stress-ng 0.13.11 g48be8ff4ffc4 + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] system: Linux autopkgtest 5.4.0-100-generic #113~18.04.1-Ubuntu SMP Mon Feb 7 15:02:55 UTC 2022 ppc64le + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] RAM total: 7.9G, RAM free: 3.3G, swap free: 1023.9M + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 processors online, 4 processors configured + 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] setting to a 5 second run per stressor + 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] dispatching hogs: 4 dev-shm + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: using cache maximum level L1 + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: shared cache buffer size: 32K + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] starting stressors + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: started [26899] (instance 0) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: started [26900] (instance 1) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: started [26901] (instance 2) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: started [26902] (instance 3) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 stressors started + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 0) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 3) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 2) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 1) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) terminated on signal: 9 (Killed) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) was killed by the OOM killer + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] terminated + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) terminated on signal: 9 (Killed) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) was possibly killed by the OOM killer + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] terminated + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: exited [26901] (instance 2) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26901] terminated + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) terminated on signal: 9 (Killed) + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) was killed by the OOM killer + 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] terminated + 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] successful run completed in 5.06s + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 corrupted bogo-ops counter, 14 vs 0 + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 hash error in bogo-ops counter and run flag, 2146579844 vs 0 + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 corrupted bogo-ops counter, 13 vs 0 + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 hash error in bogo-ops counter and run flag, 1093487894 vs 0 + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 corrupted bogo-ops counter, 13 vs 0 + 11:35:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 hash error in bogo-ops counter and run flag, 1093487894 vs 0 + 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] metrics-check: stressor metrics corrupted, data is compromised + 11:35:08 DEBUG| [stdout] + 11:35:08 DEBUG| [stdout] [ 3840.094607] stress-ng invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=1000 + 11:35:08 DEBUG| [stdout] [ 3840.094611] CPU: 2 PID: 26903
[Bug 1961076] [NEW] linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
Public bug reported: This is a scripted bug report about ADT failures while running linux- hwe-5.4 tests for linux-hwe-5.4/5.4.0-100.113~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: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz ** Affects: stress-ng Importance: Undecided Status: New ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux-hwe-5.4 ADT test failure with linux-hwe-5.4/5.4.0-100.113~18.04.1 + linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1 ** Also affects: linux-hwe-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: stress-ng (Ubuntu) Importance: Undecided Status: New ** Also affects: stress-ng Importance: Undecided Status: New ** No longer affects: stress-ng (Ubuntu) ** No longer affects: stress-ng (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961076 Title: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux- hwe-5.4/5.4.0-100.113~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1961076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951135] Re: hirsute:linux-aws ubuntu_ltp Failed test cases : read_all_proc
Also found on impish/linux 5.13.0-28.31 running generic-64k on a arm64 box. ** Tags added: 5.13 impish 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/1951135 Title: hirsute:linux-aws ubuntu_ltp Failed test cases : read_all_proc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951135/+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
This patch was also already applied to Bionic via " Bionic update: upstream stable patchset 2022-01-27" (bug 1959335). ** 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/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 1959709] Re: Bionic update: upstream stable patchset 2022-02-01
** 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/1959709 Title: Bionic update: upstream stable patchset 2022-02-01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959335] Re: Bionic update: upstream stable patchset 2022-01-27
Skipped patch 358926f3c499 "recordmcount.pl: fix typo in s390 mcount regex" as it has already been applied for Ubuntu-4.15.0-169.177. ** 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/1959335 Title: Bionic update: upstream stable patchset 2022-01-27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959335/+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
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: Fix Committed => Invalid -- 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 1958299] Re: Support CIFS for CUDA
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: Fix Committed => Invalid -- 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 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
Confirmed that systemd storage testacase is now successful with impish:linux 5.13.0-30.33: amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220207_183233_91879@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220207_164846_df7a7@/log.gz ppc64el - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220207_155813_b0af1@/log.gz ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960034 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960034/+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
Attached is the testcase log from the run with the previous focal:linux kernel version (5.4.0-97.110). I believe that it's very unlikely that this issue is caused by a kernel change. Between versions 5.4.0-97.110 and 5.4.0-99.112 only a few cifs patches were reverted to fix a regression (https://launchpad.net/ubuntu/+source/linux/5.4.0-99.112). These patches were applied to 5.4.0-97.110 and reverted on 5.4.0-99.112. I haven't looked at the lxc testcases, but cifs changes should unlikely cause lxc failures. ** Attachment added: "sru-generic-metal-akis.amd64-5.4.0-97.110-ubuntu_lxc-log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+attachment/5559658/+files/sru-generic-metal-akis.amd64-5.4.0-97.110-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 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
All ubuntu_kernel_selftests.ftrace:ftracetest tests completed successfully with bionic:linux 4.15.0-169.177: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/s390x/l/linux/20220207_154815_bf623@/log.gz ** 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/1959752 Title: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958228] Re: aufs build is broken on 5.11 kernels
Only a few 5.11 kernels have AUFS config enabled and focal:linux- hwe-5.11 is not one of them, so the fix cannot be verified with this kernel. However, this fix has been cherry-picked by focal:linux- oracle-5.11 and focal:linux-riscv-5.11 by versions which were already promoted to -updates: https://launchpad.net/ubuntu/+source/linux-oracle-5.11/5.11.0-1028.31~20.04.1 https://launchpad.net/ubuntu/+source/linux-riscv-5.11/5.11.0-1029.32~20.04.1 Therefore I will mark this bug as verified in Focal. ** 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/1958228 Title: aufs build is broken on 5.11 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958228] Re: aufs build is broken on 5.11 kernels
Changing nomination from hirsute/linux to focal/linux-hwe-5.11 as Hirsute has reached EOL. ** Also affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958228 Title: aufs build is broken on 5.11 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
For the record, this is the stack trace produced by the 'storage' systemd testcase: Feb 4 12:47:07 autopkgtest kernel: [ 119.567510] BUG: kernel NULL pointer dereference, address: 0030 Feb 4 12:47:07 autopkgtest kernel: [ 119.568255] #PF: supervisor read access in kernel mode Feb 4 12:47:07 autopkgtest kernel: [ 119.568712] #PF: error_code(0x) - not-present page Feb 4 12:47:07 autopkgtest kernel: [ 119.569243] PGD 8ab43067 P4D 8ab43067 PUD b07c067 PMD 0 Feb 4 12:47:07 autopkgtest kernel: [ 119.569880] Oops: [#1] SMP PTI Feb 4 12:47:07 autopkgtest kernel: [ 119.570195] CPU: 0 PID: 787 Comm: python3 Not tainted 5.13.0-29-generic #32-Ubuntu Feb 4 12:47:07 autopkgtest kernel: [ 119.570940] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Feb 4 12:47:07 autopkgtest kernel: [ 119.571732] RIP: 0010:blk_mq_cancel_work_sync+0x5/0x60 Feb 4 12:47:07 autopkgtest kernel: [ 119.572232] Code: 4c 89 f7 e8 8d 13 00 00 e9 4b ff ff ff 48 8b 45 d0 49 89 85 e8 00 00 00 31 c0 eb a0 b8 ea ff ff ff eb c1 66 90 0f 1f 44 00 00 <48> 83 7f 30 00 74 45 55 48 89 e5 41 54 49 89 fc 48 8d bf f8 04 00 Feb 4 12:47:07 autopkgtest kernel: [ 119.573881] RSP: 0018:a78a40dd7960 EFLAGS: 00010246 Feb 4 12:47:07 autopkgtest kernel: [ 119.574339] RAX: RBX: 9b3ec7df7b00 RCX: 0286 Feb 4 12:47:07 autopkgtest kernel: [ 119.574938] RDX: a78a40dd7920 RSI: 875ac156 RDI: Feb 4 12:47:07 autopkgtest kernel: [ 119.575545] RBP: a78a40dd7978 R08: 9b3ecbd347c0 R09: Feb 4 12:47:07 autopkgtest kernel: [ 119.576147] R10: R11: 9b3ec229bb90 R12: 9b3ecbd34520 Feb 4 12:47:07 autopkgtest kernel: [ 119.576756] R13: R14: R15: 9b3ec82d21d8 Feb 4 12:47:07 autopkgtest kernel: [ 119.577350] FS: 7fd4d6a39c00() GS:9b3f3dc0() knlGS: Feb 4 12:47:07 autopkgtest kernel: [ 119.578040] CS: 0010 DS: ES: CR0: 80050033 Feb 4 12:47:07 autopkgtest kernel: [ 119.578537] CR2: 0030 CR3: 0b072000 CR4: 06f0 Feb 4 12:47:07 autopkgtest kernel: [ 119.579168] Call Trace: Feb 4 12:47:07 autopkgtest kernel: [ 119.579399] Feb 4 12:47:07 autopkgtest kernel: [ 119.579591] ? disk_release+0x24/0xa0 Feb 4 12:47:07 autopkgtest kernel: [ 119.579939] device_release+0x3b/0xa0 Feb 4 12:47:07 autopkgtest kernel: [ 119.580268] kobject_cleanup+0x44/0x150 Feb 4 12:47:07 autopkgtest kernel: [ 119.580617] kobject_put+0x53/0x70 Feb 4 12:47:07 autopkgtest kernel: [ 119.580924] put_device+0x13/0x20 Feb 4 12:47:07 autopkgtest kernel: [ 119.581288] put_disk+0x1b/0x20 Feb 4 12:47:07 autopkgtest kernel: [ 119.581653] sg_device_destroy+0x54/0x90 Feb 4 12:47:07 autopkgtest kernel: [ 119.582003] sg_remove_device+0x128/0x170 Feb 4 12:47:07 autopkgtest kernel: [ 119.582354] device_del+0x138/0x3e0 Feb 4 12:47:07 autopkgtest kernel: [ 119.582659] device_unregister+0x1b/0x60 Feb 4 12:47:07 autopkgtest kernel: [ 119.583002] __scsi_remove_device+0x110/0x150 Feb 4 12:47:07 autopkgtest kernel: [ 119.583403] scsi_forget_host+0x5f/0x70 Feb 4 12:47:07 autopkgtest kernel: [ 119.583744] scsi_remove_host+0x77/0x110 Feb 4 12:47:07 autopkgtest kernel: [ 119.584091] sdebug_driver_remove+0x4c/0xb0 [scsi_debug] Feb 4 12:47:07 autopkgtest kernel: [ 119.584555] __device_release_driver+0x181/0x240 Feb 4 12:47:07 autopkgtest kernel: [ 119.584961] device_release_driver+0x29/0x40 Feb 4 12:47:07 autopkgtest kernel: [ 119.585334] bus_remove_device+0xe1/0x150 Feb 4 12:47:07 autopkgtest kernel: [ 119.585682] device_del+0x19c/0x3e0 Feb 4 12:47:07 autopkgtest kernel: [ 119.585986] device_unregister+0x1b/0x60 Feb 4 12:47:07 autopkgtest kernel: [ 119.586326] sdebug_do_remove_host+0xd9/0xf0 [scsi_debug] Feb 4 12:47:07 autopkgtest kernel: [ 119.586797] add_host_store+0xe0/0x100 [scsi_debug] Feb 4 12:47:07 autopkgtest kernel: [ 119.587232] ? __virt_addr_valid+0x49/0x70 Feb 4 12:47:07 autopkgtest kernel: [ 119.587597] drv_attr_store+0x24/0x30 Feb 4 12:47:07 autopkgtest kernel: [ 119.587917] sysfs_kf_write+0x3e/0x50 Feb 4 12:47:07 autopkgtest kernel: [ 119.588248] kernfs_fop_write_iter+0x137/0x1c0 Feb 4 12:47:07 autopkgtest kernel: [ 119.588653] new_sync_write+0x114/0x1a0 Feb 4 12:47:07 autopkgtest kernel: [ 119.589042] vfs_write+0x1bd/0x250 Feb 4 12:47:07 autopkgtest kernel: [ 119.589384] ksys_write+0x67/0xe0 Feb 4 12:47:07 autopkgtest kernel: [ 119.589767] __x64_sys_write+0x19/0x20 Feb 4 12:47:07 autopkgtest kernel: [ 119.590159] do_syscall_64+0x61/0xb0 Feb 4 12:47:07 autopkgtest kernel: [ 119.590565] ? handle_mm_fault+0xda/0x2c0 Feb 4 12:47:07 autopkgtest kernel: [ 119.590993] ? do_user_addr_fault+0x1d0/0x660 Feb 4 12:47:07 autopkgtest kernel: [ 119.591435] ?
[Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
** 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/1959752 Title: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959752/+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
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959752 Title: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959752/+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
The regression was introduced by the following commit applied to bionic:linux: commit 699bf409d4d2895733d3e2f2eb01166d141650ce Author: Jerome Marchand Date: Fri Dec 10 10:38:27 2021 +0100 recordmcount.pl: look for jgnop instruction as well as bcrl on s390 BugLink: https://bugs.launchpad.net/bugs/1957957 commit 85bf17b28f97ca2749968d8786dc423db320d9c2 upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959752 Title: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959752] [NEW] ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
Public bug reported: 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_ftrace_filter' for reading: No such device head: cannot open 'set_ftrace_notrace' for reading: No such device ==> set_ftrace_pid <== no pid With kernel 4.15.0-167-generic: root@kleber-bionic-2:/sys/kernel/debug/tracing# head set_ftrace_* ==> set_ftrace_filter <== all functions enabled ==> set_ftrace_notrace <== no functions disabled ==> set_ftrace_pid <== no pid ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Description changed: All ftrace tests
