[Kernel-packages] [Bug 2012584] [NEW] [ADL-PS] Audio is malfunction
Public bug reported: [Impact] audio on adl-ps is not working [Fix] adding the pci id of sof and the link to the soundwire [Test Case] 1.Boot OS. 3.Check audio device by aplay and speaker-test [Where problems could occur] Low, the fix limits to adl-ps series ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-iotg (Ubuntu Jammy) Importance: Medium Assignee: Jian Hui Lee (jianhuilee) Status: New ** Tags: lookout-canyon oem-priority originate-from-1999615 ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Invalid ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Description changed: [Impact] - audio is not working + audio on adl-ps is not working [Fix] adding the pci id of sof and the link to the soundwire [Test Case] 1.Boot OS. 3.Check audio device by aplay and speaker-test [Where problems could occur] Low, the fix limits to adl-ps series ** Tags added: lookout-canyon oem-priority originate-from-1999615 ** No longer affects: hwe-next -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2012584 Title: [ADL-PS] Audio is malfunction Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: [Impact] audio on adl-ps is not working [Fix] adding the pci id of sof and the link to the soundwire [Test Case] 1.Boot OS. 3.Check audio device by aplay and speaker-test [Where problems could occur] Low, the fix limits to adl-ps series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2012584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
No PowerPC for riscv. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001618 Title: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are not supported. test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to select_runtime err=-524 ... test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to select_runtime err=-524 ... test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed] Please find attachment for the complete test log. [Fix] * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg These patches can be cherry-picked into Kinetic kernel. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/ Steps: 1. Reboot with the patched kernel 2. Run: sudo dmesg -C sudo modprobe test_bpf sudo dmesg Tested with Power9 node baltar, with the patched kernel there will be no failure reported by the test_bpf: test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed] [Where problems could occur] This patchset just broaden the BPF operations support on ppc64, we might see some new failures when using these instruction somewhere in the future. Cascardo: The existing atomic operations may regress as well, since they now produce different code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
From Dilyn's steps, he install the beta version of the bluez, and here is what I found. 1. power cycle the machine 2. install beta bluez, the advinfo doesn't work acelankao@ubuntu:~$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ snap install --channel=22/beta bluez bluez (22/beta) 5.64-3 from Canonical✓ installed acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Reading adv features failed with status 0x0c (Not Supported) 1. removed the beta bluez, and install stable bluez acelankao@ubuntu:~$ sudo snap remove bluez bluez removed acelankao@ubuntu:~$ sudo snap install bluez bluez (20/stable) 5.53-7 from Canonical✓ installed 2. power cycle the machine, and then advinfo works acelankao@ubuntu:~$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes bluez 5.53-7 33420/stable canonical✓ - checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Supported flags: connectable general-discoverable limited-discoverable managed-flags tx-power scan-rsp-appearance scan-rsp-local-name Secondary-channel-1M Secondary-channel-2M Secondary-channel-CODED Max advertising data len: 31 Max scan response data len: 31 Max instances: 8 Instances list with 0 items BTW, the BT firmware is intel/ibt-0040-0041.sfi [ 15.452255] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 15.452260] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 15.453014] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi [ 16.965744] Bluetooth: hci0: Waiting for firmware download to complete [ 16.966269] Bluetooth: hci0: Firmware loaded in 1477780 usecs [ 16.966446] Bluetooth: hci0: Waiting for device to boot [ 16.985279] Bluetooth: hci0: Device booted in 18524 usecs [ 16.987502] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc [ 16.990290] Bluetooth: hci0: Applying Intel DDC parameters completed [ 16.994174] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020 -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to:
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
-- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
-- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Tried many different ways to recover the status(advinfo should work), but in vain, so I removed customer's snaps, removed the beta bluez, installed the stable bluez and then power cycle the machine. The advinfo works again. acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes bluez 5.53-7 33420/stable canonical✓ - checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ snap connections bluez Interface Plug Slot Notes bluetooth-control bluez:bluetooth-control - - bluez bluez:client bluez:service - home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control- - uhid bluez:uhid :uhid - uinput bluez:uinput - - acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Unable to open mgmt_socket acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Supported flags: connectable general-discoverable limited-discoverable managed-flags tx-power scan-rsp-appearance scan-rsp-local-name Secondary-channel-1M Secondary-channel-2M Secondary-channel-CODED Max advertising data len: 31 Max scan response data len: 31 Max instances: 8 Instances list with 0 items -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
** Attachment added: "lsusb_vvv.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656717/+files/lsusb_vvv.log -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
acelankao@ubuntu:~/bci-snaps$ snap connections bluez Interface PlugSlot Notes bluetooth-control bluez:bluetooth-control - - bluez blackrock-bci-moveagain:bluez bluez:service manual bluez bluez:clientbluez:service - dbus blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez manual home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control - - uhid bluez:uhid :uhid - uinput bluez:uinput- - acelankao@ubuntu:~/bci-snaps$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~/bci-snaps$ snap connections bluez Interface PlugSlotNotes bluetooth-control bluez:bluetooth-control :bluetooth-control manual bluez blackrock-bci-moveagain:bluez bluez:service manual bluez bluez:clientbluez:service - dbus blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez manual home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control - - uhid bluez:uhid :uhid - uinput bluez:uinput- - acelankao@ubuntu:~/bci-snaps$ sudo blackrock-bci-moveagain.bledemo Error: NotSupported acelankao@ubuntu:~/bci-snaps$ sudo bluez.btmgmt advinfo Reading adv features failed with status 0x0c (Not Supported) ** Attachment added: "lspci_nnvvk.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656716/+files/lspci_nnvvk.log -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
I followed the steps Dilyn provides, and the bt adv feature is gone, even if I connected the bluez:bluetooth-control manually. acelankao@ubuntu:~/bci-snaps$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~/bci-snaps$ snap install --dangerous blackrock-bci-libtorch.snap blackrock-bci-libtorch 1.11.0-cuda113 installed acelankao@ubuntu:~/bci-snaps$ snap install --dangerous blackrock-bci-moveagain.snap blackrock-bci-moveagain 0+git.3f19fe7 installed acelankao@ubuntu:~/bci-snaps$ snap install --channel=22/beta bluez bluez (22/beta) 5.64-3 from Canonical✓ installed acelankao@ubuntu:~/bci-snaps$ /snap/blackrock-bci-moveagain/current/bin/setup.sh Warning: Failed to connect 'bluez'. Please connect manually, available providers are: - bluez:service Added: - blackrock-bci-moveagain as moveagain acelankao@ubuntu:~/bci-snaps$ snap connect blackrock-bci-moveagain:bluez bluez:service acelankao@ubuntu:~/bci-snaps$ snap connect blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez acelankao@ubuntu:~/bci-snaps$ sudo blackrock-bci-moveagain.bledemo Error: NotSupported ** Attachment added: "pc-kernel.info.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656715/+files/pc-kernel.info.log -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012020] Re: Release 5.4.0-1097 Floods NFS server with 50-600 metadata requests per second per server
*** This bug is a duplicate of bug 2009325 *** https://bugs.launchpad.net/bugs/2009325 ** This bug has been marked a duplicate of bug 2009325 NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2012020 Title: Release 5.4.0-1097 Floods NFS server with 50-600 metadata requests per second per server Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws-5.4 package in Ubuntu: Confirmed Status in linux-signed-aws-5.4 package in Ubuntu: Confirmed Bug description: We are observing a massive uptick in metadata requests to an NFSv4.1 (AWS EFS) network drive that is linked to a one or more web servers. This started happening about a week ago across a number of stacks on AWS. This issue ended up exhausting all the burst credits we had accrued and caused a production outage. Diagnostics... `nfsiostat` shows 50-600 ops/s on the servers where it is happening. `nfsstat -m` shows these mount flags: `Flags: rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,noresvport,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=x.x.x.x,fsc,local_lock=none,addr=y.y.y.y` `nfstrace --mode=live --verbose=2` shows that the same operations are happening repeatedly on 2-5 filehandles; ``` CALL [ operations: 4 tag: void minor version: 1 [ SEQUENCE(53) [ sessionid: 0xeab1201a93b66961 sequenceid: 0xfc12c slotid: 2 cache this: 0 ] [ PUTFH(22) [ object: 839c9918169aed49bd6f96adab5438bc47b1460162fe4a739cd8c98405868b2b5de303ed1f4ecfa82c26f5ca1db4cce8e63aad38fe72a397bdae51d8a7e93eb118ad8c736b30323165273b9c805db85936cf3be626b6ba4165ecf9755a54fdd174a535e217ffee4fa0166feea6e86becf9fa16280fd877b3545e07fe03aede08 ] [ ACCESS(3) [ READ LOOKUP MODIFY EXTEND DELETE ] [ GETATTR(9) [ mask: 0x1830 CHANGE SIZE TIME_METADATA TIME_MODIFY ] ] REPLY [ operations: 4 status: OK tag: void [ SEQUENCE(53) [ status: OK session: 0xeab1201a93b66961 sequenceid: 0xfc12c slotid: 2 highest slotid: 63 target highest slotid: 63 status flags: 0 ] [ PUTFH(22) [ status: OK ] [ ACCESS(3) [ status: OK supported: READ LOOKUP MODIFY EXTEND DELETE access: READ LOOKUP MODIFY EXTEND DELETE ] [ GETATTR(9) [ status: OK mask: 0x1830 CHANGE SIZE TIME_METADATA TIME_MODIFY ] ] ``` `lsof -N` shows nothing using files from the NFS drive. Unmounting and remounting the disk stops the issue temporarily I also enabled rpcdebugging via `rpcdebug -m nfs -s all` and a snippet of the output is below; ``` Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213426] NFS: nfs_update_inode(0:55/1440391441734181492 fh_crc=0xc29dd48a ct=2 info=0x26040) Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213428] NFS: permission(0:55/1440391441734181492), mask=0x1, res=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213430] NFS: nfs_lookup_revalidate_done(/Components) is valid Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213432] --> nfs41_call_sync_prepare data->seq_server 8a198bb4 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213433] --> nfs4_alloc_slot used_slots= highest_used=4294967295 max_slots=64 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213433] <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213436] encode_sequence: sessionid=1354075206:678036945:0:16777216 seqid=238661 slotid=0 max_slotid=0 cache_this=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213842] decode_attr_type: type=00 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213843] decode_attr_change: change attribute=2153 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213844] decode_attr_size: file size=71680 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213845] decode_attr_fsid: fsid=(0x0/0x0) Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213845] decode_attr_fileid: fileid=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213846] decode_attr_fs_locations: fs_locations done, error = 0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213846] decode_attr_mode: file mode=00 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213847] decode_attr_nlink: nlink=1 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213848] decode_attr_rdev: rdev=(0x0:0x0) Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213848] decode_attr_space_used: space used=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213849] decode_attr_time_access: atime=0 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213849] decode_attr_time_metadata: ctime=1677729393 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213850] decode_attr_time_modify: mtime=1677729393 Mar 17 10:20:41 ip-10-1-2-84 kernel: [ 3897.213851] decode_attr_mounted_on_fileid: fileid=0 Mar 17 10:20:41 ip-10-1-2-84
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Package changed: linux-oracle (Ubuntu) => linux-oracle-5.15 (Ubuntu)
** Changed in: linux-oracle-5.15 (Ubuntu)
Status: New => In Progress
** Changed in: linux-oracle-5.15 (Ubuntu)
Assignee: (unassigned) => Cory Todd (corytodd)
** Changed in: linux-oracle-5.15 (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux-oracle-5.15 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oracle-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oracle-5.15 (Ubuntu Focal)
Assignee: (unassigned) => Cory Todd (corytodd)
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Assignee: (unassigned) => Cory Todd (corytodd)
** Changed in: linux-oracle-5.15 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
In Progress
Status in linux-oracle-5.15 source package in Focal:
In Progress
Status in linux-oracle-5.15 source package in Jammy:
In Progress
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected for both the alarm and update tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle-5.15/+bug/2011854/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
The core issue is that with f2a7f3238777, the kernel on the affected
systems no longer uses hpet for the rtc alarm and update interrupts.
This may indicate that their non-hpet implementation is faulty. By
removing the ACPI_FADT_LOW_POWER_S0 check from use_acpi_alaram_quirks,
the kernel expects to use the acpi alarm by way of use_hpet_alarm().
Other facts:
- this patch has only been applied to Jammy. Kinetic and Focal do not have the
latest patches affecting rtc-cmos.
- applying these patches to jammy:linux-gcp work correctly on a g1-small
instance. This system is able to use the acpi alarm for both alarm and update
interrupts.
I see two options:
1) Revert f2a7f3238777 as a SAUCE patch. The justification for this commit
seems to be based on the suspend-to-idle use case, notwithstanding the alarm
from S0 use case.
2) Patch in a more specific quirk and get it upstreamed. It seems like the
quirk that was removed was hiding a bug on this particular system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle package in Ubuntu:
New
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected for both the alarm and update tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2011854/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012571] [NEW] net/sched: cls_api: Support hardware miss to tc action
Public bug reported: * Explain the bug(s) Currently tc miss interface only supports resuming from a specific tc chain. If a packet modification is done before a missable action such as CT and there is a miss in CT after it, this may cause a miss match when resuming re-executing the same chain in software, and wrong packet count. This use case for example is a stateless (static) nat. * brief explanation of fixes Add support for missing to a specific action instance, and support of per action hardware stats to update what was actually done in hardware. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules with packet modification before the CT action (such as statless nat): e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk actions=mod_nw_dst=1.1.1.2,ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new actions=ct(commit),output:2" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, actions=output:2" ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, actions=mod_nw_src=1.1.1.2,output:1" Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2 For VF2, add route and static neighbour to floating (router) ip 5.5.5.5 Then run a TCP connection, e.g: on mlx5 VF1 iperf -s #(which will listen on 1.1.1.2) on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2) Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i 1.1.1.1 See tuples were offloaded: ipv4 2 tcp 6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. offload for modifications + ct and tc packet count. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/2012571 Title: net/sched: cls_api: Support hardware miss to tc action Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Currently tc miss interface only supports resuming from a specific tc chain. If a packet modification is done before a missable action such as CT and there is a miss in CT after it, this may cause a miss match when resuming re-executing the same chain in software, and wrong packet count. This use case for example is a stateless (static) nat. * brief explanation of fixes Add support for missing to a specific action instance, and support of per action hardware stats to update what was actually done in hardware. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules with packet modification before the CT action (such as statless nat): e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk actions=mod_nw_dst=1.1.1.2,ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new actions=ct(commit),output:2" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, actions=output:2" ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, actions=mod_nw_src=1.1.1.2,output:1" Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2 For VF2, add route and static neighbour to floating (router) ip 5.5.5.5 Then run a TCP connection, e.g: on mlx5 VF1 iperf -s #(which will listen on 1.1.1.2) on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2) Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i 1.1.1.1 See tuples were offloaded: ipv4 2 tcp 6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. offload for modifications + ct and tc packet count. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
** Description changed: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] + Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] + Regression Risk is Low + [Other Info] - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1998544_hpwdt + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
Dell has stated that this has been tested on systems with both AMD and Intel CPU's mproved boot up time in Performance Per Watt (DAPC) before/after boot times results, With PATCH # systemd-analyze Startup finished in 13.569s (kernel) + 9.136s (userspace) = 22.705s graphical.target reached after 8.460s in userspace # systemd-analyze Startup finished in 13.188s (kernel) + 8.504s (userspace) = 21.692s graphical.target reached after 8.123s in userspace # systemd-analyze Startup finished in 13.720s (kernel) + 9.235s (userspace) = 22.956s graphical.target reached after 8.807s in userspace # systemd-analyze Startup finished in 13.967s (kernel) + 8.896s (userspace) = 22.863s graphical.target reached after 8.489s in userspace WithOut PATCH # systemd-analyze Startup finished in 14.137s (kernel) + 14.879s (userspace) = 29.016s graphical.target reached after 14.460s in userspace # systemd-analyze Startup finished in 14.149s (kernel) + 12.344s (userspace) = 26.494s graphical.target reached after 11.900s in userspace # systemd-analyze Startup finished in 14.434s (kernel) + 13.047s (userspace) = 27.481s graphical.target reached after 12.602s in userspace # systemd-analyze Startup finished in 14.462s (kernel) + 12.908s (userspace) = 27.371s graphical.target reached after 12.481s in userspace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
So this is great news, Thank you so much. Yours, Carsten On Wed, Mar 22, 2023 at 1:45 PM Mario Limonciello < 2006...@bugs.launchpad.net> wrote: > Tested kinetic kernel 5.19.0-38.39 and focal kernel 5.15.0-69.76 and > both pass. > > ** Tags added: verification-done-focal verification-done-kinetic > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2006458 > > Title: > Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm > FastConnect 6900 > > Status in linux-firmware package in Ubuntu: > Fix Released > Status in linux-firmware source package in Focal: > Fix Committed > Status in linux-firmware source package in Jammy: > Fix Committed > Status in linux-firmware source package in Kinetic: > Fix Committed > Status in linux-firmware source package in Lunar: > Fix Released > > Bug description: > [Impact] > > To whom it may concern: > > I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 > convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue > is related to FW revision > WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes > bundled with Ubuntu 22.10. > > It appears the SoC increasingly triggering wake-ups after being > suspended for approx. 4 hrs. > > Read the full story at [4]. > > The solution is to upgrade SoC firmware to rev > WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] > > Best regards,Carsten > > [1] > https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 > [2] > https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 > [3] > https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 > [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 > > [Fix] > > Upgrade firmware, as mentioned above. > > [Test case] > > Verify WiFi functionality on WCN6855 works and that unplugging power > cord during suspend doesn't wake system. > > [Where Problems might occur] > > It's firmware, what could possibly go wrong? If so, connectivity > issues wit ath11k based NICs. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+subscriptions > > -- 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/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 [Fix] Upgrade firmware, as mentioned above. [Test case] Verify WiFi functionality on WCN6855 works and that unplugging power cord during suspend doesn't wake system. [Where Problems might occur] It's firmware, what could possibly go wrong? If so, connectivity issues wit ath11k based NICs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
I'm still seeing it on 5.19.0-38-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012559] 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/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: Confirmed Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression
Hello :) I just updated to linux 5.19.0-38 and the bug seems to be gone :) But other users still have it like FedKad on https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log Thanks, best regards, Laurent Lyaudet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009271 Title: Too many BDL entries regression Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: Hello, Thanks for your hard work :) I got this error after kernel update to 5.19.0-35 as explained here : https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log and here : https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u A load of syslog "Too many BDL entries" appears. Have a nice week-end, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5004 F wireplumber /dev/snd/controlC1: laurent5004 F wireplumber /dev/snd/seq:laurent5000 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 16:47:55 2023 InstallationDate: Installed on 2020-07-01 (976 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012561] Re: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/2012561 Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1 Status in linux-base package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-base 4.5ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Mar 22 16:20:41 2023 DuplicateSignature: package:linux-base:4.5ubuntu9 Setting up linux-base (4.5ubuntu9) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package linux-base (--configure): installed linux-base package post-installation script subprocess returned error exit status 1 ErrorMessage: installed linux-base package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-11-10 (497 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-base Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-03-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/2012561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012561] [NEW] package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-base 4.5ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Mar 22 16:20:41 2023 DuplicateSignature: package:linux-base:4.5ubuntu9 Setting up linux-base (4.5ubuntu9) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package linux-base (--configure): installed linux-base package post-installation script subprocess returned error exit status 1 ErrorMessage: installed linux-base package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-11-10 (497 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-base Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-03-22 (0 days ago) ** Affects: linux-base (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 linux-base in Ubuntu. https://bugs.launchpad.net/bugs/2012561 Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1 Status in linux-base package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-base 4.5ubuntu9 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Mar 22 16:20:41 2023 DuplicateSignature: package:linux-base:4.5ubuntu9 Setting up linux-base (4.5ubuntu9) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package linux-base (--configure): installed linux-base package post-installation script subprocess returned error exit status 1 ErrorMessage: installed linux-base package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-11-10 (497 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-base Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-03-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/2012561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006937] Re: Update the NVIDIA 525 series to 525.89.02
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.89.02-0ubuntu0.22.10.1 --- nvidia-graphics-drivers-525 (525.89.02-0ubuntu0.22.10.1) kinetic; urgency=medium * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. * debian/templates/control.in: - Switch libcuda1 and libnvidia-ml1 Provides to libcuda.so.1 and libnvidia-ml.so.1. This makes CUDA (from Multiverse) installable again. -- Alberto Milone Tue, 28 Feb 2023 10:44:20 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2006937 Title: Update the NVIDIA 525 series to 525.89.02 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 source package in Bionic: Triaged Status in nvidia-graphics-drivers-525 source package in Focal: Triaged Status in nvidia-graphics-drivers-525 source package in Jammy: Triaged Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 525.89.02 [Kinetic, Jammy] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. * debian/templates/control.in: - Switch libcuda1 and libnvidia-ml1 Provides to libcuda.so.1 and libnvidia-ml.so.1. This makes CUDA (from Multiverse) installable again. [Focal, Bionic] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2006937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012559] [NEW] 6.2 kernel won't boot, may be nvidia related?
Public bug reported: After installing most recent Lunar updates, linux-image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "journalctl log from right before the first reboot attempt with the new kernel" https://bugs.launchpad.net/bugs/2012559/+attachment/5656653/+files/log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: New Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
** Changed in: linux-gcp (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: In Progress Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
** Changed in: linux-aws (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: In Progress Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003398] Re: [23.04 FEAT] Support for List-Directed dump from ECKD DASD - kernel part
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003398 Title: [23.04 FEAT] Support for List-Directed dump from ECKD DASD - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Support for List-Directed dump from ECKD DASD. This is required to support Secure Boot from a DASD. Secure boot is required by NIAP's Common Criteria OSPP v4.2 profile which is a prereq for US government clients. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959974] Re: [23.04 FEAT] KVM: Improve memory reclaiming for Secure Execution guests on new IBM Z Hardware
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: ubuntu-z-systems Status: In Progress => 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/1959974 Title: [23.04 FEAT] KVM: Improve memory reclaiming for Secure Execution guests on new IBM Z Hardware Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: KVM: Improve memory reclaiming for Secure Execution guests on new IBM Z Hardware Description: Currently, Secure Execution guest memory needs to be exported or destroyed, when a secure guest is rebooted or shut down. So far this happens in a serialized manner, which takes long and also causes the host system to become unresponsive for extended periods, if very large guests are terminated. This feature implements changes to the KVM memory management required to improve the scalability. Category: kernel Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933180] Re: [23.04 FEAT] KVM: Improve memory reclaiming for z15 Secure Execution guests
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933180 Title: [23.04 FEAT] KVM: Improve memory reclaiming for z15 Secure Execution guests Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Currently, Secure Execution guest memory needs to be exported or destroyed, when a secure guest is rebooted or shut down. On the z15 this currently happens in a serialized manner, which takes long and also causes the host system to become unresponsive for extended periods, if very large guests are terminated. Changes to the KVM memory management will be required to improve the scalability. Value: Scalability improvement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983224] Re: [23.04 FEAT] [VS2029] KVM: Provide virtual CPU topology to guests - kernel part
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983224 Title: [23.04 FEAT] [VS2029] KVM: Provide virtual CPU topology to guests - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Currently, KVM guests will see an evenly distributed CPU topology, where every CPU resides on a separate drawer. This may not be optimal for scheduling decisions. The goal is to allow to specify a virtual CPU topology which can help to configure the guest for better performance. The full range of topology nodes should be configurable (drawer -> book -> chip -> core -> thread). This has a kernel, qemu and libvirt part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1983224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982341] Re: [23.04 FEAT] Transparent DASD PPRC (Peer-to-Peer Remote Copy) handling
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982341 Title: [23.04 FEAT] Transparent DASD PPRC (Peer-to-Peer Remote Copy) handling Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Enable user of Linux on Z to use DASD volumes in a PPRC (Peer-to-Peer Remote Copy) relation like a normal DASD volume. Value: - Required for hyperswap implementation - Reduce complexity and increase stability when using PPRC with DASD (due to no dm-multipath tools being required) - Allow for use with zdsfs on PPRC setups (where no dm-multitpathing is possible due to raw track access mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982378] Re: [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT-Protection facility support
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982378 Title: [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT- Protection facility support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Support for new IBM Z Hardware. Target public release: kernel 5.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003394] Re: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003394 Title: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Support for List-Directed IPL and re-IPL from ECKD DASD. Required to enable Secure Boot from DASD. Business Case: Security, HW support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003547] Re: [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003547 Title: [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003637] Re: [23.04 FEAT] zcrypt DD: AP command filtering
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003637 Title: [23.04 FEAT] zcrypt DD: AP command filtering Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Support Stateless AP Commands. This will mainly affect error processing and recognizing new error types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982378] Re: [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT-Protection facility support
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982378 Title: [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT- Protection facility support Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Support for new IBM Z Hardware. Target public release: kernel 5.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003547] Re: [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2)
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003547 Title: [23.04] net/smc: Alibaba patches about tunable buffer sizes may cause errors and need to be removed (kernel 6.2) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: There are two patches about tunable buffer sizes that are changing the conventional behavior in our SMC code. This change of behavior might not be expected by our clients, which could lead to problems. Therefore, we need to remove these two patches from v6.2 / lunar, until we can provide an appropriate solution. The two patches to be removed depend on each other, but don't have any further dependencies to other code/commits. Please remove / revert the following two patches: 0227f058aa29 net/smc: Unbind r/w buffer size from clcsock and make them tunable 77eee3251431 net/smc: Introduce a specific sysctl for TEST_LINK time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003394] Re: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003394 Title: [23.04 FEAT] Support for List-Directed IPL and re-IPL from ECKD DASD Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Support for List-Directed IPL and re-IPL from ECKD DASD. Required to enable Secure Boot from DASD. Business Case: Security, HW support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Released Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987394] Re: Enable kernel config for P2PDMA
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987394 Title: Enable kernel config for P2PDMA Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] We have a request to enable HSA_AMD_P2P for oem-6.0 "HSA kernel driver support for peer-to-peer for AMD GPU devices" [What could go wrong] this is a new config item, shouldn't affect the rest of the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003637] Re: [23.04 FEAT] zcrypt DD: AP command filtering
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003637 Title: [23.04 FEAT] zcrypt DD: AP command filtering Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Support Stateless AP Commands. This will mainly affect error processing and recognizing new error types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed"
- SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is
initialized"
-- Andrea Righi Wed, 15 Mar 2023 23:54:18
+0100
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002089
Title:
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1:
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
[Fix]
The t7xx driver once received following fixes to complete its functions in
v6.1-rc1:
d20ef656f994 net: wwan: t7xx: Add AP CLDMA
007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
140424d90165 net: wwan: t7xx: PCIe reset rescan
87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump
collection
b0bc1709b768 net: wwan: t7xx: Devlink documentation
However it was soon reverted for a second revision. Before that, in bug
1990700
we need the first (reverted) patch "net: wwan: t7xx: Add AP CLDMA" to fix
device
suspend in a minimum level for development. Then, in this bug 2002089, a fully
revised resubmission is now available.
An additional patch from v6.1, commit bb67012331f7 ("net: devlink:
extend info_get() version put to indicate a flash component"), is
necessary for oem-6.0 backport.
[Test Case]
Modprobe on new platforms that suffers this invalid device status issue,
and run suspend/resume tests to ensure bug 1990700 is still in a good
state.
[Where problems could occur]
This re-introduce the device firmware update support via devlink, so far
it has been tested many times from 3rd party/vendor, but might still
bump into platform compatibility issue as we have here.
[Other Info]
While this is only planned for oem-6.0/oem-6.1 and on, only U/L/OEM-6.x
are nominated for fix.
== original bug report ==
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1216 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-05 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enp0s31f6 no wireless extensions.
wwan0 no wireless extensions.
MachineType: Dell Inc. Precision 3480
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem
root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1010-oem N/A
linux-backports-modules-6.0.0-1010-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy
Uname: Linux 6.0.0-1010-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007654] Re: enable Rust support in the kernel
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed"
- SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is
initialized"
-- Andrea Righi Wed, 15 Mar 2023 23:54:18
+0100
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => 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/2007654
Title:
enable Rust support in the kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Rust support has been merged starting with linux 6.1.
This support allows to write external kernel modules using the Rust
language. Modules written in this way are linked against the linux
kernel and can be loaded/unloaded like any other .ko module.
Main advantages of writing modules in Rust are:
- memory safety:
- no out of bounds accesses
- no use after free
- data race safety
- strongly typed and statically typed
- code extremely compact
Roughly 70% of the security issues that the MSRC assigns a CVE to are memory
safety issues:
- Rust allows to write more secure and robust kernel code (reduce kernel
CVEs)
We should provide a Rust-enabled kernel so that people have the
possibility to implement their own external kernel modules in Rust.
[Test case]
Build the following "hello world" test module:
== hello_rust.rs ==
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
type: HelloRust,
name: "hello_rust",
author: "Andrea Righi ",
description: "Rust hello world example",
license: "GPL",
}
struct HelloRust {
}
impl kernel::Module for HelloRust {
fn init(_module: &'static ThisModule) -> Result {
pr_info!("Hello from Rust\n");
Ok(HelloRust { })
}
}
impl Drop for HelloRust {
fn drop( self) {
pr_info!("Goodbye from Rust\n");
}
}
== Makefile ==
NAME=hello_rust
ifndef KERNELRELEASE
ifndef KDIR
KDIR:=/lib/modules/`uname -r`/build
endif
PWD := $(shell pwd)
all:
$(MAKE) -C $(KDIR) M=$(PWD) modules
install:
$(MAKE) -C $(KDIR) M=$(PWD) modules_install
clean:
rm -f *.o *.ko *.mod* .*.cmd *.d Module.symvers modules.order
rm -rf .tmp_versions
else
obj-m := $(NAME).o
endif
[Fix]
Building the Rust support in the kernel requires specific versions of the
Rust compiler and bindgen utility, same to build the external modules in Rust):
- rustc 1.62.0
- bindgen 0.56.0
- clang/llvm (already required by BPF)
Archive should provide these versions (ideally with a version suffix
to avoid conflicting with the stock versions, e.g., rustc-1.62 and
bindgen-0.56).
In addition to that the kernel needs some packaging adjustments to use
these special toolchain binaries and some special (not yet upstream)
patches that would allow to enable mandatory features required in our
generic kernel, such as:
UBUNTU: SAUCE: allows to enable Rust with modversions
UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion
UBUNTU: SAUCE: scripts: Exclude Rust CUs with pahole
UBUNTU: SAUCE: rust: allow to use INIT_STACK_ALL_ZERO
With all of the above we can enable CONFIG_RUST in the kernel and
provide support to build external modules (.ko) using Rust.
[Regression potential]
We may see build regressions due to the inavailability of the proper
toolchain versions. Moreover these toolchain dependencies need to be
maintained, making sure to be always aligned with upstream
requirements, when stable updates are applied to the kernel.
Moreover, hwe kernels require special attention, since this feature
won't be available in old releases (unless the proper toolchain
requirements are met).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007654/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007530] Re: Built-in camera device dies after runtime suspended
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007530 Title: Built-in camera device dies after runtime suspended Status in HWE Next: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] Add the xHC ID to an existing quirk fixes the issue https://www.spinics.net/lists/kernel/msg4689370.html [Test] Verified by me and QA. [Where problems could occur] It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008519 Title: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: [SRU Justification] == Impact == See original description. The goal is to adjust the behavior of the balanced governor for certain Xeon CPUs (those are CPUs rather seen in servers so there should be no impact on laptop users). While the initial request was Jammy/5.15 only we should do this to Kinetic and Lunar as well so the experience is the same regardless of release. == Fix == This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a specific CPU model. For Jammy/5.15 this requires one additional change which introduces the EPP tweak for Alderlake. == Test case == == Regression Potential == The change modifies how quickly CPUs scale up (and probably down) depending on workload. Power usage unlikely is of that much concern in server space. Maybe increased heat would be observed. For Jammy there is the additional risk of havind a different power usage on Alderlake which is a Laptop CPU. However that change is part of v5.17 and thus would already be in effect with current 22.04 HWE. == Original description == [Feature Description] Ubuntu uses powersave governor as the default.While the powersave governor has much lower power, the performance is lower than +25% for several workloads compared to performance governor. Report is published: www.Phoronix.com showing difference of 37% The goal here is to keep mean performance delta of powersave governor from performance governor around 10% to 12% by running wide variety of server workloads. For some bursty workload, this delta can be still large, as ramp up of frequency will still lag with powersave governor irrespective of EPP setting. The performance governor always requests maximum frequency. Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for powersave governor is around 12%. But the EPP 0x20 has 18% lower average power. Also experiments are done by raising intel_pstate sysfs min_perf_pct as high as 50%. This didn't bring in any additional improvements compared to just changing EPP. Target Kernel: 6.3 Target Release: 22.04 (5.15 kernel) [HW/SW Information] Sapphire Rapids [Business Justification] Performance Improvements Upstream: Merged 6.3 Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed"
- SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is
initialized"
-- Andrea Righi Wed, 15 Mar 2023 23:54:18
+0100
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009024] Re: Fail to output sound to external monitor which connects via docking station
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009024 Title: Fail to output sound to external monitor which connects via docking station Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] No sound output from the external monitor which connect via some docking station. It only happens when user boot the system with docking station connected. Re-plug the docking station can fix this issue. Or plug the docking station later won't trigger this problem. [Fix] Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start sending an "audio keepalive" to the monitor as soon as it is connected. [Test] Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the system with the dock connected. Play sound via HDMI/DP port and check if there's any audio output from the external monitor. [Where problems could occur] It sends the "audio keepalive"(silent stream) to the monitor when connected. Doesn't affect original workflow of the audio system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009127] Re: Lunar update: v6.2.1 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2009127 Title: Lunar update: v6.2.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.1 upstream stable release from git://git.kernel.org/ uaccess: Add speculation barrier to copy_from_user() x86/alternatives: Introduce int3_emulate_jcc() x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions x86/static_call: Add support for Jcc tail-calls HID: mcp-2221: prevent UAF in delayed work wifi: mwifiex: Add missing compatible string for SD8787 audit: update the mailing list in MAINTAINERS platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY platform/x86: nvidia-wmi-ec-backlight: Add force module parameter ext4: Fix function prototype mismatch for ext4_feat_ktype randstruct: disable Clang 15 support bpf: add missing header file include Linux 6.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2009283 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: [Impact] CONFIG_SERIAL_8250_MID=y is required to properly use the serial console on some platforms that are using the "mid" serial driver (such as some Intel SoC platforms). The generic kernel should build this driver statically to make sure we properly support these platforms. [Test case] Boot the Ubuntu generic kernel on a system that is using the "mid" serial driver (e.g, no PCI serial). [Fix] Enable CONFIG_SERIAL_8250_MID=y. [Regression potential] Kernel footprint is increased a bit with this change (around +9K), so we may see little performance regressions at boot time in really small platforms (additional memory usage is probably negligible), but it is worth it, otherwise we won't be able to properly support these platforms. NOTE: we may want to disable this option in the could kernels and derivatives and keep it only for the generic. [Original bug report] Starting from 5.19 HWE kernel, this option became as dedicated module instead of being compiled into the kernel. 5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m On 5.15 it was OK ~$ uname -r 5.19.0-32-generic $ cat /boot/config-5.19.0-32-generic | grep 8250_MID CONFIG_SERIAL_8250_MID=m Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels. Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338 Some discussion: https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009355] Re: linux-libc-dev is no longer multi-arch safe
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2009355 Title: linux-libc-dev is no longer multi-arch safe Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack): trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386 I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch /install /scripts. But these files are different on different arch (or different build, since it embeds build path) ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <== cmd_arch/x86/include/generated/asm/syscalls_32.h := sh /build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 /build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl arch/x86/include/generated/asm/syscalls_32.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009358] Re: Lunar update: v6.2.2 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2009358 Title: Lunar update: v6.2.2 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.2 upstream stable release from git://git.kernel.org/ Linux 6.2.2 USB: core: Don't hold device lock while reading the "descriptors" sysfs file usb: typec: pd: Remove usb_suspend_supported sysfs from sink PDO arm64: dts: uniphier: Fix property name in PXs3 USB node usb: gadget: u_serial: Add null pointer check in gserial_resume USB: serial: option: add support for VW/Skoda "Carstick LTE" usb: dwc3: pci: add support for the Intel Meteor Lake-M wifi: rtw88: usb: drop now unnecessary URB size check wifi: rtw88: usb: send Zero length packets if necessary wifi: rtw88: usb: Set qsel correctly scripts/tags.sh: fix incompatibility with PCRE2 drm/amd/display: Properly reuse completion structure drm/amd/display: Move DCN314 DOMAIN power control to DMCUB vc_screen: don't clobber return value in vcs_read bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state crypto: arm64/sm4-gcm - Fix possible crash in GCM cryption ALSA: hda: cs35l41: Correct error condition handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009642] Re: mt7921: add support of MTFG table
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => 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/2009642 Title: mt7921: add support of MTFG table Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver to enable 6G power enhance feature. [Fix] Add MTFG table in driver and update firmware to support it. Lunar already got the firmware, so SRU for Jammy only. Kernel commit is a new feature and it requests more than 10 unrelated commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version. [Test] Verified WiFi on 2.4/5GHz only because of no 6G environment. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011379] Re: Speaker / Audio/Mic mute LED don't work on a HP platform
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011379 Title: Speaker / Audio/Mic mute LED don't work on a HP platform Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The speaker / audio/mic mute LEDs don't work on a HP platform. [Fix] This is HP platform needs ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED quirk to make mic-mute/audio-mute/speaker working. [Test] After applying the fix, the speaker / audio/mic mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then these functions may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011413] Re: lunar/linux 6.2 fails to boot on ppc64el
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed"
- SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is
initialized"
-- Andrea Righi Wed, 15 Mar 2023 23:54:18
+0100
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => 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/2011413
Title:
lunar/linux 6.2 fails to boot on ppc64el
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Try to boot the latest lunar/linux 6.2.0-16.16 on a ppc64 VM triggers
the following bug at boot:
event-sources: Unable to request interrupt 23 for
/event-sources/hot-plug-events
WARNING: CPU: 0 PID: 1 at arch/powerpc/platforms/pseries/event_sources.c:26
request_event_sources_irqs+0xbc/0xf0
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 6.2.2-kc #1
Hardware name: IBM pSeries (emulated by qemu) POWER9 (raw) 0x4e1200 0xf05
of:SLOF,HEAD pSeries
NIP: c2022eec LR: c2022ee8 CTR:
REGS: c3483910 TRAP: 0700 Tainted: GW (6.2.2-kc)
MSR: 82029033 CR: 24483200 XER:
CFAR: c0180838 IRQMASK: 0
GPR00: c2022ee8 c3483bb0 c1a5ce00 0050
GPR04: c2437d78 c2437e28 0001 0001
GPR08: c2437d00 0001 44483200
GPR12: c272 c0012758
GPR16:
GPR20:
GPR24: c20033fc cccd c00e07f0
GPR28: c0db0520 c000fff92ac0 0017
NIP [c2022eec] request_event_sources_irqs+0xbc/0xf0
LR [c2022ee8] request_event_sources_irqs+0xb8/0xf0
Call Trace:
[c3483bb0] [c2022ee8] request_event_sources_irqs+0xb8/0xf0
(unreliable)
[c3483c40] [c2022fa0]
__machine_initcall_pseries_init_ras_hotplug_IRQ+0x80/0xb0
[c3483c70] [c00121b8] do_one_initcall+0x98/0x300
[c3483d50] [c2004b28] kernel_init_freeable+0x2ec/0x370
[c3483df0] [c0012780] kernel_init+0x30/0x190
[c3483e50] [c000cf5c] ret_from_kernel_thread+0x5c/0x64
--- interrupt: 0 at 0x0
[Test case]
Simply boot the kernel in a ppc64 vm.
[Fix]
Bisecting the problem shows that the commit that introduced the bug is
the following:
baa49d81a94b ("powerpc/pseries: hvcall stack frame overhead")
To fix the problem we just need to revert this commit and also the
following (because we need to re-introduce STACK_FRAME_OVERHEAD):
dfecd06bc552 ("powerpc: remove STACK_FRAME_OVERHEAD")
[Regression potential]
This restores a previous behavior on powerpc and without this it's
impossible to boot. However, we are likely to get a proper fix
upstream, so reverting the commit should be considered only as a
temporary workaround, until we get a proper upstream fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011413/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011425] Re: Lunar update: v6.2.3 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2011425 Title: Lunar update: v6.2.3 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.3 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011428] Re: Lunar update: v6.2.4 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2011428 Title: Lunar update: v6.2.4 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.4 upstream stable release from git://git.kernel.org/ Linux 6.2.4 Revert "blk-cgroup: dropping parent refcount after pd_free_fn() is done" Revert "blk-cgroup: synchronize pd_free_fn() from blkg_free_workfn() and blkcg_deactivate_policy()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011430] Re: Lunar update: v6.2.5 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2011430 Title: Lunar update: v6.2.5 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.5 upstream stable release from git://git.kernel.org/ Linux 6.2.5 usb: gadget: uvc: fix missing mutex_unlock() if kstrtou8() fails arm64: efi: Make efi_rt_lock a raw_spinlock media: uvcvideo: Fix race condition with usb_kill_urb drm/i915: Fix system suspend without fbdev being initialized drm/i915/dp_mst: Fix payload removal during output disabling drm/display/dp_mst: Handle old/new payload states in drm_dp_remove_payload() drm/i915/dp_mst: Add the MST topology state for modesetted CRTCs drm/display/dp_mst: Fix payload addition on a disconnected sink drm/display/dp_mst: Fix down message handling after a packet reception error drm/display/dp_mst: Fix down/up message handling after sink disconnect drm/display/dp_mst: Add drm_atomic_get_old_mst_topology_state() vDPA/ifcvf: allocate the adapter in dev_add() vDPA/ifcvf: manage ifcvf_hw in the mgmt_dev vDPA/ifcvf: ifcvf_request_irq works on ifcvf_hw vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator from the adapter vDPA/ifcvf: decouple vq irq requester from the adapter vDPA/ifcvf: decouple config IRQ releaser from the adapter vDPA/ifcvf: decouple vq IRQ releasers from the adapter vDPA/ifcvf: alloc the mgmt_dev before the adapter vDPA/ifcvf: decouple config space ops from the adapter vDPA/ifcvf: decouple hw features manipulators from the adapter x86/resctl: fix scheduler confusion with 'current' net: tls: avoid hanging tasks on the tx_lock eth: fealnx: bring back this old driver soundwire: cadence: Drain the RX FIFO after an IO timeout soundwire: cadence: Remove wasted space in response_buf RDMA/cma: Distinguish between sockaddr_in and sockaddr_in6 by size phy: rockchip-typec: Fix unsigned comparison with less than zero PCI: pciehp: Add Qualcomm quirk for Command Completed erratum PCI: Add ACS quirk for Wangxun NICs PCI: loongson: Add more devices that need MRRS quirk kernel/fail_function: fix memory leak with using debugfs_lookup() drivers: base: dd: fix memory leak with using debugfs_lookup() drivers: base: component: fix memory leak with using debugfs_lookup() misc: vmw_balloon: fix memory leak with using debugfs_lookup() tty: pcn_uart: fix memory leak with using debugfs_lookup() PCI: Distribute available resources for root buses, too PCI: Take other bus devices into account when distributing resources PCI: Align extra resources for hotplug bridges properly usb: gadget: uvc: Make bSourceID read/write usb: uvc: Enumerate valid values for color matching USB: ene_usb6250: Allocate enough memory for full object usb: host: xhci: mvebu: Iterate over array indexes instead of using pointer math USB: gadget: pxa27x_udc: fix memory leak with using debugfs_lookup() USB: gadget: pxa25x_udc: fix memory leak with using debugfs_lookup() USB: gadget: lpc32xx_udc: fix memory leak with using debugfs_lookup() USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup() USB: gadget: gr_udc: fix memory leak with using debugfs_lookup() USB: isp1362: fix memory leak with using debugfs_lookup() USB: isp116x: fix memory leak with using debugfs_lookup() USB: fotg210: fix memory leak with using debugfs_lookup() USB: sl811: fix memory leak with using debugfs_lookup() USB: uhci: fix memory leak with using debugfs_lookup() USB: ULPI: fix memory leak with using debugfs_lookup() USB: chipidea: fix memory leak with using debugfs_lookup() USB: dwc3: fix memory leak with using debugfs_lookup() staging: pi433: fix memory leak with using debugfs_lookup() PCI: loongson: Prevent LS7A MRRS
[Kernel-packages] [Bug 2011431] Re: Lunar update: v6.2.6 upstream stable release
This bug was fixed in the package linux - 6.2.0-18.18 --- linux (6.2.0-18.18) lunar; urgency=medium * lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750) * lunar/linux 6.2 fails to boot on arm64 (LP: #2011748) - SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed" - SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is initialized" -- Andrea Righi Wed, 15 Mar 2023 23:54:18 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => 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/2011431 Title: Lunar update: v6.2.6 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.6 upstream stable release from git://git.kernel.org/ Linux 6.2.6 staging: rtl8192e: Remove call_usermodehelper starting RadioPower.sh staging: rtl8192e: Remove function ..dm_check_ac_dc_power calling a script wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free for wext" tpm: disable hwrng for fTPM on some AMD designs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011748] Re: lunar/linux 6.2 fails to boot on arm64
This bug was fixed in the package linux - 6.2.0-18.18
---
linux (6.2.0-18.18) lunar; urgency=medium
* lunar/linux: 6.2.0-18.18 -proposed tracker (LP: #2011750)
* lunar/linux 6.2 fails to boot on arm64 (LP: #2011748)
- SAUCE: Revert "efi: random: fix NULL-deref when refreshing seed"
- SAUCE: Revert "efi: random: refresh non-volatile random seed when RNG is
initialized"
-- Andrea Righi Wed, 15 Mar 2023 23:54:18
+0100
** Changed in: linux (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2011748
Title:
lunar/linux 6.2 fails to boot on arm64
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind)
idle=b10c/1/0x4000 softirq=164/164 fqs=6443
[ 72.058520] (detected by 28, t=15005 jiffies, g=449, q=174 ncpus=32)
[ 72.064949] Task dump for CPU 22:
[ 72.068251] task:kworker/u64:5 state:R running task stack:0
pid:447 ppid:2 flags:0x000a
[ 72.078156] Workqueue: efi_rts_wq efi_call_rts
[ 72.082595] Call trace:
[ 72.085029] __switch_to+0xbc/0x100
The bug doesn't seem to happen on arm64 virtual machines, it happens
only on physical arm64 systems.
This regression has been introduced by:
e7b813b32a42 ("efi: random: refresh non-volatile random seed when RNG
is initialized")
[Test case]
Boot the kernel on a physical arm64 board (i.e., kuzzle in our lab).
[Fix]
Revert commit e7b813b32a42 for now, at the same time address this
issue upstream in order to find a proper fix.
[Regression potential]
We may want to address this upstream to find a proper fix. Reverting
the commit restores the previous behavior, but we also lose the
capability of having a better RNG on the affected arm64 hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008824] Re: sched: cpumask: improve on cpumask_local_spread() locality
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008824 Title: sched: cpumask: improve on cpumask_local_spread() locality Status in linux package in Ubuntu: In Progress Bug description: A patch series landed upstream during the v6.3 merge window that shows impressive performance improvements in iperf3 multi-stream performance on NUMA based systems w/ Mellanox network controllers: https://www.spinics.net/lists/linux-rdma/msg115357.html It would be valuable to land those in lunar, allowing our LTS users to adopt them more quickly starting with the HWE kernel in 22.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y
Hello! Thanks for addressing this issue. Will this fix reach jammy HWE kernel at some point? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009283 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: [Impact] CONFIG_SERIAL_8250_MID=y is required to properly use the serial console on some platforms that are using the "mid" serial driver (such as some Intel SoC platforms). The generic kernel should build this driver statically to make sure we properly support these platforms. [Test case] Boot the Ubuntu generic kernel on a system that is using the "mid" serial driver (e.g, no PCI serial). [Fix] Enable CONFIG_SERIAL_8250_MID=y. [Regression potential] Kernel footprint is increased a bit with this change (around +9K), so we may see little performance regressions at boot time in really small platforms (additional memory usage is probably negligible), but it is worth it, otherwise we won't be able to properly support these platforms. NOTE: we may want to disable this option in the could kernels and derivatives and keep it only for the generic. [Original bug report] Starting from 5.19 HWE kernel, this option became as dedicated module instead of being compiled into the kernel. 5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m On 5.15 it was OK ~$ uname -r 5.19.0-32-generic $ cat /boot/config-5.19.0-32-generic | grep 8250_MID CONFIG_SERIAL_8250_MID=m Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels. Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338 Some discussion: https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-iot/5.4.0-1013.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-iot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-iot/5.4.0-1013.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-iot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
With 5.19.9000-37-generic my HDMI sound is back! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002984] Re: [UBUNTU 20.04] zfcp: fix double free of FSF request when qdio send fails
*** This bug is a duplicate of bug 2002256 ***
https://bugs.launchpad.net/bugs/2002256
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002984
Title:
[UBUNTU 20.04] zfcp: fix double free of FSF request when qdio send
fails
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description: zfcp: fix double free of FSF request when qdio send
fails
Symptom: When doing maintenance actions on FCP devices that turn off a
FCP device while I/O is still running on it in Linux - for
example turning off the channel path of the FCP device - the
Linux kernel crashes.
Problem: We used to use the wrong type of integer in
'zfcp_fsf_req_send()' to cache the FSF request ID when sending
a
new FSF request. This is used in case the sending fails and we
need to remove the request from our internal hash table again
(so we don't keep an invalid reference and use it when we free
the request again).
In 'zfcp_fsf_req_send()' we used to cache the ID as 'int'
(signed and 32 bit wide), but the rest of the zfcp code (and
the
firmware specification) handles the ID as 'unsigned long'/'u64'
(unsigned and 64 bit wide [s390x ELF ABI]).
For one this has the obvious problem that when the ID grows
past 32 bit (this can happen reasonably fast) it is truncated
to
32 bit when storing it in the cache variable and so doesn't
match the original ID anymore.
The second less obvious problem is that even when the
original ID has not yet grown past 32 bit, as soon as the 32nd
bit is set in the original ID (0x8000 = 2'147'483'648) we
will have a mismatch when we cast it back to 'unsigned long'
because casting the signed type 'int' into the wider type
'unsigned long' will use a sign-extending instruction, and so
flip all leading zeros to one instead.
If we can't successfully remove the request from the hash table
again after 'zfcp_qdio_send()' fails (this happens regularly
when zfcp cannot notify the adapter about new work because the
adapter is already gone during e.g. a ChpID toggle) we will end
up with a double free.
We unconditionally free the request in the calling function
when 'zfcp_fsf_req_send()' fails, but because the request is
still in the hash table we end up with a stale memory
reference,
and once the zfcp adapter is either reset during recovery or
shutdown we end up freeing the same memory twice.
Solution: To fix this, simply change the type of the cache variable to
'unsigned long', like the rest of zfcp and also the argument
for
'zfcp_reqlist_find_rm()'. This prevents truncation and wrong
sign extension and so can successfully remove the request from
the hash table.
Reproduction: Run I/O on a FCP device for so long that you have sent
2'147'483'648 requests. The current request number can not be
read directly from user space, but can be read indirectly by
using 'zfcp_ping' and 'zfcpdbf' (use the correct
device-bus-ID):
sudo sh -c 'zfcp_ping -a "${0}" 0x \
2>/dev/null 1>&2; zfcpdbf "${0}" -x all -i SAN 2>/dev/null
\
| grep -E -e "^(Timestamp|Request ID)[[:blank:]]+:" | tail
\
-n2' 0.0.1700
After having reached 0x8000 requests, stop all I/O on the
FCP device and start only a single process doing
single-threaded
synchronous, direct I/O on the FCP device (always only one
outstanding I/O operation).
While this I/O process is running, turn of the channel path
(ChpID) that is used for the FCP device/subchannel. This will
not always trigger the bug, but occasionally it will.
Proof that it hit the correct code-path in zfcp can be
found
by using 'zfcpdbf' again (use the correct device-bus-ID):
zfcpdbf 0.0.1700 -x all -i REC 2>/dev/null | grep
'fsrs__1'
In case you hit the correct code-path this will print some
lines
starting with 'Tag'.
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
Released with jammy/linux-azure 5.15.0-1035.42 ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: In Progress Status in linux-aws source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress Status in linux-gcp source package in Kinetic: New Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
Released with jammy/linux-aws 5.15.0-1032.36 ** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: In Progress Status in linux-aws source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress Status in linux-gcp source package in Kinetic: New Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
The issue has been observed with 5.19 kernels on Amazon and Azure ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: In Progress Status in linux-aws source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress Status in linux-gcp source package in Kinetic: New Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2002984] Re: [UBUNTU 20.04] zfcp: fix double free of FSF request when qdio send fails
*** This bug is a duplicate of bug 2002256 ***
https://bugs.launchpad.net/bugs/2002256
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
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/2002984
Title:
[UBUNTU 20.04] zfcp: fix double free of FSF request when qdio send
fails
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description: zfcp: fix double free of FSF request when qdio send
fails
Symptom: When doing maintenance actions on FCP devices that turn off a
FCP device while I/O is still running on it in Linux - for
example turning off the channel path of the FCP device - the
Linux kernel crashes.
Problem: We used to use the wrong type of integer in
'zfcp_fsf_req_send()' to cache the FSF request ID when sending
a
new FSF request. This is used in case the sending fails and we
need to remove the request from our internal hash table again
(so we don't keep an invalid reference and use it when we free
the request again).
In 'zfcp_fsf_req_send()' we used to cache the ID as 'int'
(signed and 32 bit wide), but the rest of the zfcp code (and
the
firmware specification) handles the ID as 'unsigned long'/'u64'
(unsigned and 64 bit wide [s390x ELF ABI]).
For one this has the obvious problem that when the ID grows
past 32 bit (this can happen reasonably fast) it is truncated
to
32 bit when storing it in the cache variable and so doesn't
match the original ID anymore.
The second less obvious problem is that even when the
original ID has not yet grown past 32 bit, as soon as the 32nd
bit is set in the original ID (0x8000 = 2'147'483'648) we
will have a mismatch when we cast it back to 'unsigned long'
because casting the signed type 'int' into the wider type
'unsigned long' will use a sign-extending instruction, and so
flip all leading zeros to one instead.
If we can't successfully remove the request from the hash table
again after 'zfcp_qdio_send()' fails (this happens regularly
when zfcp cannot notify the adapter about new work because the
adapter is already gone during e.g. a ChpID toggle) we will end
up with a double free.
We unconditionally free the request in the calling function
when 'zfcp_fsf_req_send()' fails, but because the request is
still in the hash table we end up with a stale memory
reference,
and once the zfcp adapter is either reset during recovery or
shutdown we end up freeing the same memory twice.
Solution: To fix this, simply change the type of the cache variable to
'unsigned long', like the rest of zfcp and also the argument
for
'zfcp_reqlist_find_rm()'. This prevents truncation and wrong
sign extension and so can successfully remove the request from
the hash table.
Reproduction: Run I/O on a FCP device for so long that you have sent
2'147'483'648 requests. The current request number can not be
read directly from user space, but can be read indirectly by
using 'zfcp_ping' and 'zfcpdbf' (use the correct
device-bus-ID):
sudo sh -c 'zfcp_ping -a "${0}" 0x \
2>/dev/null 1>&2; zfcpdbf "${0}" -x all -i SAN 2>/dev/null
\
| grep -E -e "^(Timestamp|Request ID)[[:blank:]]+:" | tail
\
-n2' 0.0.1700
After having reached 0x8000 requests, stop all I/O on the
FCP device and start only a single process doing
single-threaded
synchronous, direct I/O on the FCP device (always only one
outstanding I/O operation).
While this I/O process is running, turn of the channel path
(ChpID) that is used for the FCP device/subchannel. This will
not always trigger the bug, but occasionally it will.
Proof that it hit the correct code-path in zfcp can be
found
[Kernel-packages] [Bug 2002256] Re: [UBUNTU 22.04] zfcp: fix double free of FSF request when qdio send fails
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002256
Title:
[UBUNTU 22.04] zfcp: fix double free of FSF request when qdio send
fails
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
Description: zfcp: fix double free of FSF request when qdio send fails
Symptom: When doing maintenance actions on FCP devices that turn off a
FCP device while I/O is still running on it in Linux - for
example turning off the channel path of the FCP device - the
Linux kernel crashes.
Problem: We used to use the wrong type of integer in
'zfcp_fsf_req_send()' to cache the FSF request ID when sending
a
new FSF request. This is used in case the sending fails and we
need to remove the request from our internal hash table again
(so we don't keep an invalid reference and use it when we free
the request again).
In 'zfcp_fsf_req_send()' we used to cache the ID as 'int'
(signed and 32 bit wide), but the rest of the zfcp code (and
the
firmware specification) handles the ID as 'unsigned long'/'u64'
(unsigned and 64 bit wide [s390x ELF ABI]).
For one this has the obvious problem that when the ID grows
past 32 bit (this can happen reasonably fast) it is truncated
to
32 bit when storing it in the cache variable and so doesn't
match the original ID anymore.
The second less obvious problem is that even when the
original ID has not yet grown past 32 bit, as soon as the 32nd
bit is set in the original ID (0x8000 = 2'147'483'648) we
will have a mismatch when we cast it back to 'unsigned long'
because casting the signed type 'int' into the wider type
'unsigned long' will use a sign-extending instruction, and so
flip all leading zeros to one instead.
If we can't successfully remove the request from the hash table
again after 'zfcp_qdio_send()' fails (this happens regularly
when zfcp cannot notify the adapter about new work because the
adapter is already gone during e.g. a ChpID toggle) we will end
up with a double free.
We unconditionally free the request in the calling function
when 'zfcp_fsf_req_send()' fails, but because the request is
still in the hash table we end up with a stale memory
reference,
and once the zfcp adapter is either reset during recovery or
shutdown we end up freeing the same memory twice.
Solution: To fix this, simply change the type of the cache variable to
'unsigned long', like the rest of zfcp and also the argument
for
'zfcp_reqlist_find_rm()'. This prevents truncation and wrong
sign extension and so can successfully remove the request from
the hash table.
Reproduction: Run I/O on a FCP device for so long that you have sent
2'147'483'648 requests. The current request number can not be
read directly from user space, but can be read indirectly by
using 'zfcp_ping' and 'zfcpdbf' (use the correct
device-bus-ID):
sudo sh -c 'zfcp_ping -a "${0}" 0x \
2>/dev/null 1>&2; zfcpdbf "${0}" -x all -i SAN 2>/dev/null
\
| grep -E -e "^(Timestamp|Request ID)[[:blank:]]+:" | tail
\
-n2' 0.0.1700
After having reached 0x8000 requests, stop all I/O on the
FCP device and start only a single process doing
single-threaded
synchronous, direct I/O on the FCP device (always only one
outstanding I/O operation).
While this I/O process is running, turn of the channel path
(ChpID) that is used for the FCP device/subchannel. This will
not always trigger the bug, but
[Kernel-packages] [Bug 2008217] Re: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201)
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2008217 Title: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201) Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Summary] The system will auto wake from suspend with bluetooth connected. Note: 1. BT headset, BT Keyboard and BT mouse all can duplicate 2. RTL 8852BE & Intel AX201 cannot duplicate [Steps to reproduce] 1. Install dell-bto-jammy-jellyfish-quilladin-X72-20230216-17.iso 2. Boot to OS 3. Pair the bluetooth headset device. 4. Enter suspend. [Expected result] The system will not auto wake when the bluetooth device is connected. [Actual result] The system will auto wake from suspend with bluetooth connected. [Failure rate] 3/10 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2000708] Re: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper)
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2000709] Re: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2004602] Re: Kinetic update: upstream stable patchset 2023-02-02
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux - 5.19.0-38.39 --- linux (5.19.0-38.39) kinetic; urgency=medium * kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.19.0-37.38) kinetic; urgency=medium * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342 composition - mm/khugepaged: take the right locks for page table retraction - mm/khugepaged: fix GUP-fast
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux-aws - 5.19.0-1022.23 --- linux-aws (5.19.0-1022.23) kinetic; urgency=medium * kinetic/linux-aws: 5.19.0-1022.23 -proposed tracker (LP: #2011996) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux-aws (5.19.0-1021.22) kinetic; urgency=medium * kinetic/linux-aws: 5.19.0-1021.22 -proposed tracker (LP: #2008287) [ Ubuntu: 5.19.0-37.38 ] * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event - btrfs: send: avoid unaligned encoded writes when attempting to clone range - ASoC: soc-pcm: Add NULL check in BE reparenting - regulator: twl6030: fix get status of twl6032 regulators - fbcon: Use kzalloc() in fbcon_prepare_logo() - usb: dwc3: gadget: Disable GUSB2PHYCFG.SUSPHY for End Transfer - 9p/xen: check logical size for buffer size - net: usb: qmi_wwan: add u-blox 0x1342
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
>From cloud-init perspective, we have seen this too in our CI/CD
integration runs on both GCP and Azure lunar daily images which allows
cloud-init to resize2fs /dev/root on first boot, but also re-invokes
resize2fs a second time to assert cloud-init can be re-run all boot
stages without having to reboot[1] This 2nd run of cloud-init invokes
resize2fs /dev/root a second time.
This failure is resize2fs a second time due to checksums is seen only on
Azure lunar daily images containing linux-azure=5.19.0.1010.9 and
e2fsprogs=1.47.0. e2fsprogs=1.47.0 was introduced in Azure daily lunar
images on image version 23.04.202303170 (image version 23.04.202303170
allows multiple calls to resize2fs /dev/root without checksum errors)
GCP: CI/CD runners in cloud-init also started failing jobs on Mar 17th as well,
presumably across the same image build update and introduction of
esfsprogs=1.47.0 in lunar.
Our internal daily test runners track this failure signal well from daily image
builds for Azure[2] and GCP lunar[3] giving us a good signal the the failure
symptom below. We can ensure
'cloudinit.subp.ProcessExecutionError: Unexpected error while running '
'command.\n'
"Command: ('resize2fs', '/dev/root')\n"
'Exit code: 1\n'
'Reason: -\n'
"Stdout: Couldn't find valid filesystem superblock.\n"
'Stderr: resize2fs 1.47.0 (5-Feb-2023)\n'
'resize2fs: Superblock checksum does not match superblock while '
'trying to open /dev/root\n'
references:
[1] cloud-init integration test which triggers multiple resize2fs /dev/root
calls
https://github.com/canonical/cloud-init/blob/main/tests/integration_tests/test_upgrade.py#L91-L105
[2]
https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-lunar-azure/
[3]
https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-lunar-gce/
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
Title:
Regression in ext4 during online resize
Status in cloud-init package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-azure package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Invalid
Status in cloud-init source package in Jammy:
New
Status in linux source package in Jammy:
Fix Committed
Status in linux-azure source package in Jammy:
New
Status in linux-gcp source package in Jammy:
Fix Released
Bug description:
Issue
resize2fs utility is used to resize the filesystem and is idempotent
in nature. But in the 5.15 kernel, successive execution of resize2fs
is returning error.
Reproduction step (on AWS):
Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
Increase the size of EBS volume.
Run sudo resize2fs /dev/xvdb multiple times.
The first execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 3
The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.
The following execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
The filesystem is already 5242880 (4k) blocks long. Nothing to do!
When you run the same step on the latest image ami-0a1d6d351894df6cc
(Linux 5.15.0-1026-aws).
The first execution returns -
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 3
The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.
The following execution returns
$ sudo resize2fs /dev/xvdb
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/xvdb
Couldn't find valid filesystem superblock.
FIX:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
Added linux-azure task here too to track that it also affects that kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: New Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: New Status in linux-gcp source package in Jammy: Fix Released Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
FYI, bit of a necro -- we're seeing this currently on the 20.04 5.15 kernel and the 23.04 5.19 kernel. I haven't checked on the proposed 6.2 kernel yet. this can be reproduced on AWS Reproduction step: 1. Create an AWS instance with AMI `ami-056a67ea1b8ffa0fc` (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. 2. Format and mount the disk - `sudo mkfs.ext4 /dev/xvdb`, `sudo mkdir -p /mnt/ssd0`, `sudo mount /dev/xvdb /mnt/ssd0` 3. Increase the size of EBS volume. 4. Run `sudo resize2fs /dev/xvdb` multiple times. The first execution returns - ``` $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. ``` The following execution returns - ``` $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! ``` When you run the same step on the latest image `ami-0a1d6d351894df6cc` (Linux 5.15.0-1026-aws). The first execution returns - ``` $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. ``` The following execution returns ``` $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012522] [NEW] package linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-32-generic package po
Public bug reported: unable to install nvidia packages ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: finger:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 22 16:13:34 2023 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-31 (49 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012522 Title: package linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux- modules-nvidia-525-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: unable to install nvidia packages ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: finger:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 22 16:13:34 2023 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-31 (49 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-525-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2012522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012520] Re: USB3 to ethernet adapter stops working (ax88179)
Following trace is also obtained: [18818.672366] [ cut here ] [18818.672374] NETDEV WATCHDOG: enxf8e43b7bdd6c (ax88179_178a): transmit queue 0 timed out [18818.672422] WARNING: CPU: 3 PID: 38259 at net/sched/sch_generic.c:529 dev_watchdog+0x21f/0x230 [18818.672437] Modules linked in: cdc_mbim cdc_wdm cdc_ncm cdc_ether tls snd_seq_dummy ccm nft_masq nft_chain_nat nf_nat nvme_fabrics bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt cmac algif_hash algif_skcipher af_alg bnep ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment xt_recent xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack snd_hda_codec_hdmi nf_defrag_ipv6 snd_sof_pci_intel_cnl nf_defrag_ipv4 snd_sof_intel_hda_common nft_compat soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek snd_soc_acpi soundwire_bus snd_hda_codec_generic ledtrig_audio snd_soc_core [18818.672556] snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec intel_tcc_cooling nf_tables snd_hda_core x86_pkg_temp_thermal intel_powerclamp btusb coretemp nfnetlink binfmt_misc snd_hwdep btrtl snd_pcm btbcm iwlmvm uvcvideo btintel kvm_intel snd_seq_midi btmtk mei_hdcp mei_pxp snd_seq_midi_event mac80211 videobuf2_vmalloc kvm libarc4 snd_rawmidi videobuf2_memops bluetooth videobuf2_v4l2 snd_seq videobuf2_common rapl snd_seq_device videodev ecdh_generic intel_cstate nls_iso8859_1 snd_timer input_leds mc joydev ecc iwlwifi snd cmdlinepart serio_raw intel_wmi_thunderbolt spi_nor mei_me mtd cfg80211 soundcore mei intel_pch_thermal intel_hid mac_hid sparse_keymap acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid ax88179_178a usbnet mii i915 drm_bud dy [18818.672677] i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc nvme i2c_i801 spi_intel_pci fb_sys_fops crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd xhci_pci psmouse nvme_core r8169 i2c_smbus spi_intel realtek thunderbolt rtsx_pci drm ahci libahci xhci_pci_renesas wmi video [18818.672720] CPU: 3 PID: 38259 Comm: skypeforlinux Tainted: P OE 5.19.0-35-generic #36~22.04.1-Ubuntu [18818.672726] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [18818.672729] RIP: 0010:dev_watchdog+0x21f/0x230 [18818.672738] Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 ef ac 70 01 01 e8 c6 9d f8 ff 44 89 f1 4c 89 e6 48 c7 c7 a8 da d0 b0 48 89 c2 e8 89 e3 1b 00 <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [18818.672741] RSP: :a020869bbdb0 EFLAGS: 00010246 [18818.672746] RAX: RBX: 8e955101a4c8 RCX: [18818.672749] RDX: RSI: RDI: [18818.672751] RBP: a020869bbdd8 R08: R09: [18818.672754] R10: R11: R12: 8e955101a000 [18818.672756] R13: 8e955101a41c R14: R15: [18818.672759] FS: 7f5bfb1b9640() GS:8e96706c() knlGS: [18818.672762] CS: 0010 DS: ES: CR0: 80050033 [18818.672765] CR2: 0e0819391000 CR3: 000199538006 CR4: 003706e0 [18818.672768] Call Trace: [18818.672771] [18818.672776] ? pfifo_fast_reset+0x170/0x170 [18818.672784] call_timer_fn+0x29/0x160 [18818.672789] ? pfifo_fast_reset+0x170/0x170 [18818.672795] __run_timers.part.0+0x1e9/0x290 [18818.672799] ? ktime_get+0x43/0xc0 [18818.672805] ? lapic_next_deadline+0x2c/0x50 [18818.672811] ? clockevents_program_event+0xb2/0x140 [18818.672818] run_timer_softirq+0x2a/0x60 [18818.672822] __do_softirq+0xd5/0x32a [18818.672827] ? hrtimer_interrupt+0x12b/0x240 [18818.672832] __irq_exit_rcu+0x8d/0xd0 [18818.672839] irq_exit_rcu+0xe/0x20 [18818.672845] sysvec_apic_timer_interrupt+0x43/0xb0 [18818.672851] asm_sysvec_apic_timer_interrupt+0x1b/0x20 [18818.672858] RIP: 0033:0x7f5c198a5a75 [18818.672862] Code: 3c 45 31 c0 90 0f b6 14 16 48 83 c1 01 41 83 c0 01 48 83 c6 01 41 0f af d1 41 89 d7 0f b6 56 ff 41 0f af d2 44 01 fa c1 fa 10 <88> 51 ff 48 63 57 3c 44 39 c2 7f cf 4c 8b 87 a8 00 00 00 41 83 c5 [18818.672866] RSP: 002b:7f5bfb1b81b8 EFLAGS: 0206 [18818.672869] RAX: 018ad4f2 RBX: 0001 RCX: 0e08104959d1
[Kernel-packages] [Bug 2012520] [NEW] USB3 to ethernet adapter stops working (ax88179)
Public bug reported: On a machine with the ax88179 USB3 ethernet adapter, the adapter works poorly. As long as there is a moderate usage of the ethernet connection everything seems to work fine. As soon as the usage pattern changes and a continuous throughput is required (typical case teleconferencing via teams, skype, etc) the adapter stops working and the following line gets repeated many many times in the system logs: ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 22 15:35:38 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (1130 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012520 Title: USB3 to ethernet adapter stops working (ax88179) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On a machine with the ax88179 USB3 ethernet adapter, the adapter works poorly. As long as there is a moderate usage of the ethernet connection everything seems to work fine. As soon as the usage pattern changes and a continuous throughput is required (typical case teleconferencing via teams, skype, etc) the adapter stops working and the following line gets repeated many many times in the system logs: ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 22 15:35:38 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (1130 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
HPE has tested this and hasn't seen any issues. ** Changed in: linux (Ubuntu Jammy) 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] [Where Problems Could Occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1998544_hpwdt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm
** Also affects: autopkgtest (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: autopkgtest (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2009436
Title:
dkms modules are not built anymore for linux-kvm
Status in autopkgtest package in Ubuntu:
Invalid
Status in dkms package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
Invalid
Status in autopkgtest source package in Jammy:
New
Status in dkms source package in Jammy:
New
Status in linux-kvm source package in Jammy:
New
Status in autopkgtest source package in Kinetic:
New
Status in dkms source package in Kinetic:
New
Status in linux-kvm source package in Kinetic:
New
Bug description:
SRU Justification
[Impact]
Some dkms modules are not built anymore when a retry is triggred from adt
matrix page.
It was noticed because these modules previously failed during build (because
a config options is disabled) but now they pass (artificial pass).
Affected modules:
1. digimend-dkms
2. oss4
3. rtl8812au
4. rtl8812ce
Looking at digimend-dkms for jammy:linux-kvm, first time the test was correct
(it failed) was when the new kernel was just pushed to proposed and adt testing
was triggered. When a manual retry was done, it passed because build was
ignored.
Looking at the artifacts (attached for both cases), ADT_TEST_TRIGGERS differs:
1. when build is triggered, ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
linux-kvm/5.15.0-1030.35 linux-signed-kvm/5.15.0-1030.35
logs
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
2. when build is not triggered,
ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
logs:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz
Last log line present in both cases is:
"I: Testing binary package $pkg".
Looking at dkms: debian/scripts/dkms-autopkgtest
After that line and the line where build is triggered the following code:
dkms_pkg=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_NAME"
2>/dev/null)
dkms_ver=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_VERSION"
2>/dev/null)
for k in /lib/modules/*/build
do
test -d "$k" || continue
kver="${k%/build}"
kver="${kver#/lib/modules/}"
# If any linux-meta is in triggers, only test abistems that
# match triggers otherwise continue. This helps integration
# with adt-matrix which specifically requests test results
# against each individual linux-meta and tracks unique results
# per kernel abi.
abistem=$(echo $kver | sed 's/-[a-z]*$//')
## abistem is 5.15.0-130
case "${ADT_TEST_TRIGGERS-}" in
*linux-meta*)
case "$ADT_TEST_TRIGGERS" in
*"$abistem"*)
;;
*)
continue
;;
esac
esac
echo "I: Trying to build $dkms_pkg/$dkms_ver for $kver"
What happens here is that it never gets passed the switch case and
build is not triggered when ADT_TEST_TRIGGERS consists of linux-meta
only, because abistem=-, but meta
version=.. Notice the dot instead of the
dash.
This justifies why the module is built when ADT_TEST_TRIGGERS=linux-
meta-kvm/5.15.0.1030.26 linux-kvm/5.15.0-1030.35 linux-signed-
kvm/5.15.0-1030.35, but not when ADT_TEST_TRIGGERS=linux-meta-
kvm/5.15.0.1030.26
[Fix]
Add an extra check for meta_version in that switch case statement.
[Testcase]
1. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. before fix
I: linux-headers-virtual
I: Testing binary package digimend-dkms
autopkgtest [11:14:45]: test dkms-autopkgtest: ---]
autopkgtest [11:14:46]: test dkms-autopkgtest: - - - - - - - - - - results -
- - - - - - - - -
dkms-autopkgtest PASS
autopkgtest [11:14:47]: summary
dkms-autopkgtest PASS
qemu-system-x86_64: terminating on signal 15 from pid 15111 (/usr/bin/python3)
2. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. with the fix
I: Testing binary package digimend-dkms
I: Trying to build digimend/10 for 5.15.0-1029-kvm
Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10
Kernel preparation unnecessary for this kernel.
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
Generic should be fine. verification-done-jammy tag will mark all of them solved I believe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
