[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
Installed 5.17.0-1009-oem unsigned kernel image on Ubuntu 22.04 and tested the fix. The fix works. My phone can connect to the wifi hotspot and browse the internet. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/jammy/+source/linux-oem-5.17/+bug/1969326/+attachment/5594782/+files/dmesg.txt -- 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/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
[Expired for linux-hwe-5.13 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => Expired -- 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/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Expired Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972140] Re: UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
Same problem with latest official 5.15.0-35-generic. I am willing to test any patched 5.15 kernel build that also includes the linux-headers package. Thanks for your efforts. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: Confirmed Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:br0.0:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about
[Kernel-packages] [Bug 1977628] [NEW] 2 USB ports have stopped working
Public bug reported: My Thinkpad X13 has 1 USB-C port that is usually used by the battery charger, and 2 USB ports. Sometime in the past 2-4 weeks, the 2 USB ports have stopped working. Nothing I plug into them causes any change in the output of `usb- devices`. It isn't a hardware fault because both ports are impacted, and one of them is seldom used. I am still able to use the USB-C port for data transfer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 3 18:10:52 2022 InstallationDate: Installed on 2021-09-23 (253 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977628 Title: 2 USB ports have stopped working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: My Thinkpad X13 has 1 USB-C port that is usually used by the battery charger, and 2 USB ports. Sometime in the past 2-4 weeks, the 2 USB ports have stopped working. Nothing I plug into them causes any change in the output of `usb- devices`. It isn't a hardware fault because both ports are impacted, and one of them is seldom used. I am still able to use the USB-C port for data transfer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 3 18:10:52 2022 InstallationDate: Installed on 2021-09-23 (253 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1977628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977622] Re: Bionic update: upstream stable patchset 2022-06-03
** 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-06-03 -upstream stable patchset 2022-06-03 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.277, v4.19.240 + + from git://git.kernel.org/ + + etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead + mm: page_alloc: fix building error on -Werror=array-compare + tracing: Dump stacktrace trigger to the corresponding instance + gfs2: assign rgrp glock before compute_bitstructs + ALSA: usb-audio: Clear MIDI port active flag after draining + tcp: fix race condition when creating child sockets from syncookies + tcp: Fix potential use-after-free due to double kfree() + dmaengine: imx-sdma: Fix error checking in sdma_event_remap + net/packet: fix packet_sock xmit return value checking + netlink: reset network and mac headers in netlink_dump() + ARM: vexpress/spc: Avoid negative array index when !SMP + platform/x86: samsung-laptop: Fix an unsigned comparison which can never be negative + ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant + vxlan: fix error return code in vxlan_fdb_append + cifs: Check the IOCB_DIRECT flag, not O_DIRECT + brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant + drm/msm/mdp5: check the return of kzalloc() + net: macb: Restart tx only if queue pointer is lagging + stat: fix inconsistency between struct stat and struct compat_stat + ata: pata_marvell: Check the 'bmdma_addr' beforing reading + dma: at_xdmac: fix a missing check on list iterator + powerpc/perf: Fix power9 event alternatives + openvswitch: fix OOB access in reserve_sfa_size() + ASoC: soc-dapm: fix two incorrect uses of list iterator + e1000e: Fix possible overflow in LTR decoding + ARC: entry: fix syscall_trace_exit argument + ext4: fix symlink file size not match to file content + ext4: fix overhead calculation to account for the reserved gdt blocks + ext4: force overhead calculation if the s_overhead_cluster makes no sense + staging: ion: Prevent incorrect reference counting behavour + block/compat_ioctl: fix range check in BLKGETSIZE + ax25: add refcount in ax25_dev to avoid UAF bugs + ax25: fix reference count leaks of ax25_dev + ax25: fix UAF bugs of net_device caused by rebinding operation + ax25: Fix refcount leaks caused by ax25_cb_del() + ax25: fix UAF bug in ax25_send_control() + ax25: fix NPD bug in ax25_disconnect + ax25: Fix NULL pointer dereferences in ax25 timers + ax25: Fix UAF bugs in ax25 timers + ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek + net/sched: cls_u32: fix possible leak in u32_init_knode() + drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised + drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare + UBUNTU: upstream stable to v4.14.277, v4.19.240 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977622 Title: Bionic update: upstream stable patchset 2022-06-03 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress 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-06-03 Ported from the following upstream stable releases: v4.14.277, v4.19.240 from git://git.kernel.org/ etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead mm: page_alloc: fix building error on -Werror=array-compare tracing: Dump
[Kernel-packages] [Bug 1977622] [NEW] Bionic update: upstream stable patchset 2022-06-03
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-06-03 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) 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 Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977622 Title: Bionic update: upstream stable patchset 2022-06-03 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress 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-06-03 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets
Need to revert this patch as it introduces a new issue for IPSec. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974096 Title: cls_flower: Fix inability to match GRE/IPIP packets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug When a packet of a new flow arrives in openvswitch kernel module, it dissects the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw- offload configuration is enabled, the daemon creates a new TC flower entry to bypass openvswitch kernel module for the flow (TC flower can also offload flows to NICs but this time that does not matter). In this processing flow, I found the following issue in cases of GRE/IPIP packets. When ovs_flow_key_extract() in openvswitch module parses a packet of a new GRE (or IPIP) flow received on non-tunneling vports, it extracts information of the outer IP header for ip_proto/src_ip/dst_ip match keys. This means ovs-vswitchd creates a TC flower entry with IP protocol/addresses match keys whose values are those of the outer IP header. OTOH, TC flower, which uses flow_dissector (different parser from openvswitch module), extracts information of the inner IP header. * How to test The following flow is an example to describe the issue in more detail. <--- Outer IP -> <-- Inner IP --> +--+--+--+--+--+--+ | ip_proto | src_ip | dst_ip | ip_proto | src_ip | dst_ip | | 47 (GRE) | 192.168.10.1 | 192.168.10.2 | 6 (TCP) | 10.0.0.1 | 10.0.0.2 | +--+--+--+--+--+--+ In this case, TC flower entry and extracted information are shown as below: - ovs-vswitchd creates TC flower entry with: - ip_proto: 47 - src_ip: 192.168.10.1 - dst_ip: 192.168.10.2 - TC flower extracts below for IP header matches: - ip_proto: 6 - src_ip: 10.0.0.1 - dst_ip: 10.0.0.2 Thus, GRE or IPIP packets never match the TC flower entry, as each dissector behaves differently. IMHO, the behavior of TC flower (flow dissector) does not look correct, as ip_proto/src_ip/dst_ip in TC flower match means the outermost IP header information except for GRE/IPIP cases. This patch adds a new flow_dissector flag FLOW_DISSECTOR_F_STOP_BEFORE_ENCAP which skips dissection of the encapsulated inner GRE/IPIP header in TC flower classifier. * What it could break. N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977620] [NEW] package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error
Public bug reported: Install failure after ubuntu upgrade to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 3 22:46:18 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2014-12-28 (2714 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1977620 Title: package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Install failure after ubuntu upgrade to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 3 22:46:18 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2014-12-28 (2714 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1977620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594744/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594746/+files/acpidump.txt ** Changed in: ubuntu-mate 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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594745/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594735/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594742/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594743/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594737/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594734/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594738/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594741/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594739/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594740/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594736/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594730/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594732/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594733/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594731/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/20/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977476] Re: powersave governor behaves diferently after resume from suspension
apport information ** Tags added: apport-collected ** Description changed: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. - Switching to other governor and go back to powersave make it to behave - normally again. + Switching to other governor and go back to powersave make it to behave normally again. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: daniel 1265 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-04-23 (41 days ago) + InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + IwConfig: + lono wireless extensions. + + eno1 no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. + Package: tlp + PackageArchitecture: amd64 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-33-generic N/A + linux-backports-modules-5.15.0-33-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 12/20/2012 + dmi.bios.release: 4.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F2 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Q77M-D2H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/20/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: To be filled by O.E.M. + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1977476/+attachment/5594729/+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/1977476 Title: powersave governor behaves diferently after resume from suspension Status in Ubuntu MATE: Confirmed Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mate-power-manager package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: powersave governor frequency and gets higher after resume from suspension, getting worse performance than ondemand governor with the computer on "idle state". powersave seems to lock on the smaller cpu frequency possible, so the fluctuation on frequency it's worng. ─nmjondemand governor doesn't seem to have the same problem, I didn't tested the others governors available. Switching to other governor and go back to powersave make it to behave normally again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1265 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: tlp PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=a3c6eef8-6149-4921-b407-7986d6fa7b10 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware
[Kernel-packages] [Bug 1977566] [NEW] package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-44-generic package post-installation script sub
Public bug reported: After restart the labtop the system raise an error alert. I've just upgrade system (sudo apt-get upgrade) using terminal due graphic assistant did not work. Audio in youtube doesn't work but using system test does. Video is working well. Thank you very much, ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 3 20:48:20 2022 ErrorMessage: installed linux-image-5.13.0-44-generic package post-installation script subprocess was interrupted InstallationDate: Installed on 2021-08-03 (304 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: linux-signed-hwe-5.13 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-44-generic package post-installation script subprocess was interrupted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977566 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-44-generic package post- installation script subprocess was interrupted Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After restart the labtop the system raise an error alert. I've just upgrade system (sudo apt-get upgrade) using terminal due graphic assistant did not work. Audio in youtube doesn't work but using system test does. Video is working well. Thank you very much, ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 3 20:48:20 2022 ErrorMessage: installed linux-image-5.13.0-44-generic package post-installation script subprocess was interrupted InstallationDate: Installed on 2021-08-03 (304 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: linux-signed-hwe-5.13 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-44-generic package post-installation script subprocess was interrupted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1977566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 406728] Favor!
Sorry to Bother, Do you order from Amazon? John Sonderegger json...@yahoo.com Propelled by Penguin Power -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/406728 Title: [Dell Inc. MM061] suspend/resume failure Status in linux package in Ubuntu: Fix Released Bug description: Intel architecture, Dell Inspiron 1505 (basically same as 6400) Suspend did not resume when I came back from a break. I didn't notice this though, so can't provide any more info. OS 9.10 alpha 3 ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 Date: Wed Jul 29 20:55:07 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=44a9b646-ba04-479b-a645-343f60e3f09b InterpreterPath: /usr/bin/python2.6 MachineType: Dell Inc. MM061 Package: linux-image-2.6.31-4-generic 2.6.31-4.23 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=c0d9e6e0-467c-4976-b439-8f7a70f783a4 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-4.23-generic RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A SourcePackage: linux Tags: resume suspend Title: [Dell Inc. MM061] suspend/resume failure Uname: Linux 2.6.31-4-generic i686 UserGroups: dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KD882 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 406728] Checking..
Sorry to Bother, Do you order from Amazon? John Sonderegger -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/406728 Title: [Dell Inc. MM061] suspend/resume failure Status in linux package in Ubuntu: Fix Released Bug description: Intel architecture, Dell Inspiron 1505 (basically same as 6400) Suspend did not resume when I came back from a break. I didn't notice this though, so can't provide any more info. OS 9.10 alpha 3 ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 Date: Wed Jul 29 20:55:07 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=44a9b646-ba04-479b-a645-343f60e3f09b InterpreterPath: /usr/bin/python2.6 MachineType: Dell Inc. MM061 Package: linux-image-2.6.31-4-generic 2.6.31-4.23 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=c0d9e6e0-467c-4976-b439-8f7a70f783a4 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-4.23-generic RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A SourcePackage: linux Tags: resume suspend Title: [Dell Inc. MM061] suspend/resume failure Uname: Linux 2.6.31-4-generic i686 UserGroups: dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KD882 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860934] Re: [nvidia] second monitor is not waking up automatically after boot and sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1860934 Title: [nvidia] second monitor is not waking up automatically after boot and sleep Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: primary screen : laptop screen secondary screen: Samsung Monitor secondary monitor is connected to laptop via HDMI port. secondary monitor won't wake up after a normal boot. secondary monitor will wake up after boot if switch to ctl+alt+f7 and then back to graphical. blacklisted `nouveau` drivers via an entry in /etc/modeprobe.d/ set the value for GRUB_CMDLINE_LINUX_DEFAULT to `""` (emprty string) and then ran `update-grub` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 07:33:52 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2020-01-25 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=77709762-71e2-437a-974a-8d580316705f ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/nvidia-graphics-drivers-435/+bug/1860934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860934] Re: [nvidia] second monitor is not waking up automatically after boot and sleep
My internal display doesn't wake up after sleep on 22.04. There was a bug report but I can't see it any longer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1860934 Title: [nvidia] second monitor is not waking up automatically after boot and sleep Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: primary screen : laptop screen secondary screen: Samsung Monitor secondary monitor is connected to laptop via HDMI port. secondary monitor won't wake up after a normal boot. secondary monitor will wake up after boot if switch to ctl+alt+f7 and then back to graphical. blacklisted `nouveau` drivers via an entry in /etc/modeprobe.d/ set the value for GRUB_CMDLINE_LINUX_DEFAULT to `""` (emprty string) and then ran `update-grub` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 07:33:52 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2020-01-25 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=77709762-71e2-437a-974a-8d580316705f ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/nvidia-graphics-drivers-435/+bug/1860934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1063.97)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1063.97) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/unknown (arm64) nvidia-graphics-drivers-390/390.151-0ubuntu0.20.04.1 (armhf) 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-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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 1976116] Re: Focal update: v5.4.191 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1976116 Title: Focal update: v5.4.191 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux 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: v5.4.191 upstream stable release from git://git.kernel.org/ etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead mm: page_alloc: fix building error on -Werror=array-compare tracing: Dump stacktrace trigger to the corresponding instance gfs2: assign rgrp glock before compute_bitstructs tcp: fix race condition when creating child sockets from syncookies tcp: Fix potential use-after-free due to double kfree() ALSA: usb-audio: Clear MIDI port active flag after draining ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek ASoC: msm8916-wcd-digital: Check failure for devm_snd_soc_register_component dmaengine: imx-sdma: Fix error checking in sdma_event_remap dmaengine: mediatek:Fix PM usage reference leak of mtk_uart_apdma_alloc_chan_resources igc: Fix infinite loop in release_swfw_sync igc: Fix BUG: scheduling while atomic rxrpc: Restore removed timer deletion net/smc: Fix sock leak when release after smc_shutdown() net/packet: fix packet_sock xmit return value checking net/sched: cls_u32: fix possible leak in u32_init_knode() l3mdev: l3mdev_master_upper_ifindex_by_index_rcu should be using netdev_master_upper_dev_get_rcu netlink: reset network and mac headers in netlink_dump() selftests: mlxsw: vxlan_flooding: Prevent flooding of unwanted packets ARM: vexpress/spc: Avoid negative array index when !SMP reset: tegra-bpmp: Restore Handle errors in BPMP response platform/x86: samsung-laptop: Fix an unsigned comparison which can never be negative ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant vxlan: fix error return code in vxlan_fdb_append cifs: Check the IOCB_DIRECT flag, not O_DIRECT mt76: Fix undefined behavior due to shift overflowing the constant brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant dpaa_eth: Fix missing of_node_put in dpaa_get_ts_info() drm/msm/mdp5: check the return of kzalloc() net: macb: Restart tx only if queue pointer is lagging scsi: qedi: Fix failed disconnect handling stat: fix inconsistency between struct stat and struct compat_stat EDAC/synopsys: Read the error count from the correct register oom_kill.c: futex: delay the OOM reaper to allow time for proper futex cleanup ata: pata_marvell: Check the 'bmdma_addr' beforing reading dma: at_xdmac: fix a missing check on list iterator drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare KVM: PPC: Fix TCE handling for VFIO drm/vc4: Use pm_runtime_resume_and_get to fix pm_runtime_get_sync() usage powerpc/perf: Fix power9 event alternatives xtensa: patch_text: Fixup last cpu should be master xtensa: fix a7 clobbering in coprocessor context load/store openvswitch: fix OOB access in reserve_sfa_size() ASoC: soc-dapm: fix two incorrect uses of list iterator e1000e: Fix possible overflow in LTR decoding ARC: entry: fix syscall_trace_exit argument arm_pmu: Validate single/group leader events ext4: fix symlink file size not match to file content ext4: fix use-after-free in ext4_search_dir ext4, doc: fix incorrect h_reserved size ext4: fix overhead calculation to account for the reserved gdt blocks ext4: force overhead calculation if the s_overhead_cluster makes no sense jbd2: fix a potential race while discarding reserved buffers after an abort spi: atmel-quadspi: Fix the buswidth adjustment between spi-mem and controller staging: ion: Prevent incorrect reference counting behavour block/compat_ioctl: fix range check in BLKGETSIZE Linux 5.4.191 UBUNTU: upstream stable to v5.4.191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977526] Re: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point
*** This bug is a duplicate of bug 1958267 *** https://bugs.launchpad.net/bugs/1958267 In fact a duplicate, sorry for the noise ** This bug has been marked a duplicate of bug 1958267 wpa can't connect to servers using TLS 1.1 or older -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977526 Title: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point Status in linux package in Ubuntu: Confirmed Bug description: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101 status=12 aid=0) [ 322.913208] wlan0: 34:62:88:c9:44:8e denied association (code=12) [ 333.076375] wlan0: authenticate with 34:62:88:c9:44:8e [ 333.076416] wlan0: bad VHT capabilities, disabling VHT [ 333.076421] wlan0: Invalid HE elem, Disable HE [ 333.080260] wlan0: send auth to 34:62:88:c9:44:8e (try 1/3) [ 333.110076] wlan0: authenticated [ 333.110537] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 333.114179] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 333.117425] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x111 status=0 aid=3) [ 333.126642] wlan0: associated [ 333.152883] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 34:62:88:c9:44:8e [ 348.360075] wlan0: deauthenticating from 34:62:88:c9:44:8e by local choice (Reason: 3=DEAUTH_LEAVING) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.35.38 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1592 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 3 15:54:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (838 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eth0 no wireless extensions. wlan0 no wireless extensions. MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-35-generic N/A linux-backports-modules-5.15.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
@kaihengfeng, the first test with unloading a limited amount of modules (due to rmmod -f limitations) did not result in 0% battery drain. So the next step would be a modified kernel that allows unloading all modules (see #56). Do you maybe have another suggestion of how to find out which module needs to be removed just before shutdown to avoid the battery drain? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
How can I test the fix? -- 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/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1063.64)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1063.64) for bionic have finished running. The following regressions have been reported in tests triggered by the package: bbswitch/0.8-4ubuntu1 (arm64) acpi-call/1.1.0-4 (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/bionic/update_excuses.html#linux-meta-raspi-5.4 [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 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable
as no activity for quite some time (same in the external bug), mark incomplete in oem-priority ** Changed in: oem-priority 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/1883065 Title: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable Status in OEM Priority Project: Incomplete Status in intel-microcode package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Already present reported in project *dell-sputnik*. (Note, it happened here also without suspend/resume.): 1. https://bugs.launchpad.net/dell-sputnik/+bug/1661741 2. Quote from https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26: > A similar bug affects several Dell laptop models: > - Dell 5480/5488 : > https://bugs.launchpad.net/dell-sputnik/+bug/1866343 > - Dell E5470 : > https://bugs.launchpad.net/dell-sputnik/+bug/1661741 > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 is not fixed; it has been changed, by error, to fixed. Please, it will be nice if somebody can change the status to "confirmed") > - Dell 7740 : > https://bugs.launchpad.net/dell-sputnik/+bug/1871491 > > I suppose that the bug can also affect Dell precision 7730 After experiencing this already on the Dell Latitude 5480/5488 (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen this now too with the Dell Precision 3540 (with dedicated AMD graphics card). Without the power cord plugged in, the system started fine, then updating packages, including the Linux kernel, turning the system off, and right back on, it went to GRUB, and GRUB was able to load Linux and initrd, and starting Linux it hung. Num lock key didn’t respond (but also didn’t blink – no idea if this should work), and Ctrl + Alt + Del didn’t work either. So, the system had to be powered off by pressing the power button for some (ten(?)) seconds. Subsequent tries didn’t help, until we remembered the issues with the other device, and plugging in the power cord fixed it. With the power cable unplugged, it didn’t boot. The state of the connected power cable only mattered, when starting the Linux kernel. That means, plugging it in, when GRUB was active, the system booted. Removing the cable, when GRUB was running, Linux hung. I tried to get Linux messages, but `debug nomodeset earlyprintk=efi` didn’t get Linux to output any messages. ### Workarounds ### I was able to get Linux booting by adding either one of the following Linux kernel parameters. 1. `maxcpus=1` (once it started with `maxcpus=2`) 2. `nosmp` 2. `acpi=off` 3. `nolapic` In this state, there was only one CPU online. Trying to bring one more online, the system always froze instantly. echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to bring a third CPU online, but the system froze when trying the fourth.) ### Reproducibilty ### Letting the system sit over night, and trying again in the morning, unfortunately, we did *not* test without a power cable plugged in, as we had an idea to test the non-USB-Type-C power cable. With that the system started. Powering the system off, and unplugging the cable, the system booted without issues. So something changed. We weren’t able to get it into a state, where it doesn’t boot in the last hour, but we would like this investigated, as we are giving these systems to our users. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1883065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977526] 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/1977526 Title: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point Status in linux package in Ubuntu: Confirmed Bug description: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101 status=12 aid=0) [ 322.913208] wlan0: 34:62:88:c9:44:8e denied association (code=12) [ 333.076375] wlan0: authenticate with 34:62:88:c9:44:8e [ 333.076416] wlan0: bad VHT capabilities, disabling VHT [ 333.076421] wlan0: Invalid HE elem, Disable HE [ 333.080260] wlan0: send auth to 34:62:88:c9:44:8e (try 1/3) [ 333.110076] wlan0: authenticated [ 333.110537] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 333.114179] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 333.117425] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x111 status=0 aid=3) [ 333.126642] wlan0: associated [ 333.152883] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 34:62:88:c9:44:8e [ 348.360075] wlan0: deauthenticating from 34:62:88:c9:44:8e by local choice (Reason: 3=DEAUTH_LEAVING) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.35.38 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1592 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 3 15:54:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (838 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eth0 no wireless extensions. wlan0 no wireless extensions. MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-35-generic N/A linux-backports-modules-5.15.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977526] [NEW] Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point
Public bug reported: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101 status=12 aid=0) [ 322.913208] wlan0: 34:62:88:c9:44:8e denied association (code=12) [ 333.076375] wlan0: authenticate with 34:62:88:c9:44:8e [ 333.076416] wlan0: bad VHT capabilities, disabling VHT [ 333.076421] wlan0: Invalid HE elem, Disable HE [ 333.080260] wlan0: send auth to 34:62:88:c9:44:8e (try 1/3) [ 333.110076] wlan0: authenticated [ 333.110537] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 333.114179] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 333.117425] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x111 status=0 aid=3) [ 333.126642] wlan0: associated [ 333.152883] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 34:62:88:c9:44:8e [ 348.360075] wlan0: deauthenticating from 34:62:88:c9:44:8e by local choice (Reason: 3=DEAUTH_LEAVING) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.35.38 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1592 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 3 15:54:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (838 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eth0 no wireless extensions. wlan0 no wireless extensions. MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-35-generic N/A linux-backports-modules-5.15.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977526 Title: Regression: upgrade to ubuntu 22.04 broke wifi access to infrastructure access point Status in linux package in Ubuntu: Confirmed Bug description: Today I have updated from 20.04 to 22.04. Now it is impossible to connect to ALMAWIFI that is my university wifi network. Being this part of EDUROAM, I strongly suspect that EDUROAM has been broken as well. The system seems to be able to connect to regular wifi networks, such as my mobile phone hotspot. However the connection to this site using WPA2 enterprise, PEAP and MSCHAP2 has now become impossible. The network manager applet keeps asking for the network password without being able to establish a connection. On the dmesg log I see: send auth to 34:62:88:c9:44:8e (try 1/3) [ 322.806267] wlan0: authenticated [ 322.806853] wlan0: VHT capa missing/short, disabling VHT/HE/EHT [ 322.807003] wlan0: associate with 34:62:88:c9:44:8e (try 1/3) [ 322.911089] wlan0: associate with 34:62:88:c9:44:8e (try 2/3) [ 322.913192] wlan0: RX AssocResp from 34:62:88:c9:44:8e (capab=0x101
[Kernel-packages] [Bug 1977510] Re: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977510 Title: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977510] [NEW] [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set
Public bug reported: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198452 severity-medium targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-198452 severity-medium targetmilestone-inin2004 ** 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/1977510 Title: [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set Status in linux package in Ubuntu: New Bug description: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
I am also affected by this issue. Thinkpad X260 / Ubuntu 22.04. Previous versions were working fine. On 22.04, kernel 5.13 did not have the issue but the Wifi was not working. Is there anything I could do to help diagnose the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977510] [NEW] [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set
You have been subscribed to a public bug: Description: hypfs: fix listing z/VM guests with access control group set Symptom: hypfs/hyptop info doesn't include z/VM guests with access control group set Problem: Currently if z/VM guest is allowed to retrieve hypervisor performance data globally for all guests (privilege class B) the query is formed in a way to include all guests but the group name is left empty. This leads to that z/VM guests which have access control group set not being included in the results (even local vm). Solution: Change the query group identifier from empty to "any" to retrieve information about all guests from any groups (or without a group set). Reproduction: Run hyptop under z/VM from a guest with privilege class B and some guest(s) with RACF/ACI groups set. Upstream-ID: 663d34c8df98740f1e90241e78e456d00b3c6cad Master-BZ ID: 196350 Distros: Ubuntu 20.04 Preventive:yes ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198452 severity-medium targetmilestone-inin2004 -- [UBUNTU 20.04] hypfs: fix listing z/VM guests with access control group set https://bugs.launchpad.net/bugs/1977510 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 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Going to wontfix for bionic since there doesn't seem to be a need for it at this point ** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Won't Fix -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Won't Fix Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977508] Re: [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev
** 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 => Medium ** Changed in: ubuntu-z-systems 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/1977508 Title: [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Description: zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Symptom: With non-NPIV FCP devices, failed recovery on gone remote port. As follow-on error, failed paths after storage target NPIV failover with IBM FCP storage based on Spectrum Virtualize such as FlashSystem 9200, V7000, SAN Volume Controller, etc. Problem: Suppose we have an environment with a number of non-NPIV FCP devices (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical FCP channel (HBA port) and its I_T nexus. Plus a number of storage target ports zoned to such shared channel. Now one target port logs out of the fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port recovery depending on the ADISC result. This happens on all such FCP devices (in different Linux images) concurrently as they all receive a copy of this RSCN. In the following we look at one of those FCP devices. Requests other than FSF_QTCB_FCP_CMND can be slow until they get a response. Depending on which requests are affected by slow responses, there are different recovery outcomes. Solution: Here we want to fix failed recoveries on port or adapter level by avoiding recovery requests that can be slow. We need the cached N_Port_ID for the remote port "link" test with ADISC. Just before sending the ADISC, we now intentionally forget the old cached N_Port_ID. The idea is that on receiving an RSCN for a port, we have to assume that any cached information about this port is stale. This forces a fresh new GID_PN [FC-GS] nameserver lookup on any subsequent recovery for the same port. Since we typically can still communicate with the nameserver efficiently, we now reach steady state quicker: Either the nameserver still does not know about the port so we stop recovery, or the nameserver already knows the port potentially with a new N_Port_ID and we can successfully and quickly perform open port recovery. For the one case, where ADISC returns successfully, we re-initialize port->d_id because that case does not involve any port recovery. This also solves a problem if the storage WWPN quickly logs into the fabric again but with a different N_Port_ID. Such as on virtual WWPN takeover during target NPIV failover. [https://www.redbooks.ibm.com/abstracts/redp5477.html] In that case the RSCN from the storage FDISC was ignored by zfcp and we could not successfully recover the failover. On some later failback on the storage, we could have been lucky if the virtual WWPN got the same old N_Port_ID from the SAN switch as we still had cached. Then the related RSCN triggered a successful port reopen recovery. However, there is no guarantee to get the same N_Port_ID on NPIV FDISC. Even though NPIV-enabled FCP devices are not affected by this problem, this code change optimizes recovery time for gone remote ports as a side effect. The timely drop of cached N_Port_IDs prevents unnecessary slow open port attempts. Reproduction: With a sufficiently shared FCP channel with non-NPIV FCP devs, perform SAN switch port disable on the storage side, or trigger storage target NPIV failover such as with Spectrum Virtualize CLI command "stopsystem -node 2". Upstream-ID: 8c9db6679be4348b8aae108e11d4be2f83976e30 Master-BZ-ID: 196197 Distros: Ubuntu 20.04 Ubuntu 21.10 Ubuntu 22.04 Author: Component: kernel To manage notifications about this bug go to:
[Kernel-packages] [Bug 1973835] Re: Ubuntu 22.04, Bluetooth issues
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** No longer affects: snappy-hwe-snaps -- 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/1973835 Title: Ubuntu 22.04, Bluetooth issues Status in bluez package in Ubuntu: New Bug description: 0 I installed Ubuntu 22.04 and the Bluetooth was working fine. I turned off the bluetooth and could not turn it back on. I did some research and found some calls to turn it back on: sudo rfkill unblock all sudo hciconfig hci0 down sudo rmmod btusb sudo modprobe btusb sudo hciconfig hci0 up Now, I can turn it on and off as I please but It is now not connecting to any device. It would connect for a brief second and then disconnect. Can't find anything from research. Anyone can help with this ? Also, Whenever I boot up windows, the bluetooth works perfectly fine on windows. So it's not an hardware issue. I ran the command: bluetoothctl and the bluetooth is cycling through connecting to the device and disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977508] [NEW] [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev
Public bug reported: Description: zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Symptom: With non-NPIV FCP devices, failed recovery on gone remote port. As follow-on error, failed paths after storage target NPIV failover with IBM FCP storage based on Spectrum Virtualize such as FlashSystem 9200, V7000, SAN Volume Controller, etc. Problem: Suppose we have an environment with a number of non-NPIV FCP devices (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical FCP channel (HBA port) and its I_T nexus. Plus a number of storage target ports zoned to such shared channel. Now one target port logs out of the fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port recovery depending on the ADISC result. This happens on all such FCP devices (in different Linux images) concurrently as they all receive a copy of this RSCN. In the following we look at one of those FCP devices. Requests other than FSF_QTCB_FCP_CMND can be slow until they get a response. Depending on which requests are affected by slow responses, there are different recovery outcomes. Solution: Here we want to fix failed recoveries on port or adapter level by avoiding recovery requests that can be slow. We need the cached N_Port_ID for the remote port "link" test with ADISC. Just before sending the ADISC, we now intentionally forget the old cached N_Port_ID. The idea is that on receiving an RSCN for a port, we have to assume that any cached information about this port is stale. This forces a fresh new GID_PN [FC-GS] nameserver lookup on any subsequent recovery for the same port. Since we typically can still communicate with the nameserver efficiently, we now reach steady state quicker: Either the nameserver still does not know about the port so we stop recovery, or the nameserver already knows the port potentially with a new N_Port_ID and we can successfully and quickly perform open port recovery. For the one case, where ADISC returns successfully, we re-initialize port->d_id because that case does not involve any port recovery. This also solves a problem if the storage WWPN quickly logs into the fabric again but with a different N_Port_ID. Such as on virtual WWPN takeover during target NPIV failover. [https://www.redbooks.ibm.com/abstracts/redp5477.html] In that case the RSCN from the storage FDISC was ignored by zfcp and we could not successfully recover the failover. On some later failback on the storage, we could have been lucky if the virtual WWPN got the same old N_Port_ID from the SAN switch as we still had cached. Then the related RSCN triggered a successful port reopen recovery. However, there is no guarantee to get the same N_Port_ID on NPIV FDISC. Even though NPIV-enabled FCP devices are not affected by this problem, this code change optimizes recovery time for gone remote ports as a side effect. The timely drop of cached N_Port_IDs prevents unnecessary slow open port attempts. Reproduction: With a sufficiently shared FCP channel with non-NPIV FCP devs, perform SAN switch port disable on the storage side, or trigger storage target NPIV failover such as with Spectrum Virtualize CLI command "stopsystem -node 2". Upstream-ID: 8c9db6679be4348b8aae108e11d4be2f83976e30 Master-BZ-ID: 196197 Distros: Ubuntu 20.04 Ubuntu 21.10 Ubuntu 22.04 Author: Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198451 severity-medium targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-198451 severity-medium targetmilestone-inin--- ** 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/1977508 Title: [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Status in linux package in Ubuntu: New Bug description: Description: zfcp: fix failed recovery on gone remote port,
[Kernel-packages] [Bug 1977508] [NEW] [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev
You have been subscribed to a public bug: Description: zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev Symptom: With non-NPIV FCP devices, failed recovery on gone remote port. As follow-on error, failed paths after storage target NPIV failover with IBM FCP storage based on Spectrum Virtualize such as FlashSystem 9200, V7000, SAN Volume Controller, etc. Problem: Suppose we have an environment with a number of non-NPIV FCP devices (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical FCP channel (HBA port) and its I_T nexus. Plus a number of storage target ports zoned to such shared channel. Now one target port logs out of the fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port recovery depending on the ADISC result. This happens on all such FCP devices (in different Linux images) concurrently as they all receive a copy of this RSCN. In the following we look at one of those FCP devices. Requests other than FSF_QTCB_FCP_CMND can be slow until they get a response. Depending on which requests are affected by slow responses, there are different recovery outcomes. Solution: Here we want to fix failed recoveries on port or adapter level by avoiding recovery requests that can be slow. We need the cached N_Port_ID for the remote port "link" test with ADISC. Just before sending the ADISC, we now intentionally forget the old cached N_Port_ID. The idea is that on receiving an RSCN for a port, we have to assume that any cached information about this port is stale. This forces a fresh new GID_PN [FC-GS] nameserver lookup on any subsequent recovery for the same port. Since we typically can still communicate with the nameserver efficiently, we now reach steady state quicker: Either the nameserver still does not know about the port so we stop recovery, or the nameserver already knows the port potentially with a new N_Port_ID and we can successfully and quickly perform open port recovery. For the one case, where ADISC returns successfully, we re-initialize port->d_id because that case does not involve any port recovery. This also solves a problem if the storage WWPN quickly logs into the fabric again but with a different N_Port_ID. Such as on virtual WWPN takeover during target NPIV failover. [https://www.redbooks.ibm.com/abstracts/redp5477.html] In that case the RSCN from the storage FDISC was ignored by zfcp and we could not successfully recover the failover. On some later failback on the storage, we could have been lucky if the virtual WWPN got the same old N_Port_ID from the SAN switch as we still had cached. Then the related RSCN triggered a successful port reopen recovery. However, there is no guarantee to get the same N_Port_ID on NPIV FDISC. Even though NPIV-enabled FCP devices are not affected by this problem, this code change optimizes recovery time for gone remote ports as a side effect. The timely drop of cached N_Port_IDs prevents unnecessary slow open port attempts. Reproduction: With a sufficiently shared FCP channel with non-NPIV FCP devs, perform SAN switch port disable on the storage side, or trigger storage target NPIV failover such as with Spectrum Virtualize CLI command "stopsystem -node 2". Upstream-ID: 8c9db6679be4348b8aae108e11d4be2f83976e30 Master-BZ-ID: 196197 Distros: Ubuntu 20.04 Ubuntu 21.10 Ubuntu 22.04 Author: Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198451 severity-medium targetmilestone-inin--- -- [UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV FCP dev https://bugs.launchpad.net/bugs/1977508 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 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Focal: 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] * The kernel crashed under load with a null pointer issue in nfs code: [556585.270959] Krnl Code:#: illegal >0002: illegal 0004: illegal 0006: illegal 0008: illegal 000a: illegal 000c: illegal 000e: illegal [556585.270967] Call Trace: [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc]) [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs] [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs] [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs] [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0 [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0 [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0 [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8 * Several dumps were generated and shared with Canonical. * Analysis (done by kernel and SEG) point to refcount leaks fixed, that are already fixed in the following commit/fix: [Fix] * ca05cbae2a0468e5d78e9b4605936a8bf5da328b ca05cbae2a04 "NFS: Fix up nfs_ctx_key_to_expire()" [Test Case] * There is unfortunately no reproducer or trigger available for this issue. * It just happens now and then under higher load. * Patched test kernels (focal 5.4 and bionic 5.4-hwe) were created and ran for more than a week in a special staging environment (at IBM) without further crashes. * Hence the test and verification will be done by the IBM Z team. [Where problems could occur] * The inode handling can become broken, in case the changes on the pointers are erroneous. * Problems with the authentication and/or the credentials could occur due to the modifications in put_rpccred, rpc_cred and rpc_auth. * The expiration of the cached credentials could be harmed as well, due to the changes in nfs_ctx_key_to_expire. * The different pointer arithmetic may cause further issues - wrong or null pointer references. * Positive is that the original commit was brought upstream by nfs experts. * A patched test kernel sustained day long runs under load in a staging and test environment. * The author of the upstream commit/patch is well known in the NFS area. [Other] * The Salesforce Case Number 00334334 is associated with this bug. * Commit ca05cbae2a04 was upstream accepted with 5.16-rc1. * But commit ca05cbae2a04 was unfortunately not tagged as stable, hence it was not picked automatically. * Since kinetic's (22.10) target kernel is 5.18, it will have the patch included, hence no dedicated PATCH request for kinetic. __ State the component where the Bug is occurring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this
[Kernel-packages] [Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- 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/1971417 Title: Fix REG_WAIT timeout for Yellow Carp Status in HWE Next: New Status in linux package in Ubuntu: Invalid 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: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] During hotplug built-in hdmi, the error message show up. #REG_WAIT timeout for yellow Carp [Fix] This tends to take miliseconds in certain scenarios and we'd rather not wait that long. Due to how this interacts with det size update and locking waiting should not be necessary as compbuf updates before unlock. Add a watch for config error instead as that is something we actually do care about. [Test Case] 1. Plug and unplug hdmi 2. cant get the error message in dmesg. [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Bug description: [Impact] The patch that we have recently re-introduced to properly support overlayfs on top of shiftfs can introduce potential kernel panics, for example: BUG: kernel NULL pointer dereference, address: 0008 [ 447.039738] #PF: supervisor read access in kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972899] Re: [Regression] Real-time Kernel Build Failure
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1972899
Title:
[Regression] Real-time Kernel Build Failure
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Committed
Bug description:
[SRU Justification]
A new commit in the Jammy 5.15.0-29.30 kernel is causing a build failure for
the real-time kernel.
After a bisect, I found this commit is causing the real-time kernel build
failure:
dc66c1b8a2be1 ("x86/pkru: Remove useless include")
Commit dc66c1b8a2be1 was added in 5.16-rc1 and not cc'd to stable. It
was picked into Jammy to enable AMX support. See bug 1967750.
The following commit resolves this regression by fixing up the includes:
35fa745286ac4 ("x86/mm: Include spinlock_t definition in pgtable")
Commit 35fa745286ac4 was merged into mainline 5.17-rc1.
[Fix]
35fa745286ac4 ("x86/mm: Include spinlock_t definition in pgtable")
[Test case]
Kernel builds are now working after picking this commit.
[Regression potential]
Low. The new commit is just including a header file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972899/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974017 Title: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: 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] * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel command line), the shadow page table code will produce too many entries in the shadow code. * The below mentioned upstream fix will prevent the entries from being piled up, by checking for existing entries at insert time. * This measurably reduces the list length and is faster than traversing the list at shutdown time only. [Fix] * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead" [Test Plan] * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed. * Ubuntu focal, impish or jammy needs to be installed and the Ubuntu LPAR setup as (1st level) KVM host, allowing nested virtualization. * Now setup one (or more) KVM virtual machines, with similar Ubuntu releases, and define one or more of them again as (2nd level) KVM host. * Define several KVM virtual machines on this (2nd level) KVM host in a memory constraint fashion, so that a lot of memory mapping is caused. * Let such a system run for a while under load. * Now shutdown one (or more) 2nd level VMs and notice the time it takes. * With the patch in place this time should be considerably quicker than without. * The result is reduced mapping (gmap_rmap) overhead, less danger of leaking memory and a better responding system. [Where problems could occur] * In case wrong entries are freed up this will harm the virtual memory management and may even lead to crashes. * In case the pointer handling is not done properly, again crashes may occur. * But with net just five new lines the patch is pretty short, readable and the modifications traceable in arch/s390/mm/gmap.c only. * The changes are limited to s390/mm only, hence don't affect other architectures. [Other Info] * The commit was upstream accepted in v5.18-rc6. * Since the planned target kernel for kinetic is 5.19, the kinetic kernel does not need to be patched. * Hence the SRUs are for jammy, impish and focal. __ KVM nesting support consumes too much memory When running KVM with nesting support (kvm.nested=1 on the kernel command line) the shadow page table code will produce too many entries in the shadow code. There is an upstream fix that will prevent the majority of the problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61 The fix is needed for 20.04 and 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974111] Re: Mute/mic LEDs no function on Elitebook 630
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- 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/1974111 Title: Mute/mic LEDs no function on Elitebook 630 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Invalid 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: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 630 G9 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- 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/1975798 Title: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH. But actually it's not there. [Fix] Read reg of sensor discovery. [Test] Verified on hardware, it show failure and driver returned. [Where problems could occur] Low risk, it may break AMD SFH driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1975798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974433] Re: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974433 Title: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: 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] * This is a hardware enablement SRU * and adds support for (new) IBM z16 counters * by exporting the extended counter set counters of the IBM z16 via sysfs. [Fix] * c9311de71635 c9311de71635d3eaa158df8516b9b99a92d60a0c "s390/cpumf: add new extended counter set for IBM z16" [Test Case] * Prepare an IBM z16 LPAR with Ubuntu 20.04, 21.10 or 22.04 (incl. this patch). * At LPARs activation profile, navigate to the Security page and within the counter facility options, select each counter set you want to use. (One may just select all for testing purposes.) * Use 'perf list' to determine if the new counters are listed. For comparing the new counters see: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git\ /commit/?id=c9311de71635d3eaa158df8516b9b99a92d60a0c * Use 'perf stat -e' to enable and make use of these counters. [What can go wrong] * Only new code is added by this commit - none is changed nor removed. * The new code may have syntactical errors, which would become visible during a test compile. * Initialization of the new struct cpumcf_z16_pmu_event_attr could be wrong. * The hex code for the counters could be wrong or mixed up, or the names might be wrong or mixed up, in which case one will get wrong or unexpected results. * The expansion of the case statement to determine the correct (z16) hardware might be wrong, using wrong case hex numbers. Which would lead to potentially counters, that may not match to the underlying hardware. [ Other info] * The commit will be upstream accepted with 5.18. (It's was brought upstream 'next-20220517'.) * Since the planned target kernel for kinetic is 5.19, this will be included. * Hence the SRU is for Focal, Impish and Jammy only. __ For IBM z16 machine the extended counter set needs to be exported by the PMU device driver CPU MF. The upstream commit from linux-next is commit-id: c9311de71635 s390/cpumf: add new extended counter set for IBM z16 The same patch will be imported into linux repo in the next merge window. Required patches are attached. They apply cleanly and compile without errors on focal (20.04) and jammy (22.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU
This bug is awaiting verification that the linux/5.15.0-36.37 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-jammy
--
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/1975804
Title:
[SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
AMD A+A GPU
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
New
Status in linux-oem-5.14 source package in Focal:
New
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[Impact]
System may hang after s2idle on AMD A+A GPU config due to the following
commits:
8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
for reset in S3") https://bugs.launchpad.net/bugs/1968475
a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371
[Fix]
Revert one commit and don't reset dGPU when s2idle
[Test]
Verified on AMD RMB, stress s2idle passed.
[Where problems could occur]
Low risk, it may break s2idle on AMD platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1975804/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
** Package changed: linux (Ubuntu) => pam (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977493 Title: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam- modules Status in Ubuntu on IBM z Systems: New Status in pam package in Ubuntu: New Bug description: ---Problem Description--- Upgrade from Ubuntu 21.10 to 22.4 fails I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com ---uname output--- Linux tuxmaker 5.13.0-44-generic #49-Ubuntu SMP Wed May 18 13:30:03 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = z15, 8561-701 ---boot type--- upgade ---Kernel cmdline used to launch install--- do-release-upgrade ---Install repository type--- Internet repository ---Install repository Location--- http://ports.ubuntu.com:80/ ---Point of failure--- Other failure during installation (stage 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976613] Re: Enable Asus USB-BT500 Bluetooth dongle(0b05:190e)
** Tags added: kern-3468 -- 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/1976613 Title: Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-firmware source package in Focal: In Progress Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1976613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977493] apt log
Default Comment by Bridge ** Attachment added: "apt log" https://bugs.launchpad.net/bugs/1977493/+attachment/5594578/+files/term.log ** 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/1977493 Title: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam- modules Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Upgrade from Ubuntu 21.10 to 22.4 fails I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com ---uname output--- Linux tuxmaker 5.13.0-44-generic #49-Ubuntu SMP Wed May 18 13:30:03 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = z15, 8561-701 ---boot type--- upgade ---Kernel cmdline used to launch install--- do-release-upgrade ---Install repository type--- Internet repository ---Install repository Location--- http://ports.ubuntu.com:80/ ---Point of failure--- Other failure during installation (stage 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977493] [NEW] Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
You have been subscribed to a public bug: ---Problem Description--- Upgrade from Ubuntu 21.10 to 22.4 fails I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com ---uname output--- Linux tuxmaker 5.13.0-44-generic #49-Ubuntu SMP Wed May 18 13:30:03 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = z15, 8561-701 ---boot type--- upgade ---Kernel cmdline used to launch install--- do-release-upgrade ---Install repository type--- Internet repository ---Install repository Location--- http://ports.ubuntu.com:80/ ---Point of failure--- Other failure during installation (stage 1) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198429 severity-high targetmilestone-inin2110 -- Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules https://bugs.launchpad.net/bugs/1977493 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 1957094] Re: on-demand mode doesn't work with nvidia-390
** Changed in: oem-priority Status: New => 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released 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 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1890130
Title:
Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
Status in HWE Next:
New
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-firmware source package in Hirsute:
Invalid
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification: linux-firmware]
[Impact]
To support new Intel Typhoon Peak Bluetooth, USB ID 8087:0032
specifically.
[Fix]
Kernel driver patchset
https://patchwork.kernel.org/project/bluetooth/list/?series=387475
targeting v5.11, as well as firmware intel/ibt-0041-0041.{ddc,sfi} from
linux-firmware commit 5cbf459c1ed9 and 7eb7fda50e9a.
[Test Case]
1. Install aforementioned firmware blobs and boot with kernel built with
these patches applied.
2. Run `btmgmt info` to find out if bluetooth controller is now
available.
[Where problems could occur]
Typhoon Peak is a whole new generation that it has its own call path to
load firmware, initial setup, etc. These patches are almost completely
isolated from previous generation, so little regression risk introduced.
== Original Bug Description ==
Device from /sys/kernel/debug/usb/devices:
T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=0032 Rev= 0.00
Prerequisite commits:
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3e4e3f73b9f4
And:
https://patchwork.kernel.org/project/bluetooth/list/?series=387475
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 2507 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-charmander+X68
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-11-09 (25 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. Latitude 5520
Package: linux
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-2005-oem
root=UUID=0ece6279-6ac8-4155-8542-c7a41c97f7d4 ro i915.enable_psr=1
ProcVersionSignature: Ubuntu
5.10.0-2005.6+lp1902848.lp1890130.4.ax210.iwlwifi.bluetooth-oem 5.10.0-rc5
RelatedPackageVersions:
linux-restricted-modules-5.10.0-2005-oem N/A
linux-backports-modules-5.10.0-2005-oem N/A
linux-firmware 1.187.3
Tags: focal
Uname: Linux 5.10.0-2005-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/19/2020
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.77
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: 2345678
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.77:bd10/19/2020:br0.4:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5520
dmi.product.sku: 0A21
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890130/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1912676 Title: Fix regression introduced by codec PM change Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] After the codec PM optimization, laptops with SOF may take very long to suspend. In addition to that, HDA may not be able to be runtim suspended again after resume from hibernation. [Fix] Prevent the SOF driver touches codec during system suspend, and properly refcount the PM usage counter. [Test] On an affected SOF system, it takes 5 mins to suspend. On another affected HDA system, S4 resume causes high power consumption becuase HDA controller can't be runtime suspended. Both issues are gone by applying these patches. [Where problems could occur] If somehow any laptop depends on the old behavior to work properly, this can break them. It's highly unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:4020]
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1902848
Title:
Support Intel AX210 wifi [8086:2725] Subsystem [8086:4020]
Status in HWE Next:
New
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Invalid
Status in linux-firmware source package in Hirsute:
Invalid
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
To support next generation of Intel AX210 WiFi family. PCI ID
[8086:2725] Subsystem [8086:4020] specifically.
So far only patchset
https://lore.kernel.org/linux-wireless/20201202124151.55050-1-l...@coelho.fi
is required on v5.10-rc6, and itself is also in mainline kernel for
v5.10-rc7 at this moment. To enable this card with oem-5.10 kernel in
Focal, firmware blob is also required and hence SRU sent.
[Fix]
Firmware iwlwifi-ty-a0-gf-a0-59.ucode from commit 4f41e9d6437d ("iwlwifi:
update and add new FWs from core56-54 release").
[Test Case]
1. Boot with kernel from mainline tip or v5.10-rc7 or newer.
2. Check with `sudo dmesg | grep iwlwifi`.
[Where problems could occur]
New device firmware for initial AX210 hardware support. As this is the
first revision of the firmware for bringing up corresponding iwlwifi
device in system, it may also introduce new issues that breaks
existing user experience. However, without corresponding firmware, the
Wi-Fi function would be completely unusable, so the risk should be
justified.
== Original Bug Description ==
Firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/iwlwifi-
ty-a0-gf-a0-59.ucode?id=4f41e9d6437d03e7ce9279076107dd08f46656f3,
which is already in mainline master.
Kernel: https://lore.kernel.org/linux-
wireless/iwlwifi.20201202143859.a06ba7540449.I7390305d088a49c1043c9b489154fe057989c18f@changeid/T/#u,
which will be included in v5.10-rc7 or newer.
04:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev
1a)
Subsystem: Intel Corporation Device [8086:0020]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR-
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
Bluetooth part in bug 1890130.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer']
failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-13 (22 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 100: ID 8087:0032 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation Rocket Lake Client Platform
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-generic
root=UUID=221267f2-0315-4b8c-98c3-6e791d5615fc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1.2-generic 5.10.0-rc2
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1-generic N/A
linux-backports-modules-5.10.0-1-generic N/A
linux-firmware1.190
RfKill:
Tags: focal
Uname: Linux 5.10.0-1-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: False
acpidump:
Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
Error executing command
[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904225 Title: Use ACPI S5 for reboot Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] On some HP laptops, BIOS hotkeys don't work right after reboot, becuase OS doesn't call _PTS to indicate ACPI it's rebooting. [Fix] Follow Windows and use S5 for reboot. [Test case] Reboot and see if hotkeys like F10/F11 can trigger BIOS functions. Hotkeys work great with the patch applied. [Where problems could occur] If there are platforms don't expect S5 for reboot then there could be unexpected result. However Windows uses S5 so that's rather unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972017] Re: Jammy/linux-azure: CONFIG_BLK_DEV_FD=n
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1972832] Re: [Azure] hv_netvsc: Add support for XDP_REDIRECT
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
This bug was fixed in the package linux-azure - 5.13.0-1026.30 --- linux-azure (5.13.0-1026.30) impish; urgency=medium * impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() - Drivers: hv: balloon: Support status report for larger page sizes - Drivers: hv: balloon: Disable balloon and hot-add accordingly * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m [ Ubuntu: 5.13.0-46.51 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.13.0-45.50 ] * impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347) * CVE-2022-1158 - KVM: x86/mmu: do compare-and-exchange of gPTE via the user address * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * re-apply missing overlayfs SAUCE patch (LP: #1967924) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Impish update: upstream stable patchset 2022-04-20 (LP: #1969666) - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5668: do not block workqueue if card is unbound - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - selftests/seccomp: Fix seccomp failure by adding missing headers - i2c: cadence: allow COMPILE_TEST - i2c: qup: allow COMPILE_TEST - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf - usb: gadget: clear related members when goto fail - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - ALSA: intel_hdmi: Fix reference to PCM buffer address - riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value - riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP - riscv: Fix config KASAN && DEBUG_VIRTUAL - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - iommu/amd: Recover from event log overflow - drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - thermal: core: Fix TZ_GET_TRIP NULL pointer dereference - ntb: intel: fix port config status offset for SPR - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: sxgbe: fix return value of __setup
[Kernel-packages] [Bug 1973169] Re: [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1970977] Re: jammy/linux-azure: Update cifs to 5.15 backport
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1972832] Re: [Azure] hv_netvsc: Add support for XDP_REDIRECT
This bug was fixed in the package linux-azure - 5.13.0-1026.30 --- linux-azure (5.13.0-1026.30) impish; urgency=medium * impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() - Drivers: hv: balloon: Support status report for larger page sizes - Drivers: hv: balloon: Disable balloon and hot-add accordingly * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m [ Ubuntu: 5.13.0-46.51 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.13.0-45.50 ] * impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347) * CVE-2022-1158 - KVM: x86/mmu: do compare-and-exchange of gPTE via the user address * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * re-apply missing overlayfs SAUCE patch (LP: #1967924) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Impish update: upstream stable patchset 2022-04-20 (LP: #1969666) - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5668: do not block workqueue if card is unbound - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - selftests/seccomp: Fix seccomp failure by adding missing headers - i2c: cadence: allow COMPILE_TEST - i2c: qup: allow COMPILE_TEST - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf - usb: gadget: clear related members when goto fail - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - ALSA: intel_hdmi: Fix reference to PCM buffer address - riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value - riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP - riscv: Fix config KASAN && DEBUG_VIRTUAL - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - iommu/amd: Recover from event log overflow - drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - thermal: core: Fix TZ_GET_TRIP NULL pointer dereference - ntb: intel: fix port config status offset for SPR - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: sxgbe: fix return value of __setup
[Kernel-packages] [Bug 1970468] Re: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04
This bug was fixed in the package linux-azure - 5.13.0-1026.30 --- linux-azure (5.13.0-1026.30) impish; urgency=medium * impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() - Drivers: hv: balloon: Support status report for larger page sizes - Drivers: hv: balloon: Disable balloon and hot-add accordingly * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m [ Ubuntu: 5.13.0-46.51 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.13.0-45.50 ] * impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347) * CVE-2022-1158 - KVM: x86/mmu: do compare-and-exchange of gPTE via the user address * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * re-apply missing overlayfs SAUCE patch (LP: #1967924) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Impish update: upstream stable patchset 2022-04-20 (LP: #1969666) - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5668: do not block workqueue if card is unbound - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - selftests/seccomp: Fix seccomp failure by adding missing headers - i2c: cadence: allow COMPILE_TEST - i2c: qup: allow COMPILE_TEST - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf - usb: gadget: clear related members when goto fail - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - ALSA: intel_hdmi: Fix reference to PCM buffer address - riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value - riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP - riscv: Fix config KASAN && DEBUG_VIRTUAL - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - iommu/amd: Recover from event log overflow - drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - thermal: core: Fix TZ_GET_TRIP NULL pointer dereference - ntb: intel: fix port config status offset for SPR - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: sxgbe: fix return value of __setup
[Kernel-packages] [Bug 1970468] Re: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04
This bug was fixed in the package linux-azure - 5.15.0-1008.9 --- linux-azure (5.15.0-1008.9) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.04.18) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m * linux: CONFIG_SERIAL_8250_MID=y (LP: #1967338) - [Config] azure: CONFIG_SERIAL_8250_MID=y * Support AMD P-State cpufreq control mechanism (LP: #1956509) // Enable speakup kernel modules to allow the speakup screen reader to function (LP: #1967702) - [Config] azure: Update configs after rebase * Azure: swiotlb patch needed for CVM (LP: #1971701) // [Azure][CVM] Fix swiotlb_max_mapping_size() for potential bounce buffer allocation failure in storvsc (LP: #1973169) - SAUCE: swiotlb: Max mapping size takes min align mask into account * Azure: swiotlb patch needed for CVM (LP: #1971701) - SAUCE: treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - SAUCE: swiotlb: use bitmap to track free slots - SAUCE: swiotlb: allocate memory in a cache-friendly way - SAUCE: swiotlb: Split up single swiotlb lock * jammy/linux-azure: Update cifs to 5.15 backport (LP: #1970977) - improve error message when mount options conflict with posix - cifs: call cifs_reconnect when a connection is marked - cifs: call helper functions for marking channels for reconnect - cifs: mark sessions for reconnection in helper function - treewide: Replace zero-length arrays with flexible-array members - smb3: fix incorrect session setup check for multiuser mounts - cifs: truncate the inode and mapping when we simulate fcollapse - cifs: use a different reconnect helper for non-cifsd threads - cifs: do not skip link targets when an I/O fails - cifs: convert the path to utf16 in smb2_query_info_compound - cifs: change smb2_query_info_compound to use a cached fid, if available - cifs: fix bad fids sent over wire - cifs: fix incorrect use of list iterator after the loop - move more common protocol header definitions to smbfs_common - smb3: move defines for ioctl protocol header and SMB2 sizes to smbfs_common - smb3: move defines for query info and query fsinfo to smbfs_common - smb3: cleanup and clarify status of tree connections - smb3: fix ksmbd bigendian bug in oplock break, and move its struct to smbfs_common - fs: Remove ->readpages address space operation - cifs: fix potential race with cifsd thread - cifs: remove check of list iterator against head past the loop body - cifs: force new session setup and tcon for dfs - cifs: update internal module number - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - cifs: Split the smb3_add_credits tracepoint - cifs: Use kzalloc instead of kmalloc/memset - cifs: fix NULL ptr dereference in refresh_mounts() - cifs: use correct lock type in cifs_reconnect() - cifs: destage any unwritten data to the server before calling copychunk_write * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: balloon: Support status report for larger page sizes [ Ubuntu: 5.15.0-35.36 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.15.0-34.35 ] * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322) * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134) - drm/amdgpu: unify BO evicting method in amdgpu_ttm - drm/amdgpu: explicitly check for s0ix when evicting resources * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 (LP: #1971597) - gpio: Request interrupts after IRQ is initialized * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552) - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 (LP: #1971418) - Revert "rfkill: make new event layout opt-in" * PCIE LnkCtl ASPM not enabled under VMD
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1975717] Re: [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0
This bug was fixed in the package linux-azure - 5.13.0-1026.30 --- linux-azure (5.13.0-1026.30) impish; urgency=medium * impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334) * [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0 (LP: #1975717) - Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64) - Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() * [Azure] hv_netvsc: Add support for XDP_REDIRECT (LP: #1972832) - hv_netvsc: Add comment of netvsc_xdp_xmit() - hv_netvsc: Add support for XDP_REDIRECT * linux-azure: Patch Set for ARM64 Images 20.04 and 18.04 (LP: #1970468) - Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb() - Drivers: hv: balloon: Support status report for larger page sizes - Drivers: hv: balloon: Disable balloon and hot-add accordingly * [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time (LP: #1972662) - PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] azure: CONFIG_HISI_PMU=m [ Ubuntu: 5.13.0-46.51 ] * CVE-2022-21499 - SAUCE: debug: Lock down kgdb [ Ubuntu: 5.13.0-45.50 ] * impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347) * CVE-2022-1158 - KVM: x86/mmu: do compare-and-exchange of gPTE via the user address * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * re-apply missing overlayfs SAUCE patch (LP: #1967924) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Impish update: upstream stable patchset 2022-04-20 (LP: #1969666) - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5668: do not block workqueue if card is unbound - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - selftests/seccomp: Fix seccomp failure by adding missing headers - i2c: cadence: allow COMPILE_TEST - i2c: qup: allow COMPILE_TEST - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf - usb: gadget: clear related members when goto fail - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - ALSA: intel_hdmi: Fix reference to PCM buffer address - riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value - riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP - riscv: Fix config KASAN && DEBUG_VIRTUAL - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - iommu/amd: Recover from event log overflow - drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - thermal: core: Fix TZ_GET_TRIP NULL pointer dereference - ntb: intel: fix port config status offset for SPR - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: sxgbe: fix return value of __setup
[Kernel-packages] [Bug 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
This bug was fixed in the package linux - 5.13.0-46.51 --- linux (5.13.0-46.51) impish; urgency=medium * CVE-2022-21499 - SAUCE: debug: Lock down kgdb linux (5.13.0-45.50) impish; urgency=medium * impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347) * CVE-2022-1158 - KVM: x86/mmu: do compare-and-exchange of gPTE via the user address * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086) - [Config] CONFIG_HISI_PMU=m * re-apply missing overlayfs SAUCE patch (LP: #1967924) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Impish update: upstream stable patchset 2022-04-20 (LP: #1969666) - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5668: do not block workqueue if card is unbound - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - selftests/seccomp: Fix seccomp failure by adding missing headers - i2c: cadence: allow COMPILE_TEST - i2c: qup: allow COMPILE_TEST - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf - usb: gadget: clear related members when goto fail - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - ALSA: intel_hdmi: Fix reference to PCM buffer address - riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value - riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP - riscv: Fix config KASAN && DEBUG_VIRTUAL - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - iommu/amd: Recover from event log overflow - drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - thermal: core: Fix TZ_GET_TRIP NULL pointer dereference - ntb: intel: fix port config status offset for SPR - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: sxgbe: fix return value of __setup handler - ibmvnic: register netdev after init of adapter - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() - efivars: Respect "block" flag in efivar_entry_set_safe() - firmware: arm_scmi: Remove space in MODULE_ALIAS name - ASoC: cs4265: Fix the duplicated control name - can: gs_usb: change active_channels's type from atomic_t to u8 - arm64: dts: rockchip: Switch RK3399-Gru DP to SPDIF output - igc: igc_read_phy_reg_gpy: drop premature return - ARM: Fix kgdb breakpoint for Thumb2 - ARM: 9182/1: mmu: fix returns from early_param() and __setup() functions - selftests: mlxsw: tc_police_scale: Make test more robust - pinctrl: sunxi: Use unique lockdep classes for IRQs - igc: igc_write_phy_reg_gpy: drop premature return - ibmvnic: free reset-work-item when flushing - memfd: fix F_SEAL_WRITE after shmem huge page allocated - s390/extable: fix exception table sorting - ARM: dts: switch timer config to common
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967069] Re: Enable headset mic on Lenovo P360
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967338] Re: linux: CONFIG_SERIAL_8250_MID=y
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1968892] Re: Micmute LED support for Zbook Fury 16 G9
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources
* amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized
* config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m
* Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
* network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"
* PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead
* Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
845/865 G9
* Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360
* WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices
* Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config
* Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
-
