[Kernel-packages] [Bug 2056387] Re: [T14 Gen 3 AMD] Fail to suspend/resume for the second time
** Summary changed: - Fail to suspend/resume for the second time + [T14 Gen 3 AMD] Fail to suspend/resume for the second time -- 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/2056387 Title: [T14 Gen 3 AMD] Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056387] Re: Fail to suspend/resume for the second time
Random pointers although I'm not sure those are identical to my issue: https://www.reddit.com/r/archlinux/comments/199am0a/thinkpad_t14_suspend_broken_in_kernel_670/ https://discussion.fedoraproject.org/t/random-resume-after-suspend-issue-on-thinkpad-t14s-amd-gen3-radeon-680m-ryzen-7/103452 -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056387] Re: Fail to suspend/resume for the second time
Multiple suspends in a row worked without an external monitor connected, but after connecting it the machine failed to suspend/resume. ** Attachment added: "failed_on_suspend_after_connecting_monitor.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+attachment/5753543/+files/failed_on_suspend_after_connecting_monitor.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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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 2056387] [NEW] Fail to suspend/resume for the second time
Public bug reported: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: N
[Kernel-packages] [Bug 2056387] Re: Fail to suspend/resume for the second time
kernel log when trying suspend/resume twice in a row. The machine got frozen while the power LED is still on in the second suspend and there is no second "PM: suspend entry (s2idle)" in the kernel log. ** Attachment added: "failed_on_second_suspend.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+attachment/5753542/+files/failed_on_second_suspend.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/2056387 Title: Fail to suspend/resume for the second time Status in linux package in Ubuntu: New Bug description: I had a similar issue before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 However, I haven't seen the issue with later kernels until getting 6.8.0-11.11+1 recently. * 6.8.0-11 - fails to suspend/resume for the second time although the first suspend/resume works * 6.6.0-14 - no issue in terms of suspend/resume One thing worth noting is that connecting an external monitor or not might be a key to trigger this issue. I cannot reproduce it when an external monitor (through USB-C to HDMI) is not connected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 11:17:31 2024 InstallationDate: Installed on 2024-01-08 (59 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) MachineType: LENOVO 21CFCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=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-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2023 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET73W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CFCTO1WW dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056387/+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)
** Also affects: charm-ovn-chassis 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/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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
Just to give another data point, I've been running 5.19 from hwe-edge (instead of hwe) for some time but I realized this suspend issue after updating hwe-edge from 5.19.0.28.29~22.04.6 to 5.19.0.32.33~22.04.9. So I went back and tested it as follows. It looks like it's a regression within 5.19. My 2 cents. machine: ThinkPad T14 Gen 3 (21CFCTO1WW) CPU: AMD Ryzen 7 PRO 6850U Ubuntu release: jammy Please note that I tested it with Secure boot *disabled* since 5.19.0-28 wouldn't boot somehow (I believe it was working fine with Secure boot enabled before). $ uname -rv 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 -> stuck at the second attempt of suspend $ uname -rv 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 -> stuck at the second attempt of suspend $ uname -rv 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 -> 10/10 suspend-resume cycles succeeded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
** Description changed: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 - After beonding is enabled on switch and server side, the system will - hang at initialing ubuntu. The kernel loads but around starting the - Network Services the system can hang for sometimes 5 minutes, and in - other cases, indefinitely. + - 5.15 in jammy -> reproducible + - 5.19 in hwe-edge -> reproducible + - 6.2.rc6 in the mainline build -> works + - Intel's ice driver 1.10.1.2.2 -> works + + + After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jan 31 13:08 seq - crw-rw 1 root audio 116, 33 Jan 31 13:08 timer + total 0 + crw-rw 1 root audio 116, 1 Jan 31 13:08 seq + crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: - { -"result": "skip" - } - DistroRelease: Ubuntu 22.04 - InstallationDate: Installed on 2023-01-27 (3 days ago) - InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) + { + "result": "skip" + }DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: - + ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: - linux-restricted-modules-5.15.0-58-generic N/A - linux-backports-modules-5.15.0-58-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.9 - RfKill: Error: [Errno 2] No such file or directory: 'rfkill' - Tags: jammy uec-images + linux-restricted-modules-5.15.0-58-generic N/A + linux-backports-modules-5.15.0-58-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.9 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. -- 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/2004262 Title: Intel E810 NICs driver in causing hangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 - 5.15 in jammy -> reproducible - 5.19 in hwe-edge -> reproducible - 6.2.rc6 in the mainline build -> works - Intel's ice driver 1.10.1.2.2 -> works After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indef
[Kernel-packages] [Bug 1967131] Re: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic
Thank you Stefan for the prompt response. I'm marking this as Invalid for the time being assuming the value was intended. ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967131 Title: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic Status in linux-kvm package in Ubuntu: Invalid Bug description: -kvm flavor has CONFIG_NR_CPUS=64 although -generic has CONFIG_NR_CPUS=8192 these days. It will be a problem especially when launching a VM on top of a hypervisor with more than 64 CPU threads available. Then the guest can only use up to 64 vCPUs even when more vCPUs are allocated by a hypervisor. I've checked the latest available package for Jammy, but there was no change around CONFIG_NR_CPUS. https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3 $ lsb_release -r Release:20.04 $ dpkg -S /boot/config* linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm $ grep CONFIG_NR_CPUS /boot/config* /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1967131/+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 1967131] [NEW] CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic
Public bug reported: -kvm flavor has CONFIG_NR_CPUS=64 although -generic has CONFIG_NR_CPUS=8192 these days. It will be a problem especially when launching a VM on top of a hypervisor with more than 64 CPU threads available. Then the guest can only use up to 64 vCPUs even when more vCPUs are allocated by a hypervisor. I've checked the latest available package for Jammy, but there was no change around CONFIG_NR_CPUS. https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3 $ lsb_release -r Release:20.04 $ dpkg -S /boot/config* linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm $ grep CONFIG_NR_CPUS /boot/config* /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64 ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967131 Title: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic Status in linux-kvm package in Ubuntu: New Bug description: -kvm flavor has CONFIG_NR_CPUS=64 although -generic has CONFIG_NR_CPUS=8192 these days. It will be a problem especially when launching a VM on top of a hypervisor with more than 64 CPU threads available. Then the guest can only use up to 64 vCPUs even when more vCPUs are allocated by a hypervisor. I've checked the latest available package for Jammy, but there was no change around CONFIG_NR_CPUS. https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3 $ lsb_release -r Release:20.04 $ dpkg -S /boot/config* linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm $ grep CONFIG_NR_CPUS /boot/config* /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1967131/+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 1936842] Re: agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442
Let me know what log / log level you want to see to compare. I'm attaching the machine log of the VM for the time being. ** Attachment added: "machine-0.log" https://bugs.launchpad.net/juju/+bug/1936842/+attachment/5533786/+files/machine-0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1936842 Title: agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442 Status in juju: In Progress Status in ubuntu-fan package in Ubuntu: New Bug description: When one runs OpenStack with MTU=1500 underlying network, Neutron/OVN by default will create a tenant/overlay network with MTU=1442(1500-58). However, when deploying a workload on top, the Fan network with Juju will use MTU=1450 which is actually bigger than that. Then, Juju agent cannot be up inside LXD/Fan on top of OpenStack. OpenStack deployment is based on https://jaas.ai/openstack-base and k8s as a workload on top of OpenStack is: https://jaas.ai/kubernetes-core $ openstack network list +--+--+--+ | ID | Name | Subnets | +--+--+--+ | ba9880e3-5f07-4b49-aeda-20dfa8fe66ec | internal | 45efcc4c-fb99-4fe8-98a4-77195ec4aef1 | | e27b1cef-c53b-42e0-b307-8ba2e622c2dd | ext_net | 5315d907-ce90-4605-ad72-b78229965b40 | +--+--+--+ $ openstack network show internal +---+--+ | Field | Value| +---+--+ ... | mtu | 1442 | | name | internal | ... | provider:network_type | geneve | | provider:physical_network | None | | provider:segmentation_id | 1410 | ... +---+--+ $ juju machines -m k8s-on-openstack Machine StateDNS Inst id Series AZMessage 0started 192.168.151.75 0e96a5b1-3665-44f6-bcb7-4851ab6cd22d focal nova ACTIVE 0/lxd/0 pending juju-b9bd8b-0-lxd-0 focal nova Container started 1started 192.168.151.66 6bfa5d2e-24e6-42b8-b5ec-1f2a0d0e6b02 focal nova ACTIVE [openstack instance/VM provisioned by Juju - ens3: mtu=1442, fan-252: mtu=1450] juju-b9bd8b-k8s-on-openstack-0:~# ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1442 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether fa:16:3e:48:85:85 brd ff:ff:ff:ff:ff:ff 3: fan-252: mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff 4: ftun0: mtu 1392 qdisc noqueue master fan-252 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 92:d7:07:6e:b4:db brd ff:ff:ff:ff:ff:ff 5: lxdbr0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:03:0e:96 brd ff:ff:ff:ff:ff:ff 7: 0lxd0-0@if6: mtu 1450 qdisc noqueue master fan-252 state UP mode DEFAULT group default qlen 1000 link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff link-netnsid 0 [lxc config of LXD container as juju machine 0/lxd/0] juju-b9bd8b-k8s-on-openstack-0:~# lxc config show juju-b9bd8b-0-lxd-0 ... user.user-data: | #cloud-config apt_mirror: "" bootcmd: - install -D -m 644 /dev/null '/etc/netplan/99-juju.yaml' - |- printf '%s\n' 'network: version: 2 ethernets: eth0: match: macaddress: 00:16:3e:82:f9:44 dhcp4: true nameservers: search: [openstack.internal] addresses: [8.8.8.8, 8.8.4.4] mtu: 1450 ... devices: eth0: host_name: 0lxd0-0 hwaddr: 00:16:3e:82:f9:44 mtu: "1450" name: eth0 nictype: bridged parent: fan-252 type: nic [cloud-init-output.log - stuck at the initial apt update and also failing to fetch the agent binary] Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~20.04.1 running 'modules:config' at Mon, 19 Jul 2021 03:27:32 +. Up 53.99 seconds. Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Err:2 http://security.ubuntu.com/ubuntu focal-secu
[Kernel-packages] [Bug 1936842] Re: agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442
Hmm, I'm not sure where the difference comes from. With Juju 2.9.16 I still see mtu=1442 on VM NIC (expected) and mtu=1450 (bigger than underlying NIC) on fan-252 bridge. ubuntu@juju-913ba4-k8s-on-openstack-0:~$ brctl show bridge name bridge id STP enabled interfaces fan-252 8000.0653e0778a0a no ftun0 veth966fdd48 lxdbr0 8000.00163e2848ef no ubuntu@juju-913ba4-k8s-on-openstack-0:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1442 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether fa:16:3e:27:18:ce brd ff:ff:ff:ff:ff:ff 3: fan-252: mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 06:53:e0:77:8a:0a brd ff:ff:ff:ff:ff:ff 4: ftun0: mtu 1392 qdisc noqueue master fan-252 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 82:8a:c4:02:b5:77 brd ff:ff:ff:ff:ff:ff 5: lxdbr0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:28:48:ef brd ff:ff:ff:ff:ff:ff 7: veth966fdd48@if6: mtu 1450 qdisc noqueue master fan-252 state UP mode DEFAULT group default qlen 1000 link/ether 06:53:e0:77:8a:0a brd ff:ff:ff:ff:ff:ff link-netnsid 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1936842 Title: agent cannot be up on LXD/Fan network on OpenStack OVN/geneve mtu=1442 Status in juju: In Progress Status in ubuntu-fan package in Ubuntu: New Bug description: When one runs OpenStack with MTU=1500 underlying network, Neutron/OVN by default will create a tenant/overlay network with MTU=1442(1500-58). However, when deploying a workload on top, the Fan network with Juju will use MTU=1450 which is actually bigger than that. Then, Juju agent cannot be up inside LXD/Fan on top of OpenStack. OpenStack deployment is based on https://jaas.ai/openstack-base and k8s as a workload on top of OpenStack is: https://jaas.ai/kubernetes-core $ openstack network list +--+--+--+ | ID | Name | Subnets | +--+--+--+ | ba9880e3-5f07-4b49-aeda-20dfa8fe66ec | internal | 45efcc4c-fb99-4fe8-98a4-77195ec4aef1 | | e27b1cef-c53b-42e0-b307-8ba2e622c2dd | ext_net | 5315d907-ce90-4605-ad72-b78229965b40 | +--+--+--+ $ openstack network show internal +---+--+ | Field | Value| +---+--+ ... | mtu | 1442 | | name | internal | ... | provider:network_type | geneve | | provider:physical_network | None | | provider:segmentation_id | 1410 | ... +---+--+ $ juju machines -m k8s-on-openstack Machine StateDNS Inst id Series AZMessage 0started 192.168.151.75 0e96a5b1-3665-44f6-bcb7-4851ab6cd22d focal nova ACTIVE 0/lxd/0 pending juju-b9bd8b-0-lxd-0 focal nova Container started 1started 192.168.151.66 6bfa5d2e-24e6-42b8-b5ec-1f2a0d0e6b02 focal nova ACTIVE [openstack instance/VM provisioned by Juju - ens3: mtu=1442, fan-252: mtu=1450] juju-b9bd8b-k8s-on-openstack-0:~# ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1442 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether fa:16:3e:48:85:85 brd ff:ff:ff:ff:ff:ff 3: fan-252: mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff 4: ftun0: mtu 1392 qdisc noqueue master fan-252 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 92:d7:07:6e:b4:db brd ff:ff:ff:ff:ff:ff 5: lxdbr0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:03:0e:96 brd ff:ff:ff:ff:ff:ff 7: 0lxd0-0@if6: mtu 1450 qdisc noqueue master fan-252 state UP mode DEFAULT group default qlen 1000 link/ether 06:28:c7:b4:50:eb brd ff:ff:ff:ff:ff:ff link-netnsi
[Kernel-packages] [Bug 1916610] Re: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered
Initially we thought we were hit by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910201 But it looks like some patches are already in focal GA kernel like https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=d256617be44956fe4f048295a71b31d44d9104d9 -- 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/1916610 Title: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered Status in MAAS: New Status in linux package in Ubuntu: Incomplete Bug description: [ 274.743265] cloud-init[3738]: Traceback (most recent call last): [ 274.759256] cloud-init[3738]: File "/curtin/curtin/commands/main.py", line 202, in main [ 274.779262] cloud-init[3738]: ret = args.func(args) [ 274.795270] cloud-init[3738]: File "/curtin/curtin/log.py", line 97, in wrapper [ 274.811254] cloud-init[3738]: return log_time("TIMED %s: " % msg, func, *args, **kwargs) [ 274.831256] cloud-init[3738]: File "/curtin/curtin/log.py", line 79, in log_time [ 274.847264] cloud-init[3738]: return func(*args, **kwargs) [ 274.863256] cloud-init[3738]: File "/curtin/curtin/commands/block_meta.py", line 111, in block_meta [ 274.883256] cloud-init[3738]: return meta_custom(args) [ 274.899263] cloud-init[3738]: File "/curtin/curtin/commands/block_meta.py", line 1911, in meta_custom [ 274.919265] cloud-init[3738]: handler(command, storage_config_dict) [ 274.935255] cloud-init[3738]: File "/curtin/curtin/commands/block_meta.py", line 1652, in bcache_handler [ 274.955255] cloud-init[3738]: bcache_dev = bcache.create_backing_device(backing_device, cache_device, [ 274.975255] cloud-init[3738]: File "/curtin/curtin/block/bcache.py", line 479, in create_backing_device [ 274.995261] cloud-init[3738]: ensure_bcache_is_registered(backing_device, target_sysfs_path) [ 275.015257] cloud-init[3738]: File "/curtin/curtin/block/bcache.py", line 436, in ensure_bcache_is_registered [ 275.035254] cloud-init[3738]: raise RuntimeError("bcache device %s can't be registered" % [ 275.055257] cloud-init[3738]: RuntimeError: bcache device /dev/nvme1n1 can't be registered [ 275.075255] cloud-init[3738]: bcache device /dev/nvme1n1 can't be registered Full log of the boot/error: https://pastebin.canonical.com/p/ggNDCwCtGq/ Booting with hwe-20.04 works. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1916610/+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 1852432] Re: i40e: Setting VF MAC address causes General Protection Fault
The general protection fault was reproducible with the current 5.3 kernel as follows by creating 10 SR-IOV sequentially. After updating it to the -proposed one as linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection fault happened with the same operations. So we can consider the fix is verified with the eoan-proposed kernel. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1852432 Title: i40e: Setting VF MAC address causes General Protection Fault Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Bug description: [Impact] * Creating SR-IOV enabled VMs in Openstack can sometimes trigger the GPF and leave system unusable [Test Case] * Continuously spin up VFs and set MAC address with e.g. ifconfig [Fix] * The fix updates the VSI pointer passed down to i40e_set_vf_mac function() if the adapter is still in reset, preventing the GPF. [Regression Potential] * Regression potential should be low, as we're now updating the VSI using the ID stored in the VF pointer * Regressions could arise from issues in VF creation or reset, as that would corrupt the new VSI pointer * Patch was validated and tested in a production environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852432/+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 1852663] Re: i40e: general protection fault in i40e_config_vf_promiscuous_mode
The general protection fault is reproducible with the current 5.3 kernel as follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs sequentially. After updating it to the -proposed one as linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection fault happened with the same operations. So we can consider the fix is verified. === Dec 08 08:39:07 hostname kernel: i40e :af:00.1: Bring down and up the VF interface to make this change effective. Dec 08 08:39:07 hostname kernel: general protection fault: [#1] SMP PTI Dec 08 08:39:07 hostname kernel: CPU: 36 PID: 3225 Comm: libvirtd Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Dec 08 08:39:07 hostname kernel: Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 Dec 08 08:39:07 hostname kernel: RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Dec 08 08:39:07 hostname kernel: Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 Dec 08 08:39:07 hostname kernel: RSP: 0018:a7045d32b760 EFLAGS: 00010202 Dec 08 08:39:07 hostname kernel: RAX: RBX: 94e379bdb000 RCX: Dec 08 08:39:07 hostname kernel: RDX: RSI: 0600 RDI: 9583a4424350 Dec 08 08:39:07 hostname kernel: RBP: a7045d32b7b0 R08: R09: 9583a54d95e0 Dec 08 08:39:07 hostname kernel: R10: R11: 0100 R12: 94e379bdba28 Dec 08 08:39:07 hostname kernel: R13: 9583a4424008 R14: 94e379bdb338 R15: 010eb7eb8c61c8cb Dec 08 08:39:07 hostname kernel: FS: 7f495b017700() GS:9533bfa8() knlGS: Dec 08 08:39:07 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Dec 08 08:39:07 hostname kernel: CR2: 7f4967d89360 CR3: 004d839c0004 CR4: 007626e0 Dec 08 08:39:07 hostname kernel: DR0: DR1: DR2: Dec 08 08:39:07 hostname kernel: DR3: DR6: fffe0ff0 DR7: 0400 Dec 08 08:39:07 hostname kernel: PKRU: 5554 Dec 08 08:39:07 hostname kernel: Call Trace: Dec 08 08:39:07 hostname kernel: i40e_ndo_set_vf_port_vlan+0x1a2/0x440 [i40e] Dec 08 08:39:07 hostname kernel: do_setlink+0x53f/0xee0 Dec 08 08:39:07 hostname kernel: ? update_load_avg+0x596/0x620 Dec 08 08:39:07 hostname kernel: ? update_curr+0x7a/0x1d0 Dec 08 08:39:07 hostname kernel: ? __switch_to_asm+0x40/0x70 Dec 08 08:39:07 hostname kernel: ? __switch_to_asm+0x34/0x70 ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1852663 Title: i40e: general protection fault in i40e_config_vf_promiscuous_mode Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification [Impact] Assign some VFs to VMs, when deleting VMs, a general protection fault occurs in i40e_config_vf_promiscuous_mode general protection fault: [#1] SMP PTI CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic #22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0 RSP: 0018:b987b5c77760 EFLAGS: 00010202 RAX: RBX: 9bb5df5a9000 RCX: RDX: RSI: 0600 RDI: 9bace4bce350 RBP: b987b5c777b0 R08: R09: 9bace56a9da0 R10: R11: 0100 R12: 9bb5df5a9a28 R13: 9bace4bce008 R14: 9bb5df5a9338 R15: 26c2b975d54f5980 FS: 7f9f07fff700() GS:9bfcff48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa73c9c0e10 CR3: 00f6ab37a002 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e] do_setlink+0x53f/0xee0 ?update_load_avg+0x596/0x620 ?update_curr+0x7a/0x1d0 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 rtnl_setlink+0x113/0x150 rtnetlink_rcv_msg+0x296/0x340 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_cond_resched+0x19/0x40 ?rtnl_calcit.isra.30+0x120/0x120 netlink_rcv_skb+0x51/0x120 rtnetlink_rcv+0x15/0x20 netlink_unicast+0x1a4/0x250 netlink_sendmsg+0x2d7/0x3d0 sock_sendmsg+0x63/0
[Kernel-packages] [Bug 1852663] Re: i40e: general protection fault in i40e_config_vf_promiscuous_mode
The general protection fault is reproducible with the current 5.3 kernel as follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs sequentially. After updating it to the -proposed one as linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection fault happened with the same operations. So we can consider the fix is verified. -- 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/1852663 Title: i40e: general protection fault in i40e_config_vf_promiscuous_mode Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification [Impact] Assign some VFs to VMs, when deleting VMs, a general protection fault occurs in i40e_config_vf_promiscuous_mode general protection fault: [#1] SMP PTI CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic #22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0 RSP: 0018:b987b5c77760 EFLAGS: 00010202 RAX: RBX: 9bb5df5a9000 RCX: RDX: RSI: 0600 RDI: 9bace4bce350 RBP: b987b5c777b0 R08: R09: 9bace56a9da0 R10: R11: 0100 R12: 9bb5df5a9a28 R13: 9bace4bce008 R14: 9bb5df5a9338 R15: 26c2b975d54f5980 FS: 7f9f07fff700() GS:9bfcff48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa73c9c0e10 CR3: 00f6ab37a002 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e] do_setlink+0x53f/0xee0 ?update_load_avg+0x596/0x620 ?update_curr+0x7a/0x1d0 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 rtnl_setlink+0x113/0x150 rtnetlink_rcv_msg+0x296/0x340 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_cond_resched+0x19/0x40 ?rtnl_calcit.isra.30+0x120/0x120 netlink_rcv_skb+0x51/0x120 rtnetlink_rcv+0x15/0x20 netlink_unicast+0x1a4/0x250 netlink_sendmsg+0x2d7/0x3d0 sock_sendmsg+0x63/0x70 ___sys_sendmsg+0x2a9/0x320 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_raw_spin_unlock_bh+0x1e/0x20 ?release_sock+0x8f/0xa0 __sys_sendmsg+0x63/0xa0 ?__sys_sendmsg+0x63/0xa0 __x64_sys_sendmsg+0x1f/0x30 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue also happens when deleting k8s pod if VF is used by k8s pod, there was a bug reported in the e1000-devel mailing list https://sourceforge.net/p/e1000/mailman/message/36766306/ The fix is suggested by Billy McFall, to add protection when accessing the hash list(vsi->mac_filter_hash), but it's not upstream yet [Test Case] Spin up some VMs with VFs, then delete all VMs [Regression Potential] Low, the fix is to add a protection for a hash list, shouldn't have potential regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852663/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
[eoan] w/o -proposed multipass@eoan:~$ dpkg -L linux-modules-5.3.0-23-generic | egrep 'i40e|iavf' /lib/modules/5.3.0-23-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/5.3.0-23-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko multipass@eoan:~$ modinfo iavf modinfo: ERROR: Module iavf not found. w/ -proposed multipass@eoan:~$ dpkg -L linux-modules-5.3.0-24-generic | egrep 'i40e|iavf' /lib/modules/5.3.0-24-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/5.3.0-24-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko /lib/modules/5.3.0-24-generic/kernel/drivers/net/ethernet/intel/iavf /lib/modules/5.3.0-24-generic/kernel/drivers/net/ethernet/intel/iavf/iavf.ko multipass@eoan:~$ modinfo iavf | head -n 20 filename: /lib/modules/5.3.0-24-generic/kernel/drivers/net/ethernet/intel/iavf/iavf.ko version:3.2.3-k license:GPL v2 description:Intel(R) Ethernet Adaptive Virtual Function Network Driver author: Intel Corporation, alias: i40evf srcversion: 00921F94A92770CAD7CA1B0 alias: pci:v8086d1889sv*sd*bc*sc*i* alias: pci:v8086d37CDsv*sd*bc*sc*i* alias: pci:v8086d1571sv*sd*bc*sc*i* alias: pci:v8086d154Csv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: iavf vermagic: 5.3.0-24-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:37:BE:2D:4B:1D:D5:90:E9:EB:DD:1F:9B:10:21:1D:97:58:77:1C:1B sig_hashalgo: sha512 ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
[disco] w/o -proposed multipass@disco:~$ dpkg -L linux-modules-5.0.0-36-generic | egrep 'i40e|iavf' /lib/modules/5.0.0-36-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/5.0.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko multipass@disco:~$ modinfo iavf modinfo: ERROR: Module iavf not found. w/ -proposed multipass@disco:~$ dpkg -L linux-modules-5.0.0-37-generic | egrep 'i40e|iavf' /lib/modules/5.0.0-37-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/5.0.0-37-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko /lib/modules/5.0.0-37-generic/kernel/drivers/net/ethernet/intel/iavf /lib/modules/5.0.0-37-generic/kernel/drivers/net/ethernet/intel/iavf/iavf.ko multipass@disco:~$ modinfo iavf | head -n 20 filename: /lib/modules/5.0.0-37-generic/kernel/drivers/net/ethernet/intel/iavf/iavf.ko version:3.2.3-k license:GPL v2 description:Intel(R) Ethernet Adaptive Virtual Function Network Driver author: Intel Corporation, alias: i40evf srcversion: BA57B7333D3CCB0A335EBC2 alias: pci:v8086d1889sv*sd*bc*sc*i* alias: pci:v8086d37CDsv*sd*bc*sc*i* alias: pci:v8086d1571sv*sd*bc*sc*i* alias: pci:v8086d154Csv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: iavf vermagic: 5.0.0-37-generic SMP mod_unload sig_id: PKCS#7 signer: sig_key: sig_hashalgo: md4 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
[bionic] w/o -proposed ubuntu@bionic:~$ dpkg -L linux-modules-4.15.0-70-generic | grep i40e /lib/modules/4.15.0-70-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/4.15.0-70-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko ubuntu@bionic:~$ modinfo i40evf modinfo: ERROR: Module i40evf not found. w/ -proposed ubuntu@bionic:~$ dpkg -L linux-modules-4.15.0-71-generic | grep i40e /lib/modules/4.15.0-71-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/4.15.0-71-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko /lib/modules/4.15.0-71-generic/kernel/drivers/net/ethernet/intel/i40evf /lib/modules/4.15.0-71-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ubuntu@bionic:~$ modinfo i40evf filename: /lib/modules/4.15.0-71-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko version:3.0.1-k license:GPL description:Intel(R) XL710 X710 Virtual Function Network Driver author: Intel Corporation, srcversion: 18F6112020282F659B005E2 alias: pci:v8086d1889sv*sd*bc*sc*i* alias: pci:v8086d37CDsv*sd*bc*sc*i* alias: pci:v8086d1571sv*sd*bc*sc*i* alias: pci:v8086d154Csv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: i40evf vermagic: 4.15.0-71-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
Marking it back to Fix Committed as I got a clarification. https://lists.ubuntu.com/archives/kernel-team/2019-November/105480.html ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => Invalid ** Changed in: livecd-rootfs (Ubuntu Disco) Status: New => Invalid ** Changed in: livecd-rootfs (Ubuntu Eoan) 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
I'm just not sure how it can be merged to focal so raised a question: https://lists.ubuntu.com/archives/kernel-team/2019-November/105393.html -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: New Status in linux source package in Focal: In Progress Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Changed in: linux (Ubuntu Disco) Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto) ** Changed in: linux (Ubuntu Eoan) Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto) ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: New Status in linux source package in Focal: In Progress Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
I've filed a follow-up bug of neutron-openvswitch on kernel upgrade: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1851764 -- 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Fix Released Status in neutron: New Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
SRU request to D/E/F: https://lists.ubuntu.com/archives/kernel-team/2019-November/105221.html -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in livecd-rootfs source package in Bionic: New Status in linux source package in Disco: In Progress Status in livecd-rootfs source package in Disco: New Status in linux source package in Eoan: In Progress Status in livecd-rootfs source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** No longer affects: livecd-rootfs (Ubuntu) -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in livecd-rootfs source package in Bionic: New Status in linux source package in Disco: New Status in livecd-rootfs source package in Disco: New Status in linux source package in Eoan: New Status in livecd-rootfs source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
Posted again with a proper subscription instead of guest post: https://lists.ubuntu.com/archives/kernel-team/2019-October/104898.html -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: In Progress Status in livecd-rootfs package in Ubuntu: Invalid Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
Have sent to kernel-t...@lists.ubuntu.com ** Patch added: "0001-UBUNTU-Packaging-include-iavf-i40evf-in-generic.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+attachment/5298618/+files/0001-UBUNTU-Packaging-include-iavf-i40evf-in-generic.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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: In Progress Status in livecd-rootfs package in Ubuntu: Invalid Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Summary changed: - cloudimg: no i40evf module so no network available with SR-IOV enabled cloud + cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Nobuto Murata (nobuto) -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: In Progress Status in livecd-rootfs package in Ubuntu: Invalid Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no i40evf module so no network available with SR-IOV enabled cloud
Hmm, ixgbevf is in linux-modules-*-generic on bionic instead of modules- extra. So I'd like i40evf in the same modules-generic set. linux-modules-4.15.0-65-generic: /lib/modules/4.15.0-65-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko -- 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/1848481 Title: cloudimg: no i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no i40evf module is available so no network available with SR-IOV enabled cloud
** Summary changed: - cloudimg: no i40evf module is available so no network with SR-IOV enabled cloud + cloudimg: no i40evf module is available so no network available with SR-IOV enabled cloud ** Summary changed: - cloudimg: no i40evf module is available so no network available with SR-IOV enabled cloud + cloudimg: no i40evf module so no network available with SR-IOV enabled cloud -- 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/1848481 Title: cloudimg: no i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1773260] Re: It doesn't have the i40evf module in ubuntu 18.04 cloud image
*** This bug is a duplicate of bug 1848481 *** https://bugs.launchpad.net/bugs/1848481 ** Package changed: compiz-plugins-main (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1848481 cloudimg: no i40evf module is available so no network with SR-IOV enabled cloud -- 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/1773260 Title: It doesn't have the i40evf module in ubuntu 18.04 cloud image Status in linux package in Ubuntu: Confirmed Bug description: I downloaded ubuntu-18.04-server-cloudimg-amd64.img from [1] and create a KVM instance with it. After I assigned a xl710 vf to the instance , I could not find the interface in the instance. After researching, I found that there is no i40evf.ko in the image, however the driver module is built to module from the kernel config located in /boot/config-4.15.0-20-generic root@ubuntu:~# modinfo i40evf modinfo: ERROR: Module i40evf not found. root@ubuntu:~# cat /boot/config-4.15.0-20-generic | grep I40EVF CONFIG_I40EVF=m Does anybody know why? Thanks very much. [1]:http://uec- images.ubuntu.com/releases/releases/18.04/release/ubuntu-18.04-server- cloudimg-amd64.img To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773260/+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 1848481] [NEW] cloudimg: no i40evf module is available so no network available with SR-IOV enabled cloud
Public bug reported: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR- IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic cpe-onsite uec-images ** 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/1848481 Title: cloudimg: no i40evf module is available so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Bug description: For example with bionic, i40evf module is in linux-modules- extra-4.15*-generic. However, cloudimg doesn't have linux-modules- extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1753662] Re: [i40e] LACP bonding start up race conditions
#146~lp1753662ThreeCommits is better at some level (around 40% failure rate to 20%). Failure rate: 187/470 (39.8%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5 14:11:49 UTC 2018 Failure rate: 138/712 (19.4%), 4.4.0-122-generic #146~lp1753662ThreeCommits SMP Fri Apr 27 16:52:26 UTC 2018 Failure rate: 308/696 (44.3%), 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016 Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar 26 14:43:35 UTC 2018 Failure rate: 4/277 (1.4%), 4.12.0-041200rc3-generic #201804132111 SMP Fri Apr 13 21:13:47 UTC 2018 Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Just for the record, up-to-date numbers after the weekend. Failure rate: 167/422 (39.6%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5 14:11:49 UTC 2018 Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar 26 14:43:35 UTC 2018 Failure rate: 4/277 (1.4%), 4.12.0-041200rc3-generic #201804132111 SMP Fri Apr 13 21:13:47 UTC 2018 Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Ok, we have some numbers with the new host. Failure rate: 45/112 (40.2%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5 14:11:49 UTC 2018 Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar 26 14:43:35 UTC 2018 Failure rate: 4/277 (1.4%), 4.12.0-041200rc3-generic #201804132111 SMP Fri Apr 13 21:13:47 UTC 2018 Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 The xenial stock kernel and -120 from -proposed (just to see if LP: #1723127 is related or not) have around 40% failure rate. However, xenial kernel with artful config (4.4.0-040400-generic #201803261439) cuts down the failure rate on some level while we didn't expect any difference from failure rate point of view. 4.12.0-041200rc3 cuts down more, then HWE eliminates the occurrence. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Just for the record, I'm using the attached rc.local for testing. ** Attachment added: "rc.local" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5116629/+files/rc.local -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I ran HWE 4.13 just to make sure the result is the same as the previous host. And as we confirmed before, the issue is not reproducible with HWE 4.13. [HWE 4.13] Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 > We should first confirm that v4.12-rc3 with Artful configs is good before > working backwards. I built that kernel and posted it here: > > http://kernel.ubuntu.com/~jsalisbury/lp1753662 I will test it and report back early next week. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I ran HWE 4.13 just to make sure the result is the same as the previous host. And as we confirmed before, the issue is not reproducible with HWE 4.13. [stock xenial] Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar 26 14:43:35 UTC 2018 [HWE 4.13] Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 > We should first confirm that v4.12-rc3 with Artful configs is good before > working backwards. I built that kernel and posted it here: > > http://kernel.ubuntu.com/~jsalisbury/lp1753662 I will test it and report back early next week. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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.
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
FWIW, I tried PCI hot-plugging to try another way for faster iterations without reboot. https://paste.ubuntu.com/p/qDVkMcTYPQ/ However, the issue wasn't reproducible with hot-plugging. Rebooting is the easiest reproduction so far. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
4.4 kernel using the Artful configs didn't make much difference. Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar 26 14:43:35 UTC 2018 I will let stock 4.4 and 4.13 hwe run just to make sure to know the occurrence rate with this host. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
FWIW, kernel trace happens with the kernel in: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/comments/77 But I will let it running anyway since I'm not sure if it affects to the testing or not. [5.999557] rtc_cmos 00:00: setting system clock to 2018-04-11 15:52:23 UTC (1523461943) [5.999637] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [5.999637] EDD information not available. [6.856436] clocksource: tsc: mask: 0x max_cycles: 0x229834d6ac9, max_idle_ns: 440795285103 ns [6.872996] Freeing unused kernel memory: 1844K (81f71000 - 8213e000) [6.885727] Write protecting the kernel read-only data: 14336k [6.897566] Freeing unused kernel memory: 1964K (880001815000 - 880001a0) [6.911315] Freeing unused kernel memory: 272K (880001dbc000 - 880001e0) [6.924438] [ cut here ] [6.934158] WARNING: CPU: 16 PID: 1 at /home/jsalisbury/bugs/lp1753662/v4.4/linux/arch/x86/mm/dump_pagetables.c:225 note_page+0x649/0x840() [6.958330] x86/mm: Found insecure W+X mapping at address 8801/0x8801 [6.973431] Modules linked in: [6.982498] CPU: 16 PID: 1 Comm: swapper/0 Not tainted 4.4.0-040400-generic #201803261439 [6.997629] Hardware name: Dell Inc. PowerEdge R730/072T6D, BIOS 2.5.5 08/16/2017 [7.012149] 9d064fa9 883f6576fd48 813da8d8 [7.026822] 883f6576fd90 883f6576fd80 8107ec52 883f6576fe90 [7.041667] 8163 0004 [7.056684] Call Trace: [7.066183] [] dump_stack+0x44/0x5c [7.078824] [] warn_slowpath_common+0x82/0xc0 [7.092586] [] warn_slowpath_fmt+0x5c/0x80 [7.106139] [] note_page+0x649/0x840 [7.119215] [] ptdump_walk_pgd_level_core+0x2f9/0x430 [7.134087] [] ptdump_walk_pgd_level_checkwx+0x17/0x20 [7.149121] [] mark_rodata_ro+0xec/0x100 [7.162852] [] ? rest_init+0x80/0x80 [7.176273] [] kernel_init+0x1d/0xe0 [7.189752] [] ret_from_fork+0x3f/0x70 [7.203505] [] ? rest_init+0x80/0x80 [7.217134] ---[ end trace 43f75b6421b8d01c ]--- [7.235677] x86/mm: Checked W+X mappings: FAILED, 235610 W+X pages found. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp.
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Finally got a machine up and running. Will resume testing shortly. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
The new environment is not fully up yet to test. ETA would be by the end of this week. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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
Re: [Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
i.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Triaged; importance=High; assignee=joseph.salisb...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=linux; component=main; status=Triaged; importance=High; > assignee=joseph.salisb...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug cdo-qa-blocker cpe-onsite uec-images > xenial > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: jsalisbury nobuto ubuntu-kernel-bot > Launchpad-Bug-Reporter: Nobuto Murata (nobuto) > Launchpad-Bug-Modifier: Joseph Salisbury (jsalisbury) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: nobuto > -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
4.12-rc4 kernel with Xenial configs looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 - relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12.0-041200rc3 #20180324 - relatively bad (60 of 499 - 12.0%) ea094f3c830a67f252677aacba5d04ebcf55c4d9 v4.12.0-041200rc3 #201803201426 - relatively bad (30 of 208 - 14.4%) 55cbdaf6399de16b61d40d49b6c8bb739a877dea v4.12.0-041200rc4 #201803221452 - relatively bad (60 of 595 - 10.1%) Is it possible to build xenial kernel (4.4) with artful config just for testing? -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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/List
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Correction: Does HWE kernel mean it's with xenial configs? Or was it built with the source release config i.e. artful? -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
BTW, have we set the baseline of "good" in this bisection with xenial configs? > 4.13.0-36(xenial HW) - good (0 of 119 - 0%) Does HWE kernel man with xenial configs? Or was it built with the source release config i.e. artful? -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
55cbdaf6399de16b61d40d49b6c8bb739a877dea looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 - relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12.0-041200rc3 #20180324 - relatively bad (60 of 499 - 12.0%) ea094f3c830a67f252677aacba5d04ebcf55c4d9 v4.12.0-041200rc3 #201803201426 - relatively bad (30 of 208 - 14.4%) 55cbdaf6399de16b61d40d49b6c8bb739a877dea -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I was pretty occupied today, so I'm going to test 55cbdaf6399de16b61d40d49b6c8bb739a877dea now and report back my tomorrow morning. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12.0-041200rc3 #20180324 relatively bad (60 of 499 - 12.0%) ea094f3c830a67f252677aacba5d04ebcf55c4d9 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
ea094f3c830a67f252677aacba5d04ebcf55c4d9 looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12.0-041200rc3 #20180324 relatively bad (6 of 56 - 10.7%) ea094f3c830a67f252677aacba5d04ebcf55c4d9 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Ok, we see some differences with the three kernels. How do we want to proceed from here? v4.12-rc3 - bad (24 of 90 - 26.6%) http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3/ v4.12-rc3 #201803151851 - relatively good (2 of 151 - 1.3%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3/ (artful configs) v4.12-rc3 #201803161156 - relatively bad (36 or 249 - 14.5%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3-xenial-configs/ (xenial configs) -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond_check_xenial_4.12.0-041200rc3-generic_201803151851.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5081137/+files/bond_check_xenial_4.12.0-041200rc3-generic_201803151851.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
The new build of v4.12-rc3 is a good build (2 of 151). 4.12.0-041200rc3-generic #201803151851 v4.12-rc3 - bad (24 of 90 - 26.6%) http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/ v4.12-rc3 - relatively good (2 of 151 - 1.3%) http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3/ So what is the difference between those two? build config? -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
v4.12-rc4 is good, 1 of 146. Going to test v4.12-rc3. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
> We may have went wrong somewhere in the bisect. However, just to be sure, I > built a v4.12-rc4 test kernel. This kernel should be bad and contain the bug. > If it does not, it may be due to the configs I'm using to build the test > kernels. I'm not following since I thought we tested that already and good. > v4.12-rc4 - relatively good (1 of 70 - 1.4%) But anyway I will let it run with your newly built one. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond_check_xenial_4.12.0-041200rc1_201803141835.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5080093/+files/bond_check_xenial_4.12.0-041200rc1_201803141835.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
4681ee21d62cfed4364e09ec50ee8e88185dd628 looks good. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc1 #201803141835 - relatively good (1 of 113 - 0.9%) 4681ee21d62cfed4364e09ec50ee8e88185dd628 v4.12.0-041200rc1 #201803141333 - relatively good (1 of 217 - 0.5%) 171d8b9363725e122b164e6b9ef2acf2f751e387 v4.12.0-041200rc1 #201803131457 - relatively good (1 of 93 - 1.1%) d38162e4b5c643733792f32be4ea107c831827b4 v4.12.0-041200rc3 #201803121355 - relatively good (1 of 252 - 0.4%) 25f480e89a022d382ddc5badc23b49426e89eabc v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%) 400129f0a3ae989c30b37104bbc23b35c9d7a9a4 v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:s
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good. The next test is with 4681ee21d62cfed4364e09ec50ee8e88185dd628. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc1 #201803141333 - relatively good (1 of 217 - 0.5%) 171d8b9363725e122b164e6b9ef2acf2f751e387 v4.12.0-041200rc1 #201803131457 - relatively good (1 of 93 - 1.1%) d38162e4b5c643733792f32be4ea107c831827b4 v4.12.0-041200rc3 #201803121355 - relatively good (1 of 252 - 0.4%) 25f480e89a022d382ddc5badc23b49426e89eabc v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%) 400129f0a3ae989c30b37104bbc23b35c9d7a9a4 v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc1_201803141333.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5079946/+files/bond_check_xenial_4.12.0-041200rc1_201803141333.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
The test is still in progress, but so far 171d8b9363725e122b164e6b9ef2acf2f751e387 looks good (0 of 21). Since I already downloaded the kernel locally, please go ahead to build the next one. Thanks, -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
d38162e4b5c643733792f32be4ea107c831827b4 looks good. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc1 #201803131457 - relatively good (1 of 93 - 1.1%) d38162e4b5c643733792f32be4ea107c831827b4 v4.12.0-041200rc3 #201803121355 - relatively good (1 of 252 - 0.4%) 25f480e89a022d382ddc5badc23b49426e89eabc v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%) 400129f0a3ae989c30b37104bbc23b35c9d7a9a4 v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc1_201803131457.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5079020/+files/bond_check_xenial_4.12.0-041200rc1_201803131457.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:s
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
The test is still in progress, but so far d38162e4b5c643733792f32be4ea107c831827b4 looks good (1 of 37). Since I already downloaded the kernel locally, please go ahead to build the next one. Thanks, -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Oh wait, > I built the next test kernel, up to the following commit: > d38162e4b5c643733792f32be4ea107c831827b4 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1753662 d38162e4b5c643733792f32be4ea107c831827b4 looks in-between v4.12-rc3 and rc4 which is expected. https://github.com/torvalds/linux/commit/d38162e4b5c643733792f32be4ea107c831827b4 However, the link says "rc1". http://kernel.ubuntu.com/~jsalisbury/lp1753662/linux-image-4.12.0-041200rc1-generic_4.12.0-041200rc1.201803131457_amd64.deb Can you confirm that the 4.12.0-041200rc1 is the expected kernel test? -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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/L
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
@Joseph, Will do. Just as a possibility, I could build a kernel on the host if that's helpful. Because the host is already reserved for this testing and has hundreds of GBs of memory and many CPU cores. If you have a pointer how to replicate your build process, that would be great. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
25f480e89a022d382ddc5badc23b49426e89eabc looks good. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc3 #201803121355 - relatively good (1 of 252 - 0.4%) 25f480e89a022d382ddc5badc23b49426e89eabc v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%) 400129f0a3ae989c30b37104bbc23b35c9d7a9a4 v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc3_201803121355.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5077704/+files/bond_check_xenial_4.12.0-041200rc3_201803121355.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdg
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
400129f0a3ae989c30b37104bbc23b35c9d7a9a4 looks good. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%) 400129f0a3ae989c30b37104bbc23b35c9d7a9a4 v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc3_201803090724.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5074297/+files/bond_check_xenial_4.12.0-041200rc3_201803090724.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
0bb230399fd337cc9a838d47a0c9ec3433aa612e seems good. I'm ready for the next test. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%) 0bb230399fd337cc9a838d47a0c9ec3433aa612e v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc3_201803081620.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5073995/+files/bond_check_xenial_4.12.0-041200rc3_201803081620.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://laun
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond_check_xenial_hwe_4.13_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5073884/+files/bond_check_xenial_hwe_4.13_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I run xenial HWE over a night while sleeping, the result was 0/119. The next test is with: v4.12.0-041200rc3 #201803081620 - ? 0bb230399fd337cc9a838d47a0c9ec3433aa612e 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc3 #201803080803 - good (0 of 22 - 0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) 4.13.0-36(xenial HW) - good (0 of 119 - 0%) -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
4.12.0-041200rc3-generic #201803080803 looks good. Please proceed to the next one. I will test it my tomorrow which would be 12 hours later from now. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12.0-041200rc3 - good (0 of 22 - 0%) #201803080803 ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) ** Attachment added: "bond_check_xenial_4.12.0-041200rc3_201803080803.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072906/+files/bond_check_xenial_4.12.0-041200rc3_201803080803.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscri
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
So far 0 of 6 with 4.12.0-041200rc3-generic #201803080803. But I will keep it running for a while to see if it becomes close to 30% or 0%. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Ok, 25% - 30% seems a baseline. I'd like to make sure v4.13 is really 0% for longer running test, but will do the bisection of v4.12-rc3 and v4.12-rc4 first. 4.4.0-116(xenial) - bad (9 of 31 - 29.0%) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 of 68 - 7.4%) v4.13 - good (0 of 41 - 0%) ** Attachment added: "bond_check_xenial_4.4.0-116_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072759/+files/bond_check_xenial_4.4.0-116_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
With rc2 result. It looks like there is a noticeable difference between v4.12-rc3 and v4.12-rc4. @Joseph, can you please start looking into diffs? I'm keeping one dedicated node just for this testing, so I can run the same script one by one for more bisections. v4.12-rc1 - bad (3 of 3) v4.12-rc2 - bad (15 of 53 - 28.3%) v4.12-rc3 - bad (24 of 90 - 26.6%) v4.12-rc4 - relatively good (1 of 70 - 1.4%) v4.12 - relatively good (5 out of 68 - 7.4%) v4.13 - good (0 out of 41 - 0%) FWIW, I will run the same test with xenial's 4.4 kernel to make sure around 30% is the base line of "bad". ** Attachment added: "bond_check_xenial_mainline_4.12-rc2_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072683/+files/bond_check_xenial_mainline_4.12-rc2_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: ht
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
With rc3, will test rc2 next. v4.12-rc1 - bad (3 out of 3) v4.12-rc3 - mixture result (24 out of 90) v4.12-rc4 - relatively good (1 out of 70) v4.12 - relatively good (5 out of 68) v4.13 - good (0 out of 41) ** Attachment added: "bond_check_xenial_mainline_4.12-rc3_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5072525/+files/bond_check_xenial_mainline_4.12-rc3_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I have let rc4 run for hours. v4.12-rc1 - bad (3 out of 3) v4.12-rc4 - relatively good (1 out of 70) v4.12 - relatively good (5 out of 68) v4.13 - good (0 out of 41) I will let rc3 run during my night. ** Attachment added: "bond_check_xenial_mainline_4.12-rc4_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071915/+files/bond_check_xenial_mainline_4.12-rc4_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
For the record, v4.12-rc1 - bad (3 out of 3) v4.12 - relatively good (5 out of 68) v4.13 - good (0 out of 41) ** Attachment added: "bond_check_xenial_mainline_4.13_full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071491/+files/bond_check_xenial_mainline_4.13_full.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond_check_xenial_mainline_4.12_full.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071492/+files/bond_check_xenial_mainline_4.12_full.log.gz -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
I run an overnight test with v4.12 just to make sure it really fixed the issue. It happened sometimes, but way less frequencies. We may need to test it longer for "good" cases since the patch may not be only one. Anyway, the current status is: v4.12-rc1 with i40e 2.1.14 - bad (3 out of 3) v4.12 with i40e 2.1.14 - relatively good (5 out of 68) The next test would be with v4.12-rc4. -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Correction. I thought v4.12-rc1 had i40e 2.1.7 because of: https://github.com/torvalds/linux/commit/15990832cd3e7e8904f8dacdabfa33adb9a836d6 But it actually has 2.1.14 from the log output. So the correct status is: v4.12-rc1 with i40e 2.1.14 - bad v4.12 with i40e 2.1.14 - good -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
v4.12-rc1 with i40e 2.1.7 - bad v4.12 with i40e 2.1.14 - good I'm running out of time. So more bisections are for tomorrow. ** Attachment added: "bond_check_xenial_mainline_4.12-rc1.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070861/+files/bond_check_xenial_mainline_4.12-rc1.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
v4.11 with i40e 1.6.27 - bad v4.12 with i40e 2.1.14 - good next: v4.12-rc1 with i40e 2.1.7 - ? ** Attachment added: "bond_check_xenial_mainline_4.12.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070835/+files/bond_check_xenial_mainline_4.12.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Not reproducible with 4.13-rc1 with 5 reboots. 4.10 - bad 4.11 - bad 4.13-rc1 - good The next is 4.12. ** Attachment added: "bond_check_xenial_mainline_4.13-rc1.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070827/+files/bond_check_xenial_mainline_4.13-rc1.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Reproducible with: v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ The next is v4.13-rc1. ** Attachment added: "bond_check_xenial_mainline_4.11.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070785/+files/bond_check_xenial_mainline_4.11.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Reproducible with: 4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ The next test will be with: v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ ** Attachment added: "bond_check_xenial_mainline_4.10.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070741/+files/bond_check_xenial_mainline_4.10.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
Thanks, I was running some tests with existing HWE kernels in xenial repo like linux-image-4.8.0-58-generic, linux-image-4.10.0-42-generic and linux-image-4.13.0-36-generic. It looks like 4.10 is the last bad one and 4.13 is the first good one. Let me double-check with those two: 4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ 4.13 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/ -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
The record of xenial default kernel. ** Attachment added: "bond_check_xenial.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070691/+files/bond_check_xenial.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
For the record of testing. ** Attachment added: "bond_check_xenial_c15e07b02bf0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070633/+files/bond_check_xenial_c15e07b02bf0.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
The kernel with c15e07b02bf0 didn't make a difference on the race condition. The issue is still reproducible. Let me know when you need my testing again with different kernels. So far, I'm using rc.local below to reboot the same node multiple times. #!/bin/sh exec >> /root/bond_check.log 2>&1 echo echo '' echo date -R uname -a ethtool -i eno1 modinfo i40e path=$(modinfo i40e | grep filename: | awk '{print $2}') sha256sum "$path" package=$(dpkg -S "$path" | cut -d: -f1) apt-cache policy "$package" if [ "$(grep state /proc/net/bonding/bond* | grep -c -v -w 61)" != 0 ]; then echo echo '*** Unexpected LACP status ***' grep -r '.*' /proc/net/bonding/bond* fi sleep 300 reboot exit 0 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
This might be related (not exactly the same): https://sourceforge.net/p/e1000/bugs/524/ One says 1.6.42 fixed his issue. Looks like Intel has around 10 releases between 1.4.25 and 2.1.14, so it may not be handy to bisect. https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=82947 -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Confirmed Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond2_status.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070466/+files/bond2_status.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: New Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "interfaces.50-cloud-init.cfg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070467/+files/interfaces.50-cloud-init.cfg -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: New Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] Re: [i40e] LACP bonding start up race conditions
** Attachment added: "bond1_status.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070465/+files/bond1_status.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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: New Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+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 1753662] [NEW] [i40e] LACP bonding start up race conditions
Public bug reported: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell- branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cpe-onsite uec-images xenial -- 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: New Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes su
[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
Is there anyone from ubuntu-fan developers willing to satisfy SRU requirements below? > Blocked on: > > * SRU paperwork > * Fixes for future stable releases > * Fix for Bionic I could try those, but it's not ideal since I have to go through sponsorship processes and guess the intention of the patch. This bug is critical to me since the proposed workaround for MAAS deployments as adding -proposed in MAAS is not realistic in production cloud because: - MAAS is not capable to add ubuntu-release aware apt line for -proposed using the custom repository management (trusty nodes will also have xenial-proposed apt line unexpectedly) - MAAS cannot specify the pin-priority of xenial-proposed using the custom repository management so unnecessary kernels and grub will be installed from -proposed I ended up using a little bit verbose late_commands in curtin_userdata which is not so handy: https://paste.ubuntu.com/26319353/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Invalid Status in OPNFV: Fix Committed Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Status in ubuntu-fan source package in Zesty: Confirmed Status in ubuntu-fan source package in Artful: Confirmed Status in ubuntu-fan source package in Bionic: Confirmed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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 1509799] Re: [FUJITSU FMVS90TB] freezes once or twice a day
The soft lockup trace is no longer reproducible after updating the system *and* disable "powertop --auto-tune" *and* disable touchpanel from BIOS. Closing this for now, but if I can reproducible it firmly with enabling some options, I will report it again. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1509799 Title: [FUJITSU FMVS90TB] freezes once or twice a day Status in linux package in Ubuntu: Invalid Bug description: This laptop freezes once or twice a day. When it freezes, no response to sysrq keys. [28932.919430] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [thermald:976] [28932.919436] Modules linked in: ctr ccm rfcomm xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables veth openvswitch libcrc32c xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables msr bnep nls_iso8859_1 arc4 intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common snd_seq_midi snd_seq_midi_event btusb videodev btrtl btbcm joydev input_leds iwlwifi btintel serio_raw snd_rawmidi hid_multitouch media snd_seq snd_hda_codec_hdmi rtsx_pci_ms snd_hda_codec_realtek memstick cfg80211 snd_hda_codec_generic bluetooth snd_soc_rt5640 [28932.919473] lpc_ich snd_hda_intel snd_soc_rl6231 snd_hda_codec snd_seq_device snd_soc_core snd_hda_core mei_me shpchp snd_hwdep mei snd_compress ac97_bus snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core 8250_fintek snd_timer snd_soc_sst_acpi mac_hid 8250_dw i2c_designware_platform spi_pxa2xx_platform i2c_designware_core fujitsu_laptop acpi_pad snd kvm_intel soundcore kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit psmouse drm_kms_helper drm ahci e1000e libahci rtsx_pci ptp pps_core sdhci_acpi video sdhci i2c_hid hid [28932.919508] CPU: 3 PID: 976 Comm: thermald Tainted: GW 4.2.0-16-generic #19-Ubuntu [28932.919510] Hardware name: FUJITSU FMVS90TB/FJNB285, BIOS Version 1.06 12/25/2014 [28932.919511] task: 88033df4 ti: 88033df48000 task.ti: 88033df48000 [28932.919513] RIP: 0010:[] [] smp_call_function_single+0xdb/0x130 [28932.919518] RSP: 0018:88033df4bc08 EFLAGS: 0202 [28932.919519] RAX: RBX: 88033df4bdb8 RCX: [28932.919520] RDX: 0003 RSI: 00fb RDI: 0282 [28932.919521] RBP: 88033df4bc58 R08: 88033a422028 R09: 8800a96afb80 [28932.919522] R10: 8802fbaeb000 R11: 88033a05a100 R12: 0002 [28932.919523] R13: 88033e03c240 R14: 0286 R15: 88033df4bba8 [28932.919524] FS: 7f771c9dc700() GS:88034ecc() knlGS: [28932.919525] CS: 0010 DS: ES: CR0: 80050033 [28932.919526] CR2: 7fed3e99 CR3: 00033dd55000 CR4: 003406e0 [28932.919527] Stack: [28932.919528] 8800a96afb80 8802ffa8e300 88033df4bc68 [28932.919530] 813f7600 88033df4bc70 0003 12bf86d1 [28932.919532] 88033df4bccc 88033df4bcc8 88033df4bca8 813f779d [28932.919533] Call Trace: [28932.919538] [] ? ucs2_strncmp+0x50/0x50 [28932.919540] [] rdmsr_on_cpu+0x5d/0x90 [28932.919546] [] sys_get_curr_temp+0x41/0xb0 [x86_pkg_temp_thermal] [28932.919549] [] thermal_zone_get_temp+0x79/0x120 [28932.919552] [] temp_show+0x2d/0x70 [28932.919554] [] dev_attr_show+0x20/0x50 [28932.919557] [] ? mutex_lock+0x16/0x40 [28932.919560] [] sysfs_kf_seq_show+0xbc/0x130 [28932.919562] [] kernfs_seq_show+0x23/0x30 [28932.919564] [] seq_read+0xec/0x390 [28932.919566] [] kernfs_fop_read+0x10a/0x160 [28932.919569] [] ? security_file_permission+0xa0/0xc0 [28932.919571] [] __vfs_read+0x18/0x40 [28932.919572] [] vfs_read+0x87/0x130 [28932.919574] [] SyS_read+0x55/0xc0 [28932.919576] [] entry_SYSCALL_64_fastpath+0x16/0x75 [28932.919579] Code: 00 00 75 70 48 83 c4 40 5b 41 5c 5d c3 48 8d 75 c8 48 89 d1 89 df 4c 89 e2 e8 12 fe ff ff 8b 55 e0 83 e2 01 74 cf f3 90 8b 55 e0 <83> e2 01 75 f6 eb c3 8b 05 30 65 df 00 85 c0 75 85 80 3d 2c 85 [28932.919599] Kernel panic - not syncing: softlockup: hung tasks [28932.919622] CPU: 3 PID: 976 Comm: thermald Tainted: GWL 4.2.0-16-generic #19-Ubuntu [28932.919647] Hardware name: FUJITSU FMVS90TB/FJN
[Kernel-packages] [Bug 1509799] Re: [FUJITSU FMVS90TB] freezes once or twice a day
>From the sticker: LIFEBOOK SH90/T FMVS90TB Specs are as follows for your reference. http://www.fmworld.net/fmv/sh/1501/spec/ ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Description changed: This laptop freezes once or twice a day. When it freezes, no response to sysrq keys. - ProblemType: KernelCrash - DistroRelease: Ubuntu 15.10 + [28932.919430] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [thermald:976] + [28932.919436] Modules linked in: ctr ccm rfcomm xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables veth openvswitch libcrc32c xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables msr bnep nls_iso8859_1 arc4 intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common snd_seq_midi snd_seq_midi_event btusb videodev btrtl btbcm joydev input_leds iwlwifi btintel serio_raw snd_rawmidi hid_multitouch media snd_seq snd_hda_codec_hdmi rtsx_pci_ms snd_hda_codec_realtek memstick cfg80211 snd_hda_codec_generic bluetooth snd_soc_rt5640 + [28932.919473] lpc_ich snd_hda_intel snd_soc_rl6231 snd_hda_codec snd_seq_device snd_soc_core snd_hda_core mei_me shpchp snd_hwdep mei snd_compress ac97_bus snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core 8250_fintek snd_timer snd_soc_sst_acpi mac_hid 8250_dw i2c_designware_platform spi_pxa2xx_platform i2c_designware_core fujitsu_laptop acpi_pad snd kvm_intel soundcore kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit psmouse drm_kms_helper drm ahci e1000e libahci rtsx_pci ptp pps_core sdhci_acpi video sdhci i2c_hid hid + [28932.919508] CPU: 3 PID: 976 Comm: thermald Tainted: GW 4.2.0-16-generic #19-Ubuntu + [28932.919510] Hardware name: FUJITSU FMVS90TB/FJNB285, BIOS Version 1.06 12/25/2014 + [28932.919511] task: 88033df4 ti: 88033df48000 task.ti: 88033df48000 + [28932.919513] RIP: 0010:[] [] smp_call_function_single+0xdb/0x130 + [28932.919518] RSP: 0018:88033df4bc08 EFLAGS: 0202 + [28932.919519] RAX: RBX: 88033df4bdb8 RCX: + [28932.919520] RDX: 0003 RSI: 00fb RDI: 0282 + [28932.919521] RBP: 88033df4bc58 R08: 88033a422028 R09: 8800a96afb80 + [28932.919522] R10: 8802fbaeb000 R11: 88033a05a100 R12: 0002 + [28932.919523] R13: 88033e03c240 R14: 0286 R15: 88033df4bba8 + [28932.919524] FS: 7f771c9dc700() GS:88034ecc() knlGS: + [28932.919525] CS: 0010 DS: ES: CR0: 80050033 + [28932.919526] CR2: 7fed3e99 CR3: 00033dd55000 CR4: 003406e0 + [28932.919527] Stack: + [28932.919528] 8800a96afb80 8802ffa8e300 88033df4bc68 + [28932.919530] 813f7600 88033df4bc70 0003 12bf86d1 + [28932.919532] 88033df4bccc 88033df4bcc8 88033df4bca8 813f779d + [28932.919533] Call Trace: + [28932.919538] [] ? ucs2_strncmp+0x50/0x50 + [28932.919540] [] rdmsr_on_cpu+0x5d/0x90 + [28932.919546] [] sys_get_curr_temp+0x41/0xb0 [x86_pkg_temp_thermal] + [28932.919549] [] thermal_zone_get_temp+0x79/0x120 + [28932.919552] [] temp_show+0x2d/0x70 + [28932.919554] [] dev_attr_show+0x20/0x50 + [28932.919557] [] ? mutex_lock+0x16/0x40 + [28932.919560] [] sysfs_kf_seq_show+0xbc/0x130 + [28932.919562] [] kernfs_seq_show+0x23/0x30 + [28932.919564] [] seq_read+0xec/0x390 + [28932.919566] [] kernfs_fop_read+0x10a/0x160 + [28932.919569] [] ? security_file_permission+0xa0/0xc0 + [28932.919571] [] __vfs_read+0x18/0x40 + [28932.919572] [] vfs_read+0x87/0x130 + [28932.919574] [] SyS_read+0x55/0xc0 + [28932.919576] [] entry_SYSCALL_64_fastpath+0x16/0x75 + [28932.919579] Code: 00 00 75 70 48 83 c4 40 5b 41 5c 5d c3 48 8d 75 c8 48 89 d1 89 df 4c 89 e2 e8 12 fe ff ff 8b 55 e0 83 e2 01 74 cf f3 90 8b 55 e0 <83> e2 01 75 f6 eb c3 8b 05 30 65 df 00 85 c0 75 85 80 3d 2c 85 + [28932.919599] Kernel panic - not syncing: softlockup: hung tasks + [28932.919622] CPU: 3 PID: 976 Comm: thermald Tainted: GWL 4.2.0-16-generic #19-Ubuntu + [28932.919647] Hardware name: FUJITSU FMVS90TB/FJNB285, BIOS Version 1.06 12/25/2014 + [28932.919671] 12bf86d1 88034ecc3df8 817e8c09 + [28932.919694] 81aae17a 88034ecc3e78 817e5f9b + [28932.919718] 0008 88034ecc3e88 88034ecc3e28 12bf86d1 + [28932.919741] Call Trace: + [28932.
[Kernel-packages] [Bug 1509799] [NEW] [FUJITSU FMVS90TB] freezes once or twice a day
Public bug reported: This laptop freezes once or twice a day. When it freezes, no response to sysrq keys. ProblemType: KernelCrash DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nobuto 4688 F pulseaudio /dev/snd/controlC0: nobuto 4688 F pulseaudio Date: Sun Oct 25 21:10:09 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=39f8577a-7689-409c-978e-c0f728e6c1c4 InstallationDate: Installed on 2015-09-30 (24 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150930) MachineType: FUJITSU FMVS90TB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:512M i8042.nomux vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kernelcrash wily -- 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/1509799 Title: [FUJITSU FMVS90TB] freezes once or twice a day Status in linux package in Ubuntu: New Bug description: This laptop freezes once or twice a day. When it freezes, no response to sysrq keys. ProblemType: KernelCrash DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nobuto 4688 F pulseaudio /dev/snd/controlC0: nobuto 4688 F pulseaudio Date: Sun Oct 25 21:10:09 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=39f8577a-7689-409c-978e-c0f728e6c1c4 InstallationDate: Installed on 2015-09-30 (24 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150930) MachineType: FUJITSU FMVS90TB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:512M i8042.nomux vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509799/+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 873087] Re: [FUJITSU FMVMGD75P] SD card is not recognized
This issue is no longer reproducible with at least current updated kernel on precise. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/873087 Title: [FUJITSU FMVMGD75P] SD card is not recognized Status in “linux” package in Ubuntu: Invalid Bug description: SD card in internal slot is not recognized. This issue is regression from natty on the same hardware, I'm afraid. dmesg output when slot-in is: [ 154.521961] mmc0: Got command interrupt 0x0003 even though no command operation was in progress. [ 154.521968] sdhci: === REGISTER DUMP (mmc0)=== [ 154.521977] sdhci: Sys addr: 0x | Version: 0xc002 [ 154.521985] sdhci: Blk size: 0x | Blk cnt: 0x [ 154.521993] sdhci: Argument: 0x8c08 | Trn mode: 0x [ 154.522001] sdhci: Present: 0x01ff | Host ctl: 0x0005 [ 154.522009] sdhci: Power:0x000f | Blk gap: 0x [ 154.522017] sdhci: Wake-up: 0x | Clock:0xa507 [ 154.522025] sdhci: Timeout: 0x | Int stat: 0x [ 154.522033] sdhci: Int enab: 0x00ff00c3 | Sig enab: 0x00ff00c3 [ 154.522041] sdhci: AC12 err: 0x | Slot int: 0x [ 154.522049] sdhci: Caps: 0x03e121a1 | Caps_1: 0x [ 154.522058] sdhci: Cmd: 0x341a | Max curr: 0x00ff [ 154.522064] sdhci: Host ctl2: 0x [ 154.522068] sdhci: === ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic-pae 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 1.23-0ubuntu3 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nobuto 1692 F pulseaudio CRDA: Error: [Errno 2] そのようなファイルやディレクトリはありません Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf0a0 irq 46' Mixer name : 'Realtek ALC269' Components : 'HDA:10ec0269,10cf,0014 HDA:11c11040,10cf14a5,00100200' Controls : 17 Simple ctrls : 11 CheckboxSubmission: 1d84ca1b2de43c2199974f7b8a6ca9cb CheckboxSystem: 0657dd966bc74d2b22e7c94051aa55af Date: Thu Oct 13 06:07:59 2011 EcryptfsInUse: Yes GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=b870a629-87d3-43ea-ae27-543c784c81b5 HotplugNewDevices: HotplugNewMounts: InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111007) MachineType: FUJITSU FMVMGD75P PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=b4b335f6-3116-4738-a884-8b65a4e9e98e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic-pae N/A linux-backports-modules-3.0.0-12-generic-pae N/A linux-firmware1.60 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNB1E6 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd03/30/2009:svnFUJITSU:pnFMVMGD75P:pvr:rvnFUJITSU:rnFJNB1E6:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVMGD75P dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/873087/+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 1189896] Re: [FUJITSU FMVS54KR] always boot with minimum backlight brightness
This issue is no longer reproducible with latest trusty kernel. Linux lifebook 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1189896 Title: [FUJITSU FMVS54KR] always boot with minimum backlight brightness Status in “linux” package in Ubuntu: Invalid Bug description: It always boot with minimum backlight brightness. just after the boot: /sys/class/backlight/acpi_video0/actual_brightness:0 /sys/class/backlight/acpi_video0/brightness:0 /sys/class/backlight/acpi_video0/max_brightness:100 /sys/class/backlight/intel_backlight/actual_brightness:41 /sys/class/backlight/intel_backlight/brightness:3487 /sys/class/backlight/intel_backlight/max_brightness:3487 I can change brightness after boot with hotkeys. ProblemType: BugDistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nobuto 2339 F pulseaudio Date: Tue Jun 11 21:55:10 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e1bbd58c-ba6f-4896-95d9-3bdb60dde26d InstallationDate: Installed on 2013-04-21 (50 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420) MachineType: FUJITSU FMVS54KR MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic.efi.signed root=UUID=f0ca756b-8b3f-4cb2-908f-5d8e2273c93e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-08 (2 days ago) dmi.bios.date: 01/07/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB24F dmi.board.vendor: FUJITSU dmi.board.version: D2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS54KR dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189896/+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