[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
a workaround could be updating to mainline 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/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. d
[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
Closing the issue as resolved. Please open a new ticket if you experience the problem again. ** Changed in: linux-firmware (Ubuntu Focal) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H 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-firmware/+bug/1956518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965307] Re: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1965307 Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux-firmware package in Ubuntu: Incomplete Bug description: 'linux-firmware_1.187.27_all.deb' in unbutu package ---> does not exist !!! And can not upgrading : package linux-firmware 1.187.26 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sirenux1759 F pulseaudio /dev/snd/controlC3: sirenux1759 F pulseaudio /dev/snd/controlC2: sirenux1759 F pulseaudio /dev/snd/controlC0: sirenux1759 F pulseaudio CasperMD5CheckResult: skip Date: Thu Mar 17 15:00:10 2022 Dependencies: DuplicateSignature: package:linux-firmware:1.187.26 Removing linux-image-generic-hwe-20.04 (5.13.0.30.33~20.04.17) ... dpkg: error processing package linux-firmware (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2022-01-19 (56 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp27s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7B07 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=c0e47fc1-d36a-4d49-a7fb-c934c673b142 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VH PLUS (MS-7B07) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.C0:bd11/06/2018:br5.13:svnMicro-StarInternationalCo.,Ltd:pnMS-7B07:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VHPLUS(MS-7B07):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B07 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1965307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966089] Re: Update OS policy capability handshake
SRUed, (OEM-5.14/OEM-5.17) https://lists.ubuntu.com/archives/kernel-team/2022-May/130093.html ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-1965785 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: New Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: == SRU JAMMY == Update int340x OS policy capability handshake; required for full functionality in thermald 2.4.9 to improve functionality for newer H/W. == The fix == Upstream commit: commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 Author: Srinivas Pandruvada Date: Mon Mar 14 15:09:37 2022 -0700 thermal: int340x: Update OS policy capability handshake Update the firmware with OS supported policies mask, so that firmware can relinquish its internal controls. Without this update several Tiger Lake laptops gets performance limited with in few seconds of executing in turbo region. The existing way of enumerating firmware policies via IDSP method and selecting policy by directly writing those policy UUIDS via _OSC method is not supported in newer generation of hardware. There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for updating policy capabilities. As part of ACPI _OSC method: Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698 Arg1 - Rev ID: 1 Arg2 - Count: 2 Arg3 - Capability buffers: Array of Arg2 DWORDS DWORD1: As defined in the ACPI 5.0 Specification - Bit 0: Query Flag - Bits 1-3: Always 0 - Bits 4-31: Reserved DWORD2 and beyond: - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to indicate it is disabled and legacy thermal mechanism should be enabled. - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling active cooling, 0 to indicate bios shall enable legacy thermal zone with active trip point. - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling passive cooling, 0 to indicate bios shall enable legacy thermal zone with passive trip point. - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling critical trip point, 0 to indicate bios shall enable legacy thermal zone with critical trip point. - Bits 4:31: Reserved From sysfs interface, there is an existing interface to update policy UUID using attribute "current_uuid". User space can write the same UUID for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user space it is assumed that dynamic tuning is active. For example $cd /sys/bus/platform/devices/INTC1040:00/uuids To support active policy $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid To support passive policy $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid To support critical policy $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid To check all the supported policies $cat current_uuid 3A95C389-E4B8-4629-A526-C52C88626BAE 42A441D6-AE6A-462b-A84B-4A8CE79027D3 97C68AE7-15FA-499c-B8C9-5DA81D606E0A To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE and INT3400_THERMAL_PASSIVE_1. If the policies are enumerated via IDSP method then legacy method is used, if not the new method is used to update policy support. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966089/+subscrip
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei, thanks for confirming the working/broken versions. I am not sure if I will be able to reproduce the issue myself. There are 270 changes between -99 and -100. If you can help me bisect them, we should be able to quickly identify the problem. Would you be able to test the kernels I provide so we can identify the breaking commit? We might need to test up to 9 more kernels. I have built the first test kernel. It can be found at: https://kernel.ubuntu.com/~kmously/kernel-kmously-d60b65f-bspU/ If you can, please install the linux-image, linux-modules and linux- modules-extra packages from the above link and attempt to reproduce the problem. Thank you. -- 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi Jaejeon, As indicated by Stephane in #30, you would need to get the latest modem firmware from Fibocom colleauges and update the firmware using Telephony tool provided by us in #27, if you have access to windows setup We would request you to retry with the latest modem firmware and share us the test results, with the updated modem firmware. Thanks and Best Regards, Murali -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966089] Re: Update OS policy capability handshake
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Bug description: == SRU JAMMY == Update int340x OS policy capability handshake; required for full functionality in thermald 2.4.9 to improve functionality for newer H/W. == The fix == Upstream commit: commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 Author: Srinivas Pandruvada Date: Mon Mar 14 15:09:37 2022 -0700 thermal: int340x: Update OS policy capability handshake Update the firmware with OS supported policies mask, so that firmware can relinquish its internal controls. Without this update several Tiger Lake laptops gets performance limited with in few seconds of executing in turbo region. The existing way of enumerating firmware policies via IDSP method and selecting policy by directly writing those policy UUIDS via _OSC method is not supported in newer generation of hardware. There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for updating policy capabilities. As part of ACPI _OSC method: Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698 Arg1 - Rev ID: 1 Arg2 - Count: 2 Arg3 - Capability buffers: Array of Arg2 DWORDS DWORD1: As defined in the ACPI 5.0 Specification - Bit 0: Query Flag - Bits 1-3: Always 0 - Bits 4-31: Reserved DWORD2 and beyond: - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to indicate it is disabled and legacy thermal mechanism should be enabled. - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling active cooling, 0 to indicate bios shall enable legacy thermal zone with active trip point. - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling passive cooling, 0 to indicate bios shall enable legacy thermal zone with passive trip point. - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling critical trip point, 0 to indicate bios shall enable legacy thermal zone with critical trip point. - Bits 4:31: Reserved From sysfs interface, there is an existing interface to update policy UUID using attribute "current_uuid". User space can write the same UUID for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user space it is assumed that dynamic tuning is active. For example $cd /sys/bus/platform/devices/INTC1040:00/uuids To support active policy $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid To support passive policy $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid To support critical policy $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid To check all the supported policies $cat current_uuid 3A95C389-E4B8-4629-A526-C52C88626BAE 42A441D6-AE6A-462b-A84B-4A8CE79027D3 97C68AE7-15FA-499c-B8C9-5DA81D606E0A To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE and INT3400_THERMAL_PASSIVE_1. If the policies are enumerated via IDSP method then legacy method is used, if not the new method is used to update policy support. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964441] Re: libwbxml < 0.11.8 issue with libexpat1 CVE-2022-25236 fix
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964441 Title: libwbxml < 0.11.8 issue with libexpat1 CVE-2022-25236 fix Status in linux package in Ubuntu: Expired Bug description: see https://github.com/libwbxml/libwbxml/releases/tag/libwbxml-0.11.8 ubuntu jammy should upgrade to 0.11.8 from 0.11.7 older versions of ubuntu should backport https://github.com/libwbxml/libwbxml/pull/78 This issue breaks for example sogo activesync (included first on jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964537] Re: Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964537 Title: Synaptics touchpad not detected on HP Laptop Model 17-cn0078cl Status in linux package in Ubuntu: Expired Bug description: 1. Laptop: HP Laptop Model 17-cn0078cl 2. Touchpad: Synaptics 3. When first appeared: 3/9/22 at initial load of Linux Mint 20.3 4. lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 5. Expected: touchpad to work 6. What actually happened: nothing, no response from the touchpad (usb mouse works ok though) 7. cat version.log Ubuntu 5.4.0-104.118-generic 5.4.166 8. cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=4091 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:14.0-1/input1:2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/0003:046D:4091.0003/input/input16 U: Uniq=4091-00-00-00-00 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input17 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=20 I: Bus=0003 Vendor=04f2 Product=b710 Version=2747 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input19 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5588060/+files/dmesg.log -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME 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/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Sorry for the delay, life happened... After mucking about with this for the past few days and not being able to get the module to compile on 5.15 for the life of me (always same error "implicit declaration of function ‘platform_get_ethdev_address’ [-Werror=implicit-function-declaration]"), I have decided to just build 5.18-rc6 out of desperation. I figured the changes should be included by now, though I'm not sure and don't know how to check... This is what I did: sudo apt install alien autoconf bison build-essential ccache fakeroot flex gawk git libattr1-dev libblkid-dev libdevmapper-dev libelf-dev libncurses5-dev libselinux-dev libssl-dev libtool libudev-dev linux-headers-$(uname -r) uuid-dev zlib1g-dev mkdir build cd build git clone git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack ubuntu_kernel cd ubuntu_kernel git checkout tags/v5.18-rc6 cp /boot/config-"$(uname -r)" .config yes '' | make oldconfig make prepare scripts cd .. git clone https://github.com/zfsonlinux/zfs.git cd zfs git checkout zfs-2.1.5-staging sh autogen.sh ./configure --prefix=/ --libdir=/lib --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=$HOME/build/ubuntu_kernel --with-linux-obj=$HOME/build/ubuntu_kernel ./copy-builtin $HOME/build/ubuntu_kernel cd ../ubuntu_kernel make menuconfig # include zfs scripts/config --set-str SYSTEM_TRUSTED_KEYS "" scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" make clean make -j 16 bindeb-pkg LOCALVERSION=-aq107-test cd .. sudo apt install ./linux-headers-5.18.0-rc6-aq107-test_5.18.0-rc6-aq107-test-1_amd64.deb ./linux-image-5.18.0-rc6-aq107-test_5.18.0-rc6-aq107-test-1_amd64.deb After a reboot I seem to get exactly the same error, stack trace is near the bottom of the log. What should I do now? -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME 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/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
I should note that regular Ubuntu 22.04 only has 'adwaita-icon-theme' installed, not 'adwaita-icon-theme-full'. To figure out which login screen it is that needs the latter, please: 1. Attach a photo of the login screen. 2. Run: dpkg -l > packages.txt and attach the resulting text file here. ** Summary changed: - [mgag200] Mouse cursor is a semi-opaque white square + [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) ** No longer affects: linux (Ubuntu) ** Package changed: mutter (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita- icon-theme-full) Status in Ubuntu: Incomplete Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972747] 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/1972747 Title: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Jammy/22.04, the kernel modules for the speakup screen reader are not available . # modprobe speakup_ltlk modprobe: FATAL: Module speakup_ltlk not found in directory /lib/modules/5.15.0-27-generic Note: This bug is similar to those originally in 21.04 and 21.10. It seems that with each new release, the speakup kernel modules are left out. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1997 F pulseaudio /dev/snd/pcmC0D0p: john 1997 F...m pulseaudio /dev/snd/controlC1: john 1997 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 20:31:45 2022 InstallationDate: Installed on 2021-08-25 (257 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-10 (0 days ago) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:sku0617: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972747] [NEW] Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04
Public bug reported: After upgrade to Jammy/22.04, the kernel modules for the speakup screen reader are not available . # modprobe speakup_ltlk modprobe: FATAL: Module speakup_ltlk not found in directory /lib/modules/5.15.0-27-generic Note: This bug is similar to those originally in 21.04 and 21.10. It seems that with each new release, the speakup kernel modules are left out. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1997 F pulseaudio /dev/snd/pcmC0D0p: john 1997 F...m pulseaudio /dev/snd/controlC1: john 1997 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 20:31:45 2022 InstallationDate: Installed on 2021-08-25 (257 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-10 (0 days ago) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:sku0617: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972747 Title: Speakup modules missing from kernel after upgrad to Ubuntu Jammy/22.04 Status in linux package in Ubuntu: New Bug description: After upgrade to Jammy/22.04, the kernel modules for the speakup screen reader are not available . # modprobe speakup_ltlk modprobe: FATAL: Module speakup_ltlk not found in directory /lib/modules/5.15.0-27-generic Note: This bug is similar to those originally in 21.04 and 21.10. It seems that with each new release, the speakup kernel modules are left out. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1997 F pulseaudio /dev/snd/pcmC0D0p: john 1997 F...m pulseaudio /dev/snd/controlC1: john 1997 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 20:31:45 2022 InstallationDate: Installed on 2021-08-25 (257 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-10 (0 days ago) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:sku0617: dmi.pr
[Kernel-packages] [Bug 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
If you can only afford to try one kernel then please make it drm-tip: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm- tip/2022-05-08/amd64/ That will tell us if the bug already has a fix upstream. Although you won't get automatic updates for that kernel so may want to uninstall the packages after you've finished testing them. -- 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 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: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launch
[Kernel-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
** Tags added: rls-jj-incoming ** Summary changed: - [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) + [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off) -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/ubuntu/+source/linux/+bug/1971146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
> Using Wayland seems to solve the issue, but there are still programs > like OBS that I need to use that can't capture the desktop That was meant to be fixed in OBS Studio 27 (bug 1838967). If it's not working in Ubuntu 22.04 then please open a new bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972728] Re: Night light not working on Nvidia Wayland
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #290 https://gitlab.gnome.org/GNOME/mutter/-/issues/290 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/290 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Triaged ** Tags added: nvidia nvidia-wayland -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1972728 Title: Night light not working on Nvidia Wayland Status in Mutter: Unknown Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972728] [NEW] Night light not working on Nvidia Wayland
You have been subscribed to a public bug: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Night light not working on Nvidia Wayland https://bugs.launchpad.net/bugs/1972728 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 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 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Information type changed from Public 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972740] [NEW] Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
Public bug reported: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. ** Affects: linux (Ubuntu) Importance: High Status: Fix Committed ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Triaged ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: High Status: Fix Committed ** Affects: linux (Ubuntu Impish) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High Status: 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- 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/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971205] Re: CVE-2022-25258 and CVE-2022-25375
** No longer affects: linux-azure-fde (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: New Status in linux-aws-5.13 package in Ubuntu: New Status in linux-aws-5.4 package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.13 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: New Status in linux-bluefield package in Ubuntu: New Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.13 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gke-5.4 package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-gkeop-5.4 package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-ibm-5.4 package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.13 package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi-5.4 package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971985] Re: Kernel 5.17.5-76051705 not supported
Dmitri's (or rather the Redditer's) solution also worked for me. -- 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/1971985 Title: Kernel 5.17.5-76051705 not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: Yesterday, after a system update for kernel 5.17.5-76051705, in Pop 22.04, the wifi did not work more. After to try uninstall e reinstall the bcmwl-kernel-package trough Pop Shop (it closes when the process is running) and terminal, it shows some of the following messages in lines: Building initial module for 5.17.5-76051705-generic ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is not supported Error! Bad return status for module build on kernel: 5.17.5-76051705-generic (x86_64) I am not sure if here is the right place to communicate this kind of problem or if it is a bug. But I think in soon others will have the same problem. Description: Pop!_OS 22.04 LTS Release: 22.04 bcmwl-kernel-source: Instalado: 6.30.223.271+bdcom-0ubuntu8 Candidato: 6.30.223.271+bdcom-0ubuntu8 Tabela de versão: *** 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1971985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path
Great thanks -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
On a Dell PowerEdge R210 II server I have the same problem: - Ubuntu 22.04 server launched from a liveusb: The screen remains black after loading the kernel - Ubuntu 22.04 desktop launched from a liveusb: The screen remains black after loading the kernel - Update Ubuntu 22.04 server on Ubuntu 21.10 server: The screen is black on reboot while ok under Ubuntu 21.10. Ssh is ok. 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) (prog-if 00 [VGA controller]) DeviceName: Embedded Video Subsystem: Dell MGA G200eW WPCM450 Flags: bus master, medium devsel, latency 0, IRQ 19, IOMMU group 5 Memory at c400 (32-bit, prefetchable) [size=8M] Memory at c500 (32-bit, non-prefetchable) [size=16K] Memory at c480 (32-bit, non-prefetchable) [size=8M] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [dc] Power Management version 1 Kernel driver in use: mgag200 Kernel modules: matroxfb_base, mgag200 $ sudo dmesg | grep -i mgag200 [3.030128] fb0: switching to mgag200 from EFI VGA [3.046095] mgag200 :03:03.0: vgaarb: deactivate vga console [3.049400] [drm] Initialized mgag200 1.0.0 20110418 for :03:03.0 on minor 0 [3.051146] fbcon: mgag200drmfb (fb0) is primary device [3.051975] mgag200 :03:03.0: [drm] drm_plane_enable_fb_damage_clips() not called [3.502482] mgag200 :03:03.0: [drm] fb0: mgag200drmfb frame buffer device $ uname -a Linux serveur 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- 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/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems:Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1&id=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
On 09.05.22 17:39, Jonathan wrote: > Do these changes also effect the linux-hwe branches? > HWE kernels are directly linked to main series kernel of the same version. A fix applied to one is also included in the related HWE 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Hi Andrea, thanks a lot! 1. In my original patch here: https://patchwork.ozlabs.org/project/ubuntu-kernel/patch/20210426081121.37363-1-alexan...@mihalicyn.com/ there was no "fput" call inside ovl_vm_prfile_set helper. fput was in the outer ovl_mmap() function in fs/overlayfs/file.c You last fix looks fully correct. 2. If we compare ovl_mmap function between 5.8 branch and 5.15: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/fs/overlayfs/file.c?h=hwe-5.8#n461 https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/fs/overlayfs/file.c?h=hwe-5.15-next&id=e3e60b65fa4db4722bd4b02a9dae58f7ff5d83d2#n528 we can see that ovl_mmap function was changed after: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/fs/overlayfs/file.c?h=hwe-5.15-next&id=2896900e22f8212606a1837d89a6bbce314ceeda that's the point where the problem was introduced and ovl_vm_prfile_set with this "fput" become incorrect. Right now, with your fix all seems correct. 3. But there is a question. Can we split this thing out of AUFS? As I mentioned before all that we really need here is this part: https://github.com/JPyke3/mbp-manjaro-kernel/blob/master/aufs5-mmap.patch Why we can't remove this `#if IS_ENABLED(CONFIG_AUFS_FS)` and use "shadow file" helper all the time? I'm ready to prepare and test full version of patches to achieve that if it's needed. Regards, Alex -- 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/1967924 Title: re-apply missing overlayfs SAUCE patch Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Starting with 5.13 we've incorrectly dropped the following sauce patch: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files This patch seems to be required to use overlayfs on top of shiftfs and without this patch we may break containers that rely on shiftfs (using zfs/ceph as storage pool w/ shiftfs enabled). [Test case] No specific test case provided. [Fix] The original SAUCE patch relies on AUFS in order to use vma->vm_prfile, but we're not providing AUFS anymore in jammy,. The fix consists of re-apply this patch with a little refactoring to be dependent on CONFIG_AUFS_FS. [Regression potential] This patch is touching overlayfs, so we may see potential regressions in overlayfs. [Original bug report] The next patch has not been ported to the the 5.13 branch: $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656 commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56 Author: Alexander Mikhalitsyn Date: Mon Apr 26 10:11:00 2021 +0200 UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files BugLink: https://bugs.launchpad.net/bugs/1857257 ... Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay") But it isn't in the 5.13 branch: $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct ovl_aio_req 7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO 1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write 1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and rebooting had no effect on the issue. White square "mouse pointer" is present on gdm login screen if /usr/share/icons/adwaita/cursors is missing (renamed). If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors and restart gdm I get valid mouse pointers. gdm is clearly looking for its cursor files in the Adwaita theme directory rather than Yaru. -- 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/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path
** Summary changed: - Regression: nfs cannot access/list wildcard file unless its cached + Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
Thanks for that, will try it. However my box is AMD therefore 1. no onboard video and 2. no Intel. Back to your request of installing an older kernel: I might have found a maintenance window. Given that I did, would you like for me to try any one? I understand you mentioned to install any of them but if we would have *1* shot, would we have any preference in terms of tag? Of course, I would need to stick to v5.something and possibly v5.1x.? -- 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 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: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+subs
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
Having this issue as same as Kes describes. Can be reproduced under Xorg environment running Nvidia 510 drivers and Ubuntu 22.04. Did not have this issue under 20.04. If I have a youtube video running the chrome window lags and the terminal window lags while moving them. If I have this page open it moves without lag. I tried to disable Desktop Icons NG, it helped the issue a bit, but there is still extreme lag. Using Wayland seems to solve the issue, but there are still programs like OBS that I need to use that can't capture the desktop ( not related to this ). Running glxgears also give me lag while moving the window. Let me know if you need me to try something specific that might help you get more data out. INXI dump: System: Host: X Kernel: 5.15.0-27-generic x86_64 bits: 64 Desktop: GNOME 42.0 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x serial: UEFI: American Megatrends v: 4021 date: 08/09/2021 CPU: Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 3400 min/max: N/A cores: 1: 3394 2: 3394 3: 3394 4: 3394 5: 3394 6: 3394 7: 3394 8: 3394 9: 3394 10: 3394 11: 3394 12: 3394 13: 3394 14: 3394 15: 3394 16: 3394 17: 3394 18: 3394 19: 3394 20: 3394 21: 3394 22: 3394 23: 3394 24: 3593 25: 3394 26: 3394 27: 3394 28: 3394 29: 3394 30: 3394 31: 3394 32: 3394 Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3080] driver: nvidia v: 510.60.02 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia gpu: nvidia resolution: 1: 5120x1440~120Hz OpenGL: renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 v: 4.6.0 NVIDIA 510.60.02 Sensors: System Temperatures: cpu: 34.5 C mobo: 34.0 C gpu: nvidia temp: 33 C Fan Speeds (RPM): fan-1: 0 fan-2: 1081 fan-3: 1135 fan-4: 1359 fan-5: 4753 fan-6: 1227 gpu: nvidia fan: 0% Info: Processes: 529 Uptime: 1d 4h 23m Memory: 31.26 GiB used: 4.54 GiB (14.5%) Shell: Bash inxi: 3.3.13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Can affected users please try kernel from https://launchpad.net/~xnox/+snap/xnox-pc-kernel/+build/1757817 ? and see if that helps to resolve the issue for them? Static analysis shows that all intel/ibt-* firmware files are now included. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: In Progress Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
https://lists.ubuntu.com/archives/kernel-team/2022-May/130086.html in review -- 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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: In Progress Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970819] 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 1970819 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
Hi Jeffrey, I did more analysis on this and found that target is posting unexpected response to FLOGI ELS command because of which we are seeing FLOGI failure. We have traced down to target issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Confirmed Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Separately will work on submitting that to our kernels. Separately will work on trying to workaround this bug in our trim- firmware scripts for kernel snaps. ** Also affects: linux (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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => 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/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The AMD based system can not reach s2idle after fix for LP: #1968475. [Fix] No need to evict resources for s2idle case. [Test] Test on a Cezanne, confirmed the 5.14.0-1035 breaks s2idle, and applying the fix can make s2idle work again. [Where problems could occur] The fix only applies to AMD APU, and the resources sould stay at carved out region over sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1972662 Title: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR, e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and most of the time is used by the host to unmap/map the vBAR from/to pBAR when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit eight times (see pci_setup_device() -> pci_read_bases() and pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4 seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total. Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c, so the bit stays in the off state before the PCI device driver calls pci_enable_device(): when the bit is off, pci_read_bases() and pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs. With this change, the boot time of such a VM is reduced by 1.8 * (8-1) * 14 = 176.4 seconds. [Test Case] Microsoft tested [Where things could go wrong] PCI BAR setup could fail or be incorrect. [Other Info] SF: #00336342 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
Everything looks good, so I re-applied the patch with the addition of this extra fix: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next&id=b4c25dba7993400e9c57d3e60bec4ab8bce1b701 -- 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/1967924 Title: re-apply missing overlayfs SAUCE patch Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Starting with 5.13 we've incorrectly dropped the following sauce patch: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files This patch seems to be required to use overlayfs on top of shiftfs and without this patch we may break containers that rely on shiftfs (using zfs/ceph as storage pool w/ shiftfs enabled). [Test case] No specific test case provided. [Fix] The original SAUCE patch relies on AUFS in order to use vma->vm_prfile, but we're not providing AUFS anymore in jammy,. The fix consists of re-apply this patch with a little refactoring to be dependent on CONFIG_AUFS_FS. [Regression potential] This patch is touching overlayfs, so we may see potential regressions in overlayfs. [Original bug report] The next patch has not been ported to the the 5.13 branch: $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656 commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56 Author: Alexander Mikhalitsyn Date: Mon Apr 26 10:11:00 2021 +0200 UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files BugLink: https://bugs.launchpad.net/bugs/1857257 ... Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay") But it isn't in the 5.13 branch: $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct ovl_aio_req 7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO 1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write 1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Do these changes also effect the linux-hwe branches? -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
I think I have a proper fix to re-introduce this patch without panicing the kernel. I'm currently running some stress tests to make sure nothing is broken. If everything goes well I'll re-introduce this patch with the proper fix. -- 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/1967924 Title: re-apply missing overlayfs SAUCE patch Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Starting with 5.13 we've incorrectly dropped the following sauce patch: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files This patch seems to be required to use overlayfs on top of shiftfs and without this patch we may break containers that rely on shiftfs (using zfs/ceph as storage pool w/ shiftfs enabled). [Test case] No specific test case provided. [Fix] The original SAUCE patch relies on AUFS in order to use vma->vm_prfile, but we're not providing AUFS anymore in jammy,. The fix consists of re-apply this patch with a little refactoring to be dependent on CONFIG_AUFS_FS. [Regression potential] This patch is touching overlayfs, so we may see potential regressions in overlayfs. [Original bug report] The next patch has not been ported to the the 5.13 branch: $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656 commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56 Author: Alexander Mikhalitsyn Date: Mon Apr 26 10:11:00 2021 +0200 UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files BugLink: https://bugs.launchpad.net/bugs/1857257 ... Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay") But it isn't in the 5.13 branch: $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct ovl_aio_req 7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO 1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write 1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland. Curiously though, when I try systemctl suspend-then-hibernate (my default way of suspending), I get the following in dmesg: NVRM: GPU :02:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. and suspend does not work (I get a login prompt) Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend-then-hibernate also works fine. Could this be a bug on systemd? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972662] [NEW] [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time
Public bug reported: SRU Justification [Impact] A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR, e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and most of the time is used by the host to unmap/map the vBAR from/to pBAR when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit eight times (see pci_setup_device() -> pci_read_bases() and pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4 seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total. Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c, so the bit stays in the off state before the PCI device driver calls pci_enable_device(): when the bit is off, pci_read_bases() and pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs. With this change, the boot time of such a VM is reduced by 1.8 * (8-1) * 14 = 176.4 seconds. [Test Case] Microsoft tested [Where things could go wrong] PCI BAR setup could fail or be incorrect. [Other Info] SF: #00336342 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Impish) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972662 Title: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR, e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and most of the time is used by the host to unmap/map the vBAR from/to pBAR when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit eight times (see pci_setup_device() -> pci_read_bases() and pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4 seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total. Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c, so the bit stays in the off state before the PCI device driver calls pci_enable_device(): when the bit is off, pci_read_bases() and pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs. With this change, the boot time of such a VM is reduced by 1.8 * (8-1) * 14 = 176.4 seconds. [Test Case] Microsoft tested [Where things could go wrong] PCI BAR setup could fail or be incorrect. [Other Info] SF: #00336342 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3 --- linux-firmware (20220329.git681281e4-0ubuntu3) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] Drop rsync from Build-Depends - [Packaging] Move obsolete scripts - [Packaging] Put symlink checking into its own script * Add missing inside-secure firmware (LP: #1970543) - [Packaging] Include inside-secure firmware * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) (LP: #1969853) - [Packaging] Include ar3k firmware -- Juerg Haefliger Fri, 29 Apr 2022 07:30:37 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1969853 Title: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] No bluetooth found on QCA9565. [Test Case] See below. [Fix] Provide ar3k/* firmware blobs. [Where Problems Could Occur] None expected, this is a regression from Impish. [Original Description] After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 2220 F pulseaudio /dev/snd/pcmC0D0p: diego 2220 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15-3567 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2021 dmi.bios.release: 2.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.18.0 dmi.board.name: 0MM5K1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970543] Re: Add missing inside-secure firmware
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3 --- linux-firmware (20220329.git681281e4-0ubuntu3) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] Drop rsync from Build-Depends - [Packaging] Move obsolete scripts - [Packaging] Put symlink checking into its own script * Add missing inside-secure firmware (LP: #1970543) - [Packaging] Include inside-secure firmware * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) (LP: #1969853) - [Packaging] Include ar3k firmware -- Juerg Haefliger Fri, 29 Apr 2022 07:30:37 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970543 Title: Add missing inside-secure firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] Firmware files for the inside-secure safexcel driver/module are missing. [Fix] Don't remove inside-secure firmwares from the package. [Where Problems Could Occur] None expected. Keep shipping the blobs as before. [Notes] These firmwares were removed because the kernel doesn't reference them. Which is a bug [1]. [1] https://lore.kernel.org/lkml/20220427074351.391580-1-jue...@protonmail.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970293] Re: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3 --- linux-firmware (20220329.git681281e4-0ubuntu3) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] Drop rsync from Build-Depends - [Packaging] Move obsolete scripts - [Packaging] Put symlink checking into its own script * Add missing inside-secure firmware (LP: #1970543) - [Packaging] Include inside-secure firmware * The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms (LP: #1970293) - amdgpu: update yellow carp DMCUB firmware * No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) (LP: #1969853) - [Packaging] Include ar3k firmware -- Juerg Haefliger Fri, 29 Apr 2022 07:30:37 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970293 Title: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Summary] 1. The system will hang on when the HDMI external monitor is connected. 2. The system will hang on after the HDMI external monitor is unplugged. 3. The system will show no display when the HDMI external monitor is unplugged, but the system not hangs on. a. if connect HDMI external monitor back, the system will hang on. b. if connect type-c HDMI external monitor, the system works well. Note: 1. Only built-in HDMI can duplicate. 2. FHD/4K monitor both can duplicate [Steps to reproduce] 2. Boot to OS 3. Connect external montior on HDMI port. [Expected result] The system can work well when the external monitor is connected. [Actual result] The system hangs on with the HDMI external monitor. [Failure rate] 2/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969853] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1969853 Title: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] No bluetooth found on QCA9565. [Test Case] See below. [Fix] Provide ar3k/* firmware blobs. [Where Problems Could Occur] None expected, this is a regression from Impish. [Original Description] After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 2220 F pulseaudio /dev/snd/pcmC0D0p: diego 2220 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15-3567 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2021 dmi.bios.release: 2.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.18.0 dmi.board.name: 0MM5K1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970293] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1970293 Title: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Summary] 1. The system will hang on when the HDMI external monitor is connected. 2. The system will hang on after the HDMI external monitor is unplugged. 3. The system will show no display when the HDMI external monitor is unplugged, but the system not hangs on. a. if connect HDMI external monitor back, the system will hang on. b. if connect type-c HDMI external monitor, the system works well. Note: 1. Only built-in HDMI can duplicate. 2. FHD/4K monitor both can duplicate [Steps to reproduce] 2. Boot to OS 3. Connect external montior on HDMI port. [Expected result] The system can work well when the external monitor is connected. [Actual result] The system hangs on with the HDMI external monitor. [Failure rate] 2/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970543] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1970543 Title: Add missing inside-secure firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] Firmware files for the inside-secure safexcel driver/module are missing. [Fix] Don't remove inside-secure firmwares from the package. [Where Problems Could Occur] None expected. Keep shipping the blobs as before. [Notes] These firmwares were removed because the kernel doesn't reference them. Which is a bug [1]. [1] https://lore.kernel.org/lkml/20220427074351.391580-1-jue...@protonmail.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
It seems that adding "intel_iommu=off" doesn't help to solve the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960213 Title: Kernel Panic on linux-image-5.15.0-18-generic Status in linux package in Ubuntu: Confirmed Bug description: Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012 On 5.13.0-29-generic boot successfully. Laptop: Lenovo Model: 20RA002SRT Stack trace in attached images. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-29-generic. ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grid 2375 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149' Mixer name : 'Conexant CX8070' Components : 'HDA:14f11f86,17aa5079,00100100 HDA:8086280b,80860101,0010' Controls : 55 Simple ctrls : 14 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 20.04 MachineType: LENOVO 20RA002SRT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-29-generic N/A linux-backports-modules-5.13.0-29-generic N/A linux-firmware 1.187.26 Tags: focal Uname: Linux 5.13.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout docker plugdev tty uucp vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 09/15/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET33W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RA002SRT dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14: dmi.product.family: ThinkPad E14 dmi.product.name: 20RA002SRT dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14 dmi.product.version: ThinkPad E14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by @vanvugt You may wanna change the file path of the temporary file thought for better performance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.l
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
@andch, after searching the internet some more, I figured out that I needed to add the proposed for focal in /etc/apt/sources.list in order to install the kernel 5.14.0-1035.38 (the same one that you installed). So I did all that, and THE FIX WORKS. My smartphone can connect to the hotspot and access the internet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** 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/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Unfortunately nvidia.NVreg_EnableS0ixPowerManagement=1 did not work on an old Asus Rog Maximus VIII mobo (Kabylake), nvidia 1650. I also tried this: /etc/modprobe.d/nvidia-power-management.conf options nvidia NVreg_PreserveVideoMemoryAllocations=1 and it didn't work either. Missing textures after suspend. Any other hint? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
oh! Sorry, I didn’t notice thar you’re using 22.04. For 5.15-genric kernel, you can monitor this bug with the Linux -> Jammy series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971985] Re: Kernel 5.17.5-76051705 not supported
Thank you Dmitri(dimastyid) for the solution! It worked for me. Is there a way to close this topic or should be it keep opened? Thanks guys -- 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/1971985 Title: Kernel 5.17.5-76051705 not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: Yesterday, after a system update for kernel 5.17.5-76051705, in Pop 22.04, the wifi did not work more. After to try uninstall e reinstall the bcmwl-kernel-package trough Pop Shop (it closes when the process is running) and terminal, it shows some of the following messages in lines: Building initial module for 5.17.5-76051705-generic ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is not supported Error! Bad return status for module build on kernel: 5.17.5-76051705-generic (x86_64) I am not sure if here is the right place to communicate this kind of problem or if it is a bug. But I think in soon others will have the same problem. Description: Pop!_OS 22.04 LTS Release: 22.04 bcmwl-kernel-source: Instalado: 6.30.223.271+bdcom-0ubuntu8 Candidato: 6.30.223.271+bdcom-0ubuntu8 Tabela de versão: *** 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1971985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
@andch, I am using Ubuntu 22.04 on my DUT. On running the following command: $ sudo apt install linux-oem-20.04d it cannot find the package It returns: E: Unable to locate package linux-oem-20.04d E: Couldn't find any package by glob 'linux-oem-20.04d' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970957] Re: suspend problem
Same here with a T460p. I noticed that the fans did not turn off, so the laptop was not in full sleep mode even thought he power indicator light was already flashing. (BTW, this was a common problem in the early days of Linux sleep capability about 15 years ago.}) -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
Driver team has highlighted this patch is required to address this issue: author James Smart 2022-04-12 15:19:44 -0700 committer Martin K. Petersen 2022-04-18 22:48:43 -0400 commit e294647b1aed4247fe52851f3a3b2b19ae906228 (patch) treefd7e11a3c6f680d5aabd468d523d08ffcd66b59f /drivers/scsi/lpfc parent b83a8c21f3fe874e12eb2b6e6c5cfb220d35c446 (diff) downloadscsi-e294647b1aed4247fe52851f3a3b2b19ae906228.tar.gz scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard lockup call trace hangs the system. Call Trace: _raw_spin_lock_irqsave+0x32/0x40 lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] lpfc_do_work+0x1485/0x1d70 [lpfc] kthread+0x112/0x130 ret_from_fork+0x1f/0x40 Kernel panic - not syncing: Hard LOCKUP The same CPU tries to claim the phba->port_list_lock twice. Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need to take the phba->port_list_lock within lpfc_dmp_dbg(). Link: https://lore.kernel.org/r/2022041008.126521-3-jsmart2...@gmail.com Co-developed-by: Justin Tee Signed-off-by: Justin Tee Signed-off-by: James Smart Signed-off-by: Martin K. Petersen Diffstat (limited to 'drivers/scsi/lpfc') -rw-r--r-- drivers/scsi/lpfc/lpfc_init.c 29 -rw-r--r-- drivers/scsi/lpfc/lpfc_logmsg.h 6 2 files changed, 4 insertions, 31 deletions diff --git a/drivers/scsi/lpfc/lpfc_init.c b/drivers/scsi/lpfc/lpfc_init.c index 461d333b1b3a8..f9cd4b72d949a 100644 --- a/drivers/scsi/lpfc/lpfc_init.c +++ b/drivers/scsi/lpfc/lpfc_init.c @@ -15700,34 +15700,7 @@ void lpfc_dmp_dbg(struct lpfc_hba *phba) unsigned int temp_idx; int i; int j = 0; - unsigned long rem_nsec, iflags; - bool log_verbose = false; - struct lpfc_vport *port_iterator; - - /* Don't dump messages if we explicitly set log_verbose for the -* physical port or any vport. -*/ - if (phba->cfg_log_verbose) - return; - - spin_lock_irqsave(&phba->port_list_lock, iflags); - list_for_each_entry(port_iterator, &phba->port_list, listentry) { - if (port_iterator->load_flag & FC_UNLOADING) - continue; - if (scsi_host_get(lpfc_shost_from_vport(port_iterator))) { - if (port_iterator->cfg_log_verbose) - log_verbose = true; - - scsi_host_put(lpfc_shost_from_vport(port_iterator)); - - if (log_verbose) { - spin_unlock_irqrestore(&phba->port_list_lock, - iflags); - return; - } - } - } - spin_unlock_irqrestore(&phba->port_list_lock, iflags); + unsigned long rem_nsec; if (atomic_cmpxchg(&phba->dbg_log_dmping, 0, 1) != 0) return; diff --git a/drivers/scsi/lpfc/lpfc_logmsg.h b/drivers/scsi/lpfc/lpfc_logmsg.h index 7d480c7987942..a5aafe230c74f 100644 --- a/drivers/scsi/lpfc/lpfc_logmsg.h +++ b/drivers/scsi/lpfc/lpfc_logmsg.h @@ -73,7 +73,7 @@ do { \ #define lpfc_printf_vlog(vport, level, mask, fmt, arg...) \ do { \ { if (((mask) & (vport)->cfg_log_verbose) || (level[1] <= '3')) { \ - if ((mask) & LOG_TRACE_EVENT) \ + if ((mask) & LOG_TRACE_EVENT && !(vport)->cfg_log_verbose) \ lpfc_dmp_dbg((vport)->phba); \ dev_printk(level, &((vport)->phba->pcidev)->dev, "%d:(%d):" \ fmt, (vport)->phba->brd_no, vport->vpi, ##arg); \ @@ -89,11 +89,11 @@ do { \ (phba)->pport->cfg_log_verbose : \ (phba)->cfg_log_verbose; \ if (((mask) & log_verbose) || (level[1] <= '3')) { \ - if ((mask) & LOG_TRACE_EVENT) \ + if ((mask) & LOG_TRACE_EVENT && !log_verbose) \ lpfc_dmp_dbg(phba); \ dev_printk(level, &((phba)->pcidev)->dev, "%d:" \ fmt, phba->brd_no, ##arg); \ - } else if (!(phba)->cfg_log_verbose)\ + } else if (!log_verbose)\ lpfc_dbg_print(phba, "%d:" fmt, phba->brd_no, ##arg); \ } \ } while (0) -- 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Server crash an
[Kernel-packages] [Bug 1972281] 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 1972281 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 Impish) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963802] Re: lenovo x260: unable to suspend or power off cleanly
Same problem occurred by upgrade (from 21.10 to 22.04) on my x260 model 20F5S3BR00. -- 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/1963802 Title: lenovo x260: unable to suspend or power off cleanly Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact has not - power led is off - have to hold down power button to 5s to fully power off. I was convinced this was a hardware issue so tried with a 20.04 live image which completed both operations sucessfully. I've tried all 5.15 kernels including the one in jammy-proposed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamespage 3148 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:17:25 2022 InstallationDate: Installed on 2018-10-18 (1234 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-05-12 (298 days ago) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Same problem on a Dell Vostro 3510. Release: 22.04, Kernel: 5.15.0-27-generic. -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Confirmed Bug description: This problem exists on an HP ProBook 440 G8 Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Wifi Adapter information : description: Wireless interface product: Wi-Fi 6 AX201 vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: 28:d0:ea:21:6a:a1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-23-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff irq:16 memory:600324c000-600324 Error Information: [ 60.882505] CPU: 6 PID: 630 Comm: wpa_supplicant Not tainted 5.15.0-23-generic #23-Ubuntu [ 60.882512] Hardware name: HP HP ProBook 440 G8 Notebook PC/8807, BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+0x52/0x58 [ 60.882532] dump_stack_lvl+0x4a/0x5f [ 60.882541] dump_stack+0x10/0x12 [ 60.882545] iwl_trans_txq_send_hcmd_sync+0x345/0x350 [iwlwifi] [ 60.882582] ? wait_woken+0x70/0x70 [ 60.882589] iwl_trans_txq_send_hcmd+0xaa/0x140 [iwlwifi] [ 60.882619] iwl_trans_send_cmd+0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_send_cmd_pdu+0x6d/0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ppag_send_cmd+0x1b5/0x270 [iwlmvm] [ 60.882695] iwl_mvm_up+0x656/0xa80 [iwlmvm] [ 60.882716] ? __iwl_err.cold+0x25/0x2a [iwlwifi] [ 60.882755] __iwl_mvm_mac_start+0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_mac_start+0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_do_open+0x488/0x9c0 [mac80211] [ 60.882926] ? ieee80211_check_concurrent_iface+0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_open+0x6c/0x90 [mac80211] [ 60.883048] __dev_open+0xf0/0x1c0 [ 60.883054] __dev_change_flags+0x1a3/0x220 [ 60.883058] dev_change_flags+0x26/0x60 [ 60.883061] devinet_ioctl+0x598/0x6f0 [ 60.883068] ? netdev_name_node_lookup_rcu+0x6b/0x80 [ 60.883075] ? _copy_from_user+0x2e/0x60 [ 60.883082] inet_ioctl+0x165/0x190 [ 60.883088] sock_do_ioctl+0x42/0x100 [ 60.883093] ? do_readlinkat+0x10f/0x120 [ 60.883099] sock_ioctl+0xef/0x310 [ 60.883103] ? do_syscall_64+0x69/0xc0 [ 60.883110] __x64_sys_ioctl+0x91/0xc0 [ 60.883116] do_syscall_64+0x59/0xc0 [ 60.883120] ? do_syscall_64+0x69/0xc0 [ 60.883125] ? do_syscall_64+0x69/0xc0 [ 60.883129] ? syscall_exit_to_user_mode+0x27/0x50 [ 60.883133] ? __x64_sys_readlink+0x1e/0x30 [ 60.883137] ? do_syscall_64+0x69/0xc0 [ 60.883142] ? do_syscall_64+0x69/0xc0 [ 60.883147] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 60.883162] RSP: 002b:7ffc168507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00:14.3: failed to send PER_PLATFORM_ANT_GAIN_CMD (-5) [ 60.894910] iwlwifi :00:14.3: mac start retry 1 [ 61.068762] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 61.068863] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 61.068866] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 [ 61.068871] iwlwifi :00:14.3: Loaded firmware version: 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode [ 61.068874] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 61.068878] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [ 61.068881] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 61.068883] iwlwifi :00:14.3: 0x004C2726 | branchlink2 [ 61.068886] iwlwifi :00:14.3: 0x004B974E | interruptlink1 [ 61.068889] i
[Kernel-packages] [Bug 1972281] [NEW] ext4: limit length to bitmap_maxbytes
Public bug reported: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the S0ix option fixed the problem for me. I've added the following option "nvidia.NVreg_EnableS0ixPowerManagement=1" to GRUB_CMDLINE_LINUX_DEFAULT. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology
[Kernel-packages] [Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, 73867c8709) drm/i915/display: Remove check for low voltage sku for max dp source rate Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722513] Re: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration
Is there any update on this? I am on Kernel 5.13.0-1022-azure and linux- cloud-tools-common 5.4.0-109.123 and the script hv_set_ifconfig is only able to manipulate /etc/network/interfaces. Kind Regards -- 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/1722513 Title: [Hyper-V] hv_set_ifconfig fails due to new netplan configuration Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Issue description: hv_set_ifconfig does not work due to new netplan configuration Platform: host independent Distribution name and release: Ubuntu 18.04 Kernel version: 4.15+ The hv_set_ifconfig script does not take in consideration netplan config files. Consequently, the changes made by hv_set_ifconfig in /etc/network/interfaces are not affecting the final network configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM
Also seen in bionic linux-ibm-5.4 5.4.0-1021.23~18.04.1 for sru-20220418 -- 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/1897764 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Groovy: Invalid Bug description: Issue found on Focal 5.4.0-49.53 zVM kernel04 Test failed with: # selftests: memory-hotplug: mem-on-off-test.sh # Test scope: 2% hotplug memory # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # offline 2% hot-pluggable memory in online state # trying to offline 1 out of 16 memory block(s): # online->offline memory0 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 0: unexpected fail # online->offline memory1 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 1: unexpected fail # online->offline memory10 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 10: unexpected fail # online->offline memory11 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 11: unexpected fail # online->offline memory12 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 12: unexpected fail # online->offline memory13 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 13: unexpected fail # online->offline memory14 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 14: unexpected fail # online->offline memory15 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 15: unexpected fail # online->offline memory2 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 2: unexpected fail # online->offline memory3 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 3: unexpected fail # online->offline memory4 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 4: unexpected fail # online->offline memory5 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 5: unexpected fail # online->offline memory6 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 6: unexpected fail # online->offline memory7 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 7: unexpected fail # online->offline memory8 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 8: unexpected fail # online->offline memory9 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 9: unexpected fail # FAILED - unable to offline some memory blocks, device busy? # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # Test with memory notifier error injection not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1 This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well. Passed with 5.4.0-44.48 Passed with 5.4.0-43.47 Failed with 5.4.0-42.46 Looks like it's not very stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels - Error: Unknown device type (missing config)
Also seen in bionic linux-ibm-5.4 5.4.0-1021.23~18.04.1 for sru-20220418 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels - Error: Unknown device type (missing config) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Status in linux-kvm source package in Focal: New Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
I can confirm the bug exists on the Ubuntu kernel 5.15.0-27 and by adding intel_iommu=off to /etc/default/grub solves the issue. Regards, Mick On 09/05/2022 02:52, Daniel van Vugt wrote: > Please try using the original Ubuntu kernel again (5.15.0-27), verify > the bug occurs, and then try comment #31. We need to verify what the > exact fix was. > -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/ubuntu/+source/linux/+bug/1971146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
@ Oibaf #19 If it can help, i start helping debug ubuntu 22.04 from the start with kernel 5.13.0-19.19-generic with light flickering (workable) see bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 and heavy unworkable flickering started (in this bug) with kernel series 5.15.0-17-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera 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: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
When I upgraded to 22.04 I started getting flicker on my external HDMI monitor. Latitude 7300, i7-8665U. A batch of flicker every 15 or 30 minutes or so, not very easy to use for bisecting... There are instances of [336186.058517] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun in dmesg but it doesn't always appear when there is flickering. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera 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: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370
Yes, I think that is correct. If you look at this diagram: https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/left?guid=guid-a06ee5db-8981-4955-86ab-82b36e5aff57&lang=en-us I normally plug the monitor with keyboard into the port labelled 2 and the network adapter into the one labelled 3, both of which are apparently Thunderbolt ports (I do not have any Thunderbolt devices, so just use them as USB-C). The remaining port, which I said above works, is the port labelled 3 in this diagram: https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/right?guid=guid-b67143e0-0e2c-4025-899a-9819aca57baa&lang=en-us and that is apparently USB-C instead of Thunderbolt. -- 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/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have just completed a fresh install of 22.04 on it. When I suspend the laptop, the USB devices that were plugged in when I suspended do not work. Specifically, I had an Ethernet adapter and a USB-C monitor with a keyboard attached through it. The monitor display works as expected, but neither the keyboard nor the Ethernet adapter work after suspending. Interestingly, I can move the Ethernet adapter to the remaining USB-C port and it works correctly. Moving it back afterwards, it still does not work. Please let me know if there is anything more I can do to help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aaron-work 35648 F pulseaudio /dev/snd/controlC0: aaron-work 35648 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 10:36:09 2022 InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971597] Re: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
Test on Barcelo. The error is seen in 5.14.0-1035-oem, but 5.14.0-1036-oem in ppa:canonical-kernel-team/ppa won't see the error. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597/+attachment/5587863/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1971597 Title: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members before initialization") attempted to fix a race condition that lead to a NULL pointer, but in the process caused a regression for _AEI/_EVT declared GPIOs. This manifests in messages showing deferred probing while trying to allocate IRQs like so: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517 amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x002C to IRQ, err -517 amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517 [ .. more of the same .. ] The code for walking _AEI doesn't handle deferred probing and so this leads to non-functional GPIO interrupts. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
For Jammy/5.15 this was fixed in v5.15.25 upstream stable release which was already included in 5.15.0-23.23 (Jammy was released with 5.15.0-27.28). ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Similarly for Impish/5.13 included in upstream stable patchset 2022-04-07 which made it into 5.13.0-41.46. ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Status: New => Fix Committed ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
For Bionic/4.15 the fix is included in upstream stable patchset 2022-03-29 which made it into 4.15.0-177.186, also to be released around today. ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Looking for the mentioned patch in Focal/5.4, this seems to be part of upstream v5.4.181 which was included in 5.4.0-110.124. That should release around today. ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967727] 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/1967727 Title: [Lenovo ThinkPad X260] Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: Confirmed Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969432] Re: 5.17 kernel won't load mok, so it refused to load dkms signed by mok
the fix is not in 5.17.0-1004-oem yet. -- 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/1969432 Title: 5.17 kernel won't load mok, so it refused to load dkms signed by mok Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Bug description: Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967727] Re: [Lenovo ThinkPad X260] Random screen blanks with "CPU pipe B FIFO underrun" error
Daniel, yes I'm using an external monitor via DP. This is the same setup I've been using for a long time with no issue. I've reverted to the Impish kernel (mainly because of an other kernel issue preventing suspend/resume) and that makes the issue disappear. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1967727 Title: [Lenovo ThinkPad X260] Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: New Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971696] Re: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket lib
oibaf packages should conflict with amber, so the bug is there ** Changed in: mesa-amber (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/1971696 Title: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist Status in mesa-amber package in Ubuntu: Invalid Bug description: Some problems with the amber driver that pops up after the startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgl1-amber-dri (not installed) Uname: Linux 5.17.5-051705-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 5 10:49:05 2022 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist InstallationDate: Installed on 2022-04-04 (30 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: mesa-amber Title: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist UpgradeStatus: Upgraded to jammy on 2022-04-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/1971696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968861] Re: Support Cirrus audio codec configurations for Odin platform
Verified 5.14.0-1035 in proposed, audio works correctly. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968861 Title: Support Cirrus audio codec configurations for Odin platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] CS8409 needs new configuration for Odin platform [Fix] Cirrus provides us 2 patches to add the support which are not in upstream yet ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg ALSA: hda/cs8409: Support new Odin Variants Below series of patch is required to be applied before these 2. https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html [Test] Verified on the target machine [Where problems could occur] The first commit only affects the new added Odin platform, and the second one do some modification for other platforms which is hard to know what may lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
Verified linux/jammy version 5.15.0-28-generic: $ uname -r 5.15.0-28-generic $ sudo cpupower frequency-info [sudo] password for ubuntu: analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 4.79 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 400 MHz and 4.79 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.05 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3200MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956509 Title: Support AMD P-State cpufreq control mechanism Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] AMD P-State CPU performance scaling driver not yet supported on AMD Zen based CPU series. [Fix] Mainline commits starting at commit d341db8f48ea ("x86/cpufeatures: Add AMD Collaborative Processor Performance Control feature flag") from v5.17. Even this committed, the defconfig will build it as module, and that prevents AMD P-State driver from actually taking effect. Therefore an additional fix to the kernel configs is necessary. [Test Case] $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz [Where problems could occur] The CPPC feature is implemented in two ways depending on underlying HW details for the APU/CPU: * Dedicated MSR * Shared memory The metrics used to measure power/performance efficiency don't show any improvement on the designs that use shared memory. They do show improvements in the MSR designs. So the code will only enable it by default on the MSR implementation. [Other Info] Althought the v5.17 kernel and newer should have already this committed, an additional fix to the kernel configs is necessary, and unstable/oem-5.17 are also nominated (in a separate thread for they don't need other parts but the config). == original bug report == https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=linux- next&id=40181d67f1e9f1ac87af9c0c194e40ab2a081974 $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956509/+subscrip
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Daniel van Vugt (vanvugt) asked for a kernel bisect with the kernel mainline PPA: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/comments/22 If someone is willing to do it he can do this (from https://wiki.ubuntu.com/Kernel/KernelBisection#Version_bisecting_upstream_kernels): The first step in the bisect process is to find the last "Good" kernel version, followed consecutively in version by the first "Bad" one. That is done by downloading, installing and testing kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=A Thanks. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera 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: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
Verified linux-oem-5.14/focal-proposed version 5.14.0-1035.38 on oem platform: $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 4.79 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 400 MHz and 4.79 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.02 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3200MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956509 Title: Support AMD P-State cpufreq control mechanism Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] AMD P-State CPU performance scaling driver not yet supported on AMD Zen based CPU series. [Fix] Mainline commits starting at commit d341db8f48ea ("x86/cpufeatures: Add AMD Collaborative Processor Performance Control feature flag") from v5.17. Even this committed, the defconfig will build it as module, and that prevents AMD P-State driver from actually taking effect. Therefore an additional fix to the kernel configs is necessary. [Test Case] $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz [Where problems could occur] The CPPC feature is implemented in two ways depending on underlying HW details for the APU/CPU: * Dedicated MSR * Shared memory The metrics used to measure power/performance efficiency don't show any improvement on the designs that use shared memory. They do show improvements in the MSR designs. So the code will only enable it by default on the MSR implementation. [Other Info] Althought the v5.17 kernel and newer should have already this committed, an additional fix to the kernel configs is necessary, and unstable/oem-5.17 are also nominated (in a separate thread for they don't need other parts but the config). == original bug report == https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=linux- next&id=40181d67f1e9f1ac87af9c0c194e40ab2a081974 $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956509/+subscriptions -- Mailing list: h
[Kernel-packages] [Bug 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS
** Tags added: kern-3230 -- 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/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS Status in linux package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: New Status in linux source package in Kinetic: Confirmed Status in linux-raspi source package in Kinetic: New Bug description: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp