[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
** Description changed: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] - After applying the quirk, the audio/mic mute LEDs are working good. + Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). -- 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/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1
** Tags added: apport-collected jammy uec-images ** Description changed: Configuration: OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN BMC Version 0.48 (Build ID: ESX303K) UEFI Version 0.62 (Build ID: ESE105G) SSD:931.51GB 7.2K SATA HDD S471A08RSH20K04054 00LF039 SSD*2(SATA 0/1):894.25GB SATA SSD HDD*2(SATA 2 alias tsata): 1TB SATA HDD Boot mode:UEFI Reproduce Steps: 1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set to "RAID",save and reboot. 2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via drive 12,13 HDD to create RAID Volume,save and reboot. 3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.004.1),the raid group under tSATA is not detected. 4.In the OS,the RAID of the tSATA group is not detected. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Nov 14 17:16 seq + crw-rw+ 1 root audio 116, 33 Nov 14 17:16 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-11-14 (0 days ago) + InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Lenovo ThinkSystem SR645 V3 MB,Genoa,DDR5,Oahu,1U + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-25-generic N/A + linux-backports-modules-5.15.0-25-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.15.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 11/14/2022 + dmi.bios.release: 1.20 + dmi.bios.vendor: Lenovo + dmi.bios.version: KAE105D-1.20 + dmi.board.asset.tag: None + dmi.board.name: SB27B31174 + dmi.board.vendor: Lenovo + dmi.board.version: 04 + dmi.chassis.asset.tag: None + dmi.chassis.type: 23 + dmi.chassis.vendor: Lenovo + dmi.chassis.version: None + dmi.ec.firmware.release: 1.20 + dmi.modalias: dmi:bvnLenovo:bvrKAE105D-1.20:bd11/14/2022:br1.20:efr1.20:svnLenovo:pnThinkSystemSR645V3MB,Genoa,DDR5,Oahu,1U:pvr04:rvnLenovo:rnSB27B31174:rvr04:cvnLenovo:ct23:cvrNone:sku7D9DRCZ000: + dmi.product.family: ThinkSystem + dmi.product.name: ThinkSystem SR645 V3 MB,Genoa,DDR5,Oahu,1U + dmi.product.sku: 7D9DRCZ000 + dmi.product.version: 04 + dmi.sys.vendor: Lenovo -- 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/1990342 Title: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Configuration: OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN BMC Version 0.48 (Build ID: ESX303K) UEFI Version 0.62 (Build ID: ESE105G) SSD:931.51GB 7.2K SATA HDD S471A08RSH20K04054 00LF039 SSD*2(SATA 0/1):894.25GB SATA SSD HDD*2(SATA 2 alias tsata): 1TB SATA HDD Boot mode:UEFI Reproduce Steps: 1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set to "RAID",save and reboot. 2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via drive 12,13 HDD to create RAID Volume,save and reboot. 3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.004.1),the raid group under tSATA is not detected. 4.In the OS,the RAID of the tSATA group is not detected. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Nov 14 17:16 seq crw-rw+ 1 root audio 116, 33 Nov 14 17:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-14 (0
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
** Description changed: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] - With firmware from bug 1997200, this will bring up MT7922 Bluetooth. + Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. -- 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/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999004] [NEW] add new device IDs in the support list of nvidia-driver-525 package
Public bug reported: please add the following deviceID (pci-id) in nv driver support list - 2717: for GN21-X11-A1 ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- 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/1999004 Title: add new device IDs in the support list of nvidia-driver-525 package Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: please add the following deviceID (pci-id) in nv driver support list - 2717: for GN21-X11-A1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/1999004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998727] Re: Fix System cannot detect bluetooth after running suspend stress test
Sent V2 for U/J/K. Add build summary https://lists.ubuntu.com/archives/kernel-team/2022-December/135478.html -- 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/1998727 Title: Fix System cannot detect bluetooth after running suspend stress test Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Bug description: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where problems could occur] just enable a function from kernel and run the code in the fw. the main risk would be related to FW. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998656] Re: iwlwifi is crashing
> It worked in Linux-source-5.15.0-53.59. But in the bug description: > This is occurring in linux-source-5.15.0-53.59. Huh? And according to the attached dmesg you're not even running an Ubuntu kernel: > BOOT_IMAGE=/vmlinuz-5.15.64-caticorn-22.11.16 Huh? -- 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/1998656 Title: iwlwifi is crashing Status in linux package in Ubuntu: Confirmed Bug description: Hello, My wifi adapter is regularly crashing with the latest kernel. The workaround appears to be the same as outlined in: https://bugzilla.kernel.org/show_bug.cgi?id=208425 which is setting the router to use 20MHz channel widths. This appears to be fixed in kernel 5.18.6 as described here: https://bugzilla.kernel.org/show_bug.cgi?id=215635#c18 However, Ubuntu 22.04 does not have kernel 5.18.6. This is occurring in linux-source-5.15.0-53.59. Thank you, Ted ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.15.64-caticorn-22.11.16 x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shofutex 2321 F pulseaudio /dev/snd/controlC0: shofutex 2321 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 18:34:41 2022 InstallationDate: Installed on 2019-09-23 (1166 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.64-hostname-22.11.16 root=/dev/mapper/ubuntu--vg-root ro quiet splash amd_iommu=on iommu=pt kvm_amd.npt=1 vfio-pci.ids=1002:67df,1002:aaf0,1022:15e0,1022:15e1 pcie_acs_override=id:1022:15e0,id:1022:15e1 amdgpu.gttsize=8192 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.64-caticorn-22.11.16 N/A linux-backports-modules-5.15.64-caticorn-22.11.16 N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-02 (214 days ago) dmi.bios.date: 07/22/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver
The attachment "0041-dev-addr-access.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1998039 Title: Network Freeze With Broadcom DKMS Wireless Driver Status in bcmwl package in Ubuntu: New Bug description: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). A search found a related issue[1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source [1] https://salsa.debian.org/diegoe/broadcom- sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998039] Re: Network Freeze With Broadcom DKMS Wireless Driver
The patch in Debian doesn't apply cleanly, so I refreshed the patch for Ubuntu. Building and testing locally with the refreshed version appears to work (my reproducer doesn't reproduce with this package). Steps: 1) Add new patch line in dkms config: debian/dkms.conf.in 2) add patch to debian/patches 3) build (dpkg-buildpackage -us -uc) 4) install and test ** Patch added: "0041-dev-addr-access.patch" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+attachment/5634972/+files/0041-dev-addr-access.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1998039 Title: Network Freeze With Broadcom DKMS Wireless Driver Status in bcmwl package in Ubuntu: New Bug description: Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset Ubuntu Release: 22.10 Kernel: 5.19.0-23-generic Symptoms: Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly related to suspend/resume). A search found a related issue[1]. $ lsmod | grep wl wl 6467584 0 cfg80211 1040384 1 wl $ dpkg -l | grep -i broadcom ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu9 amd64Broadcom 802.11 Linux STA wireless driver source [1] https://salsa.debian.org/diegoe/broadcom- sta/-/commit/720ac7c23d78d771219ed4c9228daa2cbb88a4ca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1998039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995903] Re: Can't boot with kernel 5.15.0-52
Before reading your comment about nvidia:520 above, I change the nvidia driver by using Software & Updates > Additional Drivers. Now it is "Using NVIDIA driver (open kernel) metapackage from nvidia- driver-525-open (proprietary, tested)". Magic, now things get reversed: - Can't boot with 5.15.0-50 - Can boot with 5.15.0-56 Btw, is it the same as `sudo ubuntu-drivers install nvidia:525`? -- 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/1995903 Title: Can't boot with kernel 5.15.0-52 Status in linux package in Ubuntu: Confirmed Bug description: These packages are installed: linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 amd64 [installed,automatic] linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 amd64 [installed,automatic] After grub and booting, there's some text appears, and then the screen goes blank. After forcing the computer to turn off, I boot again but using 5.15.0-50, it can boot like usual. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 2015 F pulseaudio /dev/snd/controlC0: fikr4n 2015 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 8 08:57:48 2022 InstallationDate: Installed on 2021-06-05 (520 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop
** Changed in: linux Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop
>From the attached kernel log: [10112.178526] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:859b, in Xorg [1998] [10112.179245] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [10112.282534] i915 :00:02.0: [drm] Xorg[1998] context reset due to GPU hang [10112.282711] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 [10112.282720] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 [10112.299590] i915 :00:02.0: [drm] HuC authenticated [10112.299976] i915 :00:02.0: [drm] GuC submission enabled [10112.299977] i915 :00:02.0: [drm] GuC SLPC enabled [10124.168247] Asynchronous wait on fence :00:02.0:Xorg[1998]:6 timed out (hint:intel_atomic_commit_ready [i915]) [10124.168641] Asynchronous wait on fence :00:02.0:Xorg[1998]:6 timed out (hint:intel_atomic_commit_ready [i915]) [10135.176271] Asynchronous wait on fence :00:02.0:Xorg[1998]:6a timed out (hint:intel_atomic_commit_ready [i915]) [10135.176691] Asynchronous wait on fence :00:02.0:Xorg[1998]:6a timed out (hint:intel_atomic_commit_ready [i915]) [10145.928345] Asynchronous wait on fence :00:02.0:Xorg[1998]:6c timed out (hint:intel_atomic_commit_ready [i915]) [10145.928723] Asynchronous wait on fence :00:02.0:Xorg[1998]:6c timed out (hint:intel_atomic_commit_ready [i915]) [10157.192386] Asynchronous wait on fence :00:02.0:Xorg[1998]:74 timed out (hint:intel_atomic_commit_ready [i915]) [10157.192755] Asynchronous wait on fence :00:02.0:Xorg[1998]:74 timed out (hint:intel_atomic_commit_ready [i915]) and [12194.234423] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:859b, in Xorg [205503] [12194.235106] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [12194.338868] i915 :00:02.0: [drm] Xorg[205503] context reset due to GPU hang [12194.339052] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 [12194.339060] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 [12194.355616] i915 :00:02.0: [drm] HuC authenticated [12194.356153] i915 :00:02.0: [drm] GuC submission enabled [12194.356158] i915 :00:02.0: [drm] GuC SLPC enabled [12203.157415] Asynchronous wait on fence :00:02.0:Xorg[205503]:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12203.157795] Asynchronous wait on fence :00:02.0:Xorg[205503]:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12214.374853] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa2c! [12214.374867] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa2a! [12214.374870] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa28! [12214.374872] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa26! [12214.374875] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa24! [12214.374877] Fence expiration time out i915-:00:02.0:Xorg<205503>:fa22! [12214.933492] Asynchronous wait on fence :00:02.0:Xorg[205503]:c timed out (hint:intel_atomic_commit_ready [i915]) [12214.933892] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12214.934191] Asynchronous wait on fence :00:02.0:Xorg[205503]:c timed out (hint:intel_atomic_commit_ready [i915]) [12214.934435] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12225.173469] Asynchronous wait on fence :00:02.0:Xorg[205503]:46 timed out (hint:intel_atomic_commit_ready [i915]) [12225.173793] Asynchronous wait on fence :00:02.0:Xorg[205503]:46 timed out (hint:intel_atomic_commit_ready [i915]) [12236.181623] Asynchronous wait on fence :00:02.0:Xorg[205503]:6a timed out (hint:intel_atomic_commit_ready [i915]) [12236.181806] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12236.181898] Asynchronous wait on fence :00:02.0:Xorg[205503]:6a timed out (hint:intel_atomic_commit_ready [i915]) [12236.181973] Asynchronous wait on fence :00:02.0:Xorg<205503>:fa3e timed out (hint:intel_atomic_commit_ready [i915]) [12247.189660] Asynchronous wait on fence :00:02.0:Xorg[205503]:9e timed out (hint:intel_atomic_commit_ready [i915]) [12247.190077] Asynchronous wait on fence :00:02.0:Xorg[205503]:9e timed out (hint:intel_atomic_commit_ready [i915]) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6757 https://gitlab.freedesktop.org/drm/intel/-/issues/6757 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/6757 Importance: Unknown Status: Unknown ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake
[Kernel-packages] [Bug 1998950] [NEW] GPU hang on Alder Lake laptop
You have been subscribed to a public bug: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kinetic ubuntu -- GPU hang on Alder Lake laptop https://bugs.launchpad.net/bugs/1998950 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996915] Re: megaraid_sas crash in ubuntu 22.04
Thanks Nilson, excellent find on the bugzilla report. The linked linux-hardening thread makes me think this is 'just' an undefined-but-safe operation: the sort of thing that's good to fix, in case a future compiler makes an unsafe optimization, but not likely to be a cause for concern today. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Information type changed from Private Security to Public Security -- 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/1996915 Title: megaraid_sas crash in ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: crash message for dmesg UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 index 2 is out of range for type 'MR_LD_SPAN_MAP [1]' CPU: 16 PID: 330 Comm: kworker/16:1H Not tainted 5.15.0-53-generic #59-Ubuntu Hardware name: GIGABYTE R282-Z91-00/MZ92-FS0-00, BIOS M10 11/23/2021 Workqueue: kblockd blk_mq_run_work_fn Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_out_of_bounds.cold+0x44/0x49 MR_GetPhyParams+0x487/0x700 [megaraid_sas] MR_BuildRaidContext+0x71e/0xb50 [megaraid_sas] ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x580 megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] megasas_queue_command+0x1c1/0x200 [megaraid_sas] ? ktime_get+0x46/0xc0 scsi_dispatch_cmd+0x96/0x200 scsi_queue_rq+0x2d5/0x690 blk_mq_dispatch_rq_list+0x13f/0x680 ? sbitmap_get+0x71/0xe0 __blk_mq_do_dispatch_sched+0xba/0x2e0 blk_mq_do_dispatch_sched+0x40/0x70 __blk_mq_sched_dispatch_requests+0x105/0x150 blk_mq_sched_dispatch_requests+0x35/0x70 __blk_mq_run_hw_queue+0x34/0xc0 blk_mq_run_work_fn+0x1f/0x30 process_one_work+0x22b/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x12a/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in subiquity:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
** Description changed: [Impact] + On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] + Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ + The patch has been accepted but still not shown in the upstream tree, so + submit this patch to oem kernels first, and will submit it to other + generic ubuntu kernels. + [Test] + Verified by our QA and ODM. [Where problems could occur] + It extends the delay time, should be no harm for existing platforms. -- 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/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress 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 source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch has been accepted but still not shown in the upstream tree, so submit this patch to oem kernels first, and will submit it to other generic ubuntu kernels. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
I have upload sosreport in Comment#1
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.57.50)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.57.50) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency/5.15.0-57.63 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-5.15/5.15.0.57.63~20.04.20)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15 (5.15.0.57.63~20.04.20) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.9 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-lowlatency-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
Also, are you sure this isn't an issue with the lab networking, since
you said that it works fine if you disable networking.
I will raise this with the team that handles the installer, because this
could be handled more gracefully.
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
can you collect a sosreport and attach that?
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
apport-collect only launches the browser to authorize collection via Launchpad. You can copy and paste, or type the URL into any browser on a different machine and authorize it. -- 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Confirmed Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems：Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage： 7MM Drive 0-1：7.68TB 7MM NVMe SSD（PN：MTFDKCB7T6TFR，FW：E2MU110） Drive 0：240GB SATA SSD （PN：SSS7B07725 ，FW：MQ31） Drive 1-2：1.92TB NVMe SSD（PN：SSDPF2KX019T1O，FW：9CV10320） Drive 3-4：400GB NVMe SSD（PN：SSDPF21Q400GB，FW：L0310600） Drive 5-8：12.0TB SATA HDD（PN：01GV193，FW：LEGNK9R5） Drive 9：240GB SATA SSD（PN：SSS7B07725，FW：MQ31） Drive 10-11：960GB SATA SSD（PN：SSS7A43198，FW：MP33） Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998656] Re: iwlwifi is crashing
It’s a regression. It worked in Linux-source-5.15.0-53.59. The issue appeared immediately on booting to the new kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998656 Title: iwlwifi is crashing Status in linux package in Ubuntu: Confirmed Bug description: Hello, My wifi adapter is regularly crashing with the latest kernel. The workaround appears to be the same as outlined in: https://bugzilla.kernel.org/show_bug.cgi?id=208425 which is setting the router to use 20MHz channel widths. This appears to be fixed in kernel 5.18.6 as described here: https://bugzilla.kernel.org/show_bug.cgi?id=215635#c18 However, Ubuntu 22.04 does not have kernel 5.18.6. This is occurring in linux-source-5.15.0-53.59. Thank you, Ted ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.15.64-caticorn-22.11.16 x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shofutex 2321 F pulseaudio /dev/snd/controlC0: shofutex 2321 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 18:34:41 2022 InstallationDate: Installed on 2019-09-23 (1166 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.64-hostname-22.11.16 root=/dev/mapper/ubuntu--vg-root ro quiet splash amd_iommu=on iommu=pt kvm_amd.npt=1 vfio-pci.ids=1002:67df,1002:aaf0,1022:15e0,1022:15e1 pcie_acs_override=id:1022:15e0,id:1022:15e1 amdgpu.gttsize=8192 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.64-caticorn-22.11.16 N/A linux-backports-modules-5.15.64-caticorn-22.11.16 N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-02 (214 days ago) dmi.bios.date: 07/22/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I'm insanely late on this, but I couldn't help but notice that nobody
mentioned Ventoy (at least ctrl+f doesn't return any results in the full
activity log for "ventoy")
Since installing via Rufus set to ISO mode has been a suggested work-
around, wouldn't this by definition mean that using Ventoy would "just
work"?
Normally I would test this myself and report back, but I'm not actually
running into this issue myself, so...
Link for those that aren't aware of what Ventoy is:
https://github.com/ventoy/Ventoy
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Workaround]
Some workarounds have been suggested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
** Also affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Also affects: ivsc-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998689] Re: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine
I installed it via Ubuntu's "use proprietary drivers" function. I double checked that I have no trace of a downloaded nVidia driver installer on my machine. -- 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/1998689 Title: Ubuntu 22.04.1 LTS does not boot after update 5.15.0-48 -> 5.15.0-56 - old kernel boots fine Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu 22.04.1 LTS auto updated from kernel 5.15.0-48 to 5.15.0-56. The new kernel does not boot. It stops right after it says the disk is clean. The cursor stops blinking less than 1 second after that and there is no additional message. The old kernel boots fine. The "ubuntu-bug" report was done with the old kernel. I am new to Ubuntu bug reporting and hope the information created by `ubuntu-bug` is added, even though I can't see it here. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2477 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 11:13:53 2022 InstallationDate: Installed on 2022-09-19 (75 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro M12SWA-TF ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=33a91d45-6bee-4e70-bc21-7956db527e81 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.7 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2022 dmi.bios.release: 2.10 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: M12SWA-TF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.0a:bd03/18/2022:br2.10:svnSupermicro:pnM12SWA-TF:pvr123456789:rvnSupermicro:rnM12SWA-TF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:sku091715D9: dmi.product.family: SMC M12 dmi.product.name: M12SWA-TF dmi.product.sku: 091715D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
This is still failing in Focal, now with linux-hwe-5.15:
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/amd64/s/systemd/20221122_044608_4c928@/log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090
Title:
systemd/245.4-4ubuntu3.6 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1
Status in linux-hwe-5.11 package in Ubuntu:
Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in linux-hwe-5.11 source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
New
Status in systemd source package in Focal:
New
Bug description:
This is a scripted bug report about ADT failures while running systemd
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
is caused by the dep8 tests of the tested source or the kernel has yet
to be determined.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
In arm64, ppc64el and s390x, 'root-unittests' fails with:
/* test_protect_sysctl */
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function
test_protect_sysctl(). A
borting.
sysctlseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at s
rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
FAIL: test-seccomp (code: 134)
In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
apparently is caused by the same 'test-seccomp.c:311' assertion
failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090
Title:
systemd/245.4-4ubuntu3.6 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1
Status in linux-hwe-5.11 package in Ubuntu:
Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in linux-hwe-5.11 source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
New
Status in systemd source package in Focal:
New
Bug description:
This is a scripted bug report about ADT failures while running systemd
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
is caused by the dep8 tests of the tested source or the kernel has yet
to be determined.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
In arm64, ppc64el and s390x, 'root-unittests' fails with:
/* test_protect_sysctl */
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function
test_protect_sysctl(). A
borting.
sysctlseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at s
rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
FAIL: test-seccomp (code: 134)
In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
apparently is caused by the same 'test-seccomp.c:311' assertion
failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998938] Re: Add support for CT accounting stats
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium -- 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/1998938 Title: Add support for CT accounting stats Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug(s) Add CT accounting stats per flow for TC CT rules. This is only available when nf_conn_acct is enabled so it won’t affect performance when not enabled. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. * How to test Enable nf_conn_acct and check ct stats. * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959911] Re: ddcci-dkms fails to install with linux 5.15 on focal
*** This bug is a duplicate of bug 1951608 *** https://bugs.launchpad.net/bugs/1951608 The focal fix for the dkms was tracked in bug 1951608. This is bug is not a kernel issue, so marking it as duplicate. ** This bug has been marked a duplicate of bug 1951608 ddcci-driver-linux: build error with linux 5.15 on 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/1959911 Title: ddcci-dkms fails to install with linux 5.15 on focal Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] dcci-dkms is failing with the following build error on focal with the new 5.15 hwe kernel: CC [M] /var/lib/dkms/ddcci/0.3.3/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.3.3/build/ddcci/ddcci.c:1222:13: error: initialization of ‘void (*)(struct device *)’ from incompatible pointer type ‘int (*)(struct device *)’ [-Werror=incompatible-pointer-types] 1222 | .remove = ddcci_device_remove | ^~~ /var/lib/dkms/ddcci/0.3.3/build/ddcci/ddcci.c:1222:13: note: (near initialization for ‘ddcci_bus_type.remove’) cc1: some warnings being treated as errors [Fix] Prototype of bus_type->remove() is changed starting with kernel 5.15 (function is not returning an int anymore, now it's a void function). Fix with a proper #ifdef macro to support both prototypes, based on the specific kernel version that we are building against to. [Test case] $ sudo apt install ddcci-dkms [Regression potential] We may see stale devices / resource leaking on removal of ddcci devices, because with kernels >= 5.15 there's basically no error handling in bus_type->remove(). Previous kernels are unaffected, because the code remains identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998734] 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/1998734 Title: My touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: Everything was working fine until it stopped. My touchpad is not giving any responce ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harsh 1203 F pulseaudio CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.85.02-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 09:38:20 2022 InstallationDate: Installed on 2022-08-14 (112 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br1xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ed3989db-f6aa-4afc-be23-7ba49fb29500 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2019 dmi.bios.release: 15.52 dmi.bios.vendor: Insyde dmi.bios.version: F.52 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.70 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.70 dmi.modalias: dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr23.70:svnHP:pnHPLaptop15g-br1xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.70:cvnHP:ct10:cvrChassisVersion:sku3WD55PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br1xx dmi.product.sku: 3WD55PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
Removed oem-priority, confirmed this is not a certified device, and it's not in the support scope. However, this is a regression that breaks previous supported hardware in mm and kernel. ** No longer affects: oem-priority ** Tags removed: oem-priority -- 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/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
In src/mm-context.c, it appears that can be disabled with an argument:
262 #if defined WITH_QRTR
263 {
264 "test-no-qrtr", 0, 0, G_OPTION_ARG_NONE, _no_qrtr,
265 "Run without qrtr support even if available",
266 NULL
267 },
268 #endif
And probably all one has to do is to test if qrtr is actually supported
by the running kernel:
330 #if defined WITH_QRTR
331 gboolean
332 mm_context_get_test_no_qrtr (void)
333 {
334 return test_no_qrtr;
335 }
336 #endif
--
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/1998194
Title:
Please add support for Qualcomm IPC Router in 5.4 focal kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
The modemmanager debian package in focal was recently upgraded to 1.18
(the jammy version was backported - see LP: #1965901). This version
has broken some Qualcomm modems as it start to require the Qualcomm
IPC Router for them, which drivers are not enabled in Ubuntu kernel
5.4. To fix this we need these options enabled in the focal kernel:
CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m
The options are already enabled in more modern Ubuntu kernel, i.e.
5.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998734] Re: My touchpad is not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1998734 Title: My touchpad is not working Status in linux package in Ubuntu: New Bug description: Everything was working fine until it stopped. My touchpad is not giving any responce ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harsh 1203 F pulseaudio CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.85.02-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.85.02-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 09:38:20 2022 InstallationDate: Installed on 2022-08-14 (112 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br1xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ed3989db-f6aa-4afc-be23-7ba49fb29500 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2019 dmi.bios.release: 15.52 dmi.bios.vendor: Insyde dmi.bios.version: F.52 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.70 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.70 dmi.modalias: dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr23.70:svnHP:pnHPLaptop15g-br1xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.70:cvnHP:ct10:cvrChassisVersion:sku3WD55PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br1xx dmi.product.sku: 3WD55PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996678] Re: containerd sporadic timeouts
This bug does not seem to be caused by containerd, so I am marking its tasks as Invalid. If you disagree, please say so. ** Changed in: containerd (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: containerd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: Invalid Status in linux source package in Focal: Fix Released Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998938] [NEW] Add support for CT accounting stats
Public bug reported: * Explain the bug(s) Add CT accounting stats per flow for TC CT rules. This is only available when nf_conn_acct is enabled so it won’t affect performance when not enabled. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. * How to test Enable nf_conn_acct and check ct stats. * What it could break. Nothing. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Add support for CT accounting stats. First commit for SW, second commit of HW offloaded rules. + Add support for CT accounting stats -- 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/1998938 Title: Add support for CT accounting stats Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Add CT accounting stats per flow for TC CT rules. This is only available when nf_conn_acct is enabled so it won’t affect performance when not enabled. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. * How to test Enable nf_conn_acct and check ct stats. * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I have now picked all the rhboot patches in 2.06-2ubuntu16~ppa1 in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
and will boot that before uploading to the archive.
This *should* allow initrds over 4GB but obviously bugs could be there.
The important bit is that we are now close to the rhboot branch again in
that file such that the whole thing is maintainable to some extent at
least.
Once this is uploaded to lunar people can test this easily on secure
boot systems without having to install PPA signing keys in MOK.
I'm gonna see if I can run some tests myself and reproduce this.
Also it turns out it fails to build the i386-efi target due to pointer
size mismatches.
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Workaround]
Some workarounds have been suggested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
[Kernel-packages] [Bug 1998843] Re: Jammy update: v5.15.78 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998843 Title: Jammy update: v5.15.78 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.78 upstream stable release from git://git.kernel.org/ scsi: lpfc: Rework MIB Rx Monitor debug info logic serial: ar933x: Deassert Transmit Enable on ->rs485_config() KVM: x86: Trace re-injected exceptions KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) drm/amd/display: explicitly disable psr_feature_enable appropriately mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page HID: playstation: add initial DualSense Edge controller support KVM: x86: Protect the unused bits in MSR exiting flags KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER RDMA/cma: Use output interface for net_dev check IB/hfi1: Correctly move list in sc_disable() RDMA/hns: Remove magic number RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() RDMA/hns: Disable local invalidate operation NFSv4: Fix a potential state reclaim deadlock NFSv4.1: Handle RECLAIM_COMPLETE trunking errors NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed NFSv4.2: Fixup CLONE dest file size for zero-length count nfs4: Fix kmemleak when allocate slot failed net: dsa: Fix possible memory leaks in dsa_loop_init() RDMA/core: Fix null-ptr-deref in ib_core_cleanup() RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() net: dsa: fall back to default tagger if we can't load the one from DT nfc: fdp: Fix potential memory leak in fdp_nci_send() nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() net: fec: fix improper use of NETDEV_TX_BUSY ata: pata_legacy: fix pdc20230_set_piomode() net: sched: Fix use after free in red_enqueue() net: tun: fix bugs for oversize packet when napi frags enabled netfilter: nf_tables: netlink notifier might race to release objects netfilter: nf_tables: release flow rule object from commit path ipvs: use explicitly signed chars ipvs: fix WARNING in __ip_vs_cleanup_batch() ipvs: fix WARNING in ip_vs_app_net_cleanup() rose: Fix NULL pointer dereference in rose_send_frame() mISDN: fix possible memory leak in mISDN_register_device() isdn: mISDN: netjet: fix wrong check of device registration btrfs: fix inode list leak during backref walking at resolve_indirect_refs() btrfs: fix inode list leak during backref walking at find_parent_nodes() btrfs: fix ulist leaks in error paths of qgroup self tests netfilter: ipset: enforce documented limit to prevent allocating huge memory Bluetooth: virtio_bt: Use skb_put to set length Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() Bluetooth: L2CAP: Fix memory leak in vhci_write net: mdio: fix undefined behavior in bit shift for __mdiobus_register ibmvnic: Free rwi on reset success stmmac: dwmac-loongson: fix invalid mdio_node net/smc: Fix possible leaked pernet namespace in smc_init() net, neigh: Fix null-ptr-deref in neigh_table_clear() ipv6: fix WARNING in ip6_route_net_exit_late() vsock: fix possible infinite sleep in vsock_connectible_wait_data() drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag drm/msm/hdmi: fix IRQ lifetime video/fbdev/stifb: Implement the stifb_fillrect() function fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards mtd: parsers: bcm47xxpart: print correct offset on read error mtd: parsers: bcm47xxpart: Fix halfblock reads s390/uaccess: add missing EX_TABLE entries to __clear_user() s390/cio: fix out-of-bounds access on cio_ignore free media: rkisp1: Don't pass the quantization to rkisp1_csm_config() media: rkisp1: Initialize color space on resizer sink and source pads media: rkisp1: Use correct macro for gradient registers media: rkisp1: Zero v4l2_subdev_format fields in when validating links media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE media:
[Kernel-packages] [Bug 1998849] Re: Charging via USB Type-C does not work on HP ZBook Power G7
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-5.15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1998849 Title: Charging via USB Type-C does not work on HP ZBook Power G7 Status in linux-meta-hwe-5.15 package in Ubuntu: Confirmed Bug description: Charging via USB Type-C does not work on HP ZBook Power G7. I can see that that charging works if laptop is suspended or turned off, but while it is booted up charging does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.15.0.56.62~20.04.22 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Dec 5 20:49:10 2022 InstallationDate: Installed on 2022-10-03 (63 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-meta-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1998849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
In 5.4 Focal CONFIG_QRTR depends on ARCH_QCOM, which is a platform config that enables ARMv8 based Qualcomm chipsets, so it can not be enabled on amd64. Also CONFIG_QRTR_MHI is not present in 5.4, which means that the implementation is incomplete with respect to what modemmanager is expecting. In later releases like Jammy, CONFIG_QRTR has no dependency on ARCH_QCOM and therefore is enabled on amd64. All QRTR modules are also there. Enabling QRTR in 5.4 kernel would require backporting patches to remove its dependence on ARCH_QCOM and to add MHI module. It is suggested to check modulemanager implementation whether hard requirement on QRTR modules can be skipped on amd64. -- 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/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] Re: focal: merge upstream wireguard
** Summary changed: - focal: merge wireguard into the kernel + focal: merge upstream wireguard ** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh - we can just run it directly but it requires iperf3 and ncat installed and a `modprobe nf_conntrack` before starting the test). [Fix] - Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. + + Apply the backported wireguard patch set provided by the upstream + maintainer as UBUNTU SAUCE patches (patch set available in + https://git.zx2c4.com/wireguard-linux branch backport-5.4.y). [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. -- 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/1998902 Title: focal: merge upstream wireguard Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh - we can just run it directly but it requires iperf3 and ncat installed and a `modprobe nf_conntrack` before starting the test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches (patch set available in https://git.zx2c4.com/wireguard-linux branch backport-5.4.y). [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] Re: focal: merge wireguard into the kernel
** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh - we can just run it - directly but it requires iperf3 and ncat installed). + directly but it requires iperf3 and ncat installed and a `modprobe + nf_conntrack` before starting the test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. -- 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/1998902 Title: focal: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh - we can just run it directly but it requires iperf3 and ncat installed and a `modprobe nf_conntrack` before starting the test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] Re: focal: merge wireguard into the kernel
** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically - ./tools/testing/selftests/wireguard/netns.sh for a wireguard smoke - test). + ./tools/testing/selftests/wireguard/netns.sh - we can just run it + directly but it requires iperf3 and ncat installed). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. -- 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/1998902 Title: focal: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh - we can just run it directly but it requires iperf3 and ncat installed and a `modprobe nf_conntrack` before starting the test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: New => Triaged ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium -- 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/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Triaged Status in linux source package in Kinetic: Triaged Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Triaged Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I also run into this problem couple of times a month.
--
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/1678184
Title:
APST quirk needed for Samsung 512GB NVMe drive
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
That patch has a quirk for certain 256GB Samsung drives found in Dell
laptops that do not behave well when APST is enabled. I am
experiencing the same symptoms with the same model laptop except with
a 512GB Samsung. Prior to manually disabling APST the drive would die
and system would go down in flames with I/O errors within 20 to 40
minutes of boot.
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB
1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ajclayton 3305 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Mar 31 09:42:38 2017
InstallationDate: Installed on 2012-09-08 (1665 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt
nouveau.modeset=0 log_buf_len=20M
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904293] Re: [i915] GPU hangs on Haswell (Acer 720p)
Launchpad has imported 63 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1843274. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-06-02T23:56:59+00:00 rxguyrx wrote: Created attachment 1694628 Tail of dmesg showing gpu hang 1. Please describe the problem: Any time I boot into a kernel in the 5.7 series (RCs up to the current stable) I get a gpu hang (with sway and openbox). I can start the WM, and usually start a terminal, but starting anything else (firefox, caja, a gome, etc.) the gui hangs. I can kill the gui via a VT and restart it, but the problem continiues. To use my computer, I must boot into a kernel in the 5.6 series. I filed a bug upstream https://gitlab.freedesktop.org/drm/intel/-/issues/1805 2. What is the Version-Release number of the kernel: 5.7.0-1.fc33.x86_64 and all 5.7 release candidates before it 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : The first kernel 5.7 RC I tried 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Always with a 5.7 kernel as illustarted in #1 above. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes as stated above. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/0 On 2020-06-02T23:58:39+00:00 rxguyrx wrote: Created attachment 1694629 GPU Crash Dump Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/1 On 2020-07-20T17:10:35+00:00 tankey wrote: Identical issue here, with all kernel ≥ 5.7 : Fedora 32 kernel update ; And Vanilla kernel. The result is unable to perform kernel updates on my machine (Acer Aspire C720P with Coreboot and Fedora since 6 years) :-( (same issue on xorg or wayland) i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 i915 :00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/2 On 2020-07-20T17:16:57+00:00 tankey wrote: Created attachment 1701790 sys class drm card0 error Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/3 On 2020-07-20T17:24:43+00:00 tankey wrote: Created attachment 1701791 sys class drm card0 error on rc3 vanilla Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/4 On 2020-07-20T17:39:32+00:00 tankey wrote: Comment on attachment 1701791 sys class drm card0 error on rc3 vanilla On rc5 vanilla (sorry for typo, not rc3 but this attachment is rc5 drm dump) same issue on all fedora kernel stable update, rawhide, and all ≥5.7 rc from kernel.org : all tested (and trying many workarounds) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/5 On 2020-07-20T18:37:58+00:00 tankey wrote: i915.enable_rc6=0 : doesnt seems to be honored anymore ( systool -m i915 -v no report about, and /sys/class/drm/card0/power/rc6_enable always return 1 : maybe/certainly i am doing thing wrong) i915.enable_guc=0 : doesnt seems to have any effect i915.enable_hangcheck=0 : completely freeze Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/6 On 2020-07-20T19:11:57+00:00 tankey wrote: Created attachment 1701804 dmesg with lots of information (+boot context +i915 context) with disable_power_well=0 Hope this helps upstream (i am at your disposal for the tests you require) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904293/comments/7 On 2020-07-20T20:45:12+00:00 tankey wrote: Created attachment 1701810 with 5.7.8 fedora kernel
[Kernel-packages] [Bug 1998902] Re: focal: merge wireguard into the kernel
** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in - tools/testing/selftests/wireguard/. + tools/testing/selftests/wireguard/ (specifically + ./tools/testing/selftests/wireguard/netns.sh for a smoke test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. ** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically - ./tools/testing/selftests/wireguard/netns.sh for a smoke test). + ./tools/testing/selftests/wireguard/netns.sh for a wireguard smoke + test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. -- 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/1998902 Title: focal: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/ (specifically ./tools/testing/selftests/wireguard/netns.sh for a wireguard smoke test). [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty
[Kernel-packages] [Bug 1998902] Re: focal: merge wireguard into the kernel
** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. + Right now the best option is to verify the availability of the + wireguard.ko module and run the kernel selftests in + tools/testing/selftests/wireguard/. + [Fix] - - Apply the backported wireguard patch set provided by the upstream - maintainer as UBUNTU SAUCE patches. + Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. -- 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/1998902 Title: focal: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. Right now the best option is to verify the availability of the wireguard.ko module and run the kernel selftests in tools/testing/selftests/wireguard/. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] Re: merge wireguard into the kernel
** Description changed: [Impact] In older kernels, like focal, Wireguard used to be maintained as an - external module (wireguard-linux-compat dkms). This dkms is not - maintained anymore, but upstream maintainer periodically provides - backported patches for older kernels (like 5.4) in this git repository + external module (wireguard-dkms). This dkms is not maintained anymore, + but upstream maintainer periodically provides backported patches for + older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. - Also this patch set is probably going to conflict with wireguard-linux- - compat dkms, but that is the whole point, we want to deprecate this dkms - and merge wireguard into our kernel directly. + Also this patch set is probably going to conflict with wireguard-dkms, + but that is the whole point, we want to deprecate this dkms and merge + wireguard into our kernel directly. ** Summary changed: - merge wireguard into the kernel + focal: merge wireguard into the kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998902 Title: focal: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990128] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
You have HW problem, i.e., your disk seems to be dying:
[ 1339.532103] ata1.00: exception Emask 0x0 SAct 0xfc07f8ff SErr 0x0 action 0x6
frozen
[ 1339.532124] ata1.00: failed command: WRITE FPDMA QUEUED
[ 1339.532130] ata1.00: cmd 61/08:00:f8:fb:9f/00:00:03:00:00/40 tag 0 ncq dma
4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 1339.532148] ata1.00: status: { DRDY }
[ 1339.532155] ata1.00: failed command: WRITE FPDMA QUEUED
[ 1339.532159] ata1.00: cmd 61/08:08:00:08:90/00:00:16:00:00/40 tag 1 ncq dma
4096 out
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 1339.532174] ata1.00: status: { DRDY }
[ 1339.532179] ata1.00: failed command: WRITE FPDMA QUEUED
[ 1339.532183] ata1.00: cmd 61/08:10:58:08:90/00:00:16:00:00/40 tag 2 ncq dma
4096 out
res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 1356.100554] EXT4-fs warning (device sda2): ext4_end_bio:342: I/O error 10
writing to inode 1838889 starting block 25639168)
[ 1356.106716] Buffer I/O error on device sda2, logical block 25506816
[ 1356.106748] Buffer I/O error on device sda2, logical block 25506817
[ 1356.106758] Buffer I/O error on device sda2, logical block 25506818
[ 1356.106765] Buffer I/O error on device sda2, logical block 25506819
[ 1356.106772] Buffer I/O error on device sda2, logical block 25506820
[ 1356.106779] Buffer I/O error on device sda2, logical block 25506821
[ 1356.106786] Buffer I/O error on device sda2, logical block 25506822
[ 1356.106796] Buffer I/O error on device sda2, logical block 25506823
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990128
Title:
package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to
install/upgrade: installed linux-firmware package post-installation
script subprocess returned error exit status 1
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
Errors were encountered while processing:
linux-firmware
linux-image-generic
linux-generic
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an
error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up linux-firmware (20220329.git681281e4-0ubuntu3.5) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-47-generic
update-initramfs: Generating /boot/initrd.img-5.13.0-40-generic
Setting up linux-image-generic (5.15.0.47.47) ...
Setting up linux-generic (5.15.0.47.47) ...
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.5
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dragon 928 F pulseaudio
/dev/snd/controlC1: dragon 928 F pulseaudio
CasperMD5CheckResult: unknown
Date: Mon Sep 19 12:51:05 2022
Dependencies: firmware-sof-signed 2.0-1ubuntu3
ErrorMessage: installed linux-firmware package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2022-03-02 (200 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 14: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 14: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 14: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid,
12M
MachineType: Gigabyte Technology Co., Ltd. H410M H V3
PackageArchitecture: all
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic
root=UUID=b0a37a7a-72cf-4f7a-80e8-e9ce73f40700 ro quiet splash pci=realloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal,
3.10.4-0ubuntu2
[Kernel-packages] [Bug 1998905] [NEW] Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
Public bug reported: [Impact] [Fix] https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1998062 somerville ** Description changed: [Impact] [Fix] + https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] ** Tags added: oem-priority originate-from-1998062 somerville ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress 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 source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] [Fix] https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998727] Re: Fix System cannot detect bluetooth after running suspend stress test
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** 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-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998727 Title: Fix System cannot detect bluetooth after running suspend stress test Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Bug description: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where problems could occur] just enable a function from kernel and run the code in the fw. the main risk would be related to FW. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1998902 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998902 Title: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-linux-compat dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard- linux-compat dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998902] [NEW] merge wireguard into the kernel
Public bug reported: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-linux-compat dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard-linux- compat dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998902 Title: merge wireguard into the kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] In older kernels, like focal, Wireguard used to be maintained as an external module (wireguard-linux-compat dkms). This dkms is not maintained anymore, but upstream maintainer periodically provides backported patches for older kernels (like 5.4) in this git repository https://git.zx2c4.com/wireguard-linux. In order to properly support Wireguard with all the recent security updates, fixes, etc. it would be more efficient for us to apply the backported patch set officially provided by the upstream maintainer, instead of maintaining these changes in a separate dkms. [Test case] We need to figure out a proper test case to verify that wireguard is applied and it's working correctly. [Fix] Apply the backported wireguard patch set provided by the upstream maintainer as UBUNTU SAUCE patches. [Where things could go wrong] We don't have a precise plan to keep the patches updated after some SRU patches are applied to our kernel. A quick and dirty solution could be to revert the wireguard patch set entirely, apply the SRU patches, then re-apply the latest wireguard patch set on top. But we probably need to figure out a better workflow. Also this patch set is probably going to conflict with wireguard- linux-compat dkms, but that is the whole point, we want to deprecate this dkms and merge wireguard into our kernel directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997841] Re: More dkms fixes for exact cc compiler
Re-open because 3.0.8-3 has restored to old behavior. ** Changed in: dkms (Ubuntu Lunar) Status: Fix Released => 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/1997841 Title: More dkms fixes for exact cc compiler Status in dkms package in Ubuntu: New Status in dkms source package in Jammy: New Status in dkms source package in Kinetic: New Status in dkms source package in Lunar: New Bug description: [ Impact ] * Previously https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991664 has fixed up some dkms modules that use makefiles without setting a CC= variable inside them. However, there is a class of dkms modules that set a CC= variable inside the makefile, and then the environment variable is ignored, thus resulting in hwe-5.19 dkms modules to FTBFS. * Fix those by setting MAKEFLAGS="--environment-overrides" to really ensure that environmental variable compiler is really being used. Observe the following: $ cat Makefile.just-cc all: echo $(CC) $ cat Makefile.cc-set CC=cc-set-in-makefile all: echo $(CC) # cmdline override works in both cases $ make -f Makefile.just-cc CC=make-var-cmdline echo make-var-cmdline make-var-cmdline $ make -f Makefile.cc-set CC=make-var-cmdline echo make-var-cmdline make-var-cmdline # environment/shell variable override only works in one of them $ CC=env-cc make -f Makefile.just-cc echo env-cc env-cc $ CC=env-cc make -f Makefile.cc-set echo cc-set-in-makefile cc-set-in-makefile # unless environment-overrides is set $ MAKEFLAGS=--environment-overrides CC=env-cc make -f Makefile.cc-set echo env-cc env-cc [ Test Plan ] * Divert /usr/bin/gcc to /bin/false $ sudo ln -sf /bin/false /usr/bin/gcc * Install a v5.19 kernel that must be built with gcc-12 and a dkms module that uses a CC variable set inside its makefile $ sudo apt install linux-virtual-hwe-22.04-edge gost-crypto-dkms * Check that dkms status has the module successfully installed for v5.19 kernel $ dkms status [ Where problems could occur ] * dkms cleans environment of all tool-chain related variables already, but MAKEFLAGS=--environment-overrides may result in additional/new/unexpected variables leaking into the dkms module build, which were previously ignored. * A better solution might be for our kernel builds to emit a makefile snippet that is included by the Kbuild makefiles, but that too will only cover a subset of dkms modules, not all of them. * It might be nice if environment-overrides command line option of make accepted a list of allowed variables that are desired to be honored from the environment. [ Other Info ] * Any better suggestions of how to handle toolchain export would be welcome here, as this is starting to be silly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1997841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
** Tags added: oem-priority originate-from-1997768 somerville -- 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/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
