[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I created a PPA with prebuilt kernels for Jammy & Focal oem in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1950062. Could you help verify them? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac 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.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951837] Re: new kernel 5.4.0-90-generic contain error with snat in vrf
Hi, Thanks for reporting this issue. If the behavior fails due to a kernel update, it's unlikely to be a problem in the user space nftables tool. Looking for suspicious commits between 5.4.0-84.94 and 5.4.0-90.101, https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=318d87fed75ab207f5913ae5c6abf4f781c507f1 looks supicious and landed in 5.4.0-89.100. However, that commit was reverted in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=cb3a632a2da90d23629b59c8da26460af0bc455a , which landed in 5.4.0-97.110, published to focal at https://launchpad.net/ubuntu/+source/linux/5.4.0-97.110 on February 7, 2022. Are you still seeing this issue? ** Changed in: nftables (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951837 Title: new kernel 5.4.0-90-generic contain error with snat in vrf Status in linux package in Ubuntu: Incomplete Status in nftables package in Ubuntu: Invalid Bug description: I update kernel 5.4.0-90-generic. Nftables(*0.9.3) not work SNAT in VRF. After reboot and use 5.4.0-84-generic all works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960893] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1960893 Title: i915 gives trace in dmesg Status in linux package in Ubuntu: Confirmed Bug description: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel: driver_attach+0x1e/0x20 [1.904705] kernel: bus_add_driver+0x135/0x200 [1.904707] kernel: driver_register+0x95/0xf0 [1.904708] kernel: __pci_register_driver+0x68/0x70 [1.904709] kernel: i915_register_pci_driver+0x23/0x30 [i915] [1.904746] kernel: i915_init+0x3b/0xfc [i915] [1.904793] kernel: ? 0xc0cad000 [1.904794] kernel: do_one_initcall+0x46/0x1d0 [1.904797] kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.904800] kernel: do_init_module+0x62/0x280 [1.904801] kernel: load_module+0xac9/0xbb0 [1.904803] kernel: __do_sys_finit_module+0xbf/0x120 [1.904804] kernel: __x64_sys_finit_module+0x18/0x20 [1.904805] kernel: do_syscall_64+0x59/0xc0 [1.904807]
[Kernel-packages] [Bug 1960893] [NEW] i915 gives trace in dmesg
Public bug reported: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel: driver_attach+0x1e/0x20 [1.904705] kernel: bus_add_driver+0x135/0x200 [1.904707] kernel: driver_register+0x95/0xf0 [1.904708] kernel: __pci_register_driver+0x68/0x70 [1.904709] kernel: i915_register_pci_driver+0x23/0x30 [i915] [1.904746] kernel: i915_init+0x3b/0xfc [i915] [1.904793] kernel: ? 0xc0cad000 [1.904794] kernel: do_one_initcall+0x46/0x1d0 [1.904797] kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.904800] kernel: do_init_module+0x62/0x280 [1.904801] kernel: load_module+0xac9/0xbb0 [1.904803] kernel: __do_sys_finit_module+0xbf/0x120 [1.904804] kernel: __x64_sys_finit_module+0x18/0x20 [1.904805] kernel: do_syscall_64+0x59/0xc0 [1.904807] kernel: ? fput+0x13/0x20 [1.904809] kernel: ? ksys_mmap_pgoff+0x150/0x2b0 [1.904810] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [1.904812] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904814] kernel: ? __x64_sys_mmap+0x33/0x40 [1.904816] kernel: ? do_syscall_64+0x69/0xc0 [1.904817] kernel: ? do_syscall_64+0x69/0xc0 [1.904818] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904819] kernel: ?
[Kernel-packages] [Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems 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/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960891] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1960891 Title: rtw_8821ce :01:00.0: failed to send h2c command Status in linux package in Ubuntu: Confirmed Bug description: Unstable Wifi Sometimes most Wifi AP's (including my own) or not seen dmesg filled with [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1239 F pulseaudio /dev/snd/pcmC0D0p: sander 1239 F...m pulseaudio /dev/snd/seq:sander 1237 F pipewire CasperMD5CheckResult: pass
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1029.32~20.04.27)
All autopkgtests for the newly accepted linux-meta-azure-5.11 (5.11.0.1029.32~20.04.27) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) snapd/2.54.2+20.04ubuntu2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960891] [NEW] rtw_8821ce 0000:01:00.0: failed to send h2c command
Public bug reported: Unstable Wifi Sometimes most Wifi AP's (including my own) or not seen dmesg filled with [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1239 F pulseaudio /dev/snd/pcmC0D0p: sander 1239 F...m pulseaudio /dev/snd/seq:sander 1237 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 06:40:43 2022 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus
[Kernel-packages] [Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Tags added: servcert-194 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960362 Title: EDAC update for AMD Genoa support in 22.04 Status in linux package in Ubuntu: In Progress Bug description: EDAC updates for AMD Genoa support for 22.04 as requested by AMD f957112423905.17EDAC: Add RDDR5 and LRDDR5 memory types e2be5955a8865.17EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Tags added: servcert-195 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: In Progress Bug description: Patch pull request to include additional support for AMD Genoa in 22.04 f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960364] Re: EDAC MCE updates for AMD Genoa in 22.04
91f75eb481cf is not a clean pull into 5.15 5176a93ab27a picks cleanly. ** Tags added: hwcert-server ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: servcert-193 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Patch pull request to include additional Genoa support in 22.04 91f75eb481cf x86/MCE/AMD, EDAC/mce_amd: Support non-uniform MCA bank type enumeration 5176a93ab27a x86/MCE/AMD, EDAC/mce_amd: Add new SMCA bank types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7
@Dariusz, You said "The situation is different on impish - on this release the mic is available out of the box.". I remember the impish doesn't install firmware-sof-signed package out of box, so the the sof-cml.ri is still provided by linux-firmware of impish, and the sof-cml.ri in is impish is identical to the sof-cml.ri in the focal. If so, I guess this is not an issue on the sof-firmware, maybe it is an issue on the kernel of 5.4.0. So could you confirm the mic could work under impish without the firmware-sof-signed package? And could you upload the complete dmesg under focal with the original sof-firmware in focal? About the bionic, I am afraid we couldn't make the mic work under it. To make the mic work, not only needs the kernel and sof-firmware, also needs to upgrade the alsa-lib, alsa-ucm-conf and pulseaudio. -- 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/1959681 Title: mic not working on HP-EliteBook-830-G7 Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Bug description: There is no audio input from the built-in mic available on Bionic & Focal on certain intel audio hw (00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8]) despite trying different kernel cmdline options (snd_hda_intel.dmic_detect=0 or snd_intel_dspcfg.dsp_driver=1). The behavior was similar on Bionic and Focal - no mic listed in alsa/pulseaudio mixers. Additionally the following can be found in the kernel log: sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver sof-audio-pci :00:1f.3: enabling device ( -> 0002) sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found The situation is different on impish - on this release the mic is available out of the box. I made a simple test of overwriting sof files inside Focal's linux- firmware package with the contents of firmware-sof-signed package from impish finding it solved the issue without any trace of errors in the logs. The same approach did not work on Bionic (despite similar kernel versions used in both 5.4.0) - due to HWE). These are some excerpts from Bionic launching impish SOF firmware: sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel sof-audio-pci :00:1f.3: firmware boot complete sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled [ Test Plan ] 1. Launch Ubuntu desktop on affected hardware. 2. Open audio mixer (e.g. pulsemixer). 3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo). Expected result: Built-in mic is available for use. Actual result: Built-in mic is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960868] Re: Dell Precision 5520 boots to the wrong VT (black screen)
XorgLogOld.txt is showing that Xorg crashed. If that's a recurring issue then it might explain this bug. It looks most likely to be bug 1811023 which is also the most common Xorg crash globally for Ubuntu right now. It also seems to mostly affect Nvidia users. Please reproduce the issue a few more times and if you keep seeing Xorg crashes like: [ 4.932] (EE) Backtrace: [ 4.932] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55ac57b32aec] [ 4.933] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f2b8ea073c0] [ 4.933] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f2b8e84418b] [ 4.933] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f2b8e823859] [ 4.934] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 4.934] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f2b8e823729] [ 4.934] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f2b8e834f36] [ 4.934] (EE) 6: /usr/lib/xorg/Xorg (dixRegisterPrivateKey+0x239) [0x55ac579efb39] [ 4.934] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_init+0xcf) [0x7f2a0961b37f] or log messages like: privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. then this is bug 1811023. ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete -- 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/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2 seems to run fine without issues. After do a software update which appears to update to LTS 20.04.3, the laptops no longer boot properly. I end up at a black screen with an underscore cursor blinking at the upper left. If I then hold the Alt key down and click the right arrow a few times followed by the left arrow a few times, eventually I see the normal GUI login screen and I can log in. Please let me know if there is anything that can be done to avoid this problem. I have tried on several Dell laptops and I get the same behavior on all of them. There seems to be something broken in Ubuntu 20.04.3 for these lapotops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.47.03 Mon Jan 24 22:58:54 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 14:37:36 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=58eb98db-d059-4fbb-8a18-0c258fd3ab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac 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.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960868] Re: Dell Precision 5520 no longer boots properly (black screen)
Sounds like a variation of bug 1878838. ** Summary changed: - Xorg freeze + Dell Precision 5520 no longer boots properly (black screen) ** Summary changed: - Dell Precision 5520 no longer boots properly (black screen) + Dell Precision 5520 boots to the wrong VT (black screen) ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- 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/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2 seems to run fine without issues. After do a software update which appears to update to LTS 20.04.3, the laptops no longer boot properly. I end up at a black screen with an underscore cursor blinking at the upper left. If I then hold the Alt key down and click the right arrow a few times followed by the left arrow a few times, eventually I see the normal GUI login screen and I can log in. Please let me know if there is anything that can be done to avoid this problem. I have tried on several Dell laptops and I get the same behavior on all of them. There seems to be something broken in Ubuntu 20.04.3 for these lapotops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.47.03 Mon Jan 24 22:58:54 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 14:37:36 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=58eb98db-d059-4fbb-8a18-0c258fd3ab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 1203062 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:br1.20:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I recently was able to work around this issue using the nvidia 510 drivers and following this suggestion: https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/3 Thus far no issues with resuming. Not sure if it helps with 460 but thought I'd share. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs
[Kernel-packages] [Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960875] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-02-14 20:28 EDT--- The root-patch which has introduced the bug is from kernel 5.11. Therefore, Ubuntu 21.10 and higher need to be fixed. The fix is already available in stable now: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/s390?h=v5.17-rc4=dd9cb842fa9d90653a9b48aba52f89c069f3bc50 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call Status in linux package in Ubuntu: New Bug description: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
I got the same issue with my Dell Inspiron 5155, everytime it went to sleep I can't boot the laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959529] Re: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Comment: #0 - D. Gary Chapman - 2022-01-26 12:43:25 == ---Problem Description--- IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 based SSC Contact Information = Gary Chapman (ch...@us.ibm.com) ---uname output--- 5.4.0-73-generic #82-Ubuntu Machine Type = IBM Z in IDAA SSC-mode lpar ---Debugger--- A debugger is not configured -- IBM SSC LEVEL: 4.1.5 IBM IDAA LEVEL: 7.5.6 On a client system we are observing this: Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 Kdump: loaded Tainted: G OE 5.4.0-73-generic #82-Ubuntu Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR) Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt [dm_crypt] Jan 19 16:25:57 data5 kernel: Call Trace: Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0) Jan 19 16:25:57 data5 kernel: [<006b6d64588a>] dump_stack+0x8a/0xb8 Jan 19 16:25:57 data5 kernel: [<006b6cfd8262>] warn_alloc+0xe2/0x160 IBM LTC Networking team has identified the upstream commit 714c9108851743bb718fbc1bfb81290f12a53854 as the root cause. This patch shows up in the Ubuntu kernel source tree: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854 but has not been ported to Ubuntu 20.04 / kernel 5.4 IDAA on SSC requests backport to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960875] [NEW] [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
Public bug reported: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-196419 severity-medium targetmilestone-inin2110 ** Tags added: architecture-s39064 bugnameltc-196419 severity-medium targetmilestone-inin2110 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call Status in linux package in Ubuntu: New Bug description: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960875] [NEW] [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
You have been subscribed to a public bug: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-196419 severity-medium targetmilestone-inin2110 -- [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call https://bugs.launchpad.net/bugs/1960875 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 1960364] 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 1960364 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/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: Incomplete Bug description: Patch pull request to include additional Genoa support in 22.04 91f75eb481cf x86/MCE/AMD, EDAC/mce_amd: Support non-uniform MCA bank type enumeration 5176a93ab27a x86/MCE/AMD, EDAC/mce_amd: Add new SMCA bank types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960364] Re: EDAC MCE updates for AMD Genoa in 22.04
** Changed in: linux (Ubuntu) Status: Invalid => 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/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: New Bug description: Patch pull request to include additional Genoa support in 22.04 91f75eb481cf x86/MCE/AMD, EDAC/mce_amd: Support non-uniform MCA bank type enumeration 5176a93ab27a x86/MCE/AMD, EDAC/mce_amd: Add new SMCA bank types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Changed in: linux (Ubuntu) Status: Invalid => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960362 Title: EDAC update for AMD Genoa support in 22.04 Status in linux package in Ubuntu: In Progress Bug description: EDAC updates for AMD Genoa support for 22.04 as requested by AMD f957112423905.17EDAC: Add RDDR5 and LRDDR5 memory types e2be5955a8865.17EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Thanks for the reply, by the way :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Hello! I think the bug can be closed: > BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. On the same date of the bluez package upgrade, I had to revert to an older kernel version due to the amdgpu driver incompatibility, so that should be the cause. The version was the Ubuntu mainline 5.11.16 (the latest compatible with 20.04 and with the amdgpu official drivers as of today), which I don't know if it's of any interest (if so, I can upload the information). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: In Progress Bug description: Patch pull request to include additional support for AMD Genoa in 22.04 f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960871] [NEW] linux-modules-extra-* fails to install due to dependency on unsigned package
Public bug reported: Several SRU tests are failing the test setup due to failure to install the modules-extra package: * Command: yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes automake bison build-essential byacc flex git keyutils libacl1-dev libaio- dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl- dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules- extra-4.15.0-1120-aws Exit status: 100 Duration: 0.908210039139 stdout: Reading package lists... Building dependency tree... Reading state information... xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). xfsprogs set to manually installed. git is already the newest version (1:2.17.1-1ubuntu0.9). git set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-extra-4.15.0-1120-aws : Depends: linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1960871 Title: linux-modules-extra-* fails to install due to dependency on unsigned package Status in linux-aws package in Ubuntu: New Bug description: Several SRU tests are failing the test setup due to failure to install the modules-extra package: * Command: yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes automake bison build-essential byacc flex git keyutils libacl1-dev libaio- dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl- dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules- extra-4.15.0-1120-aws Exit status: 100 Duration: 0.908210039139 stdout: Reading package lists... Building dependency tree... Reading state information... xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). xfsprogs set to manually installed. git is already the newest version (1:2.17.1-1ubuntu0.9). git set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-extra-4.15.0-1120-aws : Depends: linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1960871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
Refactored this to only address hwmon patches. ** Description changed: Patch pull request to include additional support for AMD Genoa in 22.04 - These two are already in Jammy: - e7d445ab26db 2021-10-19 14:07:17 +0200 x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c - 1ff2fc02862d 2021-12-05 16:44:52 +0100 x86/sme: Explicitly map new EFI memmap table as encrypted - - These remain to pick: - f95711242390 2021-12-10 12:51:28 +0100 EDAC: Add RDDR5 and LRDDR5 memory types - - e2be5955a886 2021-12-10 12:54:33 +0100 EDAC/amd64: Add support for AMD - Family 19h Models 10h-1Fh and A0h-AFh - - 5176a93ab27a 2021-12-22 17:19:18 +0100 x86/MCE/AMD, EDAC/mce_amd: Add - new SMCA bank types - - 91f75eb481cf 2021-12-22 17:22:09 +0100 x86/MCE/AMD, EDAC/mce_amd: - Support non-uniform MCA bank type enumeration - - 8bb050cd5cf4 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Support up to 12 - CCDs on AMD Family of processors - - 3cf90efa1367 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Add support for - AMD Family 19h Models 10h-1Fh and A0h-AFh - - f707bcb5d1cb 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Remove unused - definitions + f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions + 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh + 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: In Progress Bug description: Patch pull request to include additional support for AMD Genoa in 22.04 f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960742] Re: System freeze
Hi thanks for your help, please check at the attachment ** Attachment added: "PREVBOOT.TXT" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+attachment/5560876/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: System freeze Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag: Default string dmi.board.name: V14 dmi.board.vendor: INET dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWZ362D.fBNAPLL02.2105061:bd05/25/2021:br5.19:efr1.2:svnINTEL:pnV14:pvrDefaultstring:rvnINET:rnV14:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku2105061: dmi.product.family: Jasper lake dmi.product.name: V14 dmi.product.sku: 2105061 dmi.product.version: Default string dmi.sys.vendor: INTEL version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956670] Re: Extend support for runtime power management for AMD's Yellow Carp
** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956670 Title: Extend support for runtime power management for AMD's Yellow Carp Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Some OEM designs may populate the secured USB port without runtime power management supported. [Fix] Adds two IDs for XHCI controllers and enable runtime PM as default. This is from kernel 5.16-rc6. [Test] This is requested by AMD. [Where problems could occur] Low risk. This patch adds two additional hardware IDs and has no impacts on other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960861] [NEW] Impish update: upstream stable patchset 2022-02-14
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-02-14 Ported from the following upstream stable releases: v5.10.93, v5.15.16 from git://git.kernel.org/ devtmpfs regression fix: reconfigure on each mount orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc() remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided perf: Protect perf_guest_cbs with RCU KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest KVM: s390: Clarify SIGP orders versus STOP/RESTART 9p: only copy valid iattrs in 9P2000.L setattr implementation video: vga16fb: Only probe for EGA and VGA 16 color graphic cards media: uvcvideo: fix division by zero at stream start rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with interrupts enabled firmware: qemu_fw_cfg: fix sysfs information leak firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries firmware: qemu_fw_cfg: fix kobject leak in probe error path KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after reboot from Windows ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk ALSA: hda/realtek: Add quirk for Legion Y9000X 2020 ALSA: hda/realtek: Re-order quirk entries for Lenovo powerpc/pseries: Get entry and uaccess flush required bits from H_GET_CPU_CHARACTERISTICS mtd: fixup CFI on ixp4xx KVM: x86: don't print when fail to read/write pv eoi memory remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP perf annotate: Avoid TUI crash when navigating in the annotation of recursive functions ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop ALSA: hda/tegra: Fix Tegra194 HDA reset failure UBUNTU: upstream stable to v5.10.93, v5.15.16 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2022-02-14 + from git://git.kernel.org/ -upstream stable patchset 2022-02-14 -from git://git.kernel.org/ + devtmpfs regression fix: reconfigure on each mount + orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc() + remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided + perf: Protect perf_guest_cbs with RCU + KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest + KVM: s390: Clarify SIGP orders versus STOP/RESTART + 9p: only copy valid iattrs in 9P2000.L setattr implementation + video: vga16fb: Only probe for EGA and VGA 16 color graphic cards + media: uvcvideo: fix division by zero at stream start + rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with interrupts enabled + firmware: qemu_fw_cfg: fix sysfs information leak + firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries + firmware:
[Kernel-packages] [Bug 1960766] Re: Introduce 510 NVIDIA driver series
This bug was fixed in the package nvidia-settings - 510.47.03-0ubuntu1 --- nvidia-settings (510.47.03-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1960766). * debian/rules.defs: - Remove final / from the URL * debian/patches/series: - Drop 07_remove_features_for_legacy.patch. * debian/patches/08_add_prime_support.patch: - Rebase on 510 * debian/patches/17_do_not_read_config_on_power_saving_mode.patch: - Refresh patch. -- Alberto Milone Mon, 14 Feb 2022 16:51:41 +0100 ** Changed in: nvidia-settings (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1960766 Title: Introduce 510 NVIDIA driver series Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-settings source package in Focal: In Progress Status in nvidia-settings source package in Impish: In Progress Bug description: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1960766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960849] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1960849 Title: Unstable boot/reboot, system hangup! Status in linux package in Ubuntu: Confirmed Bug description: After many attempt to boot with repair mode and different kernels I somewhere can work but from time to time some apps (Firefox, Ubuntu software, pgAdmin) do not start at all. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sp 2331 F pulseaudio /dev/snd/controlC0: sp 2331 F pulseaudio CasperMD5CheckMismatches: ./pool/main/g/gcc-11/gcc-11_11.2.0-7ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 19:23:37 2022 InstallationDate: Installed on 2022-01-28 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=0f6f9eda-8b75-4524-885f-f90e6cda3b35 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960808] 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 1960808 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/1960808 Title: Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile Status in linux package in Ubuntu: Incomplete Bug description: When trying to suspend my Laptop (clicking suspend in the drop down menu) the screen goes black and all lights go out, but then everything springs back to life and the computer shows me the login screen again. When clicking suspend (in the drop down menu) again the GUI crashes(Only if I haven't logged back in). When restarting the GUI is back. The same problem occurs if the computer hibernates. But this only occurs when having opened a profile that is not the default one in Firefox. Hibernating without having done anything works just fine. (I am up to date with every package 14.2.2022) I am using the Xorg driver. 1) $lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2) $apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $apt-cache policy pm-utils pm-utils: Installed: (none) Candidate: 1.4.1-19 Version table: 1.4.1-19 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages ^ Is pm-utils the issue ? It is not. I installed the Package with Synaptic Package manager but there is no change 3) I expected my computer to hibernate/Suspend. 4) It did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960808] Re: Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960808 Title: Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile Status in linux package in Ubuntu: Incomplete Bug description: When trying to suspend my Laptop (clicking suspend in the drop down menu) the screen goes black and all lights go out, but then everything springs back to life and the computer shows me the login screen again. When clicking suspend (in the drop down menu) again the GUI crashes(Only if I haven't logged back in). When restarting the GUI is back. The same problem occurs if the computer hibernates. But this only occurs when having opened a profile that is not the default one in Firefox. Hibernating without having done anything works just fine. (I am up to date with every package 14.2.2022) I am using the Xorg driver. 1) $lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2) $apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $apt-cache policy pm-utils pm-utils: Installed: (none) Candidate: 1.4.1-19 Version table: 1.4.1-19 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages ^ Is pm-utils the issue ? It is not. I installed the Package with Synaptic Package manager but there is no change 3) I expected my computer to hibernate/Suspend. 4) It did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960808] [NEW] Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile
You have been subscribed to a public bug: When trying to suspend my Laptop (clicking suspend in the drop down menu) the screen goes black and all lights go out, but then everything springs back to life and the computer shows me the login screen again. When clicking suspend (in the drop down menu) again the GUI crashes(Only if I haven't logged back in). When restarting the GUI is back. The same problem occurs if the computer hibernates. But this only occurs when having opened a profile that is not the default one in Firefox. Hibernating without having done anything works just fine. (I am up to date with every package 14.2.2022) I am using the Xorg driver. 1) $lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 2) $apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $apt-cache policy pm-utils pm-utils: Installed: (none) Candidate: 1.4.1-19 Version table: 1.4.1-19 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages ^ Is pm-utils the issue ? It is not. I installed the Package with Synaptic Package manager but there is no change 3) I expected my computer to hibernate/Suspend. 4) It did not. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile https://bugs.launchpad.net/bugs/1960808 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 1960849] [NEW] Unstable boot/reboot, system hangup!
Public bug reported: After many attempt to boot with repair mode and different kernels I somewhere can work but from time to time some apps (Firefox, Ubuntu software, pgAdmin) do not start at all. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sp 2331 F pulseaudio /dev/snd/controlC0: sp 2331 F pulseaudio CasperMD5CheckMismatches: ./pool/main/g/gcc-11/gcc-11_11.2.0-7ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 19:23:37 2022 InstallationDate: Installed on 2022-01-28 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=0f6f9eda-8b75-4524-885f-f90e6cda3b35 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960849 Title: Unstable boot/reboot, system hangup! Status in linux package in Ubuntu: New Bug description: After many attempt to boot with repair mode and different kernels I somewhere can work but from time to time some apps (Firefox, Ubuntu software, pgAdmin) do not start at all. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sp 2331 F pulseaudio /dev/snd/controlC0: sp 2331 F pulseaudio CasperMD5CheckMismatches: ./pool/main/g/gcc-11/gcc-11_11.2.0-7ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 19:23:37 2022 InstallationDate: Installed on 2022-01-28 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=0f6f9eda-8b75-4524-885f-f90e6cda3b35 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Kernel-packages] [Bug 1960826] 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 1960826 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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Incomplete Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: New Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] [NEW] NFSv4 performance problem with newer kernels
You have been subscribed to a public bug: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- NFSv4 performance problem with newer kernels https://bugs.launchpad.net/bugs/1960826 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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U. The issue is not present with kernels 5.9.10 or 5.15.23. It is present with the default kernel from the most recent KDE Neon (5.13). Here's a short video, it's the same pattern (static and vertical lines on the right) as the other video in this thread: https://twitter.com/tlhunter/status/1493107390731874305 The pattern is reminiscent to an HDMI desync issue but the vertical lines do make it distinct. It appeared to affect the laptop screen but not an external display. The static appeared after the screen went to sleep and woke back up, though I don't believe the system went to sleep. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US 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.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
It wasn't fixed with switching to gdm3, sorry, I deleted my comment above. -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960841] Re: Make linux-tools-common Provide linux-cpupower
Marking as confirmed to make the bot happy (logs aren't relevant to the issue) ** 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/1960841 Title: Make linux-tools-common Provide linux-cpupower Status in linux package in Ubuntu: Confirmed Bug description: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa-ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960841] 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 1960841 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/1960841 Title: Make linux-tools-common Provide linux-cpupower Status in linux package in Ubuntu: Incomplete Bug description: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa-ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960841] [NEW] Make linux-tools-common Provide linux-cpupower
Public bug reported: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa- ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960841 Title: Make linux-tools-common Provide linux-cpupower Status in linux package in Ubuntu: Incomplete Bug description: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa-ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
https://lists.ubuntu.com/archives/kernel-team/2022-February/128061.html
** Description changed:
[Impact]
- * Missing firmware for Intel ICE driver on Bionic,
-which is supported by the HWE kernel from Focal.
-
+ * Missing firmware for Intel ICE driver on Bionic,
+ which is supported by the HWE kernel from Focal.
+
[Fix]
- * commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
-brings the Bionic package in line with Focal (ice-1.3.4.0.pkg/LICENSE.ice)
+ * commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
+ brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
- * Without firmware:
-
- ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
- ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
- ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
- ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
+ * Without firmware:
- * With firmware:
+ ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
+ ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
+ ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
+ ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
- ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
- ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
- ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
- ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
-
+ * With firmware:
+
+ ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
+ ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
+ ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
+ ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
+
[Where problems could occur]
- * Systems with devices managed by the ice driver on Bionic HWE kernel from
Focal.
-
- * The firmware enables advanced features, increasing driver exposure and
device activity.
+ * Systems with devices managed by the ice driver on Bionic HWE kernel
+ from Focal.
- * This has been available on Focal, which helps with some chance of issues
being hit and
-reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
+ * The firmware enables advanced features, increasing driver exposure
+ and device activity.
+
+ * This has been available on Focal, which helps with some chance of issues
being hit and
+ reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
In Progress
Status in linux-firmware source package in Focal:
Invalid
Status in linux-firmware source package in Impish:
Invalid
Status in linux-firmware source package in Jammy:
Invalid
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
[Kernel-packages] [Bug 1960839] Re: Bionic: missing firmware file /lib/firmware/intel/ice/ddp/ice.pkg for ice driver (HWE kernel)
Bionic test package:
$ dpkg-deb -c linux-firmware_1.173.20+test20220214b1_all.deb | grep -w ice
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/ddp/
-rw-r--r-- root/root577796 2022-02-13 23:10
./lib/firmware/intel/ice/ddp/ice-1.3.4.0.pkg
-rw-r--r-- root/root 2041 2022-02-13 23:21
./usr/share/doc/linux-firmware/licenses/LICENSE.ice
lrwxrwxrwx root/root 0 2022-02-13 23:10
./lib/firmware/intel/ice/ddp/ice.pkg -> ice-1.3.4.0.pkg
Focal package:
$ dpkg-deb -c linux-firmware_1.187.26_all.deb | grep -w ice
drwxr-xr-x root/root 0 2022-01-28 06:54 ./lib/firmware/intel/ice/
drwxr-xr-x root/root 0 2022-01-28 06:54 ./lib/firmware/intel/ice/ddp/
-rw-r--r-- root/root577796 2022-01-28 06:54
./lib/firmware/intel/ice/ddp/ice-1.3.4.0.pkg
-rw-r--r-- root/root 2041 2022-01-28 06:54
./usr/share/doc/linux-firmware/licenses/LICENSE.ice
lrwxrwxrwx root/root 0 2022-01-28 06:54
./lib/firmware/intel/ice/ddp/ice.pkg -> ice-1.3.4.0.pkg
** Summary changed:
- Bionic: missing firmware file /lib/firmware/intel/ice/ddp/ice.pkg for ice
driver (HWE kernel)
+ Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
In Progress
Status in linux-firmware source package in Focal:
Invalid
Status in linux-firmware source package in Impish:
Invalid
Status in linux-firmware source package in Jammy:
Invalid
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] [NEW] Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Public bug reported:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0 build
0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be read.
Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0 build
0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Bionic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux-firmware (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Invalid
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
In Progress
Status in linux-firmware source package in Focal:
Invalid
Status in linux-firmware source package in Impish:
Invalid
Status in linux-firmware source package in Jammy:
Invalid
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Kernel re-spun. 5.13.0-30 is expected to be released to -updates by 2022/Feb/17[1]. [1] https://lists.ubuntu.com/archives/kernel-sru- announce/2022-February/000198.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960549] Re: Azure: CIFS backport request
** Changed in: linux-azure (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1960549
Title:
Azure: CIFS backport request
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft is asking to have 3 CIFS patches backported to focal/linux-
azure.
506c1da44fee32ba1d3a70413289ad58c772bba6 ("cifs: use the expiry output of
dns_query to schedule next resolution")
4ac0536f8874a903a72bddc57eb88db774261e3a ("cifs: set a minimum of 120s for
next dns resolution")
7be3248f313930ff3d3436d4e9ddbe9fccc1f541 ("cifs: To match file servers, make
sure the server hostname matches")
This is a second attempt because the first backport attempt caused a
regression. This set has been thoroughly tested by Microsoft,
especially for the case that was causing the regression (DFS enabled
shares).
[Where things could go wrong]
Share connection attempts could fail. DFS shares could cause kernel
panics.
[Other Info]
SF: #00324495
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960549/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960766] Re: Introduce 510 NVIDIA driver series
** Changed in: nvidia-settings (Ubuntu) Status: Triaged => In Progress ** Changed in: nvidia-settings (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: nvidia-settings (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: nvidia-settings (Ubuntu Impish) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1960766 Title: Introduce 510 NVIDIA driver series Status in nvidia-settings package in Ubuntu: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-settings source package in Focal: In Progress Status in nvidia-settings source package in Impish: In Progress Bug description: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1960766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect
** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1958990 Title: Add sunrpc module parameters for NFSv3 nconnect Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-5.11 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of 2 module parameters to sunrpc. The primary purpose of which is to restrict or pin NFSv3 TCP connections to one server in order to take advantage of local server connection caching. In the presence of a load balancer, round robin connection requests defeats the advantages of local caching. [Test Plan] Microsoft tested [Where things could go wrong] NFSv3 connection attempts could be slow or fail altogether. [Other Info] SF: #00312346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958252] Re: Support networking XDP
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1958252 Title: Support networking XDP Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure source package in Focal: In Progress Status in linux-azure-5.11 source package in Focal: New Status in linux-azure source package in Hirsute: Won't Fix Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.11 source package in Impish: Invalid Bug description: SRU Justification [Impact] Enable XDP support in Azure tuned kernels. [Test Plan] Microsoft tested. [Where things could go wrong] Network performance could be impacted or base functionality could fail. [Other Info] SF: #00324494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: In Progress Status in linux-signed-azure package in Ubuntu: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-meta-azure source package in Hirsute: Fix Released Status in linux-signed-azure source package in Hirsute: Fix Released Status in linux-azure source package in Impish: In Progress Status in linux-meta-azure source package in Impish: In Progress Status in linux-signed-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: In Progress Status in linux-signed-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959012] Re: MANA updates
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1959012
Title:
MANA updates
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-azure source package in Focal:
New
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Bug description:
SRU Justification
[Impact]
The MANA driver is missing 2 updates.
commit 6cc74443a7732d7e93bee3d0c3704a22cc7274d9 ("net: mana: Add RX fencing")
commit 9acfc57fa2b8944ed079cedbf846823ea32b8a31 ("net: mana: Fix memory leak
in mana_hwc_create_wq")
[Test Plan]
Microsoft tested
[Where things could go wrong]
Fencing requests could get dropped or sent out of order.
[Other Info]
SF: #00324494
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959012/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()
** Changed in: kunpeng920/ubuntu-18.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953386 Title: hisi_sas driver may oops in prep_ssp_v3_hw() Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] The hisi_sas driver occasionally oopses on boot. [ 32.724666] Unable to handle kernel NULL pointer dereference at virtual address 0110 [ 32.732720] Mem abort info: [ 32.735504] ESR = 0x9604 [ 32.738546] Exception class = DABT (current EL), IL = 32 bits [ 32.70] SET = 0, FnV = 0 [ 32.747482] EA = 0, S1PTW = 0 [ 32.750612] Data abort info: [ 32.753478] ISV = 0, ISS = 0x0004 [ 32.757298] CM = 0, WnR = 0 [ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [ 32.766755] [0110] *pgd= [ 32.771700] Internal error: Oops: 9604 [#1] SMP [ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3 hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x (ptrval)) [ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24 [ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 32.834884] Workqueue: :74:02.0_disco_q sas_discover_domain [libsas] [ 32.839182] hns3 :bd:00.0 enp189s0f0: renamed from eth8 [ 32.841558] pstate: a0c9 (NzCv daif +PAN +UAO) [ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.864354] sp : 21833a00 [ 32.867653] x29: 21833a00 x28: b790728621e0 [ 32.872940] x27: b790728607d8 x26: b79072861158 [ 32.878227] x25: d7b07b9340a0 x24: 0028 [ 32.883515] x23: d7906cd69400 x22: d7906cd69418 [ 32.02] x21: b79072aad3d0 x20: 21b33000 [ 32.894089] x19: b79072aad3d0 x18: 0030 [ 32.899376] x17: 9e710776 x16: 3efb16aabb00 [ 32.904663] x15: x14: 3efb976abcef [ 32.909950] x13: 0006 x12: b79072863480 [ 32.915237] x11: b79072aad3e0 x10: b79072861148 [ 32.920524] x9 : x8 : 24cc0fb0 [ 32.925812] x7 : x6 : 003f [ 32.931099] x5 : 0040 x4 : 20a0 [ 32.936386] x3 : d79071e2d400 x2 : 21833bb4 [ 32.941673] x1 : b79072863460 x0 : 28a0 [ 32.946960] Call trace: [ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main] [ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main] [ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main] [ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas] [ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas] [ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas] [ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas] [ 33.000192] sas_discover_domain+0x340/0x664 [libsas] [ 33.005225] process_one_work+0x1bc/0x3ec [ 33.009217] worker_thread+0x58/0x4a0 [ 33.012863] kthread+0x13c/0x170 [ 33.016077] ret_from_fork+0x10/0x18 [ 33.019638] Code: 2a004820 2a04 f9400ed8 f9410061 (3943a319) [ 33.025705] ---[ end trace da9256b7aa3297ba ]--- [Test Case] Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller. [Fix] e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd [Where things could go wrong] We could potentially be trading one boot time crash for another that hasn't popped up in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1953386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960322] Re: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960322 Title: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of [1] in order to better account for dropped packets. Patch [2] is not strictly required, but will prevent context adjustments with future patches. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=e4b7621982d29f26ff4d39af389e5e675a4ffed4 [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=68f831355052 [Test Plan] Microsoft tested [Where things could go wrong] RX dropped statistics could be in error. [Other Info] SF: #00327708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
Also, ubuntu_lxc fails on jammy now; even though it is still using impish branch of tests. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and now have a few tests failing on all architectures and systems as of Feb 4th 2022 it seems. Log with details is attached in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960539] Re: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960539 Title: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure blob driver adds support for accelerated access to Azure Blob storage for Azure VMs. Azure host uses its native network to perform Blob requests directly to Blob servers. [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression since this is an elective module. [Other Info] SF: #00327792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560776/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560777/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560783/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560786/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560775/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560782/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560784/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560787/+files/acpidump.txt
** 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/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560781/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560778/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560785/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560779/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560780/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560774/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
such as linux-firmware (761MB uncompressed). I would prefer to remove
linux-firmware to reduce disk space and bandwidth usage, but linux-
image-generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual,
but linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose
for their respective linux-modules-extra-${VERSION}-xxx packages. It
would be very helpful to me (and, I'm sure, many others) to complete
the set with a linux-modules-extra-generic metapackage that would
depend on the latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-28-generic N/A
linux-backports-modules-5.13.0-28-generic N/A
linux-firmware 1.201.3
RfKill:
Tags: impish
Uname: Linux 5.13.0-28-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Re: Create linux-modules-extra-generic metapackage
apport information
** Tags added: apport-collected impish
** Description changed:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to keep
it installed and updated.
Since it is a virtual machine, there is no need to install packages such
as linux-firmware (761MB uncompressed). I would prefer to remove linux-
firmware to reduce disk space and bandwidth usage, but linux-image-
generic depends on it.
I would remove linux-image-generic and rely on linux-image-virtual, but
linux-image-virtual does not depend on linux-modules-
extra-${VERSION}-generic, and there is no linux-modules-extra-generic
metapackage. I would have to manually install linux-modules-
extra-${VERSION}-generic every time I update the kernel.
There are already linux-modules-extra-aws, linux-modules-extra-gcp and
linux-modules-extra-gke metapackages which fulfill the same purpose for
their respective linux-modules-extra-${VERSION}-xxx packages. It would
be very helpful to me (and, I'm sure, many others) to complete the set
with a linux-modules-extra-generic metapackage that would depend on the
latest linux-modules-extra-${VERSION}-generic.
Thank you for your consideration.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ccherlin 1645 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-01-05 (405 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ IwConfig:
+ lono wireless extensions.
+
+ ens33 no wireless extensions.
+
+ docker0 no wireless extensions.
+ Lsusb:
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+ Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+ Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+ /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+ |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+ |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
+ /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=screen-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1
zswap.compressor=lz4
+ ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
+ RelatedPackageVersions:
+ linux-restricted-modules-5.13.0-28-generic N/A
+ linux-backports-modules-5.13.0-28-generic N/A
+ linux-firmware 1.201.3
+ RfKill:
+
+ Tags: impish
+ Uname: Linux 5.13.0-28-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _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.
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1960633/+attachment/5560773/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create linux-modules-extra-generic metapackage
Status in linux package in Ubuntu:
Confirmed
Bug description:
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains several
critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
keep it installed and updated.
Since it is a virtual machine, there is no need to install packages
[Kernel-packages] [Bug 1960820] Re: linux-azure: Missing ext4 commits
https://lists.ubuntu.com/archives/kernel-team/2022-February/128036.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960820] Re: linux-azure: Missing ext4 commits
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
@tjaalton: This kernel has been tested on 6 laptop types and passes on all of them. Tested subsystems included USB, Bluetooth, Wi-Fi, Ethernet and many others. We can get you a full report if you like. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: On many CLEVO chassis computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960820] [NEW] linux-azure: Missing ext4 commits
Public bug reported: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Impish) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: New ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959569] Re: Focal update: upstream stable patchset 2022-01-31
** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1959569 Title: Focal update: upstream stable patchset 2022-01-31 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed 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: upstream stable patchset 2022-01-31 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1959569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
closing as -1021 seems to work ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: On many CLEVO chassis computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1960771 Title: Use EC GPE for s2idle wakeup on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Opening lid doesn't wakeup some AMD platforms from s2idle. [Fix] Use EC GPE for lid events to wakeup the laptops. [Test] Close and only the lid. The affected laptop now can be woken up by lid. [Where problems could occur] The original issue was later fixed by "pinctrl: amd: Fix wakeups when IRQ is shared with SCI". However, EC GPE is prone to cause spurious wakeup, so we still need to keep an eye on the regression reports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1960771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression and it lands mainline since v5.16-rc2. After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2205 F pulseaudio /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1021-oem N/A linux-backports-modules-5.14.0-1021-oem N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960766] Re: Introduce 510 NVIDIA driver series
** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: New => Triaged ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-settings (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-settings (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nvidia-settings (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-settings (Ubuntu Focal) Status: New => Triaged ** Changed in: nvidia-settings (Ubuntu Impish) Status: New => Triaged ** Changed in: nvidia-settings (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Impish) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Impish) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1960766 Title: Introduce 510 NVIDIA driver series Status in nvidia-settings package in Ubuntu: Triaged Status in nvidia-settings source package in Bionic: Triaged Status in nvidia-settings source package in Focal: Triaged Status in nvidia-settings source package in Impish: Triaged Bug description: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1960766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] WCN685x hw2.1 takes additional/updated firmware for both WiFi and Bluetooth function. ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 [Fix] WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except for the directory path and a board-2.bin. For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from mainline are neccessary for Focal. Jammy has all of them already. For kernel, many of the prerequisite works have been committed for hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G will be turned off for the lack of userspace support, the only fix necessary is to correct read mask of version info register. ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14 in bug 1939528, so only oem-5.14 has to be reverted. [Test Case] WiFi and Bluetooth devices should be up and running, pass basic operations. $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai [Where problems could occur] At the time being, WCN685x WiFi 6G support will be turnef off deliberately due to the lack of full support in the userspace management tools. [Other Info] While this is a new hardware model from OEM program, it's only nominated for Focal oem-5.14 kernel and the coming LTS Jammy. == original bug report == ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
impish 5.13.0-30 verification passed. ubuntu@segers:~$ uname -a; lsb_release -a; sudo dmesg | grep "fail to alloc uacce" Linux segers 5.13.0-30-generic #33-Ubuntu SMP Fri Feb 4 17:05:14 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] WCN685x hw2.1 takes additional/updated firmware for both WiFi and Bluetooth function. ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 [Fix] WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except for the directory path and a board-2.bin. For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from mainline are neccessary for Focal. Jammy has all of them already. For kernel, many of the prerequisite works have been committed for hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G will be turned off for the lack of userspace support, the only fix necessary is to correct read mask of version info register. ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14 in bug 1939528, so only oem-5.14 has to be reverted. [Test Case] WiFi and Bluetooth devices should be up and running, pass basic operations. $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai [Where problems could occur] At the time being, WCN685x WiFi 6G support will be turnef off deliberately due to the lack of full support in the userspace management tools. [Other Info] While this is a new hardware model from OEM program, it's only nominated for Focal oem-5.14 kernel and the coming LTS Jammy. == original bug report == ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
That other issue could be the same, I just wish someone there would have reproduced the exact stack trace attached by Boris here to be more certain, which I reproduce as: WARNING: CPU: 0 PID: 18016 at /var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:3935 nv_restore_user_channels+0xce/0xe0 [nvidia] Call Trace: nv_set_system_power_state+0x22b/0x3e0 [nvidia] nv_procfs_write_suspend+0xe9/0x140 [nvidia] proc_reg_write+0x5a/0x90 ? __cond_resched+0x1a/0x50 vfs_write+0xc3/0x250 ksys_write+0x67/0xe0 __x64_sys_write+0x19/0x20 do_syscall_64+0x61/0xb0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x20 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae WARNING: CPU: 0 PID: 18016 at /var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:4152 nv_set_system_power_state+0x2d0/0x3e0 [nvidia] nv_procfs_write_suspend+0xe9/0x140 [nvidia] proc_reg_write+0x5a/0x90 ? __cond_resched+0x1a/0x50 vfs_write+0xc3/0x250 ksys_write+0x67/0xe0 __x64_sys_write+0x19/0x20 do_syscall_64+0x61/0xb0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x20 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
BTW, the workaround from: https://forums.developer.nvidia.com/t/fixed- suspend-resume-issues-with-the-driver- version-470/187150/3?u=cirosantilli worked for me. I wouldn't expect that workaround to be affected by lightdm vs gdm3, but maybe it is: sudo systemctl stop nvidia-suspend.service sudo systemctl stop nvidia-hibernate.service sudo systemctl stop nvidia-resume.service sudo systemctl disable nvidia-suspend.service sudo systemctl disable nvidia-hibernate.service sudo systemctl disable nvidia-resume.service sudo mv /lib/systemd/system-sleep/nvidia ~/nvidia.bak -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup impish on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from impish-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in impish-proposed is as expected. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and now have a few tests failing on all architectures and systems as of Feb 4th 2022 it seems. Log with details is attached in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup focal on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from focal-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in focal-proposed is as expected. ** 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 nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] WCN685x hw2.1 takes additional/updated firmware for both WiFi and Bluetooth function. ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 [Fix] WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except for the directory path and a board-2.bin. For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from mainline are neccessary for Focal. Jammy has all of them already. For kernel, many of the prerequisite works have been committed for hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G will be turned off for the lack of userspace support, the only fix necessary is to correct read mask of version info register. ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14 in bug 1939528, so only oem-5.14 has to be reverted. [Test Case] WiFi and Bluetooth devices should be up and running, pass basic operations. $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai [Where problems could occur] At the time being, WCN685x WiFi 6G support will be turnef off deliberately due to the lack of full support in the userspace management tools. [Other Info] While this is a new hardware model from OEM program, it's only nominated for Focal oem-5.14 kernel and the coming LTS Jammy. == original bug report == ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Not sure if this was the main reason, but it seems the problem was fixed for me, when I switched the display manager from lightdm to gdm3. I'm using nvidia-driver-510 now and I have no problems with resuming after suspending anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Working on crypto module testcase.. ** Changed in: kunpeng920/ubuntu-20.04 Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Incomplete => In Progress ** Changed in: kunpeng920 Status: Incomplete => In Progress ** Changed in: kunpeng920 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
probably also related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-460/+bug/1911055 -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
Not sure if this was the main reason, but it seems the problem was fixed for me, when I switched the display manager from lightdm to gdm3. I'm using nvidia-driver-510 now and I have no problems with resuming after suspending anymore. -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
