[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Same test in #7 for bionic and so far all 13 deploy looks good, no soft lockup. Looks this is a focal kernel issue and I will try to reboot into different focal kernel. ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:
[Kernel-packages] [Bug 1997667] Re: Wifi device crashes after somet time
Which kernel/firmware work? And which don't? Sorry I need version numbers otherwise I can't look at differences that might cause this. When did you start noticing this behavior? After a kernel upgrade? After a firmware upgrade? Both? After an upgrade from an older release to Kinetic? ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1997667 Title: Wifi device crashes after somet time Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Kinetic: Incomplete Bug description: Release of Ubuntu 22.10 Version of linux-firmware: 20220923.gitf09bebf3-0ubuntu1 Wifi device disables after some time working on my laptop. It starts again after I reboot. Error log from dmesg: [30840.202025] ret_from_fork+0x1f/0x30 [30840.202031] [30840.202032] ---[ end trace ]--- [30840.202035] [ cut here ] [30840.202037] sta_info_move_state() returned -5 [30840.202073] WARNING: CPU: 0 PID: 42196 at net/mac80211/sta_info.c:275 sta_info_free+0x127/0x130 [mac80211] [30840.202137] Modules linked in: ccm rfcomm snd_seq_dummy snd_hrtimer snd_hda_codec_hdmi cmac algif_hash snd_sof_pci_intel_apl algif_skcipher snd_sof_intel_hda_common af_alg soundwire_intel bnep soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils soundwire_bus snd_soc_avs snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core rtsx_usb_ms snd_soc_sst_ipc memstick snd_ctl_led uvcvideo snd_soc_sst_dsp videobuf2_vmalloc snd_hda_codec_realtek snd_soc_acpi_intel_match videobuf2_memops videobuf2_v4l2 snd_soc_acpi intel_pmc_bxt intel_rapl_msr intel_telemetry_pltdrv snd_soc_core intel_punit_ipc intel_telemetry_core snd_hda_codec_generic snd_compress ledtrig_audio x86_pkg_temp_thermal btusb ac97_bus videobuf2_common intel_powerclamp joydev mei_hdcp mei_pxp snd_pcm_dmaengine btrtl btbcm btintel btmtk videodev coretemp snd_hda_intel mc bluetooth snd_intel_dspcfg kvm_intel snd_intel_sdw_acpi snd_hda_codec ecdh_generic ecc snd_hda_core kv m iwlmvm [30840.202200] snd_hwdep snd_pcm mac80211 snd_seq_midi snd_seq_midi_event libarc4 snd_rawmidi rapl intel_cstate hid_multitouch snd_seq binfmt_misc input_leds iwlwifi snd_seq_device serio_raw snd_timer acer_wmi processor_thermal_device_pci_legacy wmi_bmof processor_thermal_device cfg80211 sparse_keymap processor_thermal_rfim processor_thermal_mbox snd processor_thermal_rapl mei_me intel_rapl_common mei soundcore intel_soc_dts_iosf nls_iso8859_1 int3403_thermal acer_wireless int3400_thermal int340x_thermal_zone acpi_thermal_rel mac_hid msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 rtsx_usb_sdmmc rtsx_usb i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper hid_generic mmc_block syscopyarea crct10dif_pclmul crc32_pclmul ghash_clmulni_intel sysfillrect sdhci_pci cqhci i2c_hid_acpi i2c_i801 sysimgblt fb_sys_fops aesni_intel intel_lpss_pci intel_lpss crypto_simd i2c_hid xhci_pci r8169 ahci drm i 2c_smbus [30840.202274] sdhci cryptd realtek xhci_pci_renesas libahci idma64 hid wmi video pinctrl_geminilake [30840.202284] CPU: 0 PID: 42196 Comm: kworker/0:0 Tainted: GW 5.19.0-21-generic #21-Ubuntu [30840.202287] Hardware name: Acer TravelMate B118-M/Virgo_GL, BIOS V1.30 11/05/2020 [30840.202289] Workqueue: events_freezable ieee80211_restart_work [mac80211] [30840.202352] RIP: 0010:sta_info_free+0x127/0x130 [mac80211] [30840.202416] Code: c4 08 5b 41 5c 5d 31 c0 31 d2 31 c9 31 f6 31 ff c3 cc cc cc cc 89 c6 48 c7 c7 b8 4f d5 c0 c6 05 fe f3 0e 00 01 e8 0e cb 7b c3 <0f> 0b e9 40 ff ff ff 66 90 0f 1f 44 00 00 55 48 8d 87 f8 0a 00 00 [30840.202418] RSP: 0018:adfa8274b850 EFLAGS: 00010246 [30840.202420] RAX: RBX: 96879c8f RCX: [30840.202422] RDX: RSI: RDI: [30840.202424] RBP: adfa8274b868 R08: R09: [30840.202426] R10: R11: R12: [30840.202427] R13: 9687958c09c0 R14: 96879c8f0af8 R15: 968782d81028 [30840.202429] FS: () GS:9687fbc0() knlGS: [30840.202431] CS: 0010 DS: ES: CR0: 80050033 [30840.202433] CR2: 7fb30802a0c8 CR3: 00010a4e CR4: 00350ef0 [30840.202435] Call Trace: [30840.202436] [30840.202438] __sta_info_destroy_part2+0x138/0x1a0 [mac80211] [30840.202502] __sta_info_flush+0x128/0x190 [mac80211] [30840.202566] ieee80211_set_disassoc+0x15d/0x590
[Kernel-packages] [Bug 1999882] Re: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part
--- Comment From nico.bo...@ibm.com 2023-03-07 03:55 EDT--- Bug has been verified and is fixed with 5.4.0-145.162. ** 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/1999882 Title: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Bug description: Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence,their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8 Preventive fix: yes Author:Nico Boehr Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the kernel part, whereas the required QEMU part is described and handled in the following related bug: Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - qemu part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1999882/+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 1999882] Comment bridged from LTC Bugzilla
--- Comment From nico.bo...@ibm.com 2023-03-07 04:01 EDT--- (In reply to comment #11) > Bug has been verified and is fixed with 5.4.0-145.162. Please note that the QEMU fix from LP 1999885 is still missing. We recommend releasing both fixes at the same time. Otherwise customers may get this warning message: warning: Unable to set KVM guest TOD clock: Operation not supported -- 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/1999882 Title: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Bug description: Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence,their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8 Preventive fix: yes Author:Nico Boehr Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the kernel part, whereas the required QEMU part is described and handled in the following related bug: Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - qemu part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1999882/+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 2007729] Re: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working
Please provide logs from when the failure happens by running: $ apport-collect 2007729 ** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007729 Title: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: this forum post, https://community.intel.com/t5/Wireless/Linux-Intel- AC-9560-iwlwifi-fails-on-kernels-above-5-10/m-p/1377826#M41506, appears to mention that QuZ-a0-jf-b0-64.ucode has this problem but QuZ-a0-jf-b0-59.ucode does not. taking a look in /lib/firmware i see the following: iwlwifi-QuZ-a0-jf-b0-48.ucode iwlwifi-QuZ-a0-jf-b0-63.ucode iwlwifi-QuZ-a0-jf-b0-50.ucode iwlwifi-QuZ-a0-jf-b0-66.ucode iwlwifi-QuZ-a0-jf-b0-53.ucode iwlwifi-QuZ-a0-jf-b0-68.ucode iwlwifi-QuZ-a0-jf-b0-55.ucode iwlwifi-QuZ-a0-jf-b0-71.ucode iwlwifi-QuZ-a0-jf-b0-59.ucode iwlwifi-QuZ-a0-jf-b0-72.ucode iwlwifi-QuZ-a0-jf-b0-62.ucode it appears to be loading iwlwifi-QuZ-a0-jf-b0-72.ucode and failing. i have removed the these entries one by one, followed by modprobe -r iwlwifi && modprobe iwlwifi untill i have found a working one, which turns out to be iwlwifi-QuZ-a0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 17:57:08 2023 InstallationDate: Installed on 2022-05-12 (281 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007729/+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 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pn
** No longer affects: linux-firmware (Ubuntu Focal) -- 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/1941044 Title: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' Status in linux-firmware package in Ubuntu: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+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 2009580] [NEW] Problems with Docker images with NFS/CIFS mounts into containers in linux-azure-5.4.0-1104
Public bug reported: Hi, As of linux-azure-5.4.0.1104 in Ubuntu Bionic (Azure) we are seeing Docker images fail to start / hang. These images mount NFS and CIFS shares into them as volumes, which I suspect might be related. I see many NFS-related changes in this new kernel version's changelog. These same containers work fine in linux-azure-5.4.0-1103. Upgrading to 1104 reproduces the behaviour. It would seem this kernel version has introduced either a bug or an incompatibility with our version of Docker. Docker version output: Server: Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.2 Git commit: 20.10.12-0ubuntu2~18.04.1 Built:Mon Apr 4 20:53:56 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.5.9-0ubuntu1~18.04.2 GitCommit: runc: Version: 1.1.0-0ubuntu1~18.04.1 GitCommit: docker-init: Version: 0.19.0 GitCommit: I'm willing to help troubleshoot the issue if needed. Thanks ** Affects: linux-meta-azure-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-meta-azure-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2009580 Title: Problems with Docker images with NFS/CIFS mounts into containers in linux-azure-5.4.0-1104 Status in linux-meta-azure-5.4 package in Ubuntu: New Bug description: Hi, As of linux-azure-5.4.0.1104 in Ubuntu Bionic (Azure) we are seeing Docker images fail to start / hang. These images mount NFS and CIFS shares into them as volumes, which I suspect might be related. I see many NFS-related changes in this new kernel version's changelog. These same containers work fine in linux-azure-5.4.0-1103. Upgrading to 1104 reproduces the behaviour. It would seem this kernel version has introduced either a bug or an incompatibility with our version of Docker. Docker version output: Server: Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.2 Git commit: 20.10.12-0ubuntu2~18.04.1 Built:Mon Apr 4 20:53:56 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.5.9-0ubuntu1~18.04.2 GitCommit: runc: Version: 1.1.0-0ubuntu1~18.04.1 GitCommit: docker-init: Version: 0.19.0 GitCommit: I'm willing to help troubleshoot the issue if needed. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure-5.4/+bug/2009580/+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 2009495] Re: [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded
** Package changed: linux (Ubuntu) => smc-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: smc-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009495 Title: [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded Status in Ubuntu on IBM z Systems: New Status in smc-tools package in Ubuntu: New Bug description: ---Problem Description--- [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded === The reason for this is that the aforementioned shared object is installed under: /usr/lib64/libsmc-preload.so Which is AFAICT not what we want, because AFAIU it violates the Debian Policy Manual (https://www.debian.org/doc/debian-policy/ch- opersys.html#s-fhs), and ld.so in Ubuntu has a default search path that understandably does not cover /usr/lib64. Interestingly the upstream Make file does try to detect if we are run on Ubuntu, and choose the install path accordingly. Hereby it relies on "lsb_release -si" returning "Ubuntu", which may or may not be a good idea -- I don't know. In any case if the upstream Makefile does not suit Ubuntu/Debian, then the packager is ought to patch it. Thus in my opinion this is a packaging problem. Contact Information = pa...@de.ibm.com ---uname output--- Linux t3545018.lnxne.boe 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ smc_run ping 172.18.39.17 ERROR: ld.so: object 'libsmc-preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. PING 172.18.39.17 (172.18.39.17) 56(84) bytes of data. BTW $ LD_PRELOAD=libsmc-preload.so LD_DEBUG=libs LD_LIBRARY_PATH=/usr/lib64/ ping 172.18.39.17 does work as expected. Userspace tool common name: smc_run The userspace tool has the following bit modes: na Userspace rpm: smc-tools_1.7.0-0ubuntu1_s390x.deb Userspace tool obtained from project website: na *Additional Instructions for pa...@de.ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2009495/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Thank you for bringing this to our attention. The following commits were made between Ubuntu versions 5.15.0-60.66 and 5.15.0-67.74: f391395fb6b1: NFS: Fix up a sparse warning bcf920d0e616: NFS: Judge the file access cache's timestamp in rcu path 2cbb6062f8eb: NFS: Clear the file access cache upon login e549585b0c95: NFSD: fix use-after-free in __nfs42_ssc_open() 68873d735d98: NFSv4: Retry LOCK on OLD_STATEID during delegation return We suspect that either the file access cache-related commits (i.e., 2cbb6062f8eb/bcf920d0e616/f391395fb6b1) or the retry lock commit (i.e., 68873d735d98) may be causing the issue you are experiencing. To help diagnose the problem, we have created a test kernel that reverts the commit 68873d735d98. To install the test kernel, please run the following commands: sudo add-apt-repository ppa:chengendu/jammy-nfs-test sudo apt update apt install linux-image-unsigned-5.15.0-67-generic After installing the test kernel, we would appreciate it if you could test it to see if the issue is resolved. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ub
[Kernel-packages] [Bug 2009542] Re: Can not select HDMI or Displayport as audio output device.
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009542 Title: Can not select HDMI or Displayport as audio output device. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description: Ubuntu 22.04.2 LTS Release: 22.04 Graphics board: Radeon RX6600 Graphics driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009542/+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 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2009276/+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 2003053] Re: NFS: client permission error after adding user to permissible group
This patch appears to have caused a massive (thousandfold) increase in NFS ACCESS operations. Tested with Ubuntu 20.04 and these kernels: 5.4.0-144-generic 5.15.0-67-generic Downgrading to either 5.4.0-139-generic or 5.15.0-60-generic resolves the issue again. One busy server using NFS went from an average of about 14 ACCESS operations per second to around 33 000 operations per second. This completely overwhelmed the NFS servers, making them practically unusable. -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Looking through the growing list of duplicates, everyone has an AMD GPU so this is almost certainly an issue in that driver. The list of cards affected so far: * RX570 (mine) * RX6700 XT (from LP: #2009275) * RX580 (from LP: #2009276) * RX6600 (from LP: #2009542) I'm happy to post any additional logs / traces that would help debug this and/or test patched kernels (worth looking at the duplicates for additional logs too). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/comments/21 We are seeing this issue with NFSv3. NFS ACCESS operations increased quadratically after upgrading to 5.4.0-144 and 5.15.0-67. Downgrading to either 5.4.0-139-generic or 5.15.0-60-generic resolves the issue again. The commit you say that you have reverted references NFSv4, which we are not using. Therefore, combined with the massive increase in ACCESS operations, I am inclined to believe that the issue is related to the file access cache-related commits and not the retry lock commit. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
In our case (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009325/comments/25), we also use NFSv3, and like Eirik Rye, we've seen this massive increase in ACCESS operations, from averages of 700/s (approx.) to peaks of 27000/s with 5.15.0-67. In case it helps. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chass
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Hello. Same here, with a readeon HD7700 and Ubuntu 22.04.2 With kernel -35 there is no hdmi audio output, but after -32 restore everything is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009595] [NEW] DEP8 failure in lunar
Public bug reported: I don't know what's wrong with this package, or with the kernel package: ubuntu@l-crash:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-6.1.0-16-generic WARNING: /usr/lib/debug/boot/vmlinux-6.1.0-16-generic and /proc/version do not match! WARNING: /proc/version indicates kernel version: 6.1.0-16-generic crash: please use the vmlinux file for that kernel version, or try using the System.map for that kernel version as an additional argument. It is the same version: ubuntu@l-crash:~$ uname -a Linux l-crash 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l|grep linux- ii binutils-x86-64-linux-gnu2.40-2ubuntu1 ii linux-base 4.5ubuntu9 ii linux-firmware 20230302.git60971a64-0ubuntu1 ii linux-headers-6.1.0-16 6.1.0-16.16 ii linux-headers-6.1.0-16-generic 6.1.0-16.16 ii linux-headers-generic6.1.0.16.16 ii linux-image-6.1.0-16-generic 6.1.0-16.16 ii linux-image-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-image-generic 6.1.0.16.16 ii linux-image-unsigned-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-libc-dev:amd64 6.1.0-16.16 ii linux-modules-6.1.0-16-generic 6.1.0-16.16 ii linux-modules-extra-6.1.0-16-generic 6.1.0-16.16 ii util-linux-extra 2.38.1-4ubuntu1 $ apt-cache policy linux-image-unsigned-6.1.0-16-generic-dbgsym linux-image-unsigned-6.1.0-16-generic-dbgsym: Installed: 6.1.0-16.16 Candidate: 6.1.0-16.16 Version table: *** 6.1.0-16.16 500 500 http://ddebs.ubuntu.com lunar/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2009595 Title: DEP8 failure in lunar Status in crash package in Ubuntu: New Bug description: I don't know what's wrong with this package, or with the kernel package: ubuntu@l-crash:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-6.1.0-16-generic WARNING: /usr/lib/debug/boot/vmlinux-6.1.0-16-generic and /proc/version do not match! WARNING: /proc/version indicates kernel version: 6.1.0-16-generic crash: please use the vmlinux file for that kernel version, or try using the System.map for that kernel version as an additional argument. It is the same version: ubuntu@l-crash:~$ uname -a Linux l-crash 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l|grep linux- ii binutils-x86-64-linux-gnu2.40-2ubuntu1 ii linux-base 4.5ubuntu9 ii linux-firmware 20230302.git60971a64-0ubuntu1 ii linux-headers-6.1.0-16 6.1.0-16.16 ii linux-headers-6.1.0-16-generic 6.1.0-16.16 ii linux-headers-generic6.1.0.16.16 ii linux-image-6.1.0-16-generic 6.1.0-16.16 ii linux-image-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-image-generic 6.1.0.16.16 ii linux-image-unsigned-6.1.0-16-generic-dbgsym 6.1.0-16.16 ii linux-libc-dev:amd64 6.1.0-16.16 ii linux-modules-6.1.0-16-generic 6.1.0-16.16 ii linux-modules-extra-6.1.0-16-generic 6.1.0-16.16 ii util-linux-extra 2.38.1-4ubuntu1 $ apt-cache policy linux-image-unsigned-6.1.0-16-generic-dbgsym linux-image-unsigned-6.1.0-16-generic-dbgsym: Installed: 6.1.0-16.16 Candidate: 6.1.0-16.16 Version table: *** 6.1.0-16.16 500 500 http://ddebs.ubuntu.com lunar/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2009595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+attachment/5652409/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Incomplete Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] [NEW] Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
Public bug reported: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "linux-5.19.apport" https://bugs.launchpad.net/bugs/2009594/+attachment/5652408/+files/linux-5.19.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Incomplete Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kerne
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Attachment added: "kernel logs with bug occuring" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+attachment/5652411/+files/dmesg-faulty-boot.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Incomplete Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Attachment added: "kernel logs on a normal working boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+attachment/5652410/+files/dmesg-working-boot.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Incomplete Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2009594 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Incomplete Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007759] Re: Spotify freezes my entire system
I see the exact same issue with spotify, Ubuntu 22.04 and kernel: Linux atomic 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux and I have a Lenovo P14s and CPU model name: AMD Ryzen 7 PRO 5850U with Radeon Graphics -- 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/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: Confirmed Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 The main error that I always get aren't included in any txt files but here is the one error I copy paste from askubuntu: retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) -- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.produc
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Hi Timo, this also affects jammy -- should I add that to the targeting, or is that to be handled separately? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@Matthias, Dave, Andy, Would you please help me to bisect it? i would appreciate a lot. here's test kernel. https://drive.google.com/drive/folders/1Hyejgp0r_Dq2gsovXqxB2BNTE8uPEd6g?usp=share_link * please disable the SecureBoot in bios and run these to install. # sudo dpkg -i *.deb ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2006259] Re: net: wwan: t7xx: Fix Runtime PM implementation
for oem-6.0 this is a "won't fix" at this point
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2006259
Title:
net: wwan: t7xx: Fix Runtime PM implementation
Status in HWE Next:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Won't Fix
Status in linux-oem-6.1 source package in Jammy:
Triaged
Status in linux source package in Kinetic:
Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Triaged
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
Upstream commit d10b3a695ba0 ("net: wwan: t7xx: Runtime PM")
introduced support for Runtime PM for this driver, but due to a bug in
the initialization logic the usage refcount would never reach 0,
leaving the feature unused. This patchset addresses that, together
with a bug found after runtime suspend was enabled.
https://lore.kernel.org/netdev/20230126132535.80339-1-min...@semihalf.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2006259/+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 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
Yes, indeed, if you check adt matrix, only build is done. Smoke testing is done during rt. They were tested locally (expect bionic which is already in updates) 1. bionic was tested on linux-gpg-4.15.0-1146.162 in rt: 731 12:56:40 DEBUG| [stdout] Preparing to unpack .../76-lttng-modules-dkms_2.10.8-1ubuntu2~18.04.5_all.deb ... 732 12:56:40 DEBUG| [stdout] Unpacking lttng-modules-dkms (2.10.8-1ubuntu2~18.04.5) ... ... 147012:58:42 INFO | == lttng smoke test trace context switches == 147112:58:42 INFO | Session test-kernel-session created. 147212:58:42 INFO | Traces will be written in /tmp/lttng-kernel-trace-22702-session 147312:58:42 INFO | PASSED (lttng create) 147412:58:42 INFO | Kernel event sched_switch created in channel channel0 147512:58:42 INFO | PASSED (lttng enable-event) 147612:58:42 INFO | Tracing started for session test-kernel-session 147712:58:42 INFO | PASSED (lttng start) 147812:58:42 INFO | Waiting for data availability. 147912:58:42 INFO | Tracing stopped for session test-kernel-session 148012:58:42 INFO | PASSED (lttng stop) 148112:58:42 INFO | Session test-kernel-session destroyed 148212:58:42 INFO | PASSED (lttng destroy) 148312:58:42 INFO | Found 26292 dd and 147227 context switches 148412:58:42 INFO | PASSED (simple system call tracing with babeltrace) 148512:58:42 INFO | 148612:58:42 INFO | Summary: 7 passed, 0 failed 148712:58:42 DEBUG| Running 'apt-get remove --yes lttng-modules-dkms' 148812:59:27 INFO | GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1677416367 localtime=Feb 26 12:59:27completed successfully 148912:59:27 INFO | END GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1677416367 localtime=Feb 26 12:59:27 2. focal 5.4.0-145.162 ubuntu@focal:~$ apt search lttng-modules-dkms Sorting... Done Full Text Search... Done lttng-modules-dkms/focal-proposed 2.12.5-1ubuntu2~20.04.5 all Linux Trace Toolkit (LTTng) kernel modules (DKMS) 13:51:57 INFO | Summary: 7 passed, 0 failed 13:51:57 DEBUG| Running 'apt-get remove --yes lttng-modules-dkms' 13:52:21 INFO | GOOD ubuntu_lttng_smoke_test.lttng-smoke-testubuntuy 13:52:21 INFO | END GOOD ubuntu_lttng_smoke_test.lttng-smoke-testubuntu1 13:52:21 DEBUG| Persistent state client._record_indent now set to 1 13:52:21 DEBUG| Persistent state client.unexpected_reboot deleted 13:52:21 INFO | END GOODtimestamp=1678197141 localtime=Mar 07 13:521 3. jammy 5.15.0-68.75 ubuntu@jammy:~$ apt search lttng-modules-dkms Sorting... Done Full Text Search... Done lttng-modules-dkms/jammy-proposed,now 2.13.8-1~ubuntu22.04.0 all [installed] Linux Trace Toolkit (LTTng) kernel modules (DKMS) 14:16:39 INFO | Summary: 7 passed, 0 failed 14:16:39 DEBUG| Running 'apt-get remove --yes lttng-modules-dkms' 14:16:52 INFO | GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-test timestamp=1678198612 localtime=Mar 07 14:16:52completed successfully 14:16:52 INFO | END GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-test timestamp=1678198612 localtime=Mar 07 14:16:52 14:16:52 DEBUG| Persistent state client._record_indent now set to 1 14:16:52 DEBUG| Persistent state client.unexpected_reboot deleted 14:16:52 INFO | END GOODtimestamp=1678198612 localtime=Mar 07 14:16:52 4. kinetic 5.19.0-37.38 ubuntu@kinetic:~$ apt search lttng-modules-dkms Sorting... Done Full Text Search... Done lttng-modules-dkms/kinetic-proposed,now 2.13.8-1~ubuntu22.10.0 all [installed] Linux Trace Toolkit (LTTng) kernel modules (DKMS) 14:25:33 INFO | Summary: 7 passed, 0 failed 14:25:33 DEBUG| Running 'apt-get remove --yes lttng-modules-dkms' 14:25:38 INFO | GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1678199138 localtime=Mar 07 14:25:38y 14:25:38 INFO | END GOOD ubuntu_lttng_smoke_test.lttng-smoke-test ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1678199138 localtime=Mar 07 14:25:38 14:25:38 DEBUG| Persistent state client._record_indent now set to 1 14:25:38 DEBUG|
[Kernel-packages] [Bug 1997346] Re: AMD Rembrandt USB4 DPIA docking handling fixes
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997346 Title: AMD Rembrandt USB4 DPIA docking handling fixes Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: To improve the DP tunneling over docking scenario. Especially for S0i3 stress, Displays might be blank or system hang. Kernel panic can be observed when the issue occurs. [ 91.782291] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: drm_dp_dpcd_probe+0xea/0xf0 [drm_display_helper] ]--- *CC to stable(v6.0.y), need to pick into hwe-5.15 as well https://patchwork.freedesktop.org/patch/510829/ https://patchwork.freedesktop.org/patch/510825/ *CCed to stable(v6.0.3) and landed in oem-6.0-1007, need to pick into hwe-5.15 as well https://github.com/torvalds/linux/commit/876fcc4222e1d0e5b73343f4010a8b66be058f48 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997346/+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 1996174] Re: CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1996174
Title:
CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0
Status in ubuntu-kernel-tests:
New
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Won't Fix
Bug description:
Issue found with J-oem-6.0.0-1007
This is not a regression as this failure can be found with older
kernel (6.0.0-1004.4) as well
Test log:
STARTubuntu_cve_kernel.CVE-2016-3672
ubuntu_cve_kernel.CVE-2016-3672timestamp=1666797878timeout=900
localtime=Oct 26 15:24:38
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_cve_kernel.CVE-2016-3672', 'ubuntu_cve_kernel.CVE-2016-3672')
Waiting for pid 55210 for 900 seconds
System python is too old, crash handling disabled
*** CVE-2016-3672 ***
Running 'make -C
/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672 check'
[stdout] make: Entering directory
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
[stdout] gcc -o show_maps show_maps.c -m32
[stdout] sudo -u ubuntu ./check.sh
[stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
[stderr] make: *** [Makefile:11: check] Error 1
A manual test shows this test case is a bit flaky for some reason:
ubuntu@curly:~/autotest-client-tests/ubuntu_cve_kernel/cves/CVE-2016-3672$
for i in {1..10}; do make check; echo $?; make clean; done
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
make: *** [Makefile:11: check] Error 1
2
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
make: *** [Makefile:11: check] Error 1
2
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
gcc -o show_maps show_maps.c -m32
sudo -u ubuntu ./check.sh
0
rm -f show_maps
I don't recall we have this issue with other kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1996174/+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 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.0 kernel
** Package changed: linux-oem-6.0 (Ubuntu) => linux-oem-6.1 (Ubuntu) ** Summary changed: - net-build failed in ubuntu_kernel_selftests with 6.0 kernel + net-build failed in ubuntu_kernel_selftests with 6.1 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.1 kernel Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: New Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type = TLS_CIPHER_SM4_CCM, |
[Kernel-packages] [Bug 1996134] Re: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007
oem-6.0 won't get this fix and should migrate to oem-6.1 soon anyway, where this is fixed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1996134 Title: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: This issue does not exist with J-oem-6.0.0-1006 With systemd 249.11-0ubuntu3.6 ubuntu@curly:~/systemd-249.11/test$ sudo ./networkd-test.py ; uname -a systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin test_bridge_init (__main__.BridgeTest) ... ok test_bridge_port_priority (__main__.BridgeTest) ... ok test_bridge_port_priority_set_zero (__main__.BridgeTest) It should be possible to set the bridge port priority to 0 ... ok test_bridge_port_property (__main__.BridgeTest) Test the "[Bridge]" section keys ... ok test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers ... ERROR test_resolved_etc_hosts (__main__.DnsmasqClientTest) resolved queries to /etc/hosts ... ok test_route_only_dns (__main__.DnsmasqClientTest) ... ok test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok test_transient_hostname (__main__.DnsmasqClientTest) networkd sets transient hostname from DHCP ... ok test_transient_hostname_with_static (__main__.DnsmasqClientTest) transient hostname is not applied if static hostname exists ... ok test_basic_matching (__main__.MatchClientTest) Verify the Name= line works throughout this class. ... ok test_inverted_matching (__main__.MatchClientTest) Verify that a '!'-prefixed value inverts the match. ... ok test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok test_dhcp_timezone (__main__.NetworkdClientTest) networkd sets time zone from DHCP ... ok test_dropin (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd does not have DHCPv6 server support' test_route_only_dns (__main__.NetworkdClientTest) ... ok test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok test_search_domains (__main__.NetworkdClientTest) ... ok test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. ... ok test_catchall_config_coldplug (__main__.UnmanagedClientTest) Verify link states with a catch-all config, cold-plug. ... ok test_unmanaged_setting (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, hot-plug. ... ok test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest) Verify link states with Unmanaged= settings, cold-plug. ... ok == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. ---
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.0 AMD64
** Package changed: linux-oem-6.0 (Ubuntu) => linux-oem-6.1 (Ubuntu)
** Summary changed:
- test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.0 AMD64
+ test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 AMD64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 AMD64
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Incomplete
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
If the symptom observed is a massive increase in ACCESS operations, it is more likely that the root cause is related to file access cache-related commits. I will build a test kernel without those commits for testing. Thanks for your help. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias
[Kernel-packages] [Bug 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.1 kernel
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.1 kernel Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type = TLS_CIPHER_SM4_CCM, |^~ |TLS_CIPHER_AES_CCM_128 tls.c: In function ‘tls_setup’: tl
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943697] Re: net veth selftest failure
Hi Andrea, what is the distro / major version of the kernel? I guess it's Lunar? ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: ubuntu-kernel-selftests ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943697 Title: net veth selftest failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is an old error that doesn't seem to happen if we run this test isolated from the others, maybe the reason is that something is not cleaned up properly (we should probably consider to exclude this test from the net tests and run it isolated as a separate test): 13232 05:16:47 DEBUG| [stdout] # selftests: net: veth.sh 13233 05:16:47 DEBUG| [stdout] # default - gro flag ok 13234 05:16:47 DEBUG| [stdout] # - peer gro flag ok 13235 05:16:47 DEBUG| [stdout] # - tso flag ok 13236 05:16:47 DEBUG| [stdout] # - peer tso flag ok 13237 05:16:47 DEBUG| [stdout] # - aggregationok 13238 05:16:48 DEBUG| [stdout] # - aggregation with TSO off ok 13239 05:16:48 DEBUG| [stdout] # with gro on - gro flag ok 13240 05:16:48 DEBUG| [stdout] # - peer gro flag ok 13241 05:16:48 DEBUG| [stdout] # - tso flag ok 13242 05:16:48 DEBUG| [stdout] # - peer tso flag ok 13243 05:16:48 DEBUG| [stdout] # - aggregation with TSO off fail - got 10 packets, expected 1 13244 05:16:48 DEBUG| [stdout] # with gro enabled on link down - gro flag ok 13245 05:16:48 DEBUG| [stdout] # - peer gro flag ok 13246 05:16:48 DEBUG| [stdout] # - tso flag ok 13247 05:16:48 DEBUG| [stdout] # - peer tso flag ok 13248 05:16:48 DEBUG| [stdout] # - aggregation with TSO off fail - got 10 packets, expected 1 13249 05:16:49 DEBUG| [stdout] # with xdp attached - gro flag ok 13250 05:16:49 DEBUG| [stdout] # - peer gro flag ok 13251 05:16:49 DEBUG| [stdout] # - tso flag ok 13252 05:16:49 DEBUG| [stdout] # - peer tso flag ok 13253 05:16:49 DEBUG| [stdout] # - aggregationfail - got 10 packets, expected 1 13254 05:16:49 DEBUG| [stdout] # - after dev off, flagok 13255 05:16:49 DEBUG| [stdout] # - peer flag ok 13256 05:16:49 DEBUG| [stdout] # - after gro on xdp off, gro flag ok 13257 05:16:49 DEBUG| [stdout] # - peer gro flag ok 13258 05:16:49 DEBUG| [stdout] # - tso flag ok 13259 05:16:49 DEBUG| [stdout] # - peer tso flag ok 13260 05:16:49 DEBUG| [stdout] # - aggregationok 13261 05:16:49 DEBUG| [stdout] # aggregation again with default and TSO off ok 13262 05:16:49 DEBUG| [stdout] not ok 49 selftests: net: veth.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : htt
[Kernel-packages] [Bug 1989983] Re: kinetic: apply new apparmor and LSM stacking patch set
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989983 Title: kinetic: apply new apparmor and LSM stacking patch set Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] Align with the latest apparmor and LSM stacking versions. To do so we need to: - revert sauce to get back to upstream apparmor, and drop old LSM stacking - pull in needed patches from upstream 6.0 - pull in needed patches from apparmor-next 6.1 This is required to properly support apparmor in Ubuntu. [Test case] We test apparmor in our RT suite. [Regression potential] We may see breakage in the apparmor tests after applying this patch set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989983/+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 2009248] Re: nvidia-dkms-510 FTBS with linux 6.2
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.108.03-0ubuntu2 --- nvidia-graphics-drivers-510 (510.108.03-0ubuntu2) lunar; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia.conf: - Add support for Linux 6.2 (LP: #2009248). -- Andrea Righi Sat, 04 Mar 2023 08:44:06 + ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/2009248 Title: nvidia-dkms-510 FTBS with linux 6.2 Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-510 fails to build with linux 6.2, reporting the following error: /var/lib/dkms/nvidia/510.108.03/build/nvidia-drm/nvidia-drm-drv.c:245:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 245 | dev->mode_config.fb_base = 0; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/510.108.03/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-510 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-510 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2009248/+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 2009246] Re: nvidia-dkms-470 FTBS with linux 6.2
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.161.03-0ubuntu2 --- nvidia-graphics-drivers-470 (470.161.03-0ubuntu2) lunar; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia.conf: - Add support for Linux 6.2 (LP: #2009246). -- Andrea Righi Sat, 04 Mar 2023 08:08:01 + ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2009246 Title: nvidia-dkms-470 FTBS with linux 6.2 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-470 fails to build with linux 6.2: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-470 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-470 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009246/+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 2009620] [NEW] No Intel sound drivers available for this Mac Mini
You have been subscribed to a public bug: No sound ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: grub-efi-amd64-signed:amd64: Install grub-efi-amd64-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 16:19:26 2023 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-package jammy -- No Intel sound drivers available for this Mac Mini https://bugs.launchpad.net/bugs/2009620 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 2009620] Re: No Intel sound drivers available for this Mac Mini
Please decide whether you are reporting a missing sound driver or the grub-install crash, you can't put two bugs into one report. Regarding the grub crash it's curious but an issue in the firmware variable handling, not grub. ** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009620 Title: No Intel sound drivers available for this Mac Mini Status in linux package in Ubuntu: Incomplete Bug description: No sound ... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: grub-efi-amd64-signed:amd64: Install grub-efi-amd64-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 16:19:26 2023 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009620/+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 2009271] Re: Too many BDL entries regression
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Kinetic) Status: New => 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/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD 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.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+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 2009629] [NEW] MicroSD card reader not recognized
Public bug reported: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New -- 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/2009629 Title: MicroSD card reader not recognized Status in linux-hwe package in Ubuntu: New Bug description: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+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 2009629] Re: MicroSD card reader not recognized
** Attachment added: "uname" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+attachment/5652516/+files/uname-a.log -- 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/2009629 Title: MicroSD card reader not recognized Status in linux-hwe package in Ubuntu: New Bug description: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+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 2009629] Re: MicroSD card reader not recognized
** Attachment added: "version" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+attachment/5652517/+files/version.log -- 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/2009629 Title: MicroSD card reader not recognized Status in linux-hwe package in Ubuntu: New Bug description: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+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 2009629] Re: MicroSD card reader not recognized
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+attachment/5652518/+files/dmesg.log -- 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/2009629 Title: MicroSD card reader not recognized Status in linux-hwe package in Ubuntu: New Bug description: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+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 2009629] Re: MicroSD card reader not recognized
** Attachment added: "lspi-vvnn" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+attachment/5652519/+files/lspci-vvnn.log -- 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/2009629 Title: MicroSD card reader not recognized Status in linux-hwe package in Ubuntu: New Bug description: Same issue as Bug #1710023 Also using Lenovo Ideapad 100s 14IBR, tested with 5.15.0-67-generic. Booting into a Live USB with an older 4.4 kernel loads the SD card correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2009629/+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 2009253] Re: nvidia-dkms-450-server FTBS with linux 6.2
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.216.04-0ubuntu2 --- nvidia-graphics-drivers-450-server (450.216.04-0ubuntu2) lunar; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia.conf: - Add support for Linux 6.2 (LP: #2009253). -- Andrea Righi Sat, 04 Mar 2023 09:43:52 + ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/2009253 Title: nvidia-dkms-450-server FTBS with linux 6.2 Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-450-server fails to build with linux 6.2, reporting the following error: /var/lib/dkms/nvidia-srv/450.216.04/build/nvidia/nv-acpi.c:84:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] 84 | .remove = nv_acpi_remove_two_args, | ^~~ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-450-server [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-450-server (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/2009253/+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 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
I had a similar issue with a black screen after kernel update to 5.19.0-35. Kernel 5.19.0-32 still worked. Updating NVIDIA drivers to 525.85.05 fixed 5.19.0-35 and broke 5.19.0-32 -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad" (no HDMI audio present, same dmesg lines as seen in the -35 kernel) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
I am affected by this as well -- Lenovo X1 Yoga gen. 6, Ubuntu 22.04.2, kernel 5.19.0-35-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2007994/+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 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (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.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2007994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
Same problem on my PC with NVIDIA GTX 770 I reverted to 5.15 and issue is gone. Good to know it is fixed in 6.1. [System] OS: Ubuntu 22.04 Jammy Jellyfish Arch:x86_64 Kernel: 5.15.0-67-generic (after reverting) Desktop: ubuntu:GNOME Display Server: x11 [CPU] Vendor: GenuineIntel Model: 12th Gen Intel(R) Core(TM) i5-12400F [Graphics] OpenGL Renderer: NVIDIA GeForce GTX 770/PCIe/SSE2 OpenGL Version: 4.6.0 NVIDIA 470.161.03 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
I attempted this and booted into kernel 5.19.0-32-generic however I then had no wifi at all. The option to connect no longer existed in the top right corner. Prior to this, it failed in the same way, with Microcode SW error detected, a second time today. It does seems like it happened less often but it's hard to prove that. I switched back to 5.15 for now so as to have a usable computer. -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2009255] Re: nvidia-dkms-515-server FTBS with linux 6.2
This bug was fixed in the package nvidia-graphics-drivers-515-server - 515.86.01-0ubuntu3 --- nvidia-graphics-drivers-515-server (515.86.01-0ubuntu3) lunar; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia.conf: - Add support for Linux 6.2 (LP: #2009255). -- Andrea Righi Sat, 04 Mar 2023 10:20:38 + ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515-server in Ubuntu. https://bugs.launchpad.net/bugs/2009255 Title: nvidia-dkms-515-server FTBS with linux 6.2 Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-515-server fails to build with linux 6.2: /var/lib/dkms/nvidia-srv/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 245 | dev->mode_config.fb_base = 0; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia-srv/515.86.01/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-515-server [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-515-server (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515-server/+bug/2009255/+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 2009254] Re: nvidia-dkms-470-server FTBS with linux 6.2
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.161.03-0ubuntu2 --- nvidia-graphics-drivers-470-server (470.161.03-0ubuntu2) lunar; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch, debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia.conf: - Add support for Linux 6.2 (LP: #2009254). -- Andrea Righi Sat, 04 Mar 2023 10:00:38 + ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2009254 Title: nvidia-dkms-470-server FTBS with linux 6.2 Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-470-server fails to build with linux 6.2: /var/lib/dkms/nvidia-srv/470.161.03/build/nvidia/nv-acpi.c:84:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] 84 | .remove = nv_acpi_remove_two_args, | ^~~ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-470-server [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-470-server (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2009254/+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 2009597] [NEW] Kerberized NFS mounts not working on Raspberry PI
You have been subscribed to a public bug: Kerberized NFS mounts stopped working on Raspberry Pi starting with Ubuntu 21.10. In 22.10 the issue still exists. The reason is that the kernel module rpcsec_gss_krb5 which is needed for establishing a kerberos protected NFS connection to the server has been removed from the kernel image and put to the linux-modules-extra package instead. In my particular case it was: linux-image-5.19.0-1011-raspi Trying to mount the NFS share resulted in the following error message: mount.nfs: an incorrect mount option was specified I did not find any documentation stating that the linux-modules-extra package needs to be installed and the kernel module has to be loaded manually. So my expectation would be either to update the documentation or to move rpcsec_gss_krb5 back to the kernel image. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kerberos nfs -- Kerberized NFS mounts not working on Raspberry PI https://bugs.launchpad.net/bugs/2009597 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1964093] Re: nfsver=3, udp not working anymore
> Looks like if I want to keep using UDP I'll need to stick with 20.04 for now, but it would be nice if it weren't disabled in 22.04. Yea, same here. I've ended up here trying to update to 22.04 but not that big of a need, just trying to be proactive. -- 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/1964093 Title: nfsver=3,udp not working anymore Status in linux package in Ubuntu: Confirmed Bug description: Package: nfs-kernel-server Architecture: amd64 Version: 1:2.6.1-1~exp1ubuntu1 nfsversion 3 with proto udp seems not to be supported by the nfs- kernel-server anymore. In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still possible. I could mount with either tcp or udp: 1. tcp mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) 2. udp mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) Now in Ubuntu 22.04 I get the message: mount.nfs: an incorrect mount option was specified I tried to enable upd in /etc/nfs.conf in section [nfsd]: [nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=n udp=y # tcp=y # vers2=n # vers3=y But there was no effect. nfs3 with udp is needed by several busybox mount binaries in initrds of Knoppix and other live distributions used via PXE boot. Best regards Jörg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+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 2009597] Re: Kerberized NFS mounts not working on Raspberry PI
** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2009597 Title: Kerberized NFS mounts not working on Raspberry PI Status in linux-raspi package in Ubuntu: New Bug description: Kerberized NFS mounts stopped working on Raspberry Pi starting with Ubuntu 21.10. In 22.10 the issue still exists. The reason is that the kernel module rpcsec_gss_krb5 which is needed for establishing a kerberos protected NFS connection to the server has been removed from the kernel image and put to the linux-modules-extra package instead. In my particular case it was: linux-image-5.19.0-1011-raspi Trying to mount the NFS share resulted in the following error message: mount.nfs: an incorrect mount option was specified I did not find any documentation stating that the linux-modules-extra package needs to be installed and the kernel module has to be loaded manually. So my expectation would be either to update the documentation or to move rpcsec_gss_krb5 back to the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2009597/+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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
Do you mean you are not able to install new driver firmware by step in #21? Did you disable secure boot? Since the step didn't include module signing, your system can't load it if the secure boot is enabled. -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 1997908] Re: Wi-Fi 6E does not work in Canada with Intel AX210
Ran the test package from a clean install. The driver upgraded to iwlwifi-ty-a0-gf-a0-72.ucode and I was able to see 6Ghz channels while in the Canadian regulatory domain. -- 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/1997908 Title: Wi-Fi 6E does not work in Canada with Intel AX210 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Kinetic: Incomplete Status in linux-firmware source package in Lunar: Fix Released Bug description: Intel has been adding support for Wi-Fi 6E (6GHz band) to additional countries as they get regulatory approval. With the base install of Ubuntu 22.10, I do not have 6GHz support while in Canada, and have confirmed with 'iw reg get'. Intel has released an updated pnvm file to support more countries: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0.pnvm?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 After copying the latest iwlwifi-ty-a0-gf-a0-72.ucode and iwlwifi- ty-a0-gf-a0.pnvm from git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git and rebooting I now have full support: $ iw reg get [...] (5945 - 5965 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5965 - 5985 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5985 - 6005 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6005 - 6025 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6025 - 6045 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6045 - 6065 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6065 - 6085 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6085 - 6105 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6105 - 6125 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6125 - 6145 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6145 - 6165 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6165 - 6185 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6185 - 6205 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6205 - 6225 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6225 - 6245 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6245 - 6265 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6265 - 6285 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6285 - 6305 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6305 - 6325 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (6325 - 6345 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (6345 - 6365 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN Can we update the linux-firmware package for kinetic to include the latest pnmv and core 72 firmware? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1997908/+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 2009287] Re: When using this kernel, the HDMI audio output dissapears
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009287/+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 2009032] Re: Kernel 5.19.0-35 killed HDMI audio for me
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 My apologies; I'm going to mark this as a duplicate of LP: #2009136 even though that bug was reported later as it's very likely the same issue (AMD-based card with HDMI audio output), and that seems to be where the kernel team are currently bisecting the issue. Sorry I didn't spot this one when reporting 2009136! ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009032 Title: Kernel 5.19.0-35 killed HDMI audio for me Status in linux package in Ubuntu: Incomplete Bug description: On Kernel 5.19.0-32 everything is working fine. But when updating to Kernel 5.19.0-35, HDMI audio is no longer listed/working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009032/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver
Would it be possible to have the RTW89 driver for the RTL8852BE added to the kernel? Every time I receive a kernel update I have to hook my machine up to a docking station (which has an RJ45) re-download and install the drivers in the terminal. This is a fairly popular wifi card, so I'm sure others are having the same issue. The drivers from github (below) work extremely well between kernel updates on Ubuntu-based Mint 21: https://github.com/HRex39/rtl8852be.git Please let me know if you need any other information. -- 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/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2009642] [NEW] mt7921: add support of MTFG table
Public bug reported: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+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 2009642] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2009642 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+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 2009642] Re: mt7921: add support of MTFG table
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Lunar) 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/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
** Also affects: charm-ovn-chassis Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: New Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
Subscribed ~Field-critical This impacts deployment on Prodstack-6. The only workaround is to reduce the number of VFs used by OVN which is not the behavior expected and reduce greatly the number of instances deployed with offloading for the whole environment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009594 Title: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE) Status in charm-ovn-chassis: New Status in linux package in Ubuntu: Confirmed Bug description: This is seen on particular with : * Charmed Openstack with Jammy Yoga * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates) * Mellanox Connectx-6 card with mlx5_core module being used * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading The servers enter into very high load (around 75~100) quickly during the boot with all process relying on network communication with the Mellanox network card being stuck or extremely slow. Kernel logs are being displayed about kworkers being blocked for more than 120 seconds The number of SR-IOV devices configured both from the firmware and the kernel seems to have a serious correlation with the likeliness of this bug to occur. Having enabled more VF seems to hugely increase the risk for this bug to arise. This does not happen systematically at every boot, but with 32 VFs on each PF, it occurs about 40% of the time. To recover the server, a cold reboot is required. Look at a quick sample of the trace, this seems to involve directly the mlx5 driver within the kernel : Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more than 120 seconds. Mar 07 05:24:56 nova-1 kernel: Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu Mar 07 05:24:56 nova-1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid: 19 ppid: 2 flags:0x4000 Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn Mar 07 05:24:56 nova-1 kernel: Call Trace: Mar 07 05:24:56 nova-1 kernel: Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0 Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110 Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30 Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750 Mar 07 05:24:56 nova-1 kernel: __mutex_lock_slowpath+0x13/0x20 Mar 07 05:24:56 nova-1 kernel: mutex_lock+0x3e/0x50 Mar 07 05:24:56 nova-1 kernel: mlx5_register_device+0x1c/0xb0 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: mlx5_init_one+0xe4/0x110 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: probe_one+0xcb/0x120 [mlx5_core] Mar 07 05:24:56 nova-1 kernel: local_pci_probe+0x4b/0x90 Mar 07 05:24:56 nova-1 kernel: work_for_cpu_fn+0x1a/0x30 Mar 07 05:24:56 nova-1 kernel: process_one_work+0x21f/0x400 Mar 07 05:24:56 nova-1 kernel: worker_thread+0x200/0x3f0 Mar 07 05:24:56 nova-1 kernel: ? rescuer_thread+0x3a0/0x3a0 Mar 07 05:24:56 nova-1 kernel: kthread+0xee/0x120 Mar 07 05:24:56 nova-1 kernel: ? kthread_complete_and_exit+0x20/0x20 Mar 07 05:24:56 nova-1 kernel: ret_from_fork+0x22/0x30 Mar 07 05:24:56 nova-1 kernel: To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
Ubuntu 22.04 users can try kernel 6.1 by: sudo apt install linux-oem-22.04c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
I have prepared a test kernel that reverts the file access cache-related commits. Please follow these steps and give it a try: 1. sudo add-apt-repository ppa:chengendu/jammy-nfs-test 2. sudo apt update 3. sudo apt install linux-headers-5.15.0-67-generic linux-image-unsigned-5.15.0-67-generic linux-modules-5.15.0-67-generic linux-modules-extra-5.15.0-67-generic 4. reboot 5. uname -rv 5.15.0-67-generic #74+test20230307b2h2cbb6062f8eb-Ubuntu SMP Tue Mar 7 23:16:16 UT In the meantime, we will also work on figuring out the error. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Confirmed Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 5.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2018 dmi.bios.vendor: P
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
Thanks for testing. The backport is tracked in LP: #2009014. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+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 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
No I don't have any AMD based system right now. It should be rather quick since the it doesn't take a long time to reproduce the issue. -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+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 2007584] Re: Jammy update: v6.1.11 upstream stable release
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority originate-from-2009584 sutton
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status in OEM Priority Project:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Confirmed
Bug description:
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:
v6.1.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: fxos8700: fix IMU data bits returned to user spa
[Kernel-packages] [Bug 2007584] Re: Jammy update: v6.1.11 upstream stable release
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Atlas Yu (pseudoc)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status in OEM Priority Project:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Confirmed
Bug description:
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:
v6.1.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: fxos8700: fix IMU data bits returned
[Kernel-packages] [Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
Added a jammy task because most people will understand that better than rls-jj-incoming. This is something I'd like to do in bugs more often, but if it's wrong (@vorlon?) then let me know. ** Also affects: egl-wayland (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: egl-wayland (Ubuntu Jammy) Status: New => Triaged ** Changed in: egl-wayland (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to egl-wayland in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions Status in NVIDIA / egl-wayland: New Status in GTK+: Fix Released Status in egl-wayland package in Ubuntu: Fix Released Status in egl-wayland source package in Jammy: Triaged Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1965563/+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 2009642] Re: mt7921: add support of MTFG table
** Changed in: linux-firmware (Ubuntu Lunar) Status: In Progress => 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/2009642 Title: mt7921: add support of MTFG table Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987269] Re: [5.18.0 mainline] mlx5 deadlock
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Expired Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14: 00074f30 R15: 7ffd50fa8f50 Aug 22 01:15:02 pc1-rb3-n3 kern
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
@Devon, are you using jammy/kinectic? -- 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/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2009642] Re: mt7921: add support of MTFG table
** Description changed: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. + Lunar already got the firmware, so SRU for Jammy only. + Kernel commit is a new feature and it requests more than 10 unrelated + commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Invalid ** Tags added: oem-priority originate-from-2008052 sutton ** Tags added: originate-from-2007990 -- 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/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@Dave, thanks here's another test kernel for bisect https://drive.google.com/drive/folders/1yRA9fYQg98yEAIeyRg6cQYGboroDEHgb?usp=share_link -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009672] [NEW] Unable to show 1920x1080 mode in HDMI output
Public bug reported: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2007729] Re: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working
** Tags added: kern-5995 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007729 Title: HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: this forum post, https://community.intel.com/t5/Wireless/Linux-Intel- AC-9560-iwlwifi-fails-on-kernels-above-5-10/m-p/1377826#M41506, appears to mention that QuZ-a0-jf-b0-64.ucode has this problem but QuZ-a0-jf-b0-59.ucode does not. taking a look in /lib/firmware i see the following: iwlwifi-QuZ-a0-jf-b0-48.ucode iwlwifi-QuZ-a0-jf-b0-63.ucode iwlwifi-QuZ-a0-jf-b0-50.ucode iwlwifi-QuZ-a0-jf-b0-66.ucode iwlwifi-QuZ-a0-jf-b0-53.ucode iwlwifi-QuZ-a0-jf-b0-68.ucode iwlwifi-QuZ-a0-jf-b0-55.ucode iwlwifi-QuZ-a0-jf-b0-71.ucode iwlwifi-QuZ-a0-jf-b0-59.ucode iwlwifi-QuZ-a0-jf-b0-72.ucode iwlwifi-QuZ-a0-jf-b0-62.ucode it appears to be loading iwlwifi-QuZ-a0-jf-b0-72.ucode and failing. i have removed the these entries one by one, followed by modprobe -r iwlwifi && modprobe iwlwifi untill i have found a working one, which turns out to be iwlwifi-QuZ-a0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 17:57:08 2023 InstallationDate: Installed on 2022-05-12 (281 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007729/+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 2009672] Re: Regression: Unable to show 1920x1080 mode in HDMI output
** Summary changed: - Unable to show 1920x1080 mode in HDMI output + Regression: Unable to show 1920x1080 mode in HDMI output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2009672 Title: Regression: Unable to show 1920x1080 mode in HDMI output Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: System can show image in HDMI output during bootup. I don't know which mode it is using during bootup. Anyway it can not show image in 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my system HDMI is just a Displayport connector with an adapter. xrandr lists the video modes of the connected HDMI monitor, and it does not show any error message or non-zero exit status when I enable 1920x1080 mode in the HDMI output; thereafter xrandr shows the mode is currently used in the HDMI output, but my monitor/TV does not show such a video mode. It can still work in 1920x1080i and lower resolution modes. The bug occurs with linux-image-5.15.0-67-generic but not with linux- image-5.15.0-60-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-67-generic 5.15.0-67.74~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Mar 8 07:51:31 2023 InstallationDate: Installed on 2019-12-05 (1188 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: Upgraded to focal on 2020-07-10 (970 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2009672/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
Verified on the following steps: 1) Enabled proposed pocket, upgrade pulseaudio and install oem kernel 6.1.0-1008.8. 2) Reboot. 3) Pair and connect AirPods, play some audio to ensure that A2DP still works. 4) Switch to HFP and I can hear sound. Microphone also works too. 5) Keep switching between A2DP and HFP profile, both of them work all the time. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
#9 doesn't seem to be a regression caused by pulseaudio. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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
