[Kernel-packages] [Bug 1933245] Re: mlx5_core: Error cqe on cqn leads to hang
As expected 5.11 did crash. Unfortunately the vmcore is not useful as it filled up disk space so it is incomplete and I had to remove it to free up some space. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933245 Title: mlx5_core: Error cqe on cqn leads to hang Status in linux-signed-hwe-5.8 package in Ubuntu: Incomplete Bug description: This bug seems to be same as this one https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1887723 Same workaround - iommu=pt - seems to prevent the hang on our new server. It is running for 5 days now without issues. Before it crashed/hanged within a day. NICs are c1:00.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5] Subsystem: Mellanox Technologies ConnectX®-5 EN network interface card for OCP2.0, Type 1, with host management, 25GbE dual-port SFP28, PCIe3.0 x8, no bracket Halogen free ; MCX542B-ACAN Flags: bus master, fast devsel, latency 0, IRQ 338, NUMA node 0 Memory at 1801a00 (64-bit, prefetchable) [size=32M] Expansion ROM at c000 [disabled] [size=1M] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=64 Masked- Capabilities: [c0] Vendor Specific Information: Len=18 Capabilities: [40] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [180] Single Root I/O Virtualization (SR-IOV) Capabilities: [230] Access Control Services Kernel driver in use: mlx5_core Kernel modules: mlx5_core not sure if it is relevant but two NICs run in LACP bond with following settings parameters: mode: 802.3ad lacp-rate: fast down-delay: 200 mii-monitor-interval: 100 transmit-hash-policy: layer3+4 I managed to capture vmcore and will try to disect it a bit when I find some time (hopefully soon) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 14:22:23 2021 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933245/+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 1929833] Re: bluez: meshctl missing
I do see an update to 5.88 with https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca, but I do not see the binary meshctl being added. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1929833] Re: bluez: meshctl missing
I do see an update of bluez to 5.58 https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca 5.58, but no changes that would add meshctl. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1923049] Re: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+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 1922350] Re: missing firmware reported when updating initramfs
** Attachment added: "5.13.0-1003-oem_focal.list" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1922350/+attachment/5506604/+files/5.13.0-1003-oem_focal.list -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1922350 Title: missing firmware reported when updating initramfs Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: In Progress Bug description: [SRU Justification] [Impact] Some kernel firmwares might be landed after linux-firmware forked for each series, or for LTS series, kernels of new versions may claim additional ones that were not previously available. This leaves devices fail to function correctly while they ought to. With a checking script that enumerates all the blobs available in upstream repo and in the Ubuntu fork of a given series, e.g. hirsute, iterate through all the installed kernel modules of a given version to check if claimed firmware blobs are available in Ubuntu's fork. Following kernel version/series have been checked: * 5.11.0-14-generic/hirsute * 5.8.0-48-generic/groovy * 5.4.0-70-generic/focal * 5.6.0-1052-oem/focal * 5.8.0-48-generic/focal * 5.10.0-1019-oem/focal * 4.15.0-140-generic/bionic * 4.18.0-25-generic/bionic * 5.0.0-65-generic/bionic * 5.4.0-70-generic/bionic And it gives following files were missing in at least one of above cases: * amdgpu/arcturus_asd.bin * amdgpu/arcturus_gpu_info.bin * amdgpu/arcturus_mec.bin * amdgpu/arcturus_mec2.bin * amdgpu/arcturus_rlc.bin * amdgpu/arcturus_sdma.bin * amdgpu/arcturus_smc.bin * amdgpu/arcturus_sos.bin * amdgpu/arcturus_ta.bin * amdgpu/arcturus_vcn.bin * amdgpu/navi12_asd.bin * amdgpu/navi12_ce.bin * amdgpu/navi12_dmcu.bin * amdgpu/navi12_gpu_info.bin * amdgpu/navi12_me.bin * amdgpu/navi12_mec.bin * amdgpu/navi12_mec2.bin * amdgpu/navi12_pfp.bin * amdgpu/navi12_rlc.bin * amdgpu/navi12_sdma.bin * amdgpu/navi12_sdma1.bin * amdgpu/navi12_smc.bin * amdgpu/navi12_sos.bin * amdgpu/navi12_ta.bin * amdgpu/navi12_vcn.bin * amdgpu/navy_flounder_ce.bin * amdgpu/navy_flounder_dmcub.bin * amdgpu/navy_flounder_me.bin * amdgpu/navy_flounder_mec.bin * amdgpu/navy_flounder_mec2.bin * amdgpu/navy_flounder_pfp.bin * amdgpu/navy_flounder_rlc.bin * amdgpu/navy_flounder_sdma.bin * amdgpu/navy_flounder_smc.bin * amdgpu/navy_flounder_sos.bin * amdgpu/navy_flounder_ta.bin * amdgpu/navy_flounder_vcn.bin * amdgpu/oland_uvd.bin * amdgpu/pitcairn_uvd.bin * amdgpu/renoir_asd.bin * amdgpu/renoir_ce.bin * amdgpu/renoir_gpu_info.bin * amdgpu/renoir_me.bin * amdgpu/renoir_mec.bin * amdgpu/renoir_mec2.bin * amdgpu/renoir_pfp.bin * amdgpu/renoir_rlc.bin * amdgpu/renoir_sdma.bin * amdgpu/renoir_ta.bin * amdgpu/renoir_vcn.bin * amdgpu/sienna_cichlid_ce.bin * amdgpu/sienna_cichlid_dmcub.bin * amdgpu/sienna_cichlid_me.bin * amdgpu/sienna_cichlid_mec.bin * amdgpu/sienna_cichlid_mec2.bin * amdgpu/sienna_cichlid_pfp.bin * amdgpu/sienna_cichlid_rlc.bin * amdgpu/sienna_cichlid_sdma.bin * amdgpu/sienna_cichlid_smc.bin * amdgpu/sienna_cichlid_sos.bin * amdgpu/sienna_cichlid_ta.bin * amdgpu/sienna_cichlid_vcn.bin * amdgpu/tahiti_uvd.bin * amdgpu/vega20_ta.bin * amdgpu/verde_uvd.bin * atmel/wilc1000_wifi_firmware-1.bin * cmmb_vega_12mhz.inp * cmmb_venice_12mhz.inp * dvb_nova_12mhz.inp * dvb_nova_12mhz_b0.inp * i915/bxt_guc_33.0.0.bin * i915/glk_guc_33.0.0.bin * i915/icl_guc_33.0.0.bin * i915/kbl_guc_33.0.0.bin * i915/skl_guc_33.0.0.bin * i915/tgl_dmc_ver2_04.bin * i915/tgl_huc_7.5.0.bin * isdbt_nova_12mhz.inp * isdbt_nova_12mhz_b0.inp * isdbt_rio.inp * iwlwifi-Qu-b0-hr-b0-59.ucode * iwlwifi-Qu-b0-jf-b0-50.ucode * iwlwifi-Qu-b0-jf-b0-59.ucode * iwlwifi-Qu-c0-hr-b0-50.ucode * iwlwifi-Qu-c0-hr-b0-59.ucode * iwlwifi-QuZ-a0-hr-b0-50.ucode * iwlwifi-QuZ-a0-hr-b0-59.ucode * iwlwifi-QuZ-a0-jf-b0-50.ucode * iwlwifi-QuZ-a0-jf-b0-59.ucode * iwlwifi-cc-a0-50.ucode * iwlwifi-cc-a0-59.ucode * mediatek/mt7663pr2h.bin * mellanox/mlxsw_spectrum-13.2000.1886.mfa2 * mellanox/mlxsw_spectrum-13.2008.1310.mfa2 * mellanox/mlxsw_spectrum2-29.2008.1310.mfa2 * mellanox/mlxsw_spectrum3-30.2008.1310.mfa2 * mrvl/sdsd8977_combo_v2.bin * mrvl/sdsd8997_combo_v4.bin * rtl_nic/rtl8125a-3.fw * rtl_nic/rtl8168fp-3.fw * rtw88/rtw8
[Kernel-packages] [Bug 1933415] [NEW] Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
Public bug reported: [Reproduce steps] 1. disconnect/connect stress $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress ignore connect bluetooth part, and set the SSID and password to proceed. 2. suspend/resume stress $ for i in $(seq 200); do \ echo "Round $i..."; \ nmcli d; \ sleep 15; \ rtcwake -m mem -s 15; \ done kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0. [100/1757] kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6 kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 ty-a0-gf-a0-59.ucode kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0 kernel: iwlwifi :03:00.0: 0x | trm_hw_status1 kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2 kernel: iwlwifi :03:00.0: 0x922A | interruptlink1 kernel: iwlwifi :03:00.0: 0x922A | interruptlink2 kernel: iwlwifi :03:00.0: 0x000161C4 | data1 kernel: iwlwifi :03:00.0: 0x0010 | data2 kernel: iwlwifi :03:00.0: 0x | data3 kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi kernel: iwlwifi :03:00.0: 0x | time gp1 kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2 kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type kernel: iwlwifi :03:00.0: 0x003B | uCode version major kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor kernel: iwlwifi :03:00.0: 0x0420 | hw version kernel: iwlwifi :03:00.0: 0x00489002 | board version kernel: iwlwifi :03:00.0: 0x8011001C | hcmd kernel: iwlwifi :03:00.0: 0xE6863000 | isr0 kernel: iwlwifi :03:00.0: 0x0104 | isr1 kernel: iwlwifi :03:00.0: 0x68FA | isr2 kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3 kernel: iwlwifi :03:00.0: 0x0020 | isr4 kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel kernel: iwlwifi :03:00.0: 0x | timestamp kernel: iwlwifi :03:00.0: 0x9890 | flow_handler kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7 kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT kernel: iwlwifi :03:00.0: 0x | umac branchlink1 kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2 kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1 kernel: iwlwifi :03:00.0: 0x | umac interruptlink2 kernel: iwlwifi :03:00.0: 0x0007 | umac data1 [55/1757] kernel: iwlwifi :03:00.0: 0x0006 | umac data2 kernel: iwlwifi :03:00.0: 0xDEADBEEF | umac data3 kernel: iwlwifi :03:00.0: 0x003B | umac major kernel: iwlwifi :03:00.0: 0x601F3A66 | umac minor kernel: iwlwifi :03:00.0: 0x00EF1CD5 | frame pointer kernel: iwlwifi :03:00.0: 0xC0885E24 | stack pointer kernel: iwlwifi :03:00.0: 0x007C019C | last host cmd kernel: iwlwifi :03:00.0: 0x | isr status reg kernel: iwlwifi :03:00.0: IML/ROM dump: kernel: iwlwifi :03:00.0: 0x0B03 | IML/ROM error/state kernel: iwlwifi :03:00.0: 0x881A | IML/ROM data1 kernel: iwlwifi :03:00.0: 0x0080 | IML/ROM WFPM_AUTH_KEY_0 kernel: iwlwifi :03:00.0: Fseq Registers: kernel: iwlwifi :03:00.0: 0x6000 | FSEQ_ERROR_CODE kernel: iwlwifi :03:00.0: 0x0044 | FSEQ_TOP_INIT_VERSION kernel: iwlwifi :03:00.0: 0x00040090 | FSEQ_CNVIO_INIT_VERSION kernel: iwlwifi :03:00.0: 0xA652 | FSEQ_OTP_VERSION kernel: iwlwifi :03:00.0: 0x0002 | FSEQ_TOP_CONTENT_VERSION kernel: iwlwifi :03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN kernel: iwlwifi :03:00.0: 0x00400410 | FSEQ_CNVI_ID kernel: iwlwifi :03:00.0: 0x00400410 | FSEQ_CNVR_ID kernel: iwlwifi :03:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP kernel: iwlw
[Kernel-packages] [Bug 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid ** Changed in: intel-microcode (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in intel-microcode package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931684/+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 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Importance: High => Critical ** Tags added: oem-priority originate-from-1931512 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933415 Title: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Bug description: [Reproduce steps] 1. disconnect/connect stress $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress ignore connect bluetooth part, and set the SSID and password to proceed. 2. suspend/resume stress $ for i in $(seq 200); do \ echo "Round $i..."; \ nmcli d; \ sleep 15; \ rtcwake -m mem -s 15; \ done kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0. [100/1757] kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6 kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 ty-a0-gf-a0-59.ucode kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0 kernel: iwlwifi :03:00.0: 0x | trm_hw_status1 kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2 kernel: iwlwifi :03:00.0: 0x922A | interruptlink1 kernel: iwlwifi :03:00.0: 0x922A | interruptlink2 kernel: iwlwifi :03:00.0: 0x000161C4 | data1 kernel: iwlwifi :03:00.0: 0x0010 | data2 kernel: iwlwifi :03:00.0: 0x | data3 kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi kernel: iwlwifi :03:00.0: 0x | time gp1 kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2 kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type kernel: iwlwifi :03:00.0: 0x003B | uCode version major kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor kernel: iwlwifi :03:00.0: 0x0420 | hw version kernel: iwlwifi :03:00.0: 0x00489002 | board version kernel: iwlwifi :03:00.0: 0x8011001C | hcmd kernel: iwlwifi :03:00.0: 0xE6863000 | isr0 kernel: iwlwifi :03:00.0: 0x0104 | isr1 kernel: iwlwifi :03:00.0: 0x68FA | isr2 kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3 kernel: iwlwifi :03:00.0: 0x0020 | isr4 kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel kernel: iwlwifi :03:00.0: 0x | timestamp kernel: iwlwifi :03:00.0: 0x9890 | flow_handler kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7 kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT kernel: iwlwifi :03:00.0: 0x | umac branchlink1 kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2 kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1 kernel: iwlwifi :03:00.0: 0x | umac interruptlink2 kernel: iwlwifi :03:00.0: 0x0007 | umac data1 [55/1757] kernel: iwlwifi :03:00.0: 0x0006 | umac data2 kernel: iwlwifi :03:00.0: 0xDEADBEEF | umac data3 kernel: iwlwifi :03:00.0: 0x003B | umac major kernel: iw
[Kernel-packages] [Bug 1710023] Re: 4.10.0-30-generic...sdhci_pci driver does not detect microSDXC while 4.8.0-36-generic works with same hardware
OK, thanks for the info. I will just close this one, please feel free to open a new issue if you are seeing this again. ** Changed in: linux-hwe (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1710023 Title: 4.10.0-30-generic...sdhci_pci driver does not detect microSDXC while 4.8.0-36-generic works with same hardware Status in linux-hwe package in Ubuntu: Won't Fix Bug description: Lenovo Ideapad 100s 14IBR microSD works with live session boot but not installed OS boot. lspci -nnk | grep -A3 'SD Host controller' 00:12.0 SD Host controller [0805]: Intel Corporation Device [8086:2296] rev 35) Subsystem: Lenovo Device [17aa:3905] Kernel modules: sdhci_pci 00:13.0 SATA controller [0106]: Intel Corporation Device [8086:22a3] (rev 35) In a normal boot that doesn't see the microSD card dana@Astrolaptop3:~$ sudo modinfo sdhci_pci filename: /lib/modules/4.10.0-30-generic/kernel/drivers/mmc/host/sdhci-pci.ko output of sudo lspci -v on normal boot from SATA (only showing SD controller section) 00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 35) (prog-if 01) Subsystem: Lenovo Device 3905 Flags: fast devsel, IRQ 18 Memory at 91315000 (32-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Kernel modules: sdhci_pci and from a live session boot that does see the microSD card ubuntu@ubuntu:~$ sudo modinfo sdhci_pci filename: /lib/modules/4.8.0-36-generic/kernel/drivers/mmc/host/sdhci-pci.ko Output of sudo lspci -v during live session when card is detected (only showing SD controller section) 00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 35) (prog-if 01) Subsystem: Lenovo Device 3905 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at 91315000 (32-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 10 17:58:43 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-05 (4 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 17:58:55.882: The udisks-daemon is running (name-owner :1.59). UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1710023/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
@Daniel, I'm undupping, the bug is referenced in the SRUes uploaded and I don't intend to a reject/rebuild/fix the vcs etc dance only to change the reference ** This bug is no longer a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I build a kernel in https://people.canonical.com/~mschiu77/lp1927545/v6/ that won't print the raw event add add keymap for the HID usage 0x0c. Seems that there's no way to distinguish Fn+F4 and Fn+F10. I add a verbose print in lenovo_event to get the value for the difference (I expect the value to be 0xdc for Fn+F4, 0xdb for the other). Please help me test it if time permits. 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1933385] Re: selftests: bpf: test_verifier fixes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933385 Title: selftests: bpf: test_verifier fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] kselftest bpf ./test_verifier fails on bionic, preventing regression from being identified. [Test case] Run selftest bpf ./test_verifier and check that it passes. [Potential regressions] The test could still fail or crash the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933385/+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 1933078] Re: BlueZ 5.59 release
uploaded, thanks Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Here is dmesg after resume from disk hibernation. ** Attachment added: "dmesg after resume from hibernate" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506670/+files/dmesg_after_resume -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1920629] Re: My touchpad is not working at all since installation, (external mouse is working peoperly).
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1920629 Title: My touchpad is not working at all since installation,(external mouse is working peoperly). Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: My touchpad is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 20 23:17:17 2021 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920629/+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 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
SRU: https://lists.ubuntu.com/archives/kernel-team/2021-June/121676.html (linux-firmware: focal) PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1933415 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933415 Title: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0. Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Bug description: [Reproduce steps] 1. disconnect/connect stress $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress ignore connect bluetooth part, and set the SSID and password to proceed. 2. suspend/resume stress $ for i in $(seq 200); do \ echo "Round $i..."; \ nmcli d; \ sleep 15; \ rtcwake -m mem -s 15; \ done kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0. [100/1757] kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6 kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 ty-a0-gf-a0-59.ucode kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0 kernel: iwlwifi :03:00.0: 0x | trm_hw_status1 kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2 kernel: iwlwifi :03:00.0: 0x922A | interruptlink1 kernel: iwlwifi :03:00.0: 0x922A | interruptlink2 kernel: iwlwifi :03:00.0: 0x000161C4 | data1 kernel: iwlwifi :03:00.0: 0x0010 | data2 kernel: iwlwifi :03:00.0: 0x | data3 kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi kernel: iwlwifi :03:00.0: 0x | time gp1 kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2 kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type kernel: iwlwifi :03:00.0: 0x003B | uCode version major kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor kernel: iwlwifi :03:00.0: 0x0420 | hw version kernel: iwlwifi :03:00.0: 0x00489002 | board version kernel: iwlwifi :03:00.0: 0x8011001C | hcmd kernel: iwlwifi :03:00.0: 0xE6863000 | isr0 kernel: iwlwifi :03:00.0: 0x0104 | isr1 kernel: iwlwifi :03:00.0: 0x68FA | isr2 kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3 kernel: iwlwifi :03:00.0: 0x0020 | isr4 kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel kernel: iwlwifi :03:00.0: 0x | timestamp kernel: iwlwifi :03:00.0: 0x9890 | flow_handler kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7 kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT kernel: iwlwifi :03:00.0: 0x | umac branchlink1 kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2 kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1 kernel: iwlwifi :03:00.0: 0x | umac interruptlink2 kernel: iwlwifi :03:00.0: 0x0007 | umac data1 [55/1757] kernel: iwlwifi :03:00.0: 0x0006 | umac data2 kernel: iwlwifi :03:00.0: 0xDEADBEEF | umac data3 kernel: iwlwifi :03:00.0: 0x003B | umac major kernel: iwlwifi :03:00.0: 0x601F3A66 | umac minor kernel: iwlwifi :03:00.0: 0x00EF1CD5 | frame pointer kernel: iwlwifi :03:00.0: 0xC0885E24 | stack pointer kernel: iwlwifi :03:00.0: 0x007C019C | last host cmd kernel: iwlwifi :03:00.0: 0x | isr status reg kernel: iwlwifi :03:00.0: IML/ROM dump: kernel: iwlwifi :03:00.0: 0x0B03 | IML/ROM error/state kernel:
[Kernel-packages] [Bug 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Please test this kernel: https://people.canonical.com/~khfeng/lp1931442/ -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Hello Kai-Heng, i have tested provided kernel and it still suffers from slow speed. Also noticed, that if i run iperf3 multiple times, it works in one-two passes and then it slows down to crawl. Then again on the next pass it works as expected. Please see attached outputs. ** Attachment added: "iperf3 output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506721/+files/iperf3_output -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
See bug 1926062 for previous SRU review. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
After doing hibernation "trick" iperf3 is working fine every time. ** Attachment added: "iperf3 after hibernation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506722/+files/iperf_after_hibernation -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1932329] Re: Benchmark if we can compress kernel modules
Whilst download size is larger, it is at no additional cost to our end users, especially in the cloud. Majority of our clouds offer free transfers inside the availability zone for which mirrors are provided. Obviously it will increase the disk/cache storage size requirements of our mirrors. Our end users have about 3 sets of kernels installed on disk, for which they do pay more per GB between 2 to 12 cents (depending on technology IOPS / hdd / sda / nvme). All things being equal our users would choose larger download sizes to gain smaller install size. I assume that we have vastly larger install base, compared to number of our mirrors. I also hope that our install base is not larger than the total bandwidth available of our mirrors, such that this switch would cause collapse of our mirror network. I also notice that kernel uses default options for zstd module compression, instead of using -19 like it recommends for the initrds. I also notice that kmod in focal doesn't support zstd. Imho we should fix above before turning this on. -- 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/1932329 Title: Benchmark if we can compress kernel modules Status in linux package in Ubuntu: In Progress Bug description: Symbol: MODULE_COMPRESS_ZSTD [=n] Type : bool = Impacts to measure and observe = == Disk space == * Inspect linux-modules-* and linux-modules-extra* deb package Installed-Size and Download-Size changes, i.e. $ apt show linux-modules-5.8.0-53-generic linux-modules- extra-5.8.0-53-generic | grep -e Package: -e Size: Package: linux-modules-5.8.0-53-generic Installed-Size: 81.5 MB Download-Size: 15.5 MB Package: linux-modules-extra-5.8.0-53-generic Installed-Size: 215 MB Download-Size: 41.5 MB In theory, there should not be a significant change in the Download- size. It is desired that there is a significant reduction in Installed-Size. Modules take up about 300MB and normally one has upto three kernel version installed, resulting in about of 1GB of disk space that one constantly pays for. == Boot Speed == In theory, boot speed may either improve or regress. It depends if disk IO is slower than decompression speed, meaning loading compressed modules is faster. Also one has to observe the changes in the initrd size. zstd(zstd) compression may result in slight growth, which shouldn't impact boot speed too much. = Outcomes = If installed size savings can be achieved without regressing bootspeed we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932329/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Here is dmesg after hibernation with 5.13.0 kernel you have provided. ** Attachment added: "dmesg 5.13.0 after hibernation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506723/+files/dmesg_5.13.0_after_hibernation -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
> Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team. I'm not sure what you mean by "upstream tributary", but if the fix exists in the main Ubuntu packaging branch used by the desktop team (ie. Vcs-Git in debian/control points to it) then that makes sense, as it was in this case. If you mean it's just fixed upstream somewhere, then that doesn't make sense - Launchpad's bug tracker expects to have a separate task to track upstream status if you want that. However, from an SRU perspective, I would expect an upload to the development release *before* an SRU is uploaded. Sometimes we make concessions (eg. during a development release freeze), but I don't think a sponsorship delay qualifies. The sponsor should be able to sponsor to the development release first, so there's no reason not to do it. I see it's there now, but please could you adjust your processes to make sure that in the normal case, this happens? This would save me reviewing the SRU twice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Unknown Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-
[Kernel-packages] [Bug 1933221] Please test proposed package
Hello Andy, or anyone else affected, Accepted bluez into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
Hello Andy, or anyone else affected, Accepted bluez into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bluez (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: bluez (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
> Gave some time between netplan apply and check without success, I can leave > it for > hours and the IP never gets assigned Indeed, I cannot see it being assigned an IPv4 address in your latest "_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171 at 15:05:29 in the journal logs, but that was before you started the experiment). > maybe what you are seeing is the manual assignment that I did with > ip addr add 192.168.171.53/24 dev enP53p0s0.171 No I don't think so, as the timestamp of your manual "ip addr add" command (08:13:02++) is after the systemd-networkd assignment in the logs (08:12:38). Also, your output clearly shows that the IP was already assigned when you tried to (re-)assign it manually (it shows the "RTNETLINK answers: File exists" error): > root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171 > RTNETLINK answers: File exists I'm a bit worried about the /etc/systemd/network/10-enP53p0s0.link file (now there seems to be another one "10-enP53p0s0.link" as well...) – Is this file needed? Why was it created? It matches on "MACAddress=82:0c:9b:c9:78:f8", which would match enP53p0s0 AND enP53p0s0.171 at the same time (they use the same inherited MAC address), leading to unspecified behavior, as we cannot rename two interfaces to the same "Name=enP53p0s0". Could you try deleting this file in /etc/systemd/network/10-enP53p0s0.link (potentially adopting your netplan YAML config to the name assigned to this interface by the kernel/systemd) and check if this makes any difference? # rm /etc/systemd/network/10-enP53p0s0.link If for some reason you cannot delete this file, try adding a "Type=!vlan" line instead: # cat /etc/systemd/network/10-enP53p0s0.link [Match] MACAddress=82:0c:9b:c9:78:f8 Type=!vlan [Link] Name=enP53p0s0 Does this make any difference when running "netplan apply && sleep 30 && networkctl status -a --no-pager"? -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (genera
[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Test package at https://launchpad.net/~timg-tpi/+archive/ubuntu/bcmwl- lp1932159 ** Changed in: bcmwl (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: bcmwl (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in bcmwl source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in bcmwl source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932993] Re: AMDGPU: Support to load new MC firmware for Polaris12 32bit ASIC
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1034.35 --- linux-oem-5.10 (5.10.0-1034.35) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1034.35 -proposed tracker (LP: #1933308) * AMDGPU: Support to load new MC firmware for Polaris12 32bit ASIC (LP: #1932993) - drm/amd/pm: correct the checks for polaris kickers - drm/amdgpu: add new MC firmware for Polaris12 32bit ASIC -- Timo Aaltonen Wed, 23 Jun 2021 12:24:04 +0300 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932993 Title: AMDGPU: Support to load new MC firmware for Polaris12 32bit ASIC Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] AMD introduce a new firmware and has been SRUed in this public bug. https://bugs.launchpad.net/ubuntu/focal/+source/linux-firmware/+bug/1929147 For the kernel(oem-5.10/groovy), also need other patches to load this firmware. [Fix] Support to load polaris12_32_mc.bin [Test] 1. Check by modinfo and cnofirm polaris12_32_mc.bin is loaded by amdgpu.ko #modinfo amdgpu | grep polaris12_32_mc.bin firmware: amdgpu/polaris12_32_mc.bin 2. Equipped the rx540(PD5001) that would trigger issue and system would bootup successfully into desktop. *some rx540(PD5000) can't trigger the issue. [Regression Potential] Medium, introduce a brand new firmware may cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932993/+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 1933388] Re: SR-IOV broken in Ubuntu 20.04.2 LTS
Hi, Gijs. Thank you for your report. Can you provide the full output of dmesg from the Ubuntu VM? Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1933388 Title: SR-IOV broken in Ubuntu 20.04.2 LTS Status in linux-azure package in Ubuntu: New Bug description: SR-IOV does not work since Ubuntu Server 18.04.2 LTS, once the HWE kernel (4.18.0-15 generic x86_64)) has been installed on that version. Please also see ticket: https://bugs.launchpad.net/ubuntu/+source /linux-hwe/+bug/1818400 This bug report was created for Ubuntu 20.04.02 LTS, since the kernel for the previous bug report is no longer being supported and a developer requested us to make a new bug report for the new Ubuntu version... Environment: Windows Server 2019 Fresh Hyper-V generation 2 VM (configuration version 9.0) SR-IOV enabled on the virtual switch (Intel I350-T2 physical network adapter) SR-IOV enabled on the virtual network card of the VM Steps to reproduce: Install Ubuntu Server 20.04.2 LTS Verify SR-IOV is enabled in the Networking tab of the Hyper-V manager Check SR-IOV status in the Networking tab of the Hyper-V manager. It will show status degraded (SR-IOV not operational) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-1033-azure 5.8.0-1033.35~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-1033.35~20.04.1-azure 5.8.18 Uname: Linux 5.8.0-1033-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 23 23:00:26 2021 InstallationDate: Installed on 2020-09-15 (281 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-azure-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1933388/+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 1930707] Re: Mic-mute/mute LEDs not work on some HP platforms
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930707 Title: Mic-mute/mute LEDs not work on some HP platforms Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC The right channel of internal speaker doesn't work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/function are work good on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/function will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930707/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay
--- Comment From stefan.ra...@de.ibm.com 2021-06-24 09:44 EDT--- Verified on hirsute-proposed. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1921870 Title: [UBUNTU 21.04] tools/kvm_stat: Add restart delay Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: [Impact] * Nice to have feature requested by IBM - a systemd service monitoring KVM guests. * Adds a new systemd service, not enabled by default. [Fix] * Install the systemd .service file when installing linux-tools-host [Test Plan] * dpkg -c linux-tools-host_5.11.0-18.19_all.deb ./lib/systemd/system/kvm_stat.service * Install the package and reboot * Check if kvm_stat is present and not active after reboot: ls -l /lib/systemd/system/kvm_stat.service systemctl -a | grep kvm_stat [Where problems could occur] * Service can be enabled and started by mistake or by any further future Makefile change (enabling all services installed by linux-tools-host). * The service logs into /var/log/kvm_stat.csv (not journal!) and package does not provide logrotate by default, thus the logging could eat entire disk space. -- Original Description -- Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, Systemd's initial attempt to start the kvm unit file may fail in case the kvm module is not loaded. However, once the kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, Systemd restarts with a minimum delay a number of times before giving up and disabling the service. Which means a subsequent kvm module load will have kvm running without monitoring. Solution: Add an appropriate delay in the unit file. Reproduction: (1) Enable the kvm service via systemctl (2) Reboot (3) Verify that the kvm module is not loaded & kvm service not running (4) Load the kvm module via 'modprobe kvm' (5) Verify that the kvm service came up within the next minute. Preventive:yes Just use the attached patch and you're good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933508] [NEW] mute/micmute LEDs no function on HP EliteBook x360 830 G8
Public bug reported: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1930708 stella ** Tags added: oem-priority originate-from-1930708 stella ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929844] Re: Memleak on restore flow when offloading conntrack.
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1929460] Re: CT: Fix CT template allocation for zone 0
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1929459] Re: CT: Offload connections with commit action
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1929736] Re: Automate soft reset of BlueField ARM via GPIO7
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1927246] Re: Remove dependency between module and driver
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1927251] Re: Increase flow insertion rate by using rw lock instead of mutex on the flow block.
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1929458] Re: CT: check offload bit on table dump
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1928852] Re: oob_net0 file transfers can crash kernel
This bug was fixed in the package linux-bluefield - 5.4.0-1013.16 --- linux-bluefield (5.4.0-1013.16) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1013.16 -proposed tracker (LP: #1930009) * Automate soft reset of BlueField ARM via GPIO7 (LP: #1929736) - SAUCE: Automate soft reset of BlueField ARM via GPIO7 * Remove dependency between module and driver (LP: #1927246) - net/sched: act_ct: Make tcf_ct_flow_table_restore_skb inline - netfilter: flowtable: Make nf_flow_table_offload_add/del_cb inline * Increase flow insertion rate by using rw lock instead of mutex on the flow block. (LP: #1927251) - netfilter: flowtable: Use rw sem as flow block lock - netfilter: flowtable: Free block_cb when being deleted * oob_net0 file transfers can crash kernel (LP: #1928852) - SAUCE: mlxbf_gige: syncup with v1.23 content * CT: Fix CT template allocation for zone 0 (LP: #1929460) - SAUCE: net/sched: act_ct: Fix ct template allocation for zone 0 * CT: Offload connections with commit action (LP: #1929459) - SAUCE: net/sched: act_ct: Offload connections with commit action * CT: check offload bit on table dump (LP: #1929458) - SAUCE: netfilter: conntrack: Check offload bit on table dump * Memleak on restore flow when offloading conntrack. (LP: #1929844) - SAUCE: skbuff: Release nfct refcount on napi stolen or re-used skbs [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tc
[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay
Thx Stefan for the verification. (I don't know why there is a verification-needed-focal tag on top, since this bug is not marked as affecting focal at all ?! To avoid any blockers, I'm changing it to done, too.) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921870 Title: [UBUNTU 21.04] tools/kvm_stat: Add restart delay Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: [Impact] * Nice to have feature requested by IBM - a systemd service monitoring KVM guests. * Adds a new systemd service, not enabled by default. [Fix] * Install the systemd .service file when installing linux-tools-host [Test Plan] * dpkg -c linux-tools-host_5.11.0-18.19_all.deb ./lib/systemd/system/kvm_stat.service * Install the package and reboot * Check if kvm_stat is present and not active after reboot: ls -l /lib/systemd/system/kvm_stat.service systemctl -a | grep kvm_stat [Where problems could occur] * Service can be enabled and started by mistake or by any further future Makefile change (enabling all services installed by linux-tools-host). * The service logs into /var/log/kvm_stat.csv (not journal!) and package does not provide logrotate by default, thus the logging could eat entire disk space. -- Original Description -- Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, Systemd's initial attempt to start the kvm unit file may fail in case the kvm module is not loaded. However, once the kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, Systemd restarts with a minimum delay a number of times before giving up and disabling the service. Which means a subsequent kvm module load will have kvm running without monitoring. Solution: Add an appropriate delay in the unit file. Reproduction: (1) Enable the kvm service via systemctl (2) Reboot (3) Verify that the kvm module is not loaded & kvm service not running (4) Load the kvm module via 'modprobe kvm' (5) Verify that the kvm service came up within the next minute. Preventive:yes Just use the attached patch and you're good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921870/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
[OS version] Focal [kernel version] 5.13-oem [Step] 1. open gnome-settings 2. turn off Bluetooth by toggle 3. turn on Bluetooth by toggle It works fine. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
[OS version] Hirsute [kernel version] 5.11.0-16-generic [Step] 1. open gnome-settings 2. turn off Bluetooth by toggle 3. turn on Bluetooth by toggle It works fine. ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933337] [NEW] bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS
You have been subscribed to a public bug: When trying to build bcmwl using the latest 5.11 HWE-edge kernel on Ubuntu 20.04 LTS, the kernel module will refuse to build: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ I understand that a fix for this has been rolled out to Hirsuite (0029 -Update-for-set_fs-removal-in-Linux-5.10.patch). Can this fix please be backported to Focal? Since it fixes the problem for people needing to run LTS and use the HWE-Edge kernel for any given reason. ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS https://bugs.launchpad.net/bugs/197 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. -- 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 1933388] Re: SR-IOV broken in Ubuntu 20.04.2 LTS
Certainly, see the attached file. ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1933388/+attachment/5506746/+files/output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1933388 Title: SR-IOV broken in Ubuntu 20.04.2 LTS Status in linux-azure package in Ubuntu: New Bug description: SR-IOV does not work since Ubuntu Server 18.04.2 LTS, once the HWE kernel (4.18.0-15 generic x86_64)) has been installed on that version. Please also see ticket: https://bugs.launchpad.net/ubuntu/+source /linux-hwe/+bug/1818400 This bug report was created for Ubuntu 20.04.02 LTS, since the kernel for the previous bug report is no longer being supported and a developer requested us to make a new bug report for the new Ubuntu version... Environment: Windows Server 2019 Fresh Hyper-V generation 2 VM (configuration version 9.0) SR-IOV enabled on the virtual switch (Intel I350-T2 physical network adapter) SR-IOV enabled on the virtual network card of the VM Steps to reproduce: Install Ubuntu Server 20.04.2 LTS Verify SR-IOV is enabled in the Networking tab of the Hyper-V manager Check SR-IOV status in the Networking tab of the Hyper-V manager. It will show status degraded (SR-IOV not operational) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-1033-azure 5.8.0-1033.35~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-1033.35~20.04.1-azure 5.8.18 Uname: Linux 5.8.0-1033-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 23 23:00:26 2021 InstallationDate: Installed on 2020-09-15 (281 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-azure-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1933388/+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 1933337] Re: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS
Wrong package ** Package changed: broadcom-sta (Ubuntu) => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/197 Title: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS Status in bcmwl package in Ubuntu: New Bug description: When trying to build bcmwl using the latest 5.11 HWE-edge kernel on Ubuntu 20.04 LTS, the kernel module will refuse to build: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ I understand that a fix for this has been rolled out to Hirsuite (0029 -Update-for-set_fs-removal-in-Linux-5.10.patch). Can this fix please be backported to Focal? Since it fixes the problem for people needing to run LTS and use the HWE-Edge kernel for any given reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/197/+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 1932171] Re: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Can't mark as duplicate of 1926937 ** No longer affects: linux-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932171 Title: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in virtualbox-hwe package in Ubuntu: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in virtualbox-hwe source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running virtualbox-hwe tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/v/virtualbox-hwe/20210611_210612_79a80@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-hwe/+bug/1932171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Test package at https://launchpad.net/~timg-tpi/+archive/ubuntu /broadcom-sta-lp1932160 ** Changed in: broadcom-sta (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: broadcom-sta (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: broadcom-sta (Ubuntu) Status: New => Fix Released ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932160 Title: broadcom-sta/6.30.223.271-12 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in broadcom-sta package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in broadcom-sta source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
decompression speed only needs to be faster than i/o speed, once that is reached the best compression ratio results in the fastest bootspped. for kernel image zstd is used with -22 --ultra, thus I can compare it with zlib -9. -- 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: New Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3 /kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
** Changed in: linux (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Fix Committed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] [NEW] Update SmartPQI driver
Public bug reported: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] TBD [Regression Risk] Low. Patch set only adds tested bug fixes and support for additional controllers that are shipping with current refreshes for various OEMs ** Affects: linux (Ubuntu) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-24 11:53 EDT--- Giving it a try without the /etc/systemd/network/ files - Checking that it is empty root@ilabg13:~# ll /etc/systemd/network/ total 8 drwxr-xr-x 2 root root 4096 Jun 24 08:41 ./ drwxr-xr-x 5 root root 4096 Jun 17 06:18 ../ - Try to assign ip via netplan root@ilabg13:~# date Thu Jun 24 08:47:45 MST 2021 root@ilabg13:~# netplan apply - Checking networkctl root@ilabg13:~# date Thu Jun 24 08:49:10 MST 2021 root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager ? 9: enP53p0s0.171 Link File: n/a Network File: n/a Type: vlan State: degraded (pending) HW Address: 82:0c:9b:c9:78:f8 MTU: 9000 (max: 65535) Queue Length (Tx/Rx): 1/1 Auto negotiation: yes Speed: 25Gbps Duplex: full Address: fe80::800c:9bff:fec9:78f8 Activation Policy: up Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Link 9 added Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: link pending udev initialization... Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: netdev has index 9 Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Saved original MTU: 9000 Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Remembering foreign address: fe80::800c:9bff:fec9:78f8/64 (valid forever) Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Gained IPv6LL Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a, scope: global, table: local, ?e: multicast Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Remembering route: dst: fe80::800c:9bff:fec9:78f8/128, src: n/a, gw: n/a, prefsrc: n/a, scope: g? type: local Jun 24 08:48:01 ilabg13.tuc.stglabs.ibm.com systemd-networkd[293700]: enP53p0s0.171: Remembering route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a, scope: global, table: main, ?ype: unicast - IP still not being assigned root@ilabg13:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: encdb0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 11.111.114.213/22 brd 11.111.115.255 scope global encdb0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever 3: ence0f: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 9.11.116.213/24 brd 9.11.116.255 scope global ence0f valid_lft forever preferred_lft forever inet6 2002:90b:e006:116:76:54ff:fe00:4/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591841sec preferred_lft 604641sec inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 4: encdc0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 11.111.112.213/22 brd 11.111.115.255 scope global encdc0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 5: encdc0.150@encdc0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 192.168.150.53/24 brd 192.168.150.255 scope global encdc0.150 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 6: encdb0.160@encdb0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 192.168.160.53/24 brd 192.168.160.255 scope global encdb0.160 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever 7: enP50s3832: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fea8:a1b2/64 scope link valid_lft forever preferred_lft forever 8: enP53p0s0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 9: enP53p0s0.171@enP53p0s0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 10: enP50s3832.170@enP50s3832: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:
[Kernel-packages] [Bug 1929657] udevadm monitor nofiles
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-24 11:57 EDT--- ** Attachment added: "udevadm monitor nofiles" https://bugs.launchpad.net/bugs/1929657/+attachment/5506750/+files/udevadm_monitor_nofiles.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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (gener
[Kernel-packages] [Bug 1929657] journalctl no files
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-24 11:57 EDT--- ** Attachment added: "journalctl no files" https://bugs.launchpad.net/bugs/1929657/+attachment/5506751/+files/journalctl_udev_nofiles.txt.zip -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (gener
[Kernel-packages] [Bug 1931959] Re: iscsi-related backports requested for Oracle-cloud
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1931959 Title: iscsi-related backports requested for Oracle-cloud Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Focal: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Bug description: As part of some work to enable high performance iscsi storage leveraging multipath, Oracle submitted and landed patches upstream, which were released as part of 5.10. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a242d59d6b908341c0d426bc6e7f8e28871cbd0 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0610959fbbca62b534f1f276873fd297f76b164b commit 2a242d59d6b908341c0d426bc6e7f8e28871cbd0 Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:53 2020 -0500 scsi: core: Add limitless cmd retry support commit 0610959fbbca62b534f1f276873fd297f76b164b Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:54 2020 -0500 scsi: sd: Allow user to configure command retries See https://canonical.lightning.force.com/lightning/r/Case/5004K05pykQQAQ/view for more info. [Impact] Optimizations/improvements in iscsi-code [Fix] 2 patches - see above [Test] Build, boot, initiate an iscsi connection to a target. [Regression Potential] Possible impact on iscsi functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1931959/+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 1928686] Re: Oracle kernel has Android related config options disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Bionic: New Status in linux-oracle source package in Focal: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Committed Bug description: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+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 1931744] Re: Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem
5.10.0-1034-oem and the issue is still there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931744 Title: Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem Status in linux-oem-5.10 package in Ubuntu: New Bug description: On all kernel versions that I used before the 5.10.0-1029-oem the internal microphone of my Dell Precision 5750 worked perfectly. After the upgrade to 5.10.0-1029-oem the internal mic stopped working but I can still use an external mic. I couldn't enable the internal mic using pavucontrol and alsamixer. P.S. Looks like there is the same issue with Dell XPS 9700 (which is no wonder): https://askubuntu.com/questions/1343942/dell-xps-17-9700 -internal-microphone-not-working lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931744/+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 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Invalid Bug description: This is something to do with the configuration or software versions running here, since we have identical hardware running in an adjacent cloud region but with different versions of the cloud/virt stack. When we boot bionic arm64 Ubuntu cloud images in "bos01" and they land on the eMAG systems, they always fail like this: ... [1.585611] Key type dns_resolver registered [1.587408] registered taskstats version 1 [1.588913] Loading compiled-in X.509 certificates [1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4' [1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [1.610861] Couldn't get size: 0x800e [1.613413] MODSIGN: Couldn't get UEFI db list [1.615920] Couldn't get size: 0x800e [1.618256] MODSIGN: Couldn't get UEFI MokListRT [1.620315] Couldn't get size: 0x800e [1.622317] MODSIGN: Couldn't get UEFI dbx list [1.624446] zswap: loaded using pool lzo/zbud [1.628185] Key type big_key registered [1.629937] Key type trusted registered [1.632012] Key type encrypted registered [1.633668] AppArmor: AppArmor sha1 policy hashing enabled [1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [1.638009] ima: Allocated hash algorithm: sha1 [1.639272] evm: HMAC attrs: 0x1 [1.640875] rtc-efi rtc-efi: setting system clock to 2021-05-11 09:28:43 UTC (1620725323) [1.646247] Freeing unused kernel memory: 5824K [1.657870] Checked W+X mappings: passed, no W+X pages found [1.660250] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.660250] [1.663294] CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-142-generic #146-Ubuntu [1.665939] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [1.668204] Call trace: [1.668981] dump_backtrace+0x0/0x198 [1.670212] show_stack+0x24/0x30 [1.671282] dump_stack+0x98/0xc8 [1.672433] panic+0x128/0x2b0 [1.673502] do_exit+0x75c/0xa80 [1.674749] do_group_exit+0x40/0xb0 [1.676191] get_signal+0x114/0x6e8 [1.677867] do_signal+0x18c/0x240 [1.679498] do_notify_resume+0xd0/0x328 [1.681302] work_pending+0x8/0x10 [1.682771] SMP: stopping secondary CPUs [1.684624] Kernel Offset: disabled [1.686119] CPU features: 0x04802008 [1.687353] Memory Limit: none [1.688453] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.688453] Full example log: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/arm64/c/chromium-browser/20210511_093739_ea3f2@/log.gz We tried to get IS to roll things back to match the working bos02, but they said it's too different and not possible. The working cloud is running Mitaka from the cloud archive on Xenial (qemu 2.5) The broken cloud is running Queens from the cloud archive on Xenial (qemu 2.11) The other thing someone suggested we try is that MDS mitigation is enabled in the broken cloud, so we could disable it. No idea if that makes sense tbh. That's about all we have right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
tarball of patches that cover these commits provided by microchip ** Attachment added: "ubuntu_21.04.tar" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+attachment/5506766/+files/ubuntu_21.04.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] TBD [Regression Risk] Low. Patch set only adds tested bug fixes and support for additional controllers that are shipping with current refreshes for various OEMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Test package at https://launchpad.net/~timg-tpi/+archive/ubuntu/lime- forensics-lp1932164 ** Changed in: lime-forensics (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: lime-forensics (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: lime-forensics (Ubuntu) Status: New => Fix Released ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid ** Patch added: "lime-forensics_1.9-1ubuntu0.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+attachment/5506767/+files/lime-forensics_1.9-1ubuntu0.3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+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 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Doing a full backport, as this was done before, and DRM changes are not trivial to backport. ** Changed in: evdi (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: evdi (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: evdi (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+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 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
I believe you are talking about v7 kernel. I've tried it and for this version dmesg was sielent on Fn+F4 and Fn+F10 pressing. -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1932169] Re: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Test package at https://launchpad.net/~timg-tpi/+archive/ubuntu /rtl8812au-lp1932169 ** Patch added: "rtl8812au_4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1932169/+attachment/5506769/+files/rtl8812au_4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3.debdiff ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid ** Changed in: rtl8812au (Ubuntu) Status: New => Fix Released ** Changed in: rtl8812au (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: rtl8812au (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932169 Title: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in rtl8812au package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Status in rtl8812au source package in Focal: In Progress Bug description: This is a scripted bug report about ADT failures while running rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932169/+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 1933532] [NEW] Large Page support disabled on Raspberry Pi kernels
Public bug reported: It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set ** Affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1933532 Title: Large Page support disabled on Raspberry Pi kernels Status in linux-raspi-5.4 package in Ubuntu: New Bug description: It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi-5.4/+bug/1933532/+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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Kai-chuan: 1. On UFW, I disabled it, but it did not work. 2. For iperf, I did not know this tool existed, and I am not sure how to generate the right data. Please advise here. 3. I also tried the new ucode file. This is what I did: I cloned the git repo and copied the file into /usr/lib/firmware. Good news is that after reboot the Internet connection worked. But I did not have the opportunity to test this during a meeting yet though. 4. Stéphane Verdy, who you probably know, gave me the "decoding ring". When Daniel van Vugt said "the kernel is about two weeks old", this newbie had no idea if this was a good thing. I thought the kernel got updated automatically - I was probably mistaken. So I updated it manually. So, interestingly, it solved PART of the problem. When I am in a 1:1 discussion, it works flawlessly on wireless. But if there are multiple people in the call, then it started having issues again. Give me a few days here. I have a few calls upcoming, I will give the wifi a try in different settings (1:1 and multiple folks) and let you know if (3) + (4) actually did the trick (because on the 1:1, I could only test (4) in isolation so far). Best Regards, Steve On Thu, Jun 24, 2021 at 12:05 AM Kai-Chuan Hsieh <1932...@bugs.launchpad.net> wrote: > ** Changed in: oem-priority >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-focal-amd64-20200502-85 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > vers
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux-aws - 5.11.0-1009.9+21.10.1 --- linux-aws (5.11.0-1009.9+21.10.1) impish; urgency=medium * impish/linux-aws: 5.11.0-1009.9+21.10.1 -proposed tracker (LP: #1930057) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-1009.9 ] * hirsute/linux-aws: 5.11.0-1009.9 -proposed tracker (LP: #1930058) * Hirsute update: v5.11.21 upstream stable release (LP: #1929455) - [Config] aws: updateconfigs for AD9467 * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] enable soundwire audio mach driver * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * Fix screen flickering w
[Kernel-packages] [Bug 1912511] Re: [SRU] Add support for E810 NIC to Ice Driver in Focal
I installed the proposed kernel and the E810 is working as expected. The interfaces came up and I was able to ping and ssh into the system using the E810 interfaces. $ uname -a Linux C6520-E810-30 5.4.0-78-generic #87-Ubuntu SMP Fri Jun 18 16:29:09 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ubuntu@C6520-E810-30:~$ sudo apt-cache policy linux-generic linux-generic: Installed: 5.4.0.78.81 Candidate: 5.4.0.78.81 Version table: *** 5.4.0.78.81 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.77.80 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912511 Title: [SRU] Add support for E810 NIC to Ice Driver in Focal Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The Intel Ice driver in 5.4 does not contain the PCIIDs necessary to allow the driver to see the E810 network cards. Without this, users running Focal GA will be unable to deploy Ubuntu via MAAS, or use these cards at all post-install when installing from an ISO. The patch to resolve this landed in Groovy, so this should be a pretty straightforward pick to 5.4. The patch set is small. [Test Case] This is easily reproducible by simply trying to install Focal onto a system with an E810 NIC. The NIC is not recognized and thus is not configurable or usable. [Where problems could occur] All this patch does is add PCI ID information for E810 to the driver to enable a wider set of cards to be used. Problems should not involve regressions to existing supported hardware, if anything the biggest issue could be discovering that after adding the PCI IDs, further patches are necessary to fully enable support in the Ice driver. [Other Info] This was reported by a hardware partner and blocks certification for systems that use E810 based NICs as their primary network devices. Git repository: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp_1912511_e810_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912511/+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 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Description changed: + [Impact] + focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. + + [Test case] + Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. + + [Potential regression] + DisplayLink devices will stop working. + + + -- + This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+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 1933541] [NEW] Groovy update: upstream stable patchset 2021-06-24
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-24 Ported from the following upstream stable releases: v5.4.125, v5.10.43 from git://git.kernel.org/ btrfs: tree-checker: do not error out if extent ref hash doesn't match net: usb: cdc_ncm: don't spew notifications hwmon: (dell-smm-hwmon) Fix index values netfilter: conntrack: unregister ipv4 sockopts on error unwind efi: Allow EFI_MEMORY_XP and EFI_MEMORY_RO both to be cleared efi: cper: fix snprintf() use in cper_dimm_err_location() vfio/pci: Fix error return code in vfio_ecap_init() vfio/pci: zap_vma_ptes() needs MMU samples: vfio-mdev: fix error handing in mdpy_fb_probe() vfio/platform: fix module_put call in error flow ipvs: ignore IP_VS_SVC_F_HASHED flag when adding service HID: pidff: fix error return code in hid_pidff_init() HID: i2c-hid: fix format string mismatch net/sched: act_ct: Fix ct template allocation for zone 0 ACPICA: Clean up context mutex during object deletion netfilter: nft_ct: skip expectations for confirmed conntrack netfilter: nfnetlink_cthelper: hit EBUSY on updates if size mismatches ieee802154: fix error return code in ieee802154_add_iface() ieee802154: fix error return code in ieee802154_llsec_getparams() ixgbevf: add correct exception tracing for XDP ipv6: Fix KASAN: slab-out-of-bounds Read in fib6_nh_flush_exceptions ice: Fix VFR issues for AVF drivers that expect ATQLEN cleared ice: Allow all LLDP packets from PF to Tx i2c: qcom-geni: Add shutdown callback for i2c i40e: optimize for XDP_REDIRECT in xsk path i40e: add correct exception tracing for XDP arm64: dts: ls1028a: fix memory node arm64: dts: zii-ultra: fix 12V_MAIN voltage ARM: dts: imx7d-meerkat96: Fix the 'tuning-step' property ARM: dts: imx7d-pico: Fix the 'tuning-step' property ARM: dts: imx: emcon-avari: Fix nxp,pca8574 #gpio-cells bus: ti-sysc: Fix flakey idling of uarts and stop using swsup_sidle_act tipc: add extack messages for bearer/media failure tipc: fix unique bearer names sanity check Bluetooth: fix the erroneous flush_work() order Bluetooth: use correct lock to prevent UAF of hdev object net: caif: added cfserl_release function net: caif: add proper error handling net: caif: fix memory leak in caif_device_notify net: caif: fix memory leak in cfusbl_device_notify HID: i2c-hid: Skip ELAN power-on command after reset HID: magicmouse: fix NULL-deref on disconnect HID: multitouch: require Finger field to mark Win8 reports as MT ALSA: timer: Fix master timer notification ALSA: hda: Fix for mute key LED for HP Pavilion 15-CK0xx ARM: dts: imx6dl-yapp4: Fix RGMII connection to QCA8334 switch ARM: dts: imx6q-dhcom: Add PU,VDD1P1,VDD2P5 regulators ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed usb: dwc2: Fix build in periphal-only mode pid: take a reference when initializing `cad_pid` ocfs2: fix data corruption by fallocate nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect drm/amdgpu: Don't query CE and UE errors drm/amdgpu: make sure we unpin the UVD BO x86/apic: Mark _all_ legacy interrupts when IO/APIC is missing btrfs: mark ordered extent and inode with error if we fail to finish btrfs: fix error handling in btrfs_del_csums btrfs: return errors from btrfs_del_csums in cleanup_ref_head btrfs: fixup error handling in fixup_inode_link_counts mm, hugetlb: fix simple resv_huge_pages underflow on UFFDIO_COPY XArray: add xa_get_order XArray: add xas_split mm/filemap: fix storing to a THP shadow entry btrfs: fix unmountable seed device after fstrim KVM: SVM: Truncate GPR value for DR and CR accesses in !64-bit mode KVM: arm64: Fix debug register indexing lib/lz4: explicitly support in-place decompression i2c: qcom-geni: Suspend and resume the bus during SYSTEM_SLEEP_PM ops neighbour: allow NUD_NOARP entries to be forced GCed hwmon: (pmbus/isl68137) remove READ_TEMPERATURE_3 for RAA228228 efi/libstub: prevent read overflow in find_file_option() HID: logitech-hidpp: initialize level variable devlink: Correct VIRTUAL port to not have phys_port attributes net/sched: act_ct: Offload connections with commit action mptcp: always parse mptcp options for MPC reqsk nvme-rdma: fix in-casule data send for chained sgls perf probe: Fix NULL pointer dereference in convert_variable_location() net: dsa: tag_8021q: fix the VLAN IDs used for encoding sub-VLANs net/tls: Replace TLS_RX_SYNC_RUNNING with RCU net/tls: Fix use-after-free after the TLS device goes down and up net/mlx5e: Fix incompatible casting net/mlx5e: Check for needed capa
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1013.11)
All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1013.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: openrazer/unknown (arm64) libvpoll-eventfd/unknown (arm64) langford/unknown (arm64) gost-crypto/unknown (arm64) wireguard-linux-compat/unknown (arm64) lime-forensics/unknown (arm64) iptables-netflow/unknown (arm64) west-chamber/unknown (arm64) openafs/unknown (arm64) jool/unknown (arm64) xtrx-dkms/unknown (arm64) systemd/unknown (arm64) mali-midgard/unknown (arm64) lttng-modules/unknown (arm64) v4l2loopback/unknown (arm64) glibc/2.33-0ubuntu5 (armhf) nat-rtsp/unknown (arm64) snapd/unknown (arm64) fwts/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933547] [NEW] tpm driver causes non-fatal kernel crash on boot
Public bug reported: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kernel: [1.138781] bus_for_each_dev+0x7e/0xc0 Jun 24 07:22:45 munin kernel: [1.138785] driver_attach+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138789] bus_add_driver+0x135/0x1f0 Jun 24 07:22:45 munin kernel: [1.138793] driver_register+0x95/0xf0 Jun 24 07:22:45 munin kernel: [1.138798] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138805] __platform_driver_register+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138811] init_tis+0x87/0xdd Jun 24 07:22:45 munin kernel: [1.138817] ? kobject_uevent+0xb/0x10 Jun 24 07:22:45 munin kernel: [1.138823] ? driver_register+0xcd/0xf0 Jun 24 07:22:45 munin kernel: [1.138828] ? agp_intel_init+0x2f/0x2f Jun 24 07:22:45 munin kernel: [1.138833] ? __pci_register_driver+0x54/0x60 Jun 24 07:22:45 munin kernel: [1.138838] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138844] do_one_initcall+0x48/0x1d0 Jun 24 07:22:45 munin kernel: [1.138851] do_initcalls+0xcc/0xec Jun 24 07:22:45 munin kernel: [1.138856] kernel_init_freeable+0x136/0x182 Jun 24 07:22:45 munin kernel: [1.138861] ? rest_init+0xba/0xba Jun 24 07:22:45 munin kernel: [1.138867] kernel_init+0xe/0x116 Jun 24 07:22:45 munin kernel: [1.138871] ret_from_fork+0x22/0x30 Jun 24 07:22:45 munin kernel: [1.13] ---[ end trace 6cb7540ffe33f117 ]--- ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic
Re: [Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
OK Kai-chuan, bad news. I got a 1:1 with Tony and... the freeze is still there, as present as ever. :( Please let me know how I can help. If you have the iperf command that would be useful, please let me know (and if I have to use it during a meeting when it freezes). Best Regards, Steve Bes On Thu, Jun 24, 2021 at 2:11 PM Steve Barriault wrote: > Hi Kai-chuan: > > 1. On UFW, I disabled it, but it did not work. > > 2. For iperf, I did not know this tool existed, and I am not sure how to > generate the right data. Please advise here. > > 3. I also tried the new ucode file. This is what I did: I cloned the git > repo and copied the file into /usr/lib/firmware. Good news is that after > reboot the Internet connection worked. But I did not have the opportunity > to test this during a meeting yet though. > > 4. Stéphane Verdy, who you probably know, gave me the "decoding ring". > When Daniel van Vugt said "the kernel is about two weeks old", this newbie > had no idea if this was a good thing. I thought the kernel got updated > automatically - I was probably mistaken. So I updated it manually. > > So, interestingly, it solved PART of the problem. When I am in a 1:1 > discussion, it works flawlessly on wireless. But if there are multiple > people in the call, then it started having issues again. > > Give me a few days here. I have a few calls upcoming, I will give the wifi > a try in different settings (1:1 and multiple folks) and let you know if > (3) + (4) actually did the trick (because on the 1:1, I could only test (4) > in isolation so far). > > Best Regards, > > Steve > > On Thu, Jun 24, 2021 at 12:05 AM Kai-Chuan Hsieh < > 1932...@bugs.launchpad.net> wrote: > >> ** Changed in: oem-priority >>Status: New => Confirmed >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1932548 >> >> Title: >> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on >> wireless [8086:a0f0] >> >> Status in OEM Priority Project: >> Confirmed >> Status in linux-oem-5.10 package in Ubuntu: >> New >> >> Bug description: >> Whenever I am using a wireless connection, the image freezes roughly >> every two minutes. Sometimes, email cannot be retrieved / computer >> complains the connection was momentarily lost. >> >> - If I am on a wire, this problem does NOT occur. >> - This problems occurs on wireless independent of the platform used >> (behavior seen in both Google Hangout and Zoom) >> - This problem does NOT occur on Windows. I did a meeting where both my >> Linux and Windows machines were connected to the same meeting and using the >> same wifi router, and while the performance on Windows was flawless, >> unfortunately it was not so on the Ubuntu box. So I don't think my wifi >> router or network is to blame. >> - As far as I can recall, the problem used not to be there 2 weeks ago. >> So it may have been introduced by a recent update. >> - As communicated before, I am on a certified machine from Dell, >> recently purchased with Ubuntu already on board from factory (I assume the >> logs there were sent to you would contain the information). >> - I tried to generate a log on the wireless, but the process did not >> let me do this very easily. I am more than happy to send you additional >> information - but please let me know which package you want me to spy upon >> exactly, as I am not sure what would be helpful in this matter. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.04 >> Package: xorg 1:7.7+19ubuntu14 >> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 >> Uname: Linux 5.10.0-1029-oem x86_64 >> ApportVersion: 2.20.11-0ubuntu27.18 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' >> CasperMD5CheckResult: skip >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Fri Jun 18 09:47:58 2021 >> DistUpgraded: Fresh install >> DistributionChannelDescriptor: >># This is the distribution channel descriptor for the OEM CDs >># For more information see >> http://wiki.ubuntu.com/DistributionChannelDescriptor >>canonical-oem-somerville-focal-amd64-20200502-85 >> DistroCodename: focal >> DistroVariant: ubuntu >> EcryptfsInUse: Yes >> ExtraDebuggingInterest: Yes >> GraphicsCard: >>Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA >> controller]) >> Subsystem: Dell Device [1028:0991] >> InstallationDate: Installed on 2021-04-24 (54 days ago) >> InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary >> 20200502-05:58 >> MachineType: Dell Inc. XPS 13 9310 >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem >> root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 03/25/2021 >> dmi.b
[Kernel-packages] [Bug 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
@cborntra v5.13 ubuntu kernel's s390 configuration with zstd -22 --ultra compression is 8.5 MB, whereas gzip -9 is 11M. Thus for gzip to win at bootspeed the decompression speed has to compensate for 2.5M of i/o and be faster than zstd. Unaccelerated decompression comparison still gives me faster decompression with less i/o with zstd compressed kernel image. At Canonical we still do not have z15 mainframe available for us to benchmark this. -- 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: New Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3 /kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1933385] Re: selftests: bpf: test_verifier fixes
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1933385 Title: selftests: bpf: test_verifier fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] kselftest bpf ./test_verifier fails on bionic, preventing regression from being identified. [Test case] Run selftest bpf ./test_verifier and check that it passes. [Potential regressions] The test could still fail or crash the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933385/+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 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] test_maps bpf selftests is failing on bionic. [Regression potential] Kernel is not changed, but test may give a false pass with this change. [Test case] The fixed test has been run on the kernel in -proposed, and passes. After building it, just run ./test_maps from tools/testing/selftests/bpf/. -- This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation
[Kernel-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: Fix Released Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925057/+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 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1932065 Title: Upstream v5.9 introduced 'module' patches that removed exported symbols Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification: [Impact] * The following patches removed an exported symbol that will cause potential disruption and breakage for customers modules: inherit TAINT_PROPRIETARY_MODULE modules: return licensing information from find_symbol modules: rename the licence field in struct symsearch to license modules: unexport __module_address modules: unexport __module_text_address modules: mark each_symbol_section static modules: mark find_symbol static modules: mark ref_module static [Fix] * Temporarily revert as SAUCE patches to allow customers time to make necessary changes to support eventual patch changes. [Test Plan] * none [Where problems could occur] * The new functionality provided by patches will be removed, since we aren't removing existing functionality the risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932065/+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 1932081] Re: Disable hv-kvp-daemon.service on certain instance types
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1932081 Title: Disable hv-kvp-daemon.service on certain instance types Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Disable hv-kvp-daemon.service on certain instance types. As requested for some azure instance types, hv-kvp-daemon is prohibited from starting, and currently it takes a long time to come up and fail. Configure to disable the service on those instances. At the moment, we can key off kernel command line to detect those. [Test Plan] * Boot preview image in azure * Check that hv-kvp-daemon.service is not running [Where problems could occur] * The conditions/detection could have been more specific as to when the daemon is pointless to run. Thus key-off kernel commandline is good enough for now, but may require changes in the future. [Other Info] @ Kernel team, also see https://trello.com/c/JbomiFOe https://lists.ubuntu.com/archives/kernel-team/2021-June/121384.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932081/+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 1930813] Re: [Asus Zenbook UX306] touchpad not recognised after upgrade 21.04
Hi, thx for your support. I've tried several kernel. 5.13-rc7, 5.11.0.22, and 5.8.18 didn't work. Touchapad was stil not recognised. It works with kernel 5.6.19. -- 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/1930813 Title: [Asus Zenbook UX306] touchpad not recognised after upgrade 21.04 Status in linux package in Ubuntu: Incomplete Bug description: Touchpad doesn't work anymore after upgrading to 21.04 on a notebook asus zenbook UX306. Worked perfectly before upgrade ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thilu 11394 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Jun 4 09:15:12 2021 InstallationDate: Installed on 2020-04-23 (406 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=884c588c-71bb-489c-a602-bb6c0463c7c0 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-04 (0 days ago) dmi.bios.date: 08/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.301:bd08/09/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930813/+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 1932209] Re: UAF on CAN J1939 j1939_can_recv
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- 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/1932209 Title: UAF on CAN J1939 j1939_can_recv Status in linux package in Ubuntu: Fix Released Bug description: [Impact] j1939_can_recv may run concurrently to can_rx_unregister on j1939_netdev_stop, which will, then, free the priv struct that is used by j1939_can_recv, leading to a system crash. [Potential regression] CAN J1939 sockets may stop working as expected. [Test case] A program that created multiple threads, binding to J1939 sockets and closing them, while sending RAW CAN sockets were run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932209/+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 1931855] Re: UAF on CAN BCM bcm_rx_handler
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- 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/1931855 Title: UAF on CAN BCM bcm_rx_handler Status in linux package in Ubuntu: Fix Released Bug description: [Impact] bcm_rx_handler may run concurrently to can_rx_unregister on bcm_release, which will, then, free the bcm_op that is used by bcm_rx_handler, leading to a system crash. [Potential regression] CAN BCM sockets may stop working as expected. [Test case] Programs from can-utils were run, some of them concurrently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931855/+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 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: Fix Released Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925057/+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 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
The changeset referenced in Comment #8 was part of a 21-part changeset shown here: https://patches.linaro.org/cover/141739/ I was able to backport these changes to our 4.15 kernel and get it booting w/ the MDS workaround enabled. One option is to SRU those (and a number of follow-up Fixes: changes for them). Presumably that's of some security benefit, though I'm not sure how significant of one. It also isn't clear exactly why those changes are needed for compat with the firmware MDS workaround. -- 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/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Invalid Bug description: This is something to do with the configuration or software versions running here, since we have identical hardware running in an adjacent cloud region but with different versions of the cloud/virt stack. When we boot bionic arm64 Ubuntu cloud images in "bos01" and they land on the eMAG systems, they always fail like this: ... [1.585611] Key type dns_resolver registered [1.587408] registered taskstats version 1 [1.588913] Loading compiled-in X.509 certificates [1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4' [1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [1.610861] Couldn't get size: 0x800e [1.613413] MODSIGN: Couldn't get UEFI db list [1.615920] Couldn't get size: 0x800e [1.618256] MODSIGN: Couldn't get UEFI MokListRT [1.620315] Couldn't get size: 0x800e [1.622317] MODSIGN: Couldn't get UEFI dbx list [1.624446] zswap: loaded using pool lzo/zbud [1.628185] Key type big_key registered [1.629937] Key type trusted registered [1.632012] Key type encrypted registered [1.633668] AppArmor: AppArmor sha1 policy hashing enabled [1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [1.638009] ima: Allocated hash algorithm: sha1 [1.639272] evm: HMAC attrs: 0x1 [1.640875] rtc-efi rtc-efi: setting system clock to 2021-05-11 09:28:43 UTC (1620725323) [1.646247] Freeing unused kernel memory: 5824K [1.657870] Checked W+X mappings: passed, no W+X pages found [1.660250] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.660250] [1.663294] CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-142-generic #146-Ubuntu [1.665939] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [1.668204] Call trace: [1.668981] dump_backtrace+0x0/0x198 [1.670212] show_stack+0x24/0x30 [1.671282] dump_stack+0x98/0xc8 [1.672433] panic+0x128/0x2b0 [1.673502] do_exit+0x75c/0xa80 [1.674749] do_group_exit+0x40/0xb0 [1.676191] get_signal+0x114/0x6e8 [1.677867] do_signal+0x18c/0x240 [1.679498] do_notify_resume+0xd0/0x328 [1.681302] work_pending+0x8/0x10 [1.682771] SMP: stopping secondary CPUs [1.684624] Kernel Offset: disabled [1.686119] CPU features: 0x04802008 [1.687353] Memory Limit: none [1.688453] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.688453] Full example log: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/arm64/c/chromium-browser/20210511_093739_ea3f2@/log.gz We tried to get IS to roll things back to match the working bos02, but they said it's too different and not possible. The working cloud is running Mitaka from the cloud archive on Xenial (qemu 2.5) The broken cloud is running Queens from the cloud archive on Xenial (qemu 2.11) The other thing someone suggested we try is that MDS mitigation is enabled in the broken cloud, so we could disable it. No idea if that makes sense tbh. That's about all we have right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931728/+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 1933078] Re: BlueZ 5.59 release
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Fix Released Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1929833] Re: bluez: meshctl missing
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Released Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: ht
[Kernel-packages] [Bug 1907886] Re: avinfo is missing
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Fix Released Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+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 1786013] Autopkgtest regression report (linux-meta-raspi/5.8.0.1030.32)
All autopkgtests for the newly accepted linux-meta-raspi (5.8.0.1030.32) for groovy have finished running. The following regressions have been reported in tests triggered by the package: dm-writeboost/unknown (arm64) lime-forensics/unknown (arm64) dpdk/unknown (arm64) nat-rtsp/unknown (arm64) fwts/unknown (arm64) jool/unknown (arm64) openafs/unknown (arm64) systemd/246.6-1ubuntu1.4 (armhf) openrazer/unknown (arm64) virtualbox-hwe/unknown (arm64) zfs-linux/unknown (arm64) evdi/unknown (arm64) r8168/unknown (arm64) gost-crypto/unknown (arm64) snapd/unknown (arm64) systemd/unknown (arm64) v4l2loopback/unknown (arm64) ddcci-driver-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1042.40)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1042.40) for focal have finished running. The following regressions have been reported in tests triggered by the package: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) glibc/2.31-0ubuntu9.2 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
@skidooman 1. the ucode should be in /lib/firmware, please check kernel log, if the latest firmware is loaded $ journalctl -k | grep "loaded firmware version" 2. the iperf test for local area network performance, you need such scenario your PC (with problem) <-Wireless-> Access Point <-Ethernet-> Any PC (testbed) Install iperf3 on both side PC $ sudo apt install iperf3 For testing Tx, run client command on your PC and server command on test bed. For testing Rx, run server command on your PC and client command on test bed. server command: $ iperf -s -i 1 client command: $ iperf -c -t 100 -i 1 you can monitor the throughput instantly on client side. the key point is the rate should comply your Wi-Fi selected modulation and stable. For example, you can see the bit rate by running $ iwconfig, the throughput roughly should be the half of the theoretical rate, which is the bit rate you are using now, sometimes it may constraint by the bus speed, but that's the other story. I think the most important part for video conference is stability, you can focus on that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-vid
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released ** Also affects: bluez (Ubuntu Impish) Importance: High Status: Fix Released ** Changed in: bluez (Ubuntu Focal) Assignee: (unassigned) => Anch (anch) ** Changed in: bluez (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Impish) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Focal) Assignee: Anch (anch) => Andy Chi (andch) ** Description changed: [Impact] - * On/off of Bluetooth in gnome-control-center will not work properly. - - * Devices are not refreshed in the list anymore. - - * The passed struct will depend on the length of the submitted read() and the -kernel version. + On/off of Bluetooth in gnome-control-center will not work properly in + kernels 5.11 (approximately) onward. Devices are not refreshed in the + list anymore. [Test Plan] - * Open gnome-control-center and select Bluetooth - - * turn off Bluetooth via UI - - * turn on Bluetooth via UI + 1. Open gnome-control-center and select Bluetooth + 2. Turn off Bluetooth via UI + 3. Turn on Bluetooth via UI + + Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] - * If user install newer kernel such as 5.13, they may have this issue. + Since the fix involves the 'rfkill' logic it has the potential to affect + any Bluetooth or Wifi on/off setting. - * Tested on Intel AX201 and Intel 6235 with kernel version - 5.13.0-1003-oem. + [Other info] - * Upstream bug in gnome-bluetooth -https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + Upstream bug in gnome-bluetooth: + https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 - * Discussion in linux-bluetooth -https://marc.info/?t=16200475893&r=1&w=2 + Discussion in linux-bluetooth: + https://marc.info/?t=16200475893&r=1&w=2 ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: bluez (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1933566] [NEW] XPS 9510 (TGL) Screen Brightness could not be changed
Public bug reported:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to control
backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Tags: oem-priority originate-from-1933030 somerville
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Invalid
** No longer affects: linux-oem-5.10 (Ubuntu Groovy)
** No longer affects: linux-oem-5.10 (Ubuntu Hirsute)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
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/1933566
Title:
XPS 9510 (TGL) Screen Brightness could not be changed
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933566/+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 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
** Description changed:
[Impact]
+ Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
+
+ kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
+ backlight support, but VBT disagrees. If your backlight controls don't
+ work try booting with i915.enable_dpcd_backlight=1. If your machine
+ needs this, please file a _new_ bug report on drm/i915, see
+ https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
+ for details.
+
+ Kernel 5.13 or newer use new way to handle DPCD backlight, and do not
+ need to this to the quirk.
[Fix]
+ Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
+ Verified on Dell XPS 9510(TGL)
- {Where problems could occur]
+ [Where problems could occur]
+ The quirk is for a dedicate panel, and won't affect other platforms.
** Description changed:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
- Kernel 5.13 or newer use new way to handle DPCD backlight, and do not
- need to this to the quirk.
+ Kernel 5.12+ support the backlight via:
+ commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
** Tags added: oem-priority originate-from-1933030 somerville
--
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/1933566
Title:
XPS 9510 (TGL) Screen Brightness could not be changed
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933566/+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 1786013] Autopkgtest regression report (linux-meta-kvm/5.8.0.1031.33)
All autopkgtests for the newly accepted linux-meta-kvm (5.8.0.1031.33) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.2 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.10.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.10.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
** Changed in: linux (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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
