[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code
** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Released Status in linux-gcp source package in Impish: Fix Released Status in linux-gcp source package in Jammy: New Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984488] Re: creating dummy network interface fails
[Expired for linux-raspi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1984488 Title: creating dummy network interface fails Status in linux-raspi package in Ubuntu: Expired Bug description: The kernel module needed for dummy network interfaces was moved from the linux-modules-5.15.0 package to the linux-modules-extras-5.15.0 package with kernel release 1013 kernel update. This caused certain services which usually bind to a dummy interface on my system to stop working after the kernel upgrade. Moving kernel modules to the optional extras package post major release is probably not wise since it can unexpectedly break systems using that major release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1013-raspi 5.15.0-1013.15 ProcVersionSignature: Ubuntu 5.15.0-1013.15-raspi 5.15.39 Uname: Linux 5.15.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Aug 10 20:52:13 2022 ImageMediaBuild: 20210819.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to jammy on 2022-05-15 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1984488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake
** Tags added: originate-from-1989404 -- 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/1989578 Title: Add HDMI codec ID for Intel Raptor Lake Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] The HDAudio is not functional on some RaptorLake machines. The audio codec is failed to be probed so no PCM stream available for audio functions. [Fix] Backport the patch from upstream which adds the support for the HDMI codec ID on RaptorLake. [Test] Power on the machine and check if the audio function's working with alsa utilities. [Where problems could occur] The change only applies to the new RaptorLake Intel HDA controller and HDMI codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989578/+subscriptions -- Mailing list: https://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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
I looked around but I can't seem to find how to add the kernel. could you tell me the command(s) or docs to try it out. thanks On 2022-10-06 02:09, Kai-Heng Feng wrote: > Please give this kernel a try: > https://people.canonical.com/~khfeng/lp1970074/ > > ** Changed in: linux (Ubuntu) > Status: Confirmed => 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: 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/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
** Tags added: originate-from-1990599 -- 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/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
https://lkml.org/lkml/2022/10/10/1235 -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: 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/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
[Kernel-packages] [Bug 1992387] [NEW] package linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 failed to install/upgrade: installed linux-modules-nvidia-515-5.15.0-50-generic package post-insta
Public bug reported: unable to save my Nvidia multi monitor display configuration file ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 10 22:09:11 2022 ErrorMessage: installed linux-modules-nvidia-515-5.15.0-50-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-03 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 failed to install/upgrade: installed linux-modules-nvidia-515-5.15.0-50-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1992387 Title: package linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 failed to install/upgrade: installed linux-modules- nvidia-515-5.15.0-50-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: unable to save my Nvidia multi monitor display configuration file ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 10 22:09:11 2022 ErrorMessage: installed linux-modules-nvidia-515-5.15.0-50-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-03 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56 failed to install/upgrade: installed linux-modules-nvidia-515-5.15.0-50-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1992387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
Please test the kernel, which adds the affected GFX to IOMMU quirk list: https://people.canonical.com/~khfeng/gfx-no-dmar/ -- 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/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Bug description: External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. The primary GPU (i915) still works fine. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic 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 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 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 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)
Please test the kernel, which adds the affected GFX to IOMMU quirk list: https://people.canonical.com/~khfeng/gfx-no-dmar/ -- 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: Incomplete Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete 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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
** Tags added: oem-priority originate-from-1991204 somerville -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] Secondary PCI Express Kernel driver in use: mtk_t7xx Kernel modules: mtk_t7xx lshw: *-generic description: Wireless controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:58:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msix msi pm bus_master cap_list configuration: driver=mtk_t7xx latency=0 resources: iomemory:600-5ff iomemory:600-5ff irq:17 memory:601e80-601e807fff memory:5e80-5eff memory:601e00-601e7f modinfo: modinfo mtk_t7xx filename: /lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko license:GPL description:MediaTek PCIe 5G WWAN modem T7xx driver author: MediaTek Inc srcversion: 5FA53465EA0167231B632D4 alias: pci:v14C3d4D75sv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: mtk_t7xx vermagic: 5.19.10-051910-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45 sig_hashalgo: sha512 signature: 78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F: 36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40: 45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D: 77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D: 9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09: 4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE: 9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD: 4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39: D2:B0:64:3D:41:FB:55:1F:AB:D3:76:65:54:C6:06:6E:F7:01:F2:F7: CE:CF:6C:76:17:1B:AD:41:69:29:FB:F8:6B:F9:74:3F:65:6B:C5:63: 98:76:D1:69:24:AA:7E:9D:D0:27:BF:AF:0B:C9:30:3C:1B:2A:AB:B9: 29:22:D5:6B:16:AB:22:43:16:A0:F6:94:EA:78:E7:54:5F:9B:2D:DA: 2E:9B:9F:81:E4:E0:B7:93:ED:9D:8F:79:19:1A:03:2C:00:C5:3A:99: A4:D0:14:6D:21:61:41:02:EC:8D:48:D5:13:0F:D7:AB:5E:B9:BF:17:
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
** Tags added: fixed-in-5.19.8 fixed-upstream -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992383] [NEW] package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1
Public bug reported: Automatic update failed. package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower- monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf- annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid- cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-script- python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf- stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf- timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1/perf- trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man1/usbip.8.gz usr/share/man/man1/usbipd.8.gz usr/share/man/man8/bpftool-btf.8.gz usr/share/man/man8/bpftool-cgroup.8.gz usr/share/man/man8/bpftool- feature.8.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool-net.8.gz usr/share/man/man8/bpftool-perf.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz usr/share/man/man8/turbostat.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools- common 5.4.0-125.141 ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21 Uname: Linux 5.14.0-1051-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: linux-intel-iotg-5.15-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 10 20:39:09 2022 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 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-5.15-tools-common_5.15.0-1016.21~20.04.1_all.deb ... Unpacking linux-intel-iotg-5.15-tools-common (5.15.0-1016.21~20.04.1) over (5.15.0-1010.14~20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-5.15-tools-common_5.15.0-1016.21~20.04.1_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-125.141 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-125.141 InstallationDate: Installed on 2022-06-08 (124 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-intel-iotg-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1992383 Title: package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf- bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf- report.1.gz
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
In case anyone is curious conversation is on-going on the kernel-team mailing list https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
@juliank please test initrd-less boot; for example lxc launch --vm which uses linux-kvm flavour booted without initrd. There are differences of the mount options as applied by initramfs- tools; systemd; and kernel itself. -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
@juliank, is this an aws system? If not there's a good chance that you are using an initramfs to mount the filesystems. That's definited in either /etc/init.d/udev or directly out of the init that lives in the initramfs. -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 I tried the suggested workaround of purging nvidia packages and running ubuntu-drivers install. What I observed is that the nvidia-driver-510 packages were removed, and ubuntu-drivers subsequently installed nvidia- driver-515. Sadly, it did not resolve the problem. Booting still halts before getting to the LUKS passphrase input screen. If I boot the 5.19.0-19 kernel with "nomodeset", it will get a bit further, to the point where I can type in my LUKS passphrase. However, X11 does not start afterwards, and I am limited to logging in on console ttys. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992344] Re: OOM on ZFS scrub
One of our ZFS storage servers crashed several times in the past. I was running out of memory and ended with a kernel panic. The server did not have a load on these occasions, as it happened on Sundays. ZFS runs its scrubs on Sunday. (on our servers) The pool size: 411TB Release: Ubuntu 22.04.1 LTS zfsutils-linux: 2.1.4-0ubuntu0.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1992344 Title: OOM on ZFS scrub Status in zfs-linux package in Ubuntu: New Bug description: Every time zfs scrub executes exhaust memory hanging the server after several hours (This is almos 600T zpool). Issue as describe in: https://github.com/openzfs/zfs/issues/13546 - Description: Ubuntu 22.04.1 LTS Release: 22.04 - zfsutils-linux: Installed: 2.1.4-0ubuntu0.1 Candidate: 2.1.4-0ubuntu0.1 Version table: *** 2.1.4-0ubuntu0.1 500 500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.1.2-1ubuntu3 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - It is expected that zfs scrub finish within acceptable amount of time despite the size of the pool. - It crashes every time causing a kernel panic and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 10 14:38:38 2022 SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-07-01 (100 days ago) modified.conffile..etc.default.zfs: [modified] mtime.conffile..etc.default.zfs: 2022-07-18T13:53:36.058781 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1992344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991790] Re: Disable sv57 as the userspace is not ready
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992365] 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/1992365 Title: unplugging the headphones jack triggered suspend Status in linux package in Ubuntu: Confirmed Bug description: The Framework laptop, with 29% battery and nothing abnormal, set itself to sleep when I pulled the audio jack to unplug my headphones. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 5327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 17:58:32 2022 InstallationDate: Installed on 2022-03-11 (213 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (164 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
I have tried `sudo apt install linux-oem-22.04a` to install linux- image-5.17.0-1018-oem and the same problem occurs: `top` lists two, not one, kworker processes running hot continuously. And with linux-image-5.10.0-50-generic (released today for Ubuntu 22.04a), same problem. -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP
[Kernel-packages] [Bug 1992365] [NEW] unplugging the headphones jack triggered suspend
Public bug reported: The Framework laptop, with 29% battery and nothing abnormal, set itself to sleep when I pulled the audio jack to unplug my headphones. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 5327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 17:58:32 2022 InstallationDate: Installed on 2022-03-11 (213 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (164 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: - The laptop, with 29% battery and nothing abnormal, set itself to sleep - when I pulled the audio jack to unplug my headphones. + The Framework laptop, with 29% battery and nothing abnormal, set itself + to sleep when I pulled the audio jack to unplug my headphones. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: albert 5327 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: albert 5327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 17:58:32 2022 InstallationDate: Installed on 2022-03-11 (213 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: - + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - linux-restricted-modules-5.15.0-48-generic N/A - linux-backports-modules-5.15.0-48-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.5 + linux-restricted-modules-5.15.0-48-generic N/A + linux-backports-modules-5.15.0-48-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: - 1: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 1: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (164 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku:
[Kernel-packages] [Bug 1992362] 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/1992362 Title: USB stops responding on XPS9320 Status in linux package in Ubuntu: Confirmed Bug description: An intermittent problem, but to reproduce: * unplug a USB device * plug it back in * notice it hasn't been detected After this point, no amount of plugging or unplugging seems to change anything: nothing appears in `dmesg`, `lsusb` shows only internal USB hardware, and video-over-USB devices do not appear in `/sys/class/drm`. Both USB ports are similarly unresponsive. The only remedy appears to be to reboot. `dmesg` shows the unplug event, but nothing after that: ``` Oct 10 16:38:55 xps9320 kernel: [ 2103.140449] usb 3-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.140457] usb 3-1.2: USB disconnect, device number 4 Oct 10 16:38:55 xps9320 kernel: [ 2103.140459] usb 3-1.2.3: USB disconnect, device number 7 Oct 10 16:38:55 xps9320 kernel: [ 2103.140462] usb 3-1.2.3.1: USB disconnect, device number 10 Oct 10 16:38:55 xps9320 kernel: [ 2103.221393] r8152 2-1.2.4:1.0 enx00e04c681052: Stop submitting intr, status -71 Oct 10 16:38:55 xps9320 kernel: [ 2103.423464] usb 3-1.2.3.2: USB disconnect, device number 11 Oct 10 16:38:55 xps9320 kernel: [ 2103.753373] usb 3-1.2.5: USB disconnect, device number 9 Oct 10 16:38:55 xps9320 kernel: [ 2103.772563] usb 3-1.5: USB disconnect, device number 6 Oct 10 16:38:55 xps9320 kernel: [ 2103.904926] usb 2-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.904947] usb 2-1.2: USB disconnect, device number 3 Oct 10 16:38:55 xps9320 kernel: [ 2103.904954] usb 2-1.2.4: USB disconnect, device number 4 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rav2115 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Oct 10 17:01:04 2022 InstallationDate: Installed on 2022-06-28 (103 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 9320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0CW9KM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/13/2022:br1.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CW9KM:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919307] Re: kernel hang
5.4 was a long time ago, so I guess there's no point keeping this open ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919307 Title: kernel hang Status in linux package in Ubuntu: Invalid Bug description: My system locked up, and stopped responding to mouse movement, keyboard, network traffic, etc. A few minutes later, it appeared to recover, although my X session restarted and I had to log back in. I found this in my kern.log: Mar 16 09:08:33 fred kernel: [83775.521219] INFO: task jbd2/dm-1-8:1142 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521223] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521226] jbd2/dm-1-8 D0 1142 2 0x80004000 Mar 16 09:08:33 fred kernel: [83775.521228] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521235] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521238] ? dm_process_bio+0x89/0x100 Mar 16 09:08:33 fred kernel: [83775.521240] ? bit_wait_timeout+0xa0/0xa0 Mar 16 09:08:33 fred kernel: [83775.521241] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521243] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521244] bit_wait_io+0x11/0x50 Mar 16 09:08:33 fred kernel: [83775.521246] __wait_on_bit+0x33/0xa0 Mar 16 09:08:33 fred kernel: [83775.521248] ? submit_bio+0x48/0x1d0 Mar 16 09:08:33 fred kernel: [83775.521250] out_of_line_wait_on_bit+0x8d/0xb0 Mar 16 09:08:33 fred kernel: [83775.521252] ? var_wake_function+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521254] __wait_on_buffer+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521258] jbd2_journal_commit_transaction+0xf50/0x17e8 Mar 16 09:08:33 fred kernel: [83775.521262] kjournald2+0xb6/0x280 Mar 16 09:08:33 fred kernel: [83775.521264] ? wait_woken+0x80/0x80 Mar 16 09:08:33 fred kernel: [83775.521267] kthread+0x104/0x140 Mar 16 09:08:33 fred kernel: [83775.521268] ? commit_timeout+0x20/0x20 Mar 16 09:08:33 fred kernel: [83775.521269] ? kthread_park+0x90/0x90 Mar 16 09:08:33 fred kernel: [83775.521271] ret_from_fork+0x35/0x40 Mar 16 09:08:33 fred kernel: [83775.521324] INFO: task alsa-sink-USB A:3405 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521326] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521327] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521328] alsa-sink-USB A D0 3405 3321 0x0320 Mar 16 09:08:33 fred kernel: [83775.521329] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521332] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521334] ? __switch_to_asm+0x34/0x70 Mar 16 09:08:33 fred kernel: [83775.521336] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521337] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521340] wait_on_page_bit+0x11c/0x200 Mar 16 09:08:33 fred kernel: [83775.521342] ? file_fdatawait_range+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521344] wait_on_page_writeback+0x43/0x90 Mar 16 09:08:33 fred kernel: [83775.521346] shmem_swapin_page+0x23b/0x660 Mar 16 09:08:33 fred kernel: [83775.521348] ? xas_load+0xd/0x80 Mar 16 09:08:33 fred kernel: [83775.521349] ? find_get_entry+0x5e/0x170 Mar 16 09:08:33 fred kernel: [83775.521351] shmem_getpage_gfp+0x3c8/0x940 Mar 16 09:08:33 fred kernel: [83775.521354] ? page_add_file_rmap+0xff/0x1a0 Mar 16 09:08:33 fred kernel: [83775.521355] shmem_fault+0x79/0x210 Mar 16 09:08:33 fred kernel: [83775.521358] __do_fault+0x3c/0x130 Mar 16 09:08:33 fred kernel: [83775.521359] do_fault+0x24b/0x640 Mar 16 09:08:33 fred kernel: [83775.521361] __handle_mm_fault+0x4c5/0x7a0 Mar 16 09:08:33 fred kernel: [83775.521363] handle_mm_fault+0xca/0x200 Mar 16 09:08:33 fred kernel: [83775.521365] do_user_addr_fault+0x1f9/0x450 Mar 16 09:08:33 fred kernel: [83775.521368] __do_page_fault+0x58/0x90 Mar 16 09:08:33 fred kernel: [83775.521369] do_page_fault+0x2c/0xe0 Mar 16 09:08:33 fred kernel: [83775.521371] page_fault+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521373] RIP: 0033:0x7f94a7e13210 Mar 16 09:08:33 fred kernel: [83775.521378] Code: Bad RIP value. Mar 16 09:08:33 fred kernel: [83775.521378] RSP: 002b:7f94a0a54390 EFLAGS: 00010206 Mar 16 09:08:33 fred kernel: [83775.521380] RAX: 7f94a2e37000 RBX: 558cba86ea00 RCX: 0001 Mar 16 09:08:33 fred kernel: [83775.521381] RDX: 000327d20610 RSI: 7f94a0a54680 RDI: 7f94a2e37000 Mar 16 09:08:33 fred kernel: [83775.521382] RBP: 7f94a0a54680
[Kernel-packages] [Bug 1992362] [NEW] USB stops responding on XPS9320
Public bug reported: An intermittent problem, but to reproduce: * unplug a USB device * plug it back in * notice it hasn't been detected After this point, no amount of plugging or unplugging seems to change anything: nothing appears in `dmesg`, `lsusb` shows only internal USB hardware, and video-over-USB devices do not appear in `/sys/class/drm`. Both USB ports are similarly unresponsive. The only remedy appears to be to reboot. `dmesg` shows the unplug event, but nothing after that: ``` Oct 10 16:38:55 xps9320 kernel: [ 2103.140449] usb 3-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.140457] usb 3-1.2: USB disconnect, device number 4 Oct 10 16:38:55 xps9320 kernel: [ 2103.140459] usb 3-1.2.3: USB disconnect, device number 7 Oct 10 16:38:55 xps9320 kernel: [ 2103.140462] usb 3-1.2.3.1: USB disconnect, device number 10 Oct 10 16:38:55 xps9320 kernel: [ 2103.221393] r8152 2-1.2.4:1.0 enx00e04c681052: Stop submitting intr, status -71 Oct 10 16:38:55 xps9320 kernel: [ 2103.423464] usb 3-1.2.3.2: USB disconnect, device number 11 Oct 10 16:38:55 xps9320 kernel: [ 2103.753373] usb 3-1.2.5: USB disconnect, device number 9 Oct 10 16:38:55 xps9320 kernel: [ 2103.772563] usb 3-1.5: USB disconnect, device number 6 Oct 10 16:38:55 xps9320 kernel: [ 2103.904926] usb 2-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.904947] usb 2-1.2: USB disconnect, device number 3 Oct 10 16:38:55 xps9320 kernel: [ 2103.904954] usb 2-1.2.4: USB disconnect, device number 4 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rav2115 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Oct 10 17:01:04 2022 InstallationDate: Installed on 2022-06-28 (103 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 9320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0CW9KM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/13/2022:br1.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CW9KM:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 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/1992362 Title: USB stops responding on XPS9320 Status in linux package in Ubuntu: New Bug description: An intermittent problem, but to reproduce: * unplug a USB device * plug it back in * notice it hasn't been detected After this point, no amount of plugging or unplugging seems to change anything: nothing appears in `dmesg`, `lsusb` shows only internal USB hardware, and video-over-USB devices do not appear in `/sys/class/drm`. Both USB ports are similarly unresponsive. The only remedy appears to be to reboot. `dmesg` shows the unplug event, but nothing after that: ``` Oct 10 16:38:55 xps9320 kernel: [ 2103.140449] usb 3-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.140457] usb 3-1.2: USB disconnect, device number 4 Oct 10 16:38:55 xps9320 kernel: [ 2103.140459] usb 3-1.2.3: USB disconnect, device number 7 Oct 10 16:38:55 xps9320 kernel: [ 2103.140462] usb 3-1.2.3.1: USB disconnect, device number 10 Oct 10 16:38:55 xps9320 kernel: [ 2103.221393] r8152 2-1.2.4:1.0 enx00e04c681052: Stop submitting intr, status -71 Oct 10 16:38:55 xps9320 kernel: [ 2103.423464] usb 3-1.2.3.2: USB disconnect, device number 11 Oct 10 16:38:55 xps9320 kernel: [ 2103.753373] usb 3-1.2.5: USB disconnect, device number 9 Oct 10 16:38:55 xps9320 kernel: [ 2103.772563] usb 3-1.5: USB disconnect, device number 6 Oct 10 16:38:55 xps9320 kernel: [ 2103.904926] usb 2-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.904947] usb 2-1.2: USB disconnect, device number 3 Oct 10 16:38:55 xps9320 kernel: [ 2103.904954] usb 2-1.2.4: USB disconnect, device number 4 ```
[Kernel-packages] [Bug 1990851] Re: Unable to boot 5.19.0-18 with modeset
Could you test this kernel - 5.19.0-19.19+i915fix - and report if it fixes your issue? https://kernel.ubuntu.com/~arighi/lp-1991703/ -- 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/1990851 Title: Unable to boot 5.19.0-18 with modeset Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to `linux-image-5.19.0-18-generic`, system seems freeze during the boot. Boot to earlier 5.19 kernel, looks fine. And 5.19.0-18 with `nomodeset` also works. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-18-generic 5.19.0-18.18 ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7 Uname: Linux 5.19.0-18-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2004 F pipewire gdm2008 F wireplumber /dev/snd/controlC0: gdm2008 F wireplumber CasperMD5CheckResult: unknown Date: Mon Sep 26 21:25:44 2022 MachineType: LENOVO 82TF ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-18-generic root=/dev/mapper/vgroot-lvroot ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-18-generic N/A linux-backports-modules-5.19.0-18-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-07 (19 days ago) dmi.bios.date: 06/16/2022 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: JYCN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y9000X IAH7 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7: dmi.product.family: Legion Y9000X IAH7 dmi.product.name: 82TF dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7 dmi.product.version: Legion Y9000X IAH7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991027] Re: rcu_preempt detected expedited stalls on CPUs/tasks
*** This bug is a duplicate of bug 1991951 ***
https://bugs.launchpad.net/bugs/1991951
Hi,
This bug a duplicate of bug 1991951, a fix is already applied and is
scheduled to be released with the next 5.19 kernel update.
** This bug has been marked a duplicate of bug 1991951
RCU stalls
--
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/1991027
Title:
rcu_preempt detected expedited stalls on CPUs/tasks
Status in linux package in Ubuntu:
Confirmed
Bug description:
[3.740699] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 2-... } 6 jiffies s: 65 root: 0x1/.
[3.740714] rcu: blocking rcu_node structures (internal RCU debug):
l=1:0-9:0x4/.
[3.740739] Task dump for CPU 2:
[3.740740] task:systemd-udevd state:R running task stack:0
pid: 534 ppid: 516 flags:0x400a
[3.740743] Call Trace:
[3.740758]
[3.740760] ? kallsyms_lookup+0x14/0x20
[3.740763] ? test_for_valid_rec+0x38/0x80
[3.740765] ? change_page_attr_set_clr+0x158/0x1d0
[3.740768] ? ftrace_module_enable+0xa6/0x210
[3.740770] ? load_module+0x636/0xcb0
[3.740772] ? __do_sys_finit_module+0xbd/0x130
[3.740773] ? __do_sys_finit_module+0xbd/0x130
[3.740775] ? __x64_sys_finit_module+0x18/0x20
[3.740776] ? do_syscall_64+0x58/0x80
[3.740778] ? ksys_mmap_pgoff+0x10c/0x250
[3.740780] ? exit_to_user_mode_prepare+0x30/0xa0
[3.740782] ? syscall_exit_to_user_mode+0x26/0x50
[3.740784] ? __x64_sys_mmap+0x33/0x50
[3.740785] ? do_syscall_64+0x67/0x80
[3.740786] ? __x64_sys_lseek+0x18/0x20
[3.740788] ? do_syscall_64+0x67/0x80
[3.740789] ? exit_to_user_mode_prepare+0x85/0xa0
[3.740791] ? syscall_exit_to_user_mode+0x26/0x50
[3.740792] ? do_syscall_64+0x67/0x80
[3.740793] ? do_syscall_64+0x67/0x80
[3.740794] ? sysvec_call_function+0x4b/0xa0
[3.740796] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[3.740797]
[3.816703] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 2-... } 25 jiffies s: 65 root: 0x1/.
[3.816719] rcu: blocking rcu_node structures (internal RCU debug):
l=1:0-9:0x4/.
[3.816745] Task dump for CPU 2:
[3.816745] task:systemd-udevd state:R running task stack:0
pid: 534 ppid: 516 flags:0x400a
[3.816747] Call Trace:
[3.816748]
[3.816749] ? kallsyms_lookup+0x14/0x20
[3.816751] ? test_for_valid_rec+0x38/0x80
[3.816753] ? change_page_attr_set_clr+0x158/0x1d0
[3.816755] ? ftrace_module_enable+0xa6/0x210
[3.816757] ? load_module+0x636/0xcb0
[3.816759] ? __do_sys_finit_module+0xbd/0x130
[3.816760] ? __do_sys_finit_module+0xbd/0x130
[3.816762] ? __x64_sys_finit_module+0x18/0x20
[3.816763] ? do_syscall_64+0x58/0x80
[3.816765] ? ksys_mmap_pgoff+0x10c/0x250
[3.816766] ? exit_to_user_mode_prepare+0x30/0xa0
[3.816768] ? syscall_exit_to_user_mode+0x26/0x50
[3.816770] ? __x64_sys_mmap+0x33/0x50
[3.816771] ? do_syscall_64+0x67/0x80
[3.816772] ? __x64_sys_lseek+0x18/0x20
[3.816773] ? do_syscall_64+0x67/0x80
[3.816774] ? exit_to_user_mode_prepare+0x85/0xa0
[3.816776] ? syscall_exit_to_user_mode+0x26/0x50
[3.816777] ? do_syscall_64+0x67/0x80
[3.816778] ? do_syscall_64+0x67/0x80
[3.816779] ? sysvec_call_function+0x4b/0xa0
[3.816781] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[3.816782]
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:crow 1930 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Sep 27 18:51:41 2022
InstallationDate: Installed on 2022-09-10 (17 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
IwConfig:
lono wireless extensions.
enp2s0no wireless extensions.
MachineType: Dell Inc. XPS 8940
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic
root=UUID=a8ff0852-c8bb-4cba-a02f-7acb738f7666 ro audit=0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
linux-backports-modules-5.19.0-15-generic N/A
[Kernel-packages] [Bug 1991951] Re: RCU stalls
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991951 Title: RCU stalls Status in linux package in Ubuntu: Fix Committed Bug description: our RCU Stall Timeouts are different to upstream defaults; with regular one 3x longer; and expedited one 1000x shorter. not sure why. Let's harmonize on 60 & 0, which is 60 for regular ones that are set on most architectures; and upstream default for the expedited ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
** Changed in: grub2-signed (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: New Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: New Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 ** This bug has been marked a duplicate of bug 1991704 Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
5.19-0-19.19+i915fix works for me. ** Attachment added: "kern.log-5.19-0-19.19+i915fix" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622740/+files/kern.log-5.19-0-19.19+i915fix -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification:
--
[Impact]
* If the mlx5 driver is reloading while the recovery flow is happening,
and if it receives new commands before the command interface is up
again, this can lead to null pointer that tries to access non-
initialized command structures.
* So it's required to avoid processing commands before the command
interface is up again.
* This is accomplished by a new cmdif state that helps to avoid
processing commands while cmdif is not ready.
[Fix]
* backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
* An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
is needed that has Mellanox cards (RoCE Express 2.1) assigned,
configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
* Now trigger a recovery (guess that can be done at the Support Element)
and reload the driver at the same time.
* Make sure the module/driver mlx5 is loaded and in use
(otherwise it can't be removed/unloaded).
* Now remove/unload the module with:
sudo modprobe -r mlx5
and (re-)load it again with:
sudo modprobe mlx5
* Due to the lack of RoCE Express 2.1 hardware,
IBM needs to do the verification.
[Where problems could occur]
* In case there is an issue with 'cmdif' it might not have the correct
interface state, which:
- either might lead to the fact that commands are not properly blocked
and the situation is similar like before
- or the commands may get always blocked,
which render the hardware useless
- or might block in wrong situation,
which will cause unexpected issues and broken behavior.
* Since the patch got upstream accepted with v5.7-rc7 it's
not new to the kernel, was already part of groovy (and above)
and is therefor already in use by newer Ubuntu releases.
[Other Info]
* Since the patch is upstream since v5.7-rc7,
it's already included in jammy and kinetic.
* Since the upstream patch incl. the line:
Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
Connect-IB adapters") it looks to me that it was forgotten
to mark the patch for upstream stable updates.
* Such SRUs for focal's 5.4 will automatically land in bionic's
hwe-5.4, too. But since this was especially requested for
bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
echo "Usage: $0 "
exit 1
fi
while true; do
cat /sys/class/net/$1/duplex > /dev/null
cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the NIC:
echo 1 > /sys/bus/pci/devices//reset
Then first I got a lot of the following messages:
mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
query port ptys failed: -5
And then as the mlx5 driver's recovery kicks in the oops as below:
[ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f
after 1 iterations
[ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called
[ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010
[ 659.104169] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 659.104171] Failing address: TEID: 0483
[ 659.104172] Fault in home space mode while using kernel ASCE.
[ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800
P:003d
[ 659.104200] Oops: 0004 ilc:2 [#1] SMP
[ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch
vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
sudo apt-get --purge remove '*nvidia*' sudo ubuntu-drivers install solved the problem for me. I am in KDE running in 5.19.0-19-generic with Nvidia 515 drivers. Thanks a lot. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Could you test this kernel - 5.19.0-19.19+i915fix - and report if it fixes your issue? https://kernel.ubuntu.com/~arighi/lp-1991703/ -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
Hi Heinrich, I can see the following in your dmesg log: NVRM: API mismatch: the client has the version 515.65.01, but NVRM: this kernel module has the version 510.85.02 Can you follow these steps, please, so that we can rule out this being the main problem? Remove any nvidia package left on your system: sudo apt-get --purge remove '*nvidia*' Finally, install the driver using the following command: sudo ubuntu-drivers install Reboot, and see if it helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] 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/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Re: Asus ROG Zephyrus GX701L sound problem
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: New Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992344] [NEW] OOM on ZFS scrub
Public bug reported: Every time zfs scrub executes exhaust memory hanging the server after several hours (This is almos 600T zpool). Issue as describe in: https://github.com/openzfs/zfs/issues/13546 - Description:Ubuntu 22.04.1 LTS Release:22.04 - zfsutils-linux: Installed: 2.1.4-0ubuntu0.1 Candidate: 2.1.4-0ubuntu0.1 Version table: *** 2.1.4-0ubuntu0.1 500 500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.1.2-1ubuntu3 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - It is expected that zfs scrub finish within acceptable amount of time despite the size of the pool. - It crashes every time causing a kernel panic and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 10 14:38:38 2022 SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-07-01 (100 days ago) modified.conffile..etc.default.zfs: [modified] mtime.conffile..etc.default.zfs: 2022-07-18T13:53:36.058781 ** Affects: zfs-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 zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1992344 Title: OOM on ZFS scrub Status in zfs-linux package in Ubuntu: New Bug description: Every time zfs scrub executes exhaust memory hanging the server after several hours (This is almos 600T zpool). Issue as describe in: https://github.com/openzfs/zfs/issues/13546 - Description: Ubuntu 22.04.1 LTS Release: 22.04 - zfsutils-linux: Installed: 2.1.4-0ubuntu0.1 Candidate: 2.1.4-0ubuntu0.1 Version table: *** 2.1.4-0ubuntu0.1 500 500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.1.2-1ubuntu3 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - It is expected that zfs scrub finish within acceptable amount of time despite the size of the pool. - It crashes every time causing a kernel panic and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 10 14:38:38 2022 SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-07-01 (100 days ago) modified.conffile..etc.default.zfs: [modified] mtime.conffile..etc.default.zfs: 2022-07-18T13:53:36.058781 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1992344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915276] Re: [Lenovo V15-IIL] Touchpad not working
@Alex tried with hwe kernel but issue still persists. tried installing oem kernel, getting below error sudo apt install linux-oem-20.04b [sudo] password for rohit: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-oem-20.04b E: Couldn't find any package by glob 'linux-oem-20.04b' -- 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/1915276 Title: [Lenovo V15-IIL] Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I have recently switched to Ubuntu from Windows 10 but during and after the installation the touchpad is unresponsive at all. I have tried almost all the things from google but nothing works. I hope this issue might get resolved soon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neutrino 1440 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:16:29 2021 InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:1135 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=e14254b4-ac0f-4e72-8e11-a450ac37103c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-10 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
So, it looks like there are multiple issues here. The NULL pointer
dereference bug that I see in comment #25 seems to be fixed by
458ec0c8f359 ("drm/i915: fix null pointer dereference"), but this can
happen only when i915 is used.
For the other problem(s) do you happen to have a kernel oops / trace?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1991703
Title:
Failure to boot with linux-image-5.19.0-18-generic and
-5.19.0-19-generic
Status in linux-signed package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Confirmed
Bug description:
Since the last kernel update today my system stops in the middle of the boot
process and does not reach KDE.
---
ProblemType: Bug
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2021-05-26 (495 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm
nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G
hugepages=4
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
linux-backports-modules-5.19.0-15-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
RfKill:
Tags: kinetic uec-images
Uname: Linux 5.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/24/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4204
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
Re-titling bug report to avoid printing unprintable characters in the
kernel upload changelog.
** Description changed:
+ earlyconsole prints on 5.19.0-1002-generic
+
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a workaround
-until the following patch is backported
+ until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
** Summary changed:
- earlyconsole prints on 5.19.0-1002-generic
+ earlyconsole prints question marks on 5.19.0-1002-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1988984
Title:
earlyconsole prints question marks on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
New
Bug description:
earlyconsole prints on 5.19.0-1002-generic
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a workaround
until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
Hello Andrea, As expected an i915 fix is irrelevant for a system without an i915 GPU. The problem persists with your kernel. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991790] Re: Disable sv57 as the userspace is not ready
** Description changed: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software - using too many bits for this "pointer tagging" technique. + using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and - other Go programs works correctly and that you can compile a + other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the kernel to downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and other Go programs work correctly and that you can compile a simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. * Qemu will no longer work with > 256 TB of memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991790] Re: Disable sv57 as the userspace is not ready
** Description changed: [ Impact ] - sv57 breaks Go since Go uses the upper bits of a pointer to store data, - and it is not ready for sv57 yet. It probably breaks other type of - software using this "pointer tagging" technic. The following patch fixes - this: at the moment, there is no way to indicate to the kernel to - downgrade to sv48, so we must patch the kernel. + * Linux 5.18 merged support for 5-level page tables (sv57), and it + does it such that 5-level page tables are used whenever the + system supports it. + + * So far only Qemu support sv57, but it breaks Go since Go uses + too many of the upper bits of pointers to store data, and is not + yet ready for sv57. It probably breaks other types of software + using too many bits for this "pointer tagging" technique. + At the moment, there is no way to indicate to the kernel to + downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) - disable_pgtable_l4(); - } - + disable_pgtable_l4(); + } + + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + - memset(early_pg_dir, 0, PAGE_SIZE); - memset(early_p4d, 0, PAGE_SIZE); - memset(early_pud, 0, PAGE_SIZE); + memset(early_pg_dir, 0, PAGE_SIZE); + memset(early_p4d, 0, PAGE_SIZE); + memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] - Build an image with the new kernel and make sure snapd started - correctly, or that you can compile a simple helloworld written in Go. + * Build an image with the patched kernel and make sure snapd and + other Go programs works correctly and that you can compile a + simple helloworld written in Go. [ Where problems could occur ] - The patch could be wrong, but I already built a kernel with it and it - worked fine. + * The patch could be buggy. + + * Qemu will no longer work with > 128 PB of memory. ** Description changed: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it - does it such that 5-level page tables are used whenever the - system supports it. + does it such that 5-level page tables are used whenever the + system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses - too many of the upper bits of pointers to store data, and is not - yet ready for sv57. It probably breaks other types of software - using too many bits for this "pointer tagging" technique. - At the moment, there is no way to indicate to the kernel to - downgrade to sv48, so we must patch the kernel: + too many of the upper bits of pointers to store data, and is not + yet ready for sv57. It probably breaks other types of software + using too many bits for this "pointer tagging" technique. + At the moment, there is no way to indicate to the kernel to + downgrade to sv48, so we must patch the kernel: diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] * Build an image with the patched kernel and make sure snapd and - other Go programs works correctly and that you can compile a - simple helloworld written in Go. + other Go programs works correctly and that you can compile a + simple helloworld written in Go. [ Where problems could occur ] * The patch could be buggy. - * Qemu will no longer work with > 128 PB of memory. + * Qemu will no longer work with > 256 TB of memory. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] * Linux 5.18 merged support for 5-level page tables (sv57), and it does it such that 5-level page tables are used whenever the system supports it. * So far only Qemu support sv57, but it breaks Go since Go uses too many of the upper bits of pointers to store data, and is not yet ready for sv57. It probably breaks other types of software using too many bits for this "pointer tagging" technique too. At the moment, there is no way to indicate to the
[Kernel-packages] [Bug 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
** Description changed:
[ Impact ]
- * When adding earlycon to the kernel command line on the
-SiFive Unmatched board the serial console will print garbage
-halfway through booting until entering userspace and other
-other drivers are loaded.
+ * When adding earlycon to the kernel command line on the
+ SiFive Unmatched board the serial console will print garbage
+ halfway through booting until entering userspace and other
+ other drivers are loaded.
- * The problem is the UART driver doesn't claim its clocks
-properly so the PWM driver will turn off the parent clock
-until PWM is needed for the LEDs on the board.
+ * The problem is the UART driver doesn't claim its clocks
+ properly so the PWM driver will turn off the parent clock
+ until PWM is needed for the LEDs on the board.
- * Compiling the PWM driver as a module so it will be loaded
-at the same time the LED drivers are loaded is a temporary
-workaround until the following patch is backported
-643792048ee8 ("serial: sifive: enable clocks for UART when probed")
+ * Compiling the PWM driver as a module so it will be loaded
+ at the same time the LED drivers are loaded is a workaround
+until the following patch is backported
+ 643792048ee8 ("serial: sifive: enable clocks for UART when probed")
- * Only the SoCs on the SiFive Unleashed and Unmatched boards use
-this PWM driver, but none of them need it at boot time, so should
-be harmless.
+ * Only the SoCs on the SiFive Unleashed and Unmatched boards use
+ this PWM driver, but none of them need it at boot time, so should
+ be harmless.
[ Test Plan ]
- * Add earlycon and watch the serial console while booting.
+ * Add earlycon and watch the serial console while booting.
- * Test that PWM leds still work after the PWM driver module is loaded.
+ * Test that PWM leds still work after the PWM driver module is loaded.
[ Where problems could occur ]
- * There might be a hidden dependency on loading the PWM driver early.
+ * There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1988984
Title:
earlyconsole prints on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
New
Bug description:
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a workaround
until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Looking at the commits between 5.19.7 and 5.19.8 this https://git.launchpad.net/~ubuntu-kernel- test/ubuntu/+source/linux/+git/mainline- crack/commit/?h=cod/mainline/v5.19.8=c2798203315f4729bab0b917bf4c17a159abf9f8 looks suspiciously like the fix for this 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
** Description changed:
+ [ Impact ]
+
+ * When adding earlycon to the kernel command line on the
+SiFive Unmatched board the serial console will print garbage
+halfway through booting until entering userspace and other
+other drivers are loaded.
+
+ * The problem is the UART driver doesn't claim its clocks
+properly so the PWM driver will turn off the parent clock
+until PWM is needed for the LEDs on the board.
+
+ * Compiling the PWM driver as a module so it will be loaded
+at the same time the LED drivers are loaded is a temporary
+workaround until the following patch is backported
+643792048ee8 ("serial: sifive: enable clocks for UART when probed")
+
+ * Only the SoCs on the SiFive Unleashed and Unmatched boards use
+this PWM driver, but none of them need it at boot time, so should
+be harmless.
+
+ [ Test Plan ]
+
+ * Add earlycon and watch the serial console while booting.
+
+ * Test that PWM leds still work after the PWM driver module is loaded.
+
+ [ Where problems could occur ]
+
+ * There might be a hidden dependency on loading the PWM driver early.
+
+ [ Other Info ]
+
+ Original bug description:
+
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1988984
Title:
earlyconsole prints on 5.19.0-1002-generic
Status in linux-meta-riscv package in Ubuntu:
New
Bug description:
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board the serial console will print garbage
halfway through booting until entering userspace and other
other drivers are loaded.
* The problem is the UART driver doesn't claim its clocks
properly so the PWM driver will turn off the parent clock
until PWM is needed for the LEDs on the board.
* Compiling the PWM driver as a module so it will be loaded
at the same time the LED drivers are loaded is a temporary
workaround until the following patch is backported
643792048ee8 ("serial: sifive: enable clocks for UART when probed")
* Only the SoCs on the SiFive Unleashed and Unmatched boards use
this PWM driver, but none of them need it at boot time, so should
be harmless.
[ Test Plan ]
* Add earlycon and watch the serial console while booting.
* Test that PWM leds still work after the PWM driver module is
loaded.
[ Where problems could occur ]
* There might be a hidden dependency on loading the PWM driver early.
[ Other Info ]
Original bug description:
With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole
output looks like:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
���
With a defconfig 5.19.6 kernel this does not occr.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1989647
Title:
Fix AMDGPU: No video output and system hangs with two monitor (dGPU:
W6400)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[Impact]
There's possibility that system will hang and no video output of two external
monitor with dGPU W6400
Monitor 1: ASUS ProArt PA238Q (FHD)
Monitor 2: Dell P2415Q (4K)
[Fix]
Introduce the dmi quirk in amdgpu,
and add dmi quirks to bypass the affected machine.
[Test Case]
Two ways to verify
Method 1:
1. Cold boot with ASUS
2. Attach Dell monitor. ASUS is primary.
3. Switch display mode to single ASUS
4. Switch disaply mode back to Joing Displays. ASUS is primary
Method 2:
1. Cold boot with two monitors. ASUS is primary
2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds
3. Plug it back to DUT
[Where problems could occur]
Low, add a dmi quirk to bypass the target machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989647/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1989046
Title:
support independent clock and LED GPIOs for Intel IPU6 platforms
Status in HWE Next:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
[SRU Justification]
[Impact]
When migrated from power_ctrl_logic driver to int3472, two additional
independent CLK/LED GPIOs other than powerdown/reset must be probed
exceptionally.
[Fix]
Vendor provided patch in
https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch.
[Test Case]
Tested on both TGL/ADL platforms against nominated kernels.
[Where problems could occur]
This adds exceptional cases with fallbacks to the original function. No
one else is affected.
[Other Info]
This is an essential part for switching from power_ctrl_logic based GPIO
control mechanism to the generic, upstreamed int3472 driver. Affects all
IPU6 platforms that are to run new IPU6 driver dump in 202208.
== original bug report ==
Per
https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026
and
https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2,
additional fix for INT3472 is necessary to probe camera sensor GPIOs
on Intel IPU6 platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989046/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988797
Title:
pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
Fatal), type=Transaction Layer, (Requester ID)
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Confirmed
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Confirmed
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
My kernel log periodically bursts with:
[10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected
(Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.593393] pcieport :00:1b.0: device [8086:7ac4] error
status/mask=0010/4000
[10405.598564] pcieport :00:1b.0:[20] UnsupReq (First)
[10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152
[10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected
(Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.614959] pcieport :00:1b.0: device [8086:7ac4] error
status/mask=0010/4000
[10405.620296] pcieport :00:1b.0:[20] UnsupReq (First)
[10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152
[10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected
(Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.636495] pcieport :00:1b.0: device [8086:7ac4] error
status/mask=0010/4000
[10405.641867] pcieport :00:1b.0:[20] UnsupReq (First)
[10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152
[10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected
(Non-Fatal), type=Transaction Layer, (Requester ID)
[10405.658369] pcieport :00:1b.0: device [8086:7ac4] error
status/mask=0010/4000
[10405.663803] pcieport :00:1b.0:[20] UnsupReq
[Kernel-packages] [Bug 1990242] Re: Intel graphic driver is not probing[8086:468b]
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990242
Title:
Intel graphic driver is not probing[8086:468b]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
[Impact]
Got blank screen after entered desktop
[Fix]
Below commit in linux-next fixes the issue.
6215a7c8f552 drm/i915: Add new ADL-S pci id
[Test]
Verified on the target machine.
[Where problems could occur]
It only adds an ID to the list, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990242/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990240
Title:
To support Intel Maple Ridge Thunderbolt [8086:1134]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
[Impact]
The TBT ID[8086:1134] the new project uses is not listed in the driver.
[Fix]
Intel submits this as we requested which is still in linux-next
https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/
[Where problems could occur]
Adding only one ID, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990240/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990330] Re: System hang during S3 test
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990330
Title:
System hang during S3 test
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[Impact]
It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R)
Silver N6005 @ 2.00GHz
[Fix]
Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and
found this below commit
567511462387 mm/memcg: protect memcg_stock with a local_lock_t
For safty, I backported the series of the patch
https://www.spinics.net/lists/cgroups/msg31595.html
But I still can reproduce the issue after applied those patches on top of
5.17 oem kernel.
So, I did a second round of bisecting and found below commit is required, too
a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device
private memory
[Test]
Done the S3 test 400 times on the target and it's still working well.
[Where problems could occur]
Hard to evaluate the impact, but from the overnight test, the memory usage is
still low, so there should be no memory leakage, and can't find any fix patch
for those applied commits from upstream and linux-next trees.
The patches are all from v5.18-rc1, so we only need them to be applied on
oem-5.17 kernel, and will let QA to do thoroughly tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990330/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/amd/display: Detect dpcd_rev when hotplug mst monitor
- drm/amd/display: Release remote dc_sink under mst scenario
* pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal),
type=Transaction Layer, (Requester ID) (LP: #1988797)
- SAUCE: PCI/PTM: Cache PTM Capability offset
- SAUCE: PCI/PTM: Add pci_upstream_ptm() helper
- SAUCE: PCI/PTM: Separate configuration and enable
- SAUCE: PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm()
- SAUCE: PCI/PTM: Move pci_ptm_info() body into its only caller
- SAUCE: PCI/PTM: Preserve RsvdP bits in PTM Control register
- SAUCE: PCI/PTM: Reorder functions in logical order
- SAUCE: PCI/PTM: Consolidate PTM interface declarations
- SAUCE: PCI/PM: Always disable PTM for all devices during suspend
- SAUCE: PCI/PM: Simplify pci_pm_suspend_noirq()
* Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
(LP: #1989647)
- drm/amd/display: Ignore First MST Sideband Message Return Error
* System hang during S3 test (LP: #1990330)
- memcg: add per-memcg total kernel memory stat
- mm/memcg: revert ("mm/memcg: optimize user context object stock access")
- mm/memcg: disable threshold event handlers on PREEMPT_RT
- mm/memcg: protect per-CPU counter by disabling preemption on PREEMPT_RT
where needed.
- mm/memcg: opencode the inner part of obj_cgroup_uncharge_pages() in
drain_obj_stock()
- mm/memcg: protect memcg_stock with a local_lock_t
- mm/memcg: disable migration instead of preemption in drain_all_stock().
- mm/memremap: avoid calling kasan_remove_zero_shadow() for device private
memory
* To support Intel Maple Ridge Thunderbolt [8086:1134] (LP: #1990240)
- thunderbolt: Add support for Intel Maple Ridge single port controller
* Intel graphic driver is not probing[8086:468b] (LP: #1990242)
- drm/i915: Add new ADL-S pci id
* support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
-- Timo Aaltonen Tue, 27 Sep 2022
15:12:42 +0300
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1990920
Title:
Fix resume on AMD platforms when TBT monitor is plugged
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-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:
New
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Confirmed
Status in linux-oem-5.14 source package in Kinetic:
Invalid
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
When TBT monitor is connected to AMD platform, system resume will hit
stack corruption or BUG_ON() macro.
[Fix]
Revert the offending commit and handle MST properly.
[Test]
The system can resume normally and no more kernel splat.
[Where problems could occur]
The new logic is restriced to MST hub, so normal DP/HDMI usage should be
unaffected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990920/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990995] Re: VM fails to boot in ScalingStack
This bug was fixed in the package linux-raspi - 5.15.0-1016.18
---
linux-raspi (5.15.0-1016.18) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1016.18 -proposed tracker (LP: #1989776)
* VM fails to boot in ScalingStack (LP: #1990995)
- [Packaging] raspi: Include virtio drivers in linux-modules
[ Ubuntu: 5.15.0-50.56 ]
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
[ Ubuntu: 5.15.0-49.55 ]
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
On my kinetic system, /dev has nosuid, but no noexec. ** Tags added: foundations-triage-discuss -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
** Attachment added: "kern.log-5.19.7" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622659/+files/kern.log-5.19.7 -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
** Attachment added: "kern.log-5.19.6" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622658/+files/kern.log-5.19.6 -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Went through all upstream 5.19.x available at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D 5.19- OK 5.19.1 - OK 5.19.2 - OK 5.19.3 - OK 5.19.4 - no amd64 build available 5.19.5 - OK 5.19.6 - NG - same problem as reported 5.19.7 - NG - same problem as reported 5.19.8 - OK 5.19.9 - OK 5.19.10 - OK 5.19.11 - OK 5.19.12 - intentionally skipped due to reported backlight problems on intel laptops 5.19.13 - OK 5.19.14 - no amd64 build available -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
is this an issue on 6.0? ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Incomplete -- 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/1989647 Title: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Incomplete Bug description: [Impact] There's possibility that system will hang and no video output of two external monitor with dGPU W6400 Monitor 1: ASUS ProArt PA238Q (FHD) Monitor 2: Dell P2415Q (4K) [Fix] Introduce the dmi quirk in amdgpu, and add dmi quirks to bypass the affected machine. [Test Case] Two ways to verify Method 1: 1. Cold boot with ASUS 2. Attach Dell monitor. ASUS is primary. 3. Switch display mode to single ASUS 4. Switch disaply mode back to Joing Displays. ASUS is primary Method 2: 1. Cold boot with two monitors. ASUS is primary 2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds 3. Plug it back to DUT [Where problems could occur] Low, add a dmi quirk to bypass the target machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990931] Re: Fix AMD W6800: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0
is this an issue on 6.0? ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => 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/1990931 Title: Fix AMD W6800: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Incomplete Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] kernel: WARNING: CPU: 2 PID: 504 at arch/x86/kernel/fpu/core.c:159 kernel_fpu_begin_mask+0xa4/0xb0 [Fix] Remove FPU codes from AMD DCN folder. [Test Case] 1. check the dmesg if the warning exist. [Where problems could occur] Low, the FPU codes are moved to DML folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 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-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux-oem-5.17 source package in Hirsute: Invalid Status in linux-oem-6.0 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux-oem-6.0 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio
[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs
Is there anything left to do here? ** Changed in: klibc (Ubuntu Bionic) Status: New => Incomplete ** Changed in: klibc (Ubuntu Cosmic) Status: New => Won't 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/1760106 Title: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: Incomplete Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
== SRU Justification ==
Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is
offline") there was a timing window during recovery, that qeth_query_card_info
could be sent to the card, even before it was ready for it, leading to a
failing cardrecovery. There is evidence that this window was hit, as not
all callers of get_link_ksettings() check for netif_device_present.
This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
by commit e6e771b3d897.
Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.
This patch is being requested in Jammy 5.15 and Kinetic 5.19.
== Fix ==
7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")
== Regression Potential ==
Low. This patch has been accepted in upstream stable and is limited to
the s390/qeth card.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification:
--
[Impact]
* If the mlx5 driver is reloading while the recovery flow is happening,
and if it receives new commands before the command interface is up
again, this can lead to null pointer that tries to access non-
initialized command structures.
* So it's required to avoid processing commands before the command
interface is up again.
* This is accomplished by a new cmdif state that helps to avoid
processing commands while cmdif is not ready.
[Fix]
* backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
* An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
is needed that has Mellanox cards (RoCE Express 2.1) assigned,
configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
* Now trigger a recovery (guess that can be done at the Support Element)
and reload the driver at the same time.
* Make sure the module/driver mlx5 is loaded and in use
(otherwise it can't be removed/unloaded).
* Now remove/unload the module with:
sudo modprobe -r mlx5
and (re-)load it again with:
sudo modprobe mlx5
* Due to the lack of RoCE Express 2.1 hardware,
IBM needs to do the verification.
[Where problems could occur]
* In case there is an issue with 'cmdif' it might not have the correct
interface state, which:
- either might lead to the fact that commands are not properly blocked
and the situation is similar like before
- or the commands may get always blocked,
which render the hardware useless
- or might block in wrong situation,
which will cause unexpected issues and broken behavior.
* Since the patch got upstream accepted with v5.7-rc7 it's
not new to the kernel, was already part of groovy (and above)
and is therefor already in use by newer Ubuntu releases.
[Other Info]
* Since the patch is upstream since v5.7-rc7,
it's already included in jammy and kinetic.
* Since the upstream patch incl. the line:
Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
Connect-IB adapters") it looks to me that it was forgotten
to mark the patch for upstream stable updates.
* Such SRUs for focal's 5.4 will automatically land in bionic's
hwe-5.4, too. But since this was especially requested for
bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
echo "Usage: $0 "
exit 1
fi
while true; do
cat /sys/class/net/$1/duplex > /dev/null
cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the NIC:
echo 1 > /sys/bus/pci/devices//reset
Then first I got a lot of the following messages:
mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
query port ptys failed: -5
And then as the mlx5 driver's recovery kicks in the oops as below:
[ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f
after 1 iterations
[ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called
[ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010
[ 659.104169] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 659.104171] Failing address: TEID: 0483
[ 659.104172] Fault in home space mode while using kernel ASCE.
[ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800
P:003d
[ 659.104200] Oops: 0004 ilc:2 [#1] SMP
[ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch
vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
So what about the missing ones then? Are those already in 6.0? ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid -- 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Incomplete Status in linux-oem-6.0 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
This dist upgrade is a massive clusterfuck. I disabled turbo and iommu. No change at all in performance. I regret the upgrade. The old 20.04 worked nicely. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
Test kernel (5.19.0-19.19+i915fix) available here: https://kernel.ubuntu.com/~arighi/lp-1991703/ It would be great if someone affected by this problem could test this out. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
Thanks Andrea for looking into the issue.
Would the code changed in 458ec0c8f359 ("drm/i915: fix null pointer
dereference") ever be executed on an AMD Ryzen processor with an Nvidia
card? Doesn't the driver framework detect that there is no i915 GPU?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1991703
Title:
Failure to boot with linux-image-5.19.0-18-generic and
-5.19.0-19-generic
Status in linux-signed package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Confirmed
Bug description:
Since the last kernel update today my system stops in the middle of the boot
process and does not reach KDE.
---
ProblemType: Bug
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2021-05-26 (495 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm
nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G
hugepages=4
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
linux-backports-modules-5.19.0-15-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
RfKill:
Tags: kinetic uec-images
Uname: Linux 5.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/24/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4204
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1987232] Re: WARN in trace_event_dyn_put_ref
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1987451] Re: Jammy update: v5.15.54 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1988338] Re: Jammy update: v5.15.55 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1988351] Re: Jammy update: v5.15.56 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1988353] Re: Jammy update: v5.15.57 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1988479] Re: Jammy update: v5.15.58 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1989221] Re: Jammy update: v5.15.60 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read
This bug was fixed in the package linux-bluefield - 5.4.0-1047.52 --- linux-bluefield (5.4.0-1047.52) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1047.52 -proposed tracker (LP: #1989866) * Focal update: v5.4.208 upstream stable release (LP: #1988225) - [Config] bluefield: updateconfigs for IMA_TEMPLATE - [Config] bluefield: updateconfigs for REFCOUNT_FULL * mlxbf-pmc: error when reading unprogrammed events (LP: #1989172) - SAUCE: mlxbf-pmc: Fix error when reading unprogrammed events * mlxbf_gige: need to clear MDIO gateway lock after read (LP: #1989495) - SAUCE: mlxbf_gige: clear MDIO gateway lock after read [ Ubuntu: 5.4.0-128.144 ] * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' [ Ubuntu: 5.4.0-127.143 ] * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug was fixed in the package linux-bluefield - 5.4.0-1047.52 --- linux-bluefield (5.4.0-1047.52) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1047.52 -proposed tracker (LP: #1989866) * Focal update: v5.4.208 upstream stable release (LP: #1988225) - [Config] bluefield: updateconfigs for IMA_TEMPLATE - [Config] bluefield: updateconfigs for REFCOUNT_FULL * mlxbf-pmc: error when reading unprogrammed events (LP: #1989172) - SAUCE: mlxbf-pmc: Fix error when reading unprogrammed events * mlxbf_gige: need to clear MDIO gateway lock after read (LP: #1989495) - SAUCE: mlxbf_gige: clear MDIO gateway lock after read [ Ubuntu: 5.4.0-128.144 ] * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' [ Ubuntu: 5.4.0-127.143 ] * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap
[Kernel-packages] [Bug 1989218] Re: Jammy update: v5.15.59 upstream stable release
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
linux (5.15.0-49.55) jammy; urgency=medium
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP: #1989218)
- Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
- Revert "ocfs2: mount shared volume without ha stack"
- ntfs: fix use-after-free in ntfs_ucsncmp()
- fs: sendfile handles O_NONBLOCK of out_fd
- secretmem: fix unhandled fault in truncate
- mm: fix page leak with multiple threads mapping the same page
- hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
- asm-generic: remove a broken and needless ifdef conditional
- s390/archrandom: prevent CPACF trng invocations in interrupt context
- nouveau/svm: Fix to migrate all requested pages
- drm/simpledrm: Fix return type of
simpledrm_simple_display_pipe_mode_valid()
- watch_queue: Fix missing rcu annotation
- watch_queue: Fix missing locking in add_watch_to_object()
- tcp: Fix data-races around sysctl_tcp_dsack.
- tcp: Fix a data-race around sysctl_tcp_app_win.
- tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
- tcp: Fix a data-race around sysctl_tcp_frto.
- tcp: Fix a data-race around sysctl_tcp_nometrics_save.
- tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
- ice: check (DD | EOF) bits on Rx
[Kernel-packages] [Bug 1990184] Re: Azure: Enable vPCI multi-MSI interrupts
This bug was fixed in the package linux-azure - 5.15.0-1021.26
---
linux-azure (5.15.0-1021.26) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1021.26 -proposed tracker (LP: #1989754)
* Packaging resync (LP: #1786013)
- [Packaging] update variants
* Azure: Enable vPCI multi-MSI interrupts (LP: #1990184)
- genirq/msi: Guard sysfs code
- genirq/msi: Remove unused domain callbacks
- genirq/msi: Fixup includes
- PCI/MSI: Make pci_msi_domain_write_msg() static
- PCI/MSI: Remove msi_desc_to_pci_sysdata()
- genirq/msi, treewide: Use a named struct for PCI/MSI attributes
- PCI: hv: Fix multi-MSI to allow more than one MSI vector
- PCI: hv: Avoid the retarget interrupt hypercall in irq_unmask() on ARM64
- PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI
- PCI: hv: Reuse existing IRTE allocation in compose_msi_msg()
- PCI: hv: Fix interrupt mapping for multi-MSI
- SAUCE: PCI: hv: Only reuse existing IRTE allocation for Multi-MSI
* Azure: Add support for multi-MSI (LP: #1981577) // Azure: Enable vPCI multi-
MSI interrupts (LP: #1990184)
- PCI: hv: Remove unused hv_set_msi_entry_from_desc()
* cma alloc failure in large 5.15 arm instances (LP: #1990167)
- [Config] Disable CONFIG_CMA for arm64
[ Ubuntu: 5.15.0-50.56 ]
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll linking optimisation
- io_uring: inline io_poll_complete
- io_uring: correct fill events helpers types
- io_uring: clean cqe filling functions
- io_uring: poll rework
- io_uring: remove poll entry from list when canceling all
- io_uring: bump poll refs to full 31-bits
- io_uring: fail links when poll fails
- io_uring: fix wrong arm_poll error handling
- io_uring: fix UAF due to missing POLLFREE handling
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809)
- selftests/net: test nexthop without gw
* ip/nexthop: fix default address selection for connected nexthop
(LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
Jammy 5.15.0-49.55 (LP: #1990124)
- ip: fix triggering of 'icmp redirect'
[ Ubuntu: 5.15.0-49.55 ]
* jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
* amdgpu module crash after 5.15 kernel update (LP: #1981883)
- drm/amdgpu: fix check in fbdev init
* scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
(LP: #1982070)
- scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
* [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
- s390/qeth: cache link_info for ethtool
* WARN in trace_event_dyn_put_ref (LP: #1987232)
- tracing/perf: Fix double put of trace event when init fails
* Jammy update: v5.15.60 upstream stable release (LP: #1989221)
- x86/speculation: Make all RETbleed mitigations 64-bit only
- selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
- selftests/bpf: Check dst_port only on the client socket
- block: fix default IO priority handling again
- tools/vm/slabinfo: Handle files in debugfs
- ACPI: video: Force backlight native for some TongFang devices
- ACPI: video: Shortening quirk list by identifying Clevo by board_name only
- ACPI: APEI: Better fix to avoid spamming the console with old error logs
- crypto: arm64/poly1305 - fix a read out-of-bound
- KVM: x86: do not report a vCPU as preempted outside instruction boundaries
- KVM: x86: do not set st->preempted when going back to user space
- KVM: selftests: Make hyperv_clock selftest more stable
- tools/kvm_stat: fix display of error when multiple processes are found
- selftests: KVM: Handle compiler optimizations in ucall
- KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
- arm64: set UXN on swapper page tables
- btrfs: zoned: prevent allocation from previous data relocation BG
- btrfs: zoned: fix critical section of relocation inode writeback
- Bluetooth: hci_bcm: Add BCM4349B1 variant
- Bluetooth: hci_bcm: Add DT compatible for CYW55572
- dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
- Bluetooth: btusb: Add support of IMC Networks PID 0x3568
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
- Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
- macintosh/adb: fix oob read in do_adb_query() function
- x86/speculation: Add RSB VM Exit protections
- x86/speculation: Add LFENCE to RSB fill sequence
- Linux 5.15.60
* Jammy update: v5.15.59 upstream stable release (LP:
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988212] Re: Focal update: v5.4.204 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988214] Re: Focal update: v5.4.205 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988215] Re: Focal update: v5.4.206 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988219] Re: Focal update: v5.4.207 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988225] Re: Focal update: v5.4.208 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1989230] Re: Focal update: v5.4.210 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1989228] Re: Focal update: v5.4.209 upstream stable release
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1989374] Re: Bionic update: upstream stable patchset 2022-09-12
This bug was fixed in the package linux - 4.15.0-194.205 --- linux (4.15.0-194.205) bionic; urgency=medium * bionic/linux: 4.15.0-194.205 -proposed tracker (LP: #1989935) * Bionic update: upstream stable patchset 2022-09-14 (LP: #1989625) - random: schedule mix_interrupt_randomness() less often - ata: libata: add qc->flags in ata_qc_complete_template tracepoint - dm era: commit metadata in postsuspend after worker stops - random: quiet urandom warning ratelimit suppression message - USB: serial: option: add Telit LE910Cx 0x1250 composition - USB: serial: option: add Quectel EM05-G modem - USB: serial: option: add Quectel RM500K module support - bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers - x86/xen: Remove undefined behavior in setup_features() - MIPS: Remove repetitive increase irq_err_count - igb: Make DMA faster when CPU is active on the PCIe link - iio: adc: vf610: fix conversion mode sysfs node name - usb: chipidea: udc: check request status before setting device address - iio:accel:bma180: rearrange iio trigger get and register - iio: accel: mma8452: ignore the return value of reset operation - iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up() - iio: trigger: sysfs: fix use-after-free on remove - iio: adc: axp288: Override TS pin bias current for some models - xtensa: xtfpga: Fix refcount leak bug in setup - xtensa: Fix refcount leak bug in time.c - powerpc: Enable execve syscall exit tracepoint - powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address - powerpc/powernv: wire up rng during setup_arch - ARM: dts: imx6qdl: correct PU regulator ramp delay - ARM: exynos: Fix refcount leak in exynos_map_pmu - ARM: Fix refcount leak in axxia_boot_secondary - ARM: cns3xxx: Fix refcount leak in cns3xxx_init - modpost: fix section mismatch check for exported init/exit sections - powerpc/pseries: wire up rng during setup_arch() - drm: remove drm_fb_helper_modinit - xen: unexport __init-annotated xen_xlate_map_ballooned_pages() - fdt: Update CRC check for rng-seed - kexec_file: drop weak attribute from arch_kexec_apply_relocations[_add] - swiotlb: skip swiotlb_bounce when orig_addr is zero - net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms - afs: Fix dynamic root getattr - iio:chemical:ccs811: rearrange iio trigger get and register - soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe - nvdimm: Fix badblocks clear off-by-one error - dm raid: fix accesses beyond end of raid member array - dm raid: fix KASAN warning in raid5_add_disks - s390/archrandom: simplify back to earlier design and initialize earlier - SUNRPC: Fix READ_PLUS crasher - net: rose: fix UAF bugs caused by timer handler - net: usb: ax88179_178a: Fix packet receiving - RDMA/qedr: Fix reporting QP timeout attribute - usbnet: fix memory allocation in helpers - net: ipv6: unexport __init-annotated seg6_hmac_net_init() - caif_virtio: fix race between virtio_device_ready() and ndo_open() - netfilter: nft_dynset: restore set element counter when failing to update - net: bonding: fix possible NULL deref in rlb code - net: bonding: fix use-after-free after 802.3ad slave unbind - nfc: nfcmrvl: Fix irq_of_parse_and_map() return value - NFC: nxp-nci: Don't issue a zero length i2c_master_read() - xen/gntdev: Avoid blocking in unmap_grant_pages() - hwmon: (ibmaem) don't call platform_device_del() if platform_device_add() fails - sit: use min - ipv6/sit: fix ipip6_tunnel_get_prl return value - net: Rename and export copy_skb_header - xen/blkfront: fix leaking data in shared pages - xen/netfront: fix leaking data in shared pages - xen/netfront: force data bouncing when backend is untrusted - xen/blkfront: force data bouncing when backend is untrusted - xen/arm: Fix race in RB-tree based P2M accounting - net: usb: qmi_wwan: add Telit 0x1060 composition - net: usb: qmi_wwan: add Telit 0x1070 composition - virtio-net: fix race between ndo_open() and virtio_device_ready() - net: tun: unlink NAPI from device on destruction - net: tun: stop NAPI when detaching queues - esp: limit skb_page_frag_refill use to a single page - mm/slub: add missing TID updates on slab deactivation - can: grcan: grcan_probe(): remove extra of_node_get() - can: gs_usb: gs_usb_open/close(): fix memory leak - usbnet: fix memory leak in error case - net: rose: fix UAF bug caused by rose_t0timer_expiry - iommu/vt-d: Fix PCI bus rescan device hot add - video: of_display_timing.h: include errno.h - powerpc/powernv: delay rng platform device creation until later in boot - xfs: remove incorrect ASSERT in xfs_rename - pinctrl: sunxi: a83t: Fix NAND function name for some pins
[Kernel-packages] [Bug 1989625] Re: Bionic update: upstream stable patchset 2022-09-14
This bug was fixed in the package linux - 4.15.0-194.205 --- linux (4.15.0-194.205) bionic; urgency=medium * bionic/linux: 4.15.0-194.205 -proposed tracker (LP: #1989935) * Bionic update: upstream stable patchset 2022-09-14 (LP: #1989625) - random: schedule mix_interrupt_randomness() less often - ata: libata: add qc->flags in ata_qc_complete_template tracepoint - dm era: commit metadata in postsuspend after worker stops - random: quiet urandom warning ratelimit suppression message - USB: serial: option: add Telit LE910Cx 0x1250 composition - USB: serial: option: add Quectel EM05-G modem - USB: serial: option: add Quectel RM500K module support - bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers - x86/xen: Remove undefined behavior in setup_features() - MIPS: Remove repetitive increase irq_err_count - igb: Make DMA faster when CPU is active on the PCIe link - iio: adc: vf610: fix conversion mode sysfs node name - usb: chipidea: udc: check request status before setting device address - iio:accel:bma180: rearrange iio trigger get and register - iio: accel: mma8452: ignore the return value of reset operation - iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up() - iio: trigger: sysfs: fix use-after-free on remove - iio: adc: axp288: Override TS pin bias current for some models - xtensa: xtfpga: Fix refcount leak bug in setup - xtensa: Fix refcount leak bug in time.c - powerpc: Enable execve syscall exit tracepoint - powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address - powerpc/powernv: wire up rng during setup_arch - ARM: dts: imx6qdl: correct PU regulator ramp delay - ARM: exynos: Fix refcount leak in exynos_map_pmu - ARM: Fix refcount leak in axxia_boot_secondary - ARM: cns3xxx: Fix refcount leak in cns3xxx_init - modpost: fix section mismatch check for exported init/exit sections - powerpc/pseries: wire up rng during setup_arch() - drm: remove drm_fb_helper_modinit - xen: unexport __init-annotated xen_xlate_map_ballooned_pages() - fdt: Update CRC check for rng-seed - kexec_file: drop weak attribute from arch_kexec_apply_relocations[_add] - swiotlb: skip swiotlb_bounce when orig_addr is zero - net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms - afs: Fix dynamic root getattr - iio:chemical:ccs811: rearrange iio trigger get and register - soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe - nvdimm: Fix badblocks clear off-by-one error - dm raid: fix accesses beyond end of raid member array - dm raid: fix KASAN warning in raid5_add_disks - s390/archrandom: simplify back to earlier design and initialize earlier - SUNRPC: Fix READ_PLUS crasher - net: rose: fix UAF bugs caused by timer handler - net: usb: ax88179_178a: Fix packet receiving - RDMA/qedr: Fix reporting QP timeout attribute - usbnet: fix memory allocation in helpers - net: ipv6: unexport __init-annotated seg6_hmac_net_init() - caif_virtio: fix race between virtio_device_ready() and ndo_open() - netfilter: nft_dynset: restore set element counter when failing to update - net: bonding: fix possible NULL deref in rlb code - net: bonding: fix use-after-free after 802.3ad slave unbind - nfc: nfcmrvl: Fix irq_of_parse_and_map() return value - NFC: nxp-nci: Don't issue a zero length i2c_master_read() - xen/gntdev: Avoid blocking in unmap_grant_pages() - hwmon: (ibmaem) don't call platform_device_del() if platform_device_add() fails - sit: use min - ipv6/sit: fix ipip6_tunnel_get_prl return value - net: Rename and export copy_skb_header - xen/blkfront: fix leaking data in shared pages - xen/netfront: fix leaking data in shared pages - xen/netfront: force data bouncing when backend is untrusted - xen/blkfront: force data bouncing when backend is untrusted - xen/arm: Fix race in RB-tree based P2M accounting - net: usb: qmi_wwan: add Telit 0x1060 composition - net: usb: qmi_wwan: add Telit 0x1070 composition - virtio-net: fix race between ndo_open() and virtio_device_ready() - net: tun: unlink NAPI from device on destruction - net: tun: stop NAPI when detaching queues - esp: limit skb_page_frag_refill use to a single page - mm/slub: add missing TID updates on slab deactivation - can: grcan: grcan_probe(): remove extra of_node_get() - can: gs_usb: gs_usb_open/close(): fix memory leak - usbnet: fix memory leak in error case - net: rose: fix UAF bug caused by rose_t0timer_expiry - iommu/vt-d: Fix PCI bus rescan device hot add - video: of_display_timing.h: include errno.h - powerpc/powernv: delay rng platform device creation until later in boot - xfs: remove incorrect ASSERT in xfs_rename - pinctrl: sunxi: a83t: Fix NAND function name for some pins
[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55
This bug was fixed in the package linux - 5.4.0-128.144 --- linux (5.4.0-128.144) focal; urgency=medium * focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152) * CVE-2022-3176 - io_uring: disable polling pollfree files * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) - selftests/net: test nexthop without gw * ip/nexthop: fix default address selection for connected nexthop (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 (LP: #1990124) - ip: fix triggering of 'icmp redirect' linux (5.4.0-127.143) focal; urgency=medium * focal/linux: 5.4.0-127.143 -proposed tracker (LP: #1989892) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.09.19) * [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery (LP: #1987287) - net/mlx5: Avoid processing commands before cmdif is ready * Focal update: v5.4.210 upstream stable release (LP: #1989230) - thermal: Fix NULL pointer dereferences in of_thermal_ functions - ACPI: video: Force backlight native for some TongFang devices - ACPI: video: Shortening quirk list by identifying Clevo by board_name only - ACPI: APEI: Better fix to avoid spamming the console with old error logs - bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads - bpf: Test_verifier, #70 error message updates for 32-bit right shift - KVM: Don't null dereference ops->destroy - selftests: KVM: Handle compiler optimizations in ucall - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - macintosh/adb: fix oob read in do_adb_query() function - x86/speculation: Add RSB VM Exit protections - x86/speculation: Add LFENCE to RSB fill sequence - Linux 5.4.210 * Focal update: v5.4.209 upstream stable release (LP: #1989228) - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put - ntfs: fix use-after-free in ntfs_ucsncmp() - s390/archrandom: prevent CPACF trng invocations in interrupt context - tcp: Fix data-races around sysctl_tcp_dsack. - tcp: Fix a data-race around sysctl_tcp_app_win. - tcp: Fix a data-race around sysctl_tcp_adv_win_scale. - tcp: Fix a data-race around sysctl_tcp_frto. - tcp: Fix a data-race around sysctl_tcp_nometrics_save. - ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS) - ice: do not setup vlan for loopback VSI - scsi: ufs: host: Hold reference returned by of_parse_phandle() - tcp: Fix a data-race around sysctl_tcp_limit_output_bytes. - tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. - net: ping6: Fix memleak in ipv6_renew_options(). - ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr - igmp: Fix data-races around sysctl_igmp_qrv. - net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() - tcp: Fix a data-race around sysctl_tcp_min_tso_segs. - tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. - tcp: Fix a data-race around sysctl_tcp_autocorking. - tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. - Documentation: fix sctp_wmem in ip-sysctl.rst - tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns. - tcp: Fix a data-race around sysctl_tcp_comp_sack_nr. - i40e: Fix interface init with MSI interrupts (no MSI-X) - sctp: fix sleep in atomic context bug in timer handlers - virtio-net: fix the race between refill work and close - perf symbol: Correct address for bss symbols - sfc: disable softirqs for ptp TX - sctp: leave the err path free in sctp_stream_init to sctp_stream_free - ARM: crypto: comment out gcc warning that breaks clang builds - mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. - scsi: core: Fix race between handling STS_RESOURCE and completion - Linux 5.4.209 * Focal update: v5.4.208 upstream stable release (LP: #1988225) - pinctrl: stm32: fix optional IRQ support to gpios - riscv: add as-options for modules with assembly compontents - mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication - lockdown: Fix kexec lockdown bypass with ima policy - xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE - PCI: hv: Fix multi-MSI to allow more than one MSI vector - PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI - PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() - PCI: hv: Fix interrupt mapping for multi-MSI - serial: mvebu-uart: correctly report configured baudrate value - xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() - power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe - pinctrl: ralink: Check for null return of devm_kcalloc -
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
This bug should be fixed by 458ec0c8f359 ("drm/i915: fix null pointer
dereference"), I'll prepare a test kernel with this fix applied on top
of 5.19.0-19.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1991703
Title:
Failure to boot with linux-image-5.19.0-18-generic and
-5.19.0-19-generic
Status in linux-signed package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Confirmed
Bug description:
Since the last kernel update today my system stops in the middle of the boot
process and does not reach KDE.
---
ProblemType: Bug
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2021-05-26 (495 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm
nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G
hugepages=4
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
linux-backports-modules-5.19.0-15-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
RfKill:
Tags: kinetic uec-images
Uname: Linux 5.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/24/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4204
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
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.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO: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-signed/+bug/1991703/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 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-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962152] Re: failed to build Intel IPU6 camera driver against linux-unstable 5.17
will the dkms package make this bug obsolete?
** Changed in: linux-oem-5.17 (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
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/1962152
Title:
failed to build Intel IPU6 camera driver against linux-unstable 5.17
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Incomplete
Bug description:
In commit 3c8c15391481 ("media: v4l: async: Rename async nf functions,
clean up long lines"), functions *v4l2_async_notifier_* had been
renamed to *v4l2_async_nf_*.
In commit 16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF
module namespace") needs the proper MODULE_IMPORT_NS(DMA_BUF) line for
those who use dma-buf.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1962152/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
