[Kernel-packages] [Bug 2049065] [NEW] netfilter: nf_nat: fix action not being set for all ct states
Public bug reported: Long story short there is a regression that affects the datapath of Open vSwitch based systems starting with the 6.2 kernel which is fixed by [0]. 0: https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049065 Title: netfilter: nf_nat: fix action not being set for all ct states Status in linux package in Ubuntu: New Bug description: Long story short there is a regression that affects the datapath of Open vSwitch based systems starting with the 6.2 kernel which is fixed by [0]. 0: https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040524] Re: openvswitch fails on raspberry pi 4
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2040524 Title: openvswitch fails on raspberry pi 4 Status in microovn: New Status in linux-raspi package in Ubuntu: New Bug description: I have a homelab and I'm experimenting with adding arm nodes to my existing cluster. MicroOVN works fine on my x86_64 nodes but fails on my arm nodes (raspberry pi 4). I am using microovn 22.03/stable (rev 295). When I run "microovn init" on the arm nodes, I get the error Error: Post "http://control.socket/cluster/control": context deadline exceeded The output from "snap services microovn" is: Service Startup Current Notes microovn.central disabled inactive - microovn.chassis enabled active- microovn.daemon enabled active- microovn.ovn-northd disabled inactive - microovn.ovn-ovsdb-server-nb disabled inactive - microovn.ovn-ovsdb-server-sb disabled inactive - microovn.refresh-expiring-certs enabled inactive timer-activated microovn.switch enabled inactive - The output from "systemctl | grep ovn" is: run-snapd-ns-microovn.mnt.mount loaded active mounted /run/snapd/ns/microovn.mnt snap-microovn-301.mount loaded active mounted Mount unit for microovn, revision 301 snap.microovn.chassis.service loaded active running Service for snap application microovn.chassis snap.microovn.daemon.service loaded active running Service for snap application microovn.daemon ● snap.microovn.switch.service loaded failed failedService for snap application microovn.switch snap.microovn.refresh-expiring-certs.timer loaded active waiting Timer refresh-expiring-certs for snap application microovn.refresh-expiring-certs The output from "journalctl -b -u snap.microovn.switch.service" is (in relevant part): Oct 25 10:55:27 pi01 systemd[1]: Started Service for snap application microovn.switch. Oct 25 10:55:28 pi01 microovn.switch[7315]: * /var/snap/microovn/common/data/switch/db/conf.db does not exist Oct 25 10:55:28 pi01 microovn.switch[7315]: * Creating empty database /var/snap/microovn/common/data/switch/db/conf.db Oct 25 10:55:28 pi01 microovn.switch[7315]: * Starting ovsdb-server Oct 25 10:55:28 pi01 ovs-vsctl[7338]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=8.3.0 Oct 25 10:55:28 pi01 ovs-vsctl[7348]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.17.7 "external-ids:system-id=\"pi01\"" "external-ids:rundir=\"/var/snap/microovn/> Oct 25 10:55:28 pi01 microovn.switch[7315]: * Configuring Open vSwitch system IDs Oct 25 10:55:28 pi01 microovn.switch[7380]: /snap/microovn/301/share/openvswitch/scripts/ovs-kmod-ctl: 112: modprobe: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/microovn/+bug/2040524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure
I think they are two distinct problems, and hopefully we would get a comment from NVIDIA/Mellanox as the statements in bug 2020409 contradicts the documentation [0] the current Netplan implementation is based on. Martin may have more details, but wanted to mention that one of our suspected culprits is with how Netplan lays out the udev rules for VF activation [1]: 1) It takes a long time when many are configured, as opposed to the expectation in the comment. 2) The process appears to be executed multiple times, which combined with the fact it takes a long time in turn may end up clashing with both the networking backends creation of the bond and the systemd unit rebinding the VFs. Bug 2020409 also raises the question if there are any bond/LAG related system bringup quirks for systems using only Scalable Functions (SF) or a combination of SFs and VFs. I have yet to see any documentation about that. 0: https://enterprise-support.nvidia.com/s/article/Configuring-VF-LAG-using-TC 1: https://github.com/canonical/netplan/blob/a7e4be03918c986020650743cb6cf0934696ef0c/src/sriov.c#L107-L112 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: Won't Fix Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel Status in linux package in Ubuntu: Fix Released Status in xdp-tools package in Ubuntu: Invalid Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel
The xdp-tools autopkgtests are passing when using the 6.2.0-18-generic kernel which is now available in -proposed. ** Summary changed: - Inconsistent autopkgtest failures in xdp-tools lunar amd64 + Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: xdp-tools (Ubuntu) Status: Triaged => Invalid ** Changed in: xdp-tools (Ubuntu) Assignee: Frode Nordahl (fnordahl) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel Status in linux package in Ubuntu: Fix Committed Status in xdp-tools package in Ubuntu: Invalid Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
However, it will probably take some time to resolve bug 1988018 so we should probably look into what interim solutions the charm could provide until we get there. ** Changed in: charm-ovn-chassis Status: New => Triaged ** Changed in: charm-ovn-chassis Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: Triaged Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
Excellent work on finding more information about the cause and a workaround, thank you for that! I think it would be appropriate to tackle this as part of the resolution of netplan.io bug 1988018 though, so the charm task would still be invalid unfortunately. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: New Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
This does indeed appear to be a serious issue, but it is unfortunately not a charm issue. It appears to me to be an issue with the mlx5 driver in the kernel which is visible in this specific environment for yet to be uncovered reasons. ** Changed in: charm-ovn-chassis Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: Invalid Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
** Attachment added: "apport-bug output as per linux kernel bug procedure requirements" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+attachment/5651265/+files/2009063.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: New Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
Note that for the log references where the autopkgtest runs using a 6.1 kernel, there appears to be a regression in the kernel. I can reproduce those locally and the problem goes away when upgrading to a mainline 6.2.0-060200.202302191831 kernel. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: New Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
** Patch added: "xdp-tools_1.3.0-2ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/xdp-tools/+bug/2007308/+attachment/5649048/+files/xdp-tools_1.3.0-2ubuntu1.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
@cjwatson thanks alot for chiming in on the issue. I added Launchpad, because I was unsure what part Launchpad has in the massaging of dependencies on the Debian import, and if something could be done there. Unfortunately even if the host had a 5.15 kernel, there is no 5.15 package in Lunar. The linux-tools-common package is currently pulled in on the back of it claiming to provide `bpftool` through a Provides stanza, however it is just a shell wrapper. I guess if we somehow could get the builder to understand that it would also need linux-tools-generic we could possibly convince Debian to accept some conditional logic in d/rules to find the bpftool binary in /usr/lib/linux-tools-* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
** Also affects: xdp-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647168/+files/UdevDb.txt ** Description changed: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 - --- + + For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: - linux-restricted-modules-5.4.0-139-generic N/A - linux-backports-modules-5.4.0-139-generic N/A - linux-firmware N/A + linux-restricted-modules-5.4.0-139-generic N/A + linux-backports-modules-5.4.0-139-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: - + dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls:
[Kernel-packages] [Bug 2007308] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] NonfreeKernelModules.txt
apport information ** Attachment added: "NonfreeKernelModules.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647163/+files/NonfreeKernelModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647167/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647166/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647164/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647162/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647161/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647160/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647159/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647158/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2007308/+attachment/5647157/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in Launchpad itself: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] [NEW] linux-tools-common: bpftool wrapper causes build failure for xdp-tools
Public bug reported: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU ** Affects: launchpad Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xdp-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected lunar package-from-proposed uec-images ** Also affects: launchpad Importance: Undecided Status: New ** Tags added: apport-collected lunar package-from-proposed uec-images ** Description changed: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.24.0-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 23.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M + MachineType: QEMU Standard PC (Q35 + ICH9, 2009) + Package: linux-tools-common 6.1.0-14.14 + PackageArchitecture: all + PciMultimedia: + +
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
** Changed in: linux (Ubuntu) Status: Expired => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Triaged Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0 07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], length 0 07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto TCP (6), length 64) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc29a (incorrect -> 0x356e), ack 1, win 487,
[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping
Thanks a lot for checking, Itai! As discussed offline, we made another attempt with 5.19.0-28-generic kernel and 22.35.2302 firmware on a different system, and also did not run into this issue there. Will set this to incomplete until we regain access to the system where this was first observed so we can compare sw/hw components. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999229 Title: mlx5 VF LAG flapping Status in linux package in Ubuntu: Incomplete Bug description: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2 This does not happen when using the Jammy 5.15 kernel, everything else in the environment being equal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14: 00074f30 R15: 7ffd50fa8f50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757271] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757646]
[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping
Looks like there are two issues here, after removing the bond, we still see the syndrome message, and traffic to instances is impacted: [Fri Dec 9 10:28:37 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3334): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 10:28:37 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 10:28:37 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999229 Title: mlx5 VF LAG flapping Status in linux package in Ubuntu: Incomplete Bug description: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2 This does not happen when using the Jammy 5.15 kernel, everything else in the environment being equal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping
** Attachment added: "apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+attachment/5635245/+files/apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999229 Title: mlx5 VF LAG flapping Status in linux package in Ubuntu: Incomplete Bug description: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2 This does not happen when using the Jammy 5.15 kernel, everything else in the environment being equal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping
** Attachment added: "syslog-kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+attachment/5635244/+files/syslog-kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999229 Title: mlx5 VF LAG flapping Status in linux package in Ubuntu: Incomplete Bug description: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2 This does not happen when using the Jammy 5.15 kernel, everything else in the environment being equal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999229] [NEW] mlx5 VF LAG flapping
Public bug reported: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2 [Fri Dec 9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2 This does not happen when using the Jammy 5.15 kernel, everything else in the environment being equal. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999229 Title: mlx5 VF LAG flapping Status in linux package in Ubuntu: Incomplete Bug description: # sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy # mlxfwmanager Querying Mellanox devices firmware ... Device #1: -- Device Type: ConnectX6DX Part Number: MCX623106AN-CDA_Ax Description: ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; PCIe 4.0/3.0 x16; PSID: MT_000359 PCI Device Name: :41:00.0 Base GUID:08c0eb03006fb26e Base MAC: 08c0eb6fb26e Versions: CurrentAvailable FW 22.34.4000 N/A PXE3.6.0700 N/A UEFI 14.27.0015 N/A # uname -a Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed, see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Problem: Severe packet loss to high speed NIC due to what appears as VF LAG flapping: [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get termination table, err -EINVAL [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad resource(0x5), syndrome (0xf2ff71), err(-22) [Fri Dec 9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create termination table rule, err -EINVAL [Fri Dec 9 07:27:19
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
The patch highlighted in #5 does not fix this issue for me without other patches from the refactor, so it may be we need to wait for the 5.19 hwe kernel to arrive to fix this issue. ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Incomplete Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0 07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], length 0 07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length
[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
I have received information about this issue possibly fixed by https://patchwork.kernel.org/project/netdevbpf/patch/20220510055743.118828-7-sae...@nvidia.com/ Pending confirmation ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel:
[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace
fwiw; I can confirm that the proposed patch also fixes issues with LXD virtual machines and block devices that was present on 5.19.0-19 and 5.19.0-20 ref bug 1992564. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Re: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working
*** This bug is a duplicate of bug 1991691 *** https://bugs.launchpad.net/bugs/1991691 ** This bug has been marked a duplicate of bug 1991691 cannot change mount namespace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working Status in linux package in Ubuntu: Confirmed Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Re: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working
For completeness, I can confirm this also happens with the 5.19.0-20 kernel currently in -proposed. ** Summary changed: - [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working + [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working Status in linux package in Ubuntu: Confirmed Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623319/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623330/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623327/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623326/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623329/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623331/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623324/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623328/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623322/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623320/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623321/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623325/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623318/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623323/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623314/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623317/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623315/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623316/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992564] Re: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working
apport information ** Tags added: apport-collected kinetic ** Description changed: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu2 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2021-01-18 (631 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) + MachineType: ASUS System Product Name + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.19.0-19-generic N/A + linux-backports-modules-5.19.0-19-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1 + Tags: kinetic + Uname: Linux 5.19.0-19-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 03/04/2022 + dmi.bios.release: 16.3 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1603 + dmi.board.asset.tag: Default string + dmi.board.name: ROG ZENITH II EXTREME ALPHA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1992564/+attachment/5623313/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1992564] [NEW] [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working
Public bug reported: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992564 Title: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working Status in linux package in Ubuntu: New Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
** Attachment added: "The issue also occurs on the 5.15.0-48.54 kernel currently in -proposed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987269/+attachment/5613800/+files/apport-bug-1987269.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14:
[Kernel-packages] [Bug 1988018] [NEW] [mlx5] Intermittent VF-LAG activation failure
Public bug reported: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Fix Committed ** Affects: netplan.io (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Committed ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: New Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: New Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
The fix for the issue boils down to these commits: 314e1105831b net/mlx5e: Add post act offload/unoffload API 8300f225268b net/mlx5e: Create new flow attr for multi table actions a81283263bb0 net/mlx5e: Use multi table support for CT and sample actions 2a829fe25d28 net/mlx5e: TC, Clean redundant counter flag from tc action parsers 7843bd604081 net/mlx5e: TC, Make post_act parse CT and sample actions However, they rely on both previous commits in the same v5.18 merge commit as well as a refactoring which has been going on over the v5.16 and v5.17 cycles. This may be complicated to backport to v5.15. So I guess the question becomes: - Would there be something we could do to adapt the fix to what is currently in v5.15? - Would an alternative be to release note this problem and point forward to a fix coming in the 22.04 HWE kernel based on v5.19 which is going to appear in not a too distant future? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Incomplete Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66:
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
fwiw; the fix is somewhere to be found in these mainline commits: b070e70381ee343dc10d2b1f0f3a6b1f940f0ae5 7843bd604081b5f005b31343cde1bb680bcc1776 2a829fe25d2809a33a6842359323bb139556c03d a81283263bb0c38b52fce6d599c2434a8d232dd6 8300f225268be9ee2c0daf5a3f23929fcdcbf213 314e1105831b45a0fe3045411d7fec4997936e86 0610f8dc0309cd0ea017d129efb95a942325344d d1a3138f7913014e0714cb1d3d44793d76fc38a1 bfbdd77ac52fecc198b049bff9574e84519ed9a5 7c5f940d264e4c3d4f4fdbb4dc84b9eca6d3ea43 4b5fba4a3ac790ad79bb4d36e7a4398702429b4d 1d5024f88dadb5949c9fd10876b3a9d2a202fc1e b98d2d722f81b2043a4458adebfbe45e239d1f79 c1e80bf4ad3e91dd21a8ccdee129052e25ace7e6 9625bf39bd4140cebd60cc658846505f4ab6c8ca 71753b8ec103fd71d6ee90e522d797ccf978e4ed 3a9e5fff2ab0d6f4af701757d35b9453dc563b78 3c87aedd48997f9ab3afdeb2084f6b6163a21db8 ed5f9cf06b20f74c1098d6d62313e3e9af217fcb 62f7991feab69ed398ad6a03b911fa0ee0549516 3ab45777a27c5f53a55a2c353b70648449ca7a33 6b23f6ab86a4f3a608b9bfa98616e99a34bb650c 8bf30be75069d6080659de9a28565c048f6cef9b 17c84cb46e33fcd682d5d5d6180162374cb24a34 6ce204eac38723d3a24c7bf148221de933bba54d d08c6e2a4d0308a7922d7ef3b1b3af45d4096aad befa41771f9e07f0a95b4a4a0d6b77fd334f4e44 76c31e5f758596509fbab120b8d055bf927ed165 c27bd1718c06eb356a4ea0ab8588ad442d953947 9536923d3f353873e54d96769fbd2e7f867a73e1 60dc0ef674ecbc944e2c236c8a71ce26440cb1a9 8348b71ccd921d0bff21b6f480ecc1e3a5033359 a572c0a748e6f7e04fb56d65139edbece4cb113d 73a3f1bcab1e66206c2de4bf11083fb8ddd5f49c 84ba8062e383c4a4f8f6388d1cfc87328f2a6115 e5d4e1da65564bb8631ecf5f08f0b2960fb0bc78 efe6f961cd2e54aca4385c7fee1c997f7c286c73 eeed226ed110ed40598e60e29b66643012277be7 3b49a7edec1df4f7019b3b872124231197267205 ff99316700799b84e842f819a44db608557bae3e 8be9686d2479a12f986dfce2f792e33ab747ac0f 918ed7bf76267e43863205e0d61a949c301f367b 09bf97923224fea7f3633648b64867a934d627f2 df67ad625b9ef1c7400f3573df8ac36ab9f56260 c118ebc98233eb1383f1adfeea4fa8e59f635088 39542e234b5215dc267b425f8315747849c5e520 There appears to have been a major refactor of drivers/net/ethernet/mellanox/mlx5/core/en_tc.c going on for the past several kernel releases. It is still not known if the fix is at the tip of that refactor or if it will be isolated and easily backportable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Incomplete Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4
[Kernel-packages] [Bug 1987618] [NEW] [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
Public bug reported:
Charmed OpenStack on Jammy.
Hardware offloaded instances that reside on the hypervisor which is also
the active OVN gateway for their network have degraded connectivity.
$ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
Setting --output-document (outputdocument) to /dev/null
DEBUG output created by Wget 1.21.2 on linux-gnu.
Reading HSTS entries from /home/ubuntu/.wget-hsts
URI encoding = ‘UTF-8’
--2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/
Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)...
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b
2620:2d:4000:1::18 2001:67c:1562::26
Connecting to nova.clouds.archive.ubuntu.com
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
Created socket 4.
Releasing 0x55ef05654490 (new refcount 1).
---request begin---
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Date: Thu, 25 Aug 2022 07:16:54 GMT
Server: Apache/2.4.29 (Ubuntu)
Vary: Accept-Encoding
Content-Length: 1779
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=UTF-8
---response end---
200 OK
Registered socket 4 for persistent reuse.
URI content encoding = ‘UTF-8’
Length: 1779 (1.7K) [text/html]
Saving to: ‘/dev/null’
/dev/null
100%[>]
1.74K --.-KB/sin 0.07s
2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]
real0m5.591s
user0m0.000s
sys 0m0.005s
$ sudo tcpdump -nevi ens3 not port 22
07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800),
length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6),
length 60)
10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect ->
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695
ecr 0,nop,wscale 7], length 0
07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800),
length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length
60)
91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq
3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val
932285789 ecr 4081686695,nop,wscale 7], length 0
07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800),
length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6),
length 52)
10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect ->
0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789],
length 0
07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800),
length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6),
length 204)
10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect ->
0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr
932285789], length 152: HTTP, length: 152
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive
07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800),
length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6),
length 52)
91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack
153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0
07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800),
length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6),
length 52)
91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq
2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770],
length 0
07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800),
length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto TCP (6),
length 64)
10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc29a (incorrect ->
0x356e), ack 1, win 487, options [nop,nop,TS val 4081691850 ecr
932285865,nop,nop,sack 1 {2008:2009}], length 0
07:16:59.531552 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800),
length 1440: (tos 0x0, ttl 58, id 15671, offset 0, flags [DF], proto TCP (6),
length 1426)
91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0x0d7c (correct), seq
1:1375, ack 153, win 508, options [nop,nop,TS val 932291230 ecr 4081691850],
length 1374: HTTP, length: 1374
HTTP/1.1 200 OK
[Kernel-packages] [Bug 1987269] [NEW] [5.18.0 mainline] mlx5 deadlock
Public bug reported: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14: 00074f30 R15: 7ffd50fa8f50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757271] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757646] INFO: task ovs-vswitchd:45997 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.764817] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.771036] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.778998] task:ovs-vswitchdstate:D stack:0 pid:45997 ppid: 1 flags:0x0002 Aug 22
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Changed in: openvswitch (Ubuntu Impish) Status: New => Won't Fix ** Changed in: ovn (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Invalid Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in openvswitch source package in Impish: Won't Fix Status in ovn source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: [Impact] Users of Open vSwitch on Focal will not be able to upgrade to v2.16.0 or newer until this long standing kernel bug has been fixed. Users of Open vSwitch on Jammy will be affected by this bug and have no user space fix available. This bug currently blocks the OpenStack Engineering team's charm product gate. [Test Plan] Execute the OVN system testsuite utilizing the kernel data path with the test synthesis patch in comment #7 applied. In addition to that validating that the OpenStack charm test gate is unblocked would be valuable. [Regression Potential] The regression potential can be considered as low because: - The calls added in the openvswitch kernel datapath code would prior to Open vSwitch 2.16.0 have been initiated from the userspace code and by chance concealed this bug. - After an optimization done in 2.16.0 the kernel bug was revealed and these calls now must be made from the kernel datapath to retain functionality in use in the wild. [Original Bug Description] If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
In addition to the verification provided in comment #26 and #28 we've
taken the neutron-api-plugin-ovn e2e charm gate with an added hairpin
test for a spin for both Focal and Jammy where we found the control to
fail as expected and successful test with the updated kernel.
$ juju run --application nova-compute 'uname -a'
- Stdout: |
Linux civil-ibex 5.4.0-123-generic #139-Ubuntu SMP Mon Jul 11 16:02:31 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/0
- Stdout: |
Linux pumped-pika 5.4.0-123-generic #139-Ubuntu SMP Mon Jul 11 16:02:31 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/1
- Stdout: |
Linux moved-toucan 5.4.0-123-generic #139-Ubuntu SMP Mon Jul 11 16:02:31
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/2
...
2022-07-19 16:25:09 [INFO] XXX HAIRPIN
2022-07-19 16:25:09 [INFO] Attempting to ssh to instance-1(10.78.95.25)
2022-07-19 16:25:09 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:09 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:09 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.25 on
instance-1
2022-07-19 16:25:10 [INFO] Attempting to ssh to instance-1(10.78.95.25)
2022-07-19 16:25:10 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:10 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:10 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.25 on
instance-1
2022-07-19 16:25:10 [INFO] Attempting to ssh to instance-1(10.78.95.25)
2022-07-19 16:25:10 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:10 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:10 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.25 on
instance-1
2022-07-19 16:25:11 [INFO] Attempting to ssh to instance(10.78.95.71)
2022-07-19 16:25:11 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:11 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:11 [INFO] Running ping -c 1 192.168.0.1 on instance
2022-07-19 16:25:11 [INFO] Attempting to ssh to instance(10.78.95.71)
2022-07-19 16:25:11 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:11 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:11 [INFO] Running ping -M do -s 1414 -c 1 192.168.0.1 on
instance
2022-07-19 16:25:12 [INFO] Attempting to ssh to instance(10.78.95.25)
2022-07-19 16:25:12 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:12 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:12 [INFO] Running ping -c 1 192.168.0.1 on instance
2022-07-19 16:25:12 [INFO] Attempting to ssh to instance(10.78.95.25)
2022-07-19 16:25:12 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:12 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:12 [INFO] Running ping -M do -s 1414 -c 1 192.168.0.1 on
instance
2022-07-19 16:25:13 [INFO] Running resource cleanup
2022-07-19 16:25:13 [INFO] Removing resources created by test
(zaza-neutrontests*)
2022-07-19 16:25:21 [INFO] ok
2022-07-19 16:25:21 [INFO]
--
2022-07-19 16:25:21 [INFO] Ran 1 test in 48.934s
2022-07-19 16:25:21 [INFO] OK
2022-07-19 16:25:21 [INFO] Events:
Test zaza.openstack.charm_tests.neutron.tests.NeutronNetworkingTest:
Start: 1658240672.1115046
Finish: 1658240721.410828
Elapsed Time: 49.29932355880737
PCT Of Run Time: 100
Metadata: {}
$ juju run --application nova-compute 'uname -a'
- Stdout: |
Linux casual-buck 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/0
- Stdout: |
Linux neat-serval 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/1
- Stdout: |
Linux brave-horse 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
UnitId: nova-compute/2
...
2022-07-19 16:25:09 [INFO] XXX HAIRPIN
2022-07-19 16:25:09 [INFO] Attempting to ssh to instance-1(10.78.95.92)
2022-07-19 16:25:09 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:09 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:09 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.92 on
instance-1
2022-07-19 16:25:09 [INFO] Attempting to ssh to instance-1(10.78.95.92)
2022-07-19 16:25:09 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:09 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:09 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.92 on
instance-1
2022-07-19 16:25:09 [INFO] Attempting to ssh to instance-1(10.78.95.92)
2022-07-19 16:25:10 [INFO] Connected (version 2.0, client OpenSSH_7.6p1)
2022-07-19 16:25:10 [INFO] Authentication (publickey) successful!
2022-07-19 16:25:10 [INFO] Running ping -M do -s 1414 -c 1 10.78.95.92 on
instance-1
2022-07-19 16:25:10 [INFO] Attempting to ssh to instance(10.78.95.29)
2022-07-19 16:25:10 [INFO] Connected
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Description changed: - If you have two hvs where hv1 is the gateway chassis and you have an - instance running on hv2. + [Impact] + Users of Open vSwitch on Focal will not be able to upgrade to v2.16.0 or newer until this long standing kernel bug has been fixed. + + Users of Open vSwitch on Jammy will be affected by this bug and + have no user space fix available. This bug currently blocks the + OpenStack Engineering team's charm product gate. + + [Test Plan] + Execute the OVN system testsuite utilizing the kernel data path with the test synthesis patch in comment #7 applied. + + In addition to that validating that the OpenStack charm test gate is + unblocked would be valuable. + + [Regression Potential] + The regression potential can be considered as low because: + - The calls added in the openvswitch kernel datapath code would + prior to Open vSwitch 2.16.0 have been initiated from the + userspace code and by chance concealed this bug. + - After an optimization done in 2.16.0 the kernel bug was + revealed and these calls now must be made from the kernel + datapath to retain functionality in use in the wild. + + [Original Bug Description] + If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 - $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 - 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1:
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
Control test: ubuntu@game-cicada:~/src/ovn$ uname -a Linux game-cicada 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ubuntu@game-cicada:~/src/ovn$ git -C ./ovs status HEAD detached at 6f24c2bc7 nothing to commit, working tree clean ubuntu@game-cicada:~/src/ovn$ git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean ubuntu@game-cicada:~/src/ovn$ wget -qO - https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5579267/+files/test-synthesis.patch|patch -p1 patching file tests/system-ovn.at Hunk #1 succeeded at 6699 (offset 15 lines). Hunk #2 succeeded at 6724 (offset 15 lines). Hunk #3 succeeded at 6750 (offset 15 lines). ubuntu@game-cicada:~/src/ovn$ make check-kernel SUDO=sudo TESTSUITEFLAGS=169 make all-am make[1]: Entering directory '/home/ubuntu/src/ovn' /bin/bash '/home/ubuntu/src/ovn/build-aux/missing' autom4te --language=autotest -I '.' -o tests/system-kmod-testsuite.tmp tests/system-kmod-testsuite.at mv tests/system-kmod-testsuite.tmp tests/system-kmod-testsuite /bin/bash '/home/ubuntu/src/ovn/build-aux/missing' autom4te --language=autotest -I '.' -o tests/system-userspace-testsuite.tmp tests/system-userspace-testsuite.at mv tests/system-userspace-testsuite.tmp tests/system-userspace-testsuite make[1]: Leaving directory '/home/ubuntu/src/ovn' set /bin/bash './tests/system-kmod-testsuite' -C tests AUTOTEST_PATH='/home/ubuntu/src/ovn/ovs/utilities:/home/ubuntu/src/ovn/ovs/vswitchd:/home/ubuntu/src/ovn/ovs/ovsdb:/home/ubuntu/src/ovn/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic'; \ sudo "$@" 169 -j1 || (test X'' = Xyes && sudo "$@" --recheck) ## ## ## ovn 22.06.90 test suite. ## ## ## 169: DNAT LR hairpin IPv4 -- ovn-northd -- parallelization=yes -- ovn_monitor_all=yes FAILED (system-ovn.at:6661) ## - ## ## Test results. ## ## - ## ERROR: 1 test was run, 1 failed unexpectedly. Verification: ubuntu@game-cicada:~/src/ovn$ uname -a Linux game-cicada 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ubuntu@game-cicada:~/src/ovn$ git -C ./ovs status HEAD detached at 6f24c2bc7 nothing to commit, working tree clean ubuntu@game-cicada:~/src/ovn$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: tests/system-ovn.at Untracked files: (use "git add ..." to include in what will be committed) tests/system-ovn.at.orig no changes added to commit (use "git add" and/or "git commit -a") ubuntu@game-cicada:~/src/ovn$ make check-kernel SUDO=sudo TESTSUITEFLAGS=169 make all-am make[1]: Entering directory '/home/ubuntu/src/ovn' make[1]: Leaving directory '/home/ubuntu/src/ovn' set /bin/bash './tests/system-kmod-testsuite' -C tests AUTOTEST_PATH='/home/ubuntu/src/ovn/ovs/utilities:/home/ubuntu/src/ovn/ovs/vswitchd:/home/ubuntu/src/ovn/ovs/ovsdb:/home/ubuntu/src/ovn/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic'; \ sudo "$@" 169 -j1 || (test X'' = Xyes && sudo "$@" --recheck) ## ## ## ovn 22.06.90 test suite. ## ## ## 169: DNAT LR hairpin IPv4 -- ovn-northd -- parallelization=yes -- ovn_monitor_all=yes ok ## - ## ## Test results. ## ## - ## 1 test was successful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Invalid Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in openvswitch source package in Impish: New Status in ovn source package in Impish: New Status in linux source package in Jammy: Fix Committed Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted,
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
Control test: ubuntu@actual-beagle:~/src/ovn$ uname -a Linux actual-beagle 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ubuntu@actual-beagle:~/src/ovn$ git -C ./ovs status HEAD detached at 6f24c2bc7 nothing to commit, working tree clean ubuntu@actual-beagle:~/src/ovn$ git status On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean ubuntu@actual-beagle:~/src/ovn$ wget -qO - https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5579267/+files/test-synthesis.patch|patch -p1 patching file tests/system-ovn.at Hunk #1 succeeded at 6699 (offset 15 lines). Hunk #2 succeeded at 6724 (offset 15 lines). Hunk #3 succeeded at 6750 (offset 15 lines). ubuntu@actual-beagle:~/src/ovn$ make check-kernel SUDO=sudo TESTSUITEFLAGS=169 make all-am make[1]: Entering directory '/home/ubuntu/src/ovn' /bin/bash /home/ubuntu/src/ovn/build-aux/missing autom4te --language=autotest -I '.' -o tests/system-kmod-testsuite.tmp tests/system-kmod-testsuite.at mv tests/system-kmod-testsuite.tmp tests/system-kmod-testsuite /bin/bash /home/ubuntu/src/ovn/build-aux/missing autom4te --language=autotest -I '.' -o tests/system-userspace-testsuite.tmp tests/system-userspace-testsuite.at mv tests/system-userspace-testsuite.tmp tests/system-userspace-testsuite make[1]: Leaving directory '/home/ubuntu/src/ovn' set /bin/bash './tests/system-kmod-testsuite' -C tests AUTOTEST_PATH='/home/ubuntu/src/ovn/ovs/utilities:/home/ubuntu/src/ovn/ovs/vswitchd:/home/ubuntu/src/ovn/ovs/ovsdb:/home/ubuntu/src/ovn/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic'; \ sudo "$@" 169 -j1 || (test X'' = Xyes && sudo "$@" --recheck) ## ## ## ovn 22.06.90 test suite. ## ## ## 169: DNAT LR hairpin IPv4 -- ovn-northd -- parallelization=yes -- ovn_monitor_all=yes FAILED (system-ovn.at:6661) ## - ## ## Test results. ## ## - ## ERROR: 1 test was run, 1 failed unexpectedly. Verification: ubuntu@actual-beagle:~/src/ovn$ uname -a Linux actual-beagle 5.4.0-123-generic #139-Ubuntu SMP Mon Jul 11 16:02:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ubuntu@actual-beagle:~/src/ovn$ git -C ovs status HEAD detached at 6f24c2bc7 nothing to commit, working tree clean ubuntu@actual-beagle:~/src/ovn$ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: tests/system-ovn.at Untracked files: (use "git add ..." to include in what will be committed) tests/system-ovn.at.orig no changes added to commit (use "git add" and/or "git commit -a") ubuntu@actual-beagle:~/src/ovn$ make check-kernel SUDO=sudo TESTSUITEFLAGS=169 make all-am make[1]: Entering directory '/home/ubuntu/src/ovn' make[1]: Leaving directory '/home/ubuntu/src/ovn' set /bin/bash './tests/system-kmod-testsuite' -C tests AUTOTEST_PATH='/home/ubuntu/src/ovn/ovs/utilities:/home/ubuntu/src/ovn/ovs/vswitchd:/home/ubuntu/src/ovn/ovs/ovsdb:/home/ubuntu/src/ovn/ovs/vtep:tests:::controller-vtep:northd:utilities:controller:ic'; \ sudo "$@" 169 -j1 || (test X'' = Xyes && sudo "$@" --recheck) ## ## ## ovn 22.06.90 test suite. ## ## ## 169: DNAT LR hairpin IPv4 -- ovn-northd -- parallelization=yes -- ovn_monitor_all=yes ok ## - ## ## Test results. ## ## - ## 1 test was successful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Invalid Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in openvswitch source package in Impish: New Status in ovn source package in Impish: New Status in linux source package in Jammy: Fix Committed Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1
[Kernel-packages] [Bug 1967856] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595908/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2]
[Kernel-packages] [Bug 1967856] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595905/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2]
[Kernel-packages] [Bug 1967856] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595906/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices:
[Kernel-packages] [Bug 1967856] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595910/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1967856] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595907/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error:
[Kernel-packages] [Bug 1967856] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595909/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such file
[Kernel-packages] [Bug 1967856] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595911/+files/acpidump.txt ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1
[Kernel-packages] [Bug 1967856] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595904/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such
[Kernel-packages] [Bug 1967856] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595903/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such
[Kernel-packages] [Bug 1967856] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595902/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2] No such file
[Kernel-packages] [Bug 1967856] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967856/+attachment/5595901/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: Invalid Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: Invalid Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Confirmed Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 9 11:35 seq crw-rw 1 root audio 116, 33 Jun 9 11:35 timer AplayDevices: Error: [Errno 2]
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
This issue has been fixed by a patch to the openvswitch datapath code in the kernel [0]. The patched kernel would be required when used in conjunction with OVN 21.12 or newer, which translates to Focal (yoga UCA), Jammy and Kinetic. 0: https://lore.kernel.org/netdev/20220606221140.488984-1-i.maxim...@ovn.org/T/#u ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: openvswitch (Ubuntu Kinetic) Importance: High Status: Invalid ** Also affects: ovn (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Jammy) Status: New => Invalid ** Changed in: ovn (Ubuntu Focal) Status: New => Invalid ** Changed in: openvswitch (Ubuntu Jammy) Status: New => Invalid ** Changed in: openvswitch (Ubuntu Focal) Status: New => Invalid ** Tags added: apport-collected jammy uec-images ** Description changed: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7
[Kernel-packages] [Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: openvswitch (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw Status in linux package in Ubuntu: Incomplete Status in openvswitch package in Ubuntu: Invalid Status in ovn package in Ubuntu: Invalid Status in linux source package in Focal: New Status in openvswitch source package in Focal: New Status in ovn source package in Focal: Invalid Status in linux source package in Jammy: New Status in openvswitch source package in Jammy: New Status in ovn source package in Jammy: Invalid Status in linux source package in Kinetic: Incomplete Status in openvswitch source package in Kinetic: Invalid Status in ovn source package in Kinetic: Invalid Bug description: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "dpctl-dump-flows.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537899/+files/dpctl-dump-flows.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537897/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537898/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "br-int-flows.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537900/+files/br-int-flows.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] [NEW] [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
Public bug reported: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Circling back to this, I did make an attempt with linux-firmware 1.198 as base and then copying in just the firmwares that appeared relevant to the hardware in question from 1.199. However I was no longer able to reproduce the issue. Now I have installed the 1.199 package again and I have had no issues after one full day of use. I wonder if this only occurred on the first boot with the new firmware, or if some other external activity caused the issue? I'm going to mark this as incomplete for now as I can no longer reproduce, feel free to downgrade to Invalid if you deem that appropriate. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Apparently the kern.log just shows boot, adding syslog excerpt with the kernel messages ** Attachment added: "syslog-excerpt.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513209/+files/syslog-excerpt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Attaching the kern.log from previous boot which shows the issues. ** Attachment added: "kern.log.1" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513187/+files/kern.log.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937415] [NEW] Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Public bug reported: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 - Package: linux-firmware 1.198 + Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: - + InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-16-generic N/A - linux-backports-modules-5.11.0-16-generic N/A - linux-firmware 1.198 + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: New
[Kernel-packages] [Bug 1907086] Re: hardware offloaded PCI devices don't have associated netlink interfaces
*** This bug is a duplicate of bug 1908351 *** https://bugs.launchpad.net/bugs/1908351 ** This bug has been marked a duplicate of bug 1908351 SR-IOV, don't do runtime reconfiguration and make use of PCI address matching -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907086 Title: hardware offloaded PCI devices don't have associated netlink interfaces Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Over time the netlink interfaces for PCI devices of VF's of a Mellanox ConnectX 5 card disappear: # mlnx-switchdev-mode show :61:00.0eno1igb PF :61:00.1eno2igb PF :81:00.0enp129s0f0 mlx5_core PF :81:00.1enp129s0f1 mlx5_core PF :81:02.6enp129s0f0v20 mlx5_core VF of enp129s0f0 :81:03.2enp129s0f0v24 mlx5_core VF of enp129s0f0 # ip link [...] 103: enp129s0f1: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 04:3f:72:9f:35:8c brd ff:ff:ff:ff:ff:ff vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 1 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 2 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 3 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 4 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 5 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 6 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 7 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 8 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 9 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 10 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 11 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 12 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 13 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 14 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 15 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 16 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 17 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 18 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 19 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 20 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 21 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 22 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 23 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 24 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 25 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 26 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 27 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 28 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off
[Kernel-packages] [Bug 1916020] Re: bcache: overflow in stripe number calculations for devices with small io_opt
On further diagnosis we discovered that this is probably already in our packages. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916020 Title: bcache: overflow in stripe number calculations for devices with small io_opt Status in linux package in Ubuntu: Invalid Bug description: Originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1783075 The problem is fixed in the 5.8 kernel, but we would need this fixed for the 5.4 kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916020] [NEW] bcache: overflow in stripe number calculations for devices with small io_opt
Public bug reported: Originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1783075 The problem is fixed in the 5.8 kernel, but we would need this fixed for the 5.4 kernel as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: ps5 ** Tags added: ps5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916020 Title: bcache: overflow in stripe number calculations for devices with small io_opt Status in linux package in Ubuntu: New Bug description: Originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1783075 The problem is fixed in the 5.8 kernel, but we would need this fixed for the 5.4 kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910201] Re: bcache: overflow in stripe number calculations for devices with small io_opt
Marking as fix released for MAAS as artifacts to deploy Focal with
hwe-20.04-edge kernel are now available.
** Changed in: maas
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910201
Title:
bcache: overflow in stripe number calculations for devices with small
io_opt
Status in MAAS:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would
like to put a Optane as cache device in front of a NVMe SSD backing
device with 512 byte optimum I/O size.
While the problem appears to be fixed for the kernel we file this bug
to document a need for Focal hwe-edge images for commissioning/deploy
in MAAS.
Excerpt from MAAS deploy log:
register_bcache: /dev/nvme1n1 > /sys/fs/bcache/registerbcache dev
/dev/nvme1n1 not ready, waiting 0.2scheck just created bcache
/dev/nvme1n1 if it is registered, try=60Running command ['udevadm',
'settle'] with allowed return codes [0] (capture=False)TIMED
udevadm_settle(): 0.015bcache device path not found:
/sys/class/block/nvme1n1/bcachebcache device was not registered,
registering /dev/nvme1n1 at /sys/fs/bcache/registerregister_bcache:
/dev/nvme1n1 > /sys/fs/bcache/registerbcache dev /dev/nvme1n1 not
ready, waiting 0.2sRepetitive error registering the bcache dev
/dev/nvme1n1An error occured handling 'bcache0': RuntimeError - bcache
device /dev/nvme1n1 can't be registeredfinish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring
bcache: bcache0TIMED BLOCK_META: 28.332finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-metaTraceback (most recent call last): File
"/curtin/curtin/commands/main.py", line 202, in mainret =
args.func(args) File "/curtin/curtin/log.py", line 97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs) File
"/curtin/curtin/log.py", line 79, in log_timereturn func(*args,
**kwargs) File "/curtin/curtin/commands/block_meta.py", line 111, in
block_metareturn meta_custom(args) File
"/curtin/curtin/commands/block_meta.py", line 1911, in meta_custom
handler(command, storage_config_dict) File
"/curtin/curtin/commands/block_meta.py", line 1652, in bcache_handler
bcache_dev = bcache.create_backing_device(backing_device, cache_device,
File "/curtin/curtin/block/bcache.py", line 479, in create_backing_device
ensure_bcache_is_registered(backing_device, target_sysfs_path)
File "/curtin/curtin/block/bcache.py", line 436, in ensure_bcache_is_registered
raise RuntimeError("bcache device %s can't be registered" %
RuntimeError: bcache device /dev/nvme1n1 can't be registeredbcache
device /dev/nvme1n1 can't be registered
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1910201/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910201] Re: bcache: overflow in stripe number calculations for devices with small io_opt
** Description changed:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would like
to put a Optane as cache device in front of a NVMe SSD backing device
with 512 byte optimum I/O size.
While the problem appears to be fixed for the kernel we file this bug to
document a need for Focal hwe-edge images for commissioning/deploy in
MAAS.
+
+ Excerpt from MAAS deploy log:
+ register_bcache: /dev/nvme1n1 > /sys/fs/bcache/registerbcache dev
/dev/nvme1n1 not ready, waiting 0.2scheck just created bcache
/dev/nvme1n1 if it is registered, try=60Running command ['udevadm',
'settle'] with allowed return codes [0] (capture=False)TIMED
udevadm_settle(): 0.015bcache device path not found:
/sys/class/block/nvme1n1/bcachebcache device was not registered,
registering /dev/nvme1n1 at /sys/fs/bcache/registerregister_bcache:
/dev/nvme1n1 > /sys/fs/bcache/registerbcache dev /dev/nvme1n1 not
ready, waiting 0.2sRepetitive error registering the bcache dev
/dev/nvme1n1An error occured handling 'bcache0': RuntimeError - bcache
device /dev/nvme1n1 can't be registeredfinish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring
bcache: bcache0TIMED BLOCK_META: 28.332finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-metaTraceback (most recent call last): File
"/curtin/curtin/commands/main.py", line 202, in mainret =
args.func(args) File "/curtin/curtin/log.py", line 97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs) File
"/curtin/curtin/log.py", line 79, in log_timereturn func(*args,
**kwargs) File "/curtin/curtin/commands/block_meta.py", line 111, in
block_metareturn meta_custom(args) File
"/curtin/curtin/commands/block_meta.py", line 1911, in meta_custom
handler(command, storage_config_dict) File
"/curtin/curtin/commands/block_meta.py", line 1652, in bcache_handler
bcache_dev = bcache.create_backing_device(backing_device, cache_device,
File "/curtin/curtin/block/bcache.py", line 479, in create_backing_device
ensure_bcache_is_registered(backing_device, target_sysfs_path)
File "/curtin/curtin/block/bcache.py", line 436, in ensure_bcache_is_registered
raise RuntimeError("bcache device %s can't be registered" %
RuntimeError: bcache device /dev/nvme1n1 can't be registeredbcache
device /dev/nvme1n1 can't be registered
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910201
Title:
bcache: overflow in stripe number calculations for devices with small
io_opt
Status in MAAS:
New
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would
like to put a Optane as cache device in front of a NVMe SSD backing
device with 512 byte optimum I/O size.
While the problem appears to be fixed for the kernel we file this bug
to document a need for Focal hwe-edge images for commissioning/deploy
in MAAS.
Excerpt from MAAS deploy log:
register_bcache: /dev/nvme1n1 > /sys/fs/bcache/registerbcache dev
/dev/nvme1n1 not ready, waiting 0.2scheck just created bcache
/dev/nvme1n1 if it is registered, try=60Running command ['udevadm',
'settle'] with allowed return codes [0] (capture=False)TIMED
udevadm_settle(): 0.015bcache device path not found:
/sys/class/block/nvme1n1/bcachebcache device was not registered,
registering /dev/nvme1n1 at /sys/fs/bcache/registerregister_bcache:
/dev/nvme1n1 > /sys/fs/bcache/registerbcache dev /dev/nvme1n1 not
ready, waiting 0.2sRepetitive error registering the bcache dev
/dev/nvme1n1An error occured handling 'bcache0': RuntimeError - bcache
device /dev/nvme1n1 can't be registeredfinish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring
bcache: bcache0TIMED BLOCK_META: 28.332finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-metaTraceback (most recent call last): File
"/curtin/curtin/commands/main.py", line 202, in mainret =
args.func(args) File "/curtin/curtin/log.py", line 97, in wrapper
[Kernel-packages] [Bug 1910201] Re: bcache: overflow in stripe number calculations for devices with small io_opt
** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910201
Title:
bcache: overflow in stripe number calculations for devices with small
io_opt
Status in MAAS:
New
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would
like to put a Optane as cache device in front of a NVMe SSD backing
device with 512 byte optimum I/O size.
While the problem appears to be fixed for the kernel we file this bug
to document a need for Focal hwe-edge images for commissioning/deploy
in MAAS.
Excerpt from MAAS deploy log:
register_bcache: /dev/nvme1n1 > /sys/fs/bcache/registerbcache dev
/dev/nvme1n1 not ready, waiting 0.2scheck just created bcache
/dev/nvme1n1 if it is registered, try=60Running command ['udevadm',
'settle'] with allowed return codes [0] (capture=False)TIMED
udevadm_settle(): 0.015bcache device path not found:
/sys/class/block/nvme1n1/bcachebcache device was not registered,
registering /dev/nvme1n1 at /sys/fs/bcache/registerregister_bcache:
/dev/nvme1n1 > /sys/fs/bcache/registerbcache dev /dev/nvme1n1 not
ready, waiting 0.2sRepetitive error registering the bcache dev
/dev/nvme1n1An error occured handling 'bcache0': RuntimeError - bcache
device /dev/nvme1n1 can't be registeredfinish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring
bcache: bcache0TIMED BLOCK_META: 28.332finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-metaTraceback (most recent call last): File
"/curtin/curtin/commands/main.py", line 202, in mainret =
args.func(args) File "/curtin/curtin/log.py", line 97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs) File
"/curtin/curtin/log.py", line 79, in log_timereturn func(*args,
**kwargs) File "/curtin/curtin/commands/block_meta.py", line 111, in
block_metareturn meta_custom(args) File
"/curtin/curtin/commands/block_meta.py", line 1911, in meta_custom
handler(command, storage_config_dict) File
"/curtin/curtin/commands/block_meta.py", line 1652, in bcache_handler
bcache_dev = bcache.create_backing_device(backing_device, cache_device,
File "/curtin/curtin/block/bcache.py", line 479, in create_backing_device
ensure_bcache_is_registered(backing_device, target_sysfs_path)
File "/curtin/curtin/block/bcache.py", line 436, in ensure_bcache_is_registered
raise RuntimeError("bcache device %s can't be registered" %
RuntimeError: bcache device /dev/nvme1n1 can't be registeredbcache
device /dev/nvme1n1 can't be registered
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1910201/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910201] [NEW] bcache: overflow in stripe number calculations for devices with small io_opt
Public bug reported: Ubuntu Focal ga kernel This problem was originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1783075 Using the linux-generic-hwe-20.04-edge packages resolves the issue. We hit this while exploring storage options for PS5 where we would like to put a Optane as cache device in front of a NVMe SSD backing device with 512 byte optimum I/O size. While the problem appears to be fixed for the kernel we file this bug to document a need for Focal hwe-edge images for commissioning/deploy in MAAS. ** Affects: maas Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: ps5 ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910201 Title: bcache: overflow in stripe number calculations for devices with small io_opt Status in MAAS: New Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu Focal ga kernel This problem was originally reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1783075 Using the linux-generic-hwe-20.04-edge packages resolves the issue. We hit this while exploring storage options for PS5 where we would like to put a Optane as cache device in front of a NVMe SSD backing device with 512 byte optimum I/O size. While the problem appears to be fixed for the kernel we file this bug to document a need for Focal hwe-edge images for commissioning/deploy in MAAS. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1910201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
