[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Do you have any news on this bug? I want to buy this laptop, but I'm afraid that the sound will not be fixed. -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA 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/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
I also can confirm that this kernel version is now working as expected. thanks for quick solution! -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996981] [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: 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-131.147 ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 18 15:10:06 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 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-131.147 InstallationDate: Installed on 2022-06-08 (162 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/1996981 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 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
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
Verified that with the both proposed kernel(-1008) and the proposed sof firmware, the audio works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Thanks for the help! This kernel works OK. ** Attachment added: "dmesg-5.15.0-1054-generic #60" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+attachment/5631312/+files/dmesg-5.15.0-1054-generic%20%2360 -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Can you please give this kernel a try: https://people.canonical.com/~khfeng/lp1996740/ -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995684] Re: Fail to handle IRQ data in hv_pci and lead to attach 8 VF to VM fail
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => 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/1995684 Title: Fail to handle IRQ data in hv_pci and lead to attach 8 VF to VM fail Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Bug description: [Impact] When creating 8 accelerated network interfaces on Azure and attaching them to a VM from kernel message, it fails to handle IRQ data in hv_pci as below: [ 15.533530] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.539856] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.546261] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.552781] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.560177] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 [ 15.566631] hv_pci 1f4aa2a4-aff1-40af-8547-12f13bf19608: Request for interrupt failed: 0xc0350005 And 2 VFs are consistently missing, only 6 seem to be working [Fix] The fix was merged to upstream hyperv tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] 1. Create 8 NICs in azure with accelerated networking enabled 2. Launch a VM with all 8 attached 3. Check the output from VM [Where problems could occur] The patch is to use the correct type for the variables and reviewed by upstream There shouldn't be any problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996955] [NEW] Check if EFI signatures are revoked at build time
Public bug reported: [ Impact ] * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] * Add test-build PPA certificate as revoked * Perform a test-build crank of linux & linux-signed, in test-build PPA * linux-signed should FTBFS in test-build PPA * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches * The verification is done on EFI signed binaries only for now. OPAL & SIPL signing checks might be implemented in the future ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed ** Description changed: [ Impact ] - * Recent kernels expose built-in trusted and revoked certificates. See + * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 - * When kernels expose such information, it is prudent to check if the + * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. - * This ensures that a given signed kernel, can perform verified kexec + * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. - * This also helps with key rotations, in case kernel is routed to be + * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] - * Add test-build PPA certificate as revoked - * Perform a test-build crank of linux & linux-signed, in test-build PPA - * linux-signed should FTBFS in test-build PPA - * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly + * Add test-build PPA certificate as revoked + * Perform a test-build crank of linux & linux-signed, in test-build PPA + * linux-signed should FTBFS in test-build PPA + * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] - * Each individual linux-signed package needs to add a build-dep on all + * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches + + * The verification is done on EFI signed binaries only for now. OPAL & + SIPL signing checks might be implemented in the future ** Summary changed: - Fail the build if EFI binaries are signed with revoked keys + Check if EFI signatures are revoked at build ** Summary changed: - Check if EFI signatures are revoked at build + Check if EFI signatures are revoked at build time -- 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/1996955 Title: Check if EFI signatures are revoked at build time Status in linux-signed package in Ubuntu: Confirmed Bug description: [ Impact ] * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] * Add test-build PPA certificate as revoked * Perform a test-build crank of linux & linux-signed, in test-build PPA * linux-signed should FTBFS in test-build PPA * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches * The verification is done on EFI signed binaries only for now. OPAL & SIPL signing checks might be implemented in the future To manage notifications about this bug go to:
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => 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/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Not only an Ubuntu bug, it also affects Fedora with similar symptoms. Also, this happens when the device connected to USBC is a charger; and it appears to stop once fully charged. -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.54.49)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.54.49) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency/5.15.0-54.60 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
oem-6.0 boots and the displays work.
BUT: there is a delay and I see a few messages "blacklist: Problem blacklisting
hash (-13)". This is probably related to secure boot.
ALSO:
Multiple error blocks like this:
[6.497583] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks:
{ 9- } 6 jiffies s: 77 root: 0x1/.
[6.497611] rcu: blocking rcu_node structures (internal RCU debug):
l=1:0-15:0x200/.
[6.497627] Task dump for CPU 9:
[6.497628] task:systemd-udevd state:R running task stack:0 pid:
445 ppid: 440 flags:0x400a
[6.497632] Call Trace:
[6.497634]
[6.497637] ? 0xc16e4000
[6.497640] ? find_kallsyms_symbol+0x8e/0x1a0
[6.497646] ? vega20_ih_get_wptr+0x80/0x80 [amdgpu]
[6.497875] ? module_address_lookup+0x68/0xc0
[6.497878] ? vega20_ih_set_clockgating_state+0x20/0x20 [amdgpu]
[6.498087] ? kallsyms_lookup_buildid+0xf7/0x180
[6.498091] ? kallsyms_lookup+0x14/0x20
[6.498094] ? test_for_valid_rec+0x38/0x80
[6.498097] ? change_page_attr_set_clr+0x150/0x1c0
[6.498101] ? ftrace_module_enable+0xad/0x2c0
[6.498103] ? set_memory_x+0x40/0x50
[6.498105] ? load_module+0x9dd/0xc60
[6.498108] ? kernel_read_file+0x24e/0x2a0
[6.498111] ? __do_sys_finit_module+0xc8/0x140
[6.498113] ? __do_sys_finit_module+0xc8/0x140
[6.498116] ? __x64_sys_finit_module+0x18/0x20
[6.498118] ? do_syscall_64+0x5c/0x90
[6.498120] ? ksys_mmap_pgoff+0x112/0x260
[6.498123] ? __secure_computing+0x93/0xf0
[6.498124] ? exit_to_user_mode_prepare+0x37/0xb0
[6.498126] ? syscall_exit_to_user_mode+0x26/0x50
[6.498128] ? __x64_sys_mmap+0x33/0x50
[6.498131] ? do_syscall_64+0x69/0x90
[6.498132] ? exit_to_user_mode_prepare+0x37/0xb0
[6.498134] ? syscall_exit_to_user_mode+0x26/0x50
[6.498135] ? __x64_sys_lseek+0x18/0x20
[6.498138] ? do_syscall_64+0x69/0x90
[6.498139] ? exit_to_user_mode_prepare+0x37/0xb0
[6.498141] ? syscall_exit_to_user_mode+0x26/0x50
[6.498142] ? do_syscall_64+0x69/0x90
[6.498144] ? do_syscall_64+0x69/0x90
[6.498145] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[6.498149]
So it has improved but it is not perfect.
** Attachment added: "dmesg-6.0.0-1007-oem #7"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+attachment/5631272/+files/dmesg-6.0.0-1007-oem%20%237
--
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/1996740
Title:
5.15.0-53-generic no longer boots
Status in linux package in Ubuntu:
Confirmed
Bug description:
Running Ubuntu 22.04.1 Jammy.
After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no
longer fully boots.
After the normal splash screen the screen goes black and the computer is not
reachable on the network. Changing to another TTY does not work.
New kernel version: 5.15.0-53.59
I will attach the output of journalctl -b -1, please let me know what other
info you need.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: johan 2549 F pulseaudio
/dev/snd/controlC0: johan 2549 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2020-12-01 (714 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
enp37s0 no wireless extensions.
wgnfs no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7C52
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: jammy wayland-session
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare
sudo
_MarkForUpload: True
dmi.bios.date: 07/23/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 3.G0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
thanks for testing! could you also try oem-6.0, install 'linux-oem-22.04b' for jammy. It should not suffer from this, meaning that the backport for the other bug was maybe 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996650] Re: Bionic update: upstream stable patchset 2022-11-15
** Changed in: linux (Ubuntu Bionic) 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/1996650 Title: Bionic update: upstream stable patchset 2022-11-15 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-11-15 Ported from the following upstream stable releases: v4.14.295, v4.19.260 v4.19.261 v4.14.296, v4.19.262 from git://git.kernel.org/ of: fdt: fix off-by-one error in unflatten_dt_nodes() gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx drm/meson: Correct OSD1 global alpha value parisc: ccio-dma: Add missing iounmap in error path in ccio_probe() cifs: don't send down the destination address to sendmsg for a SOCK_STREAM ASoC: nau8824: Fix semaphore unbalance at error paths regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe() ALSA: hda/sigmatel: Keep power up while beep is enabled net: usb: qmi_wwan: add Quectel RM520N MIPS: OCTEON: irq: Fix octeon_irq_force_ciu_mapping() mksysmap: Fix the mismatch of 'L0' symbols in System.map video: fbdev: pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write ALSA: hda/sigmatel: Fix unused variable warning for beep power change wifi: mac80211: Fix UAF in ieee80211_scan_rx() USB: core: Fix RST error in hub.c USB: serial: option: add Quectel BG95 0x0203 composition USB: serial: option: add Quectel RM520N ALSA: hda/tegra: set depop delay for tegra ALSA: hda: add Intel 5 Series / 3400 PCI DID mm/slub: fix to return errno if kmalloc() fails arm64: dts: rockchip: Remove 'enable-active-low' from rk3399-puma netfilter: nf_conntrack_sip: fix ct_sip_walk_headers netfilter: nf_conntrack_irc: Tighten matching on DCC message iavf: Fix cached head and tail value for iavf_get_tx_pending ipvlan: Fix out-of-bound bugs caused by unset skb->mac_header net: team: Unsync device addresses on ndo_stop MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko of: mdio: Add of_node_put() when breaking out of for_each_xx netfilter: ebtables: fix memory leak when blob is malformed can: gs_usb: gs_can_open(): fix race dev->can.state condition perf kcore_copy: Do not check /proc/modules is unchanged net: sunhme: Fix packet reception for len < RX_COPY_THRESHOLD serial: Create uart_xmit_advance() serial: tegra: Use uart_xmit_advance(), fixes icount.tx accounting s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup Drivers: hv: Never allocate anything besides framebuffer from framebuffer memory region ext4: make directory inode spreading reflect flexbg size nvmet: fix a use-after-free i40e: Fix VF set max MTU size i40e: Fix set max_tx_rate when it is lower than 1 Mbps perf jit: Include program header in ELF files workqueue: don't skip lockdep work dependency in cancel_work_sync() UBUNTU: Upstream stable to v4.14.295, v4.19.260 mmc: moxart: fix 4-bit bus width and remove 8-bit bus width mm/page_alloc: fix race condition between build_all_zonelists and page allocation mm: prevent page_frag_alloc() from corrupting the memory mm/migrate_device.c: flush TLB while holding PTL soc: sunxi: sram: Actually claim SRAM regions soc: sunxi: sram: Fix debugfs info for A64 SRAM C Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in suspend/resume time" Input: melfas_mip4 - fix return value check in mip4_probe() usbnet: Fix memory leak in usbnet_disconnect() selftests: Fix the if conditions of in test_extra_filter() UBUNTU: Upstream stable to v4.19.261 uas: add no-uas quirk for Hiksemi usb_disk usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS uas: ignore UAS for Thinkplus chips net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455 ntfs: fix BUG_ON in ntfs_lookup_inode_by_name() nvme: add new line after variable declatation nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices clk: iproc: Minor tidy up of iproc pll data structures clk: iproc: Do not rely on node name for correct PLL setup Makefile.extrawarn: Move -Wcast-function-type-strict to W=1 ARM: fix function graph tracer and unwinder dependencies UBUNTU: [Config] updateconfigs for UNWINDER_ARM
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
** Attachment added: "dmesg of boot 5.15.0-53-generic #59+revert1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+attachment/5631265/+files/dmesg-5.15.0-53-generic%20%2359+revert1 -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
@Timo, Your packages work, the system boots now correctly. Thanks for your help! -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1958416 Title: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: Fix Committed Bug description: [Impact] Small SWIOTLB might cause DMA failures during High IO on GCP instances using SEV. [Test case] Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, and look for DMA overflow or full swiotlb messages on dmesg. [Potential regression] Boot failures should not be discarded when SWIOTLB cannot be allocated. -- ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 From the serial console: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask bus mask 0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938685] [ cut here ] Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] WARNING: CPU: 34 PID: 8648 at /build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938691] Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_piix4 gve Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938712] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938714] RIP: 0010:report_addr+0x33/0x90 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938716] RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RAX: RBX: 9773f8b960b0 RCX: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938718] RDX: RSI: 9753ff897448 RDI: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] RBP: bd77cf99f4e8 R08: 0305 R09: 0022 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938719] R10: 0016dfee R11: bd77cf99f218 R12: 0002 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938720] R13: 9753abfe9000 R14: 0001 R15: 0100 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] FS: 7f55bb523740() GS:9753ff88() knlGS: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938723] CS: 0010 DS: ES: CR0: 80050033 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938724] CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938726] Call Trace: Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938730] dma_direct_map_page+0xe2/0xf0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938731] dma_direct_map_sg+0x6c/0xc0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938735] nvme_queue_rq+0x6fb/0xbd0 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938738] __blk_mq_try_issue_directly+0x139/0x200 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [ 137.938741] ? mempool_free_slab+0x1/0x20 Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
please test the kernel build from #31 -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
** Changed in: strace (Ubuntu) Assignee: (unassigned) => Adrien Nader (adrien-n) -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Triaged Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu Jammy) 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Status in xserver-xorg-video-intel source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Status in xserver-xorg-video-intel source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1996806] Re: Azure: Jammy fio test causes panic
** Description changed:
SRU Justification
[Impact]
During Storage performance tests, 16 disks are attached and fio is ran.
The fio command does not consistently result in a kernel panic, but the
test runs fio enough times to result in consistent kernel panic. The
panic is most often observed on instances with many cores and disks.
[Test Case]
Using an instance with 96 cores and 16 disks:
sudo fio --ioengine=libaio --bs=1024K
--filename=/dev/sda:/dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi:/dev/sdj:/dev/sdk:/dev/sdl:/dev/sdm:/dev/sdn:/dev/sdo:/dev/sdp
--readwrite=read --runtime=120 --iodepth=32 --numjob=96
--name=iteration23 --direct=1 --size=8192M --group_reporting
--overwrite=1
+ Test results from Microsoft and myself are positive. No panics were
+ observed.
+
[Regression Potential]
The fix is an upstream patch from 5.17, commit
0bd2fbee9d0b7f801a9c0264d90b1e0d8053f395 ('scsi: storvsc: Fix unsigned
comparison to zero'). Regression potential is low.
[Other Info]
SF: #00346757
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1996806
Title:
Azure: Jammy fio test causes panic
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Bug description:
SRU Justification
[Impact]
During Storage performance tests, 16 disks are attached and fio is
ran. The fio command does not consistently result in a kernel panic,
but the test runs fio enough times to result in consistent kernel
panic. The panic is most often observed on instances with many cores
and disks.
[Test Case]
Using an instance with 96 cores and 16 disks:
sudo fio --ioengine=libaio --bs=1024K
--filename=/dev/sda:/dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi:/dev/sdj:/dev/sdk:/dev/sdl:/dev/sdm:/dev/sdn:/dev/sdo:/dev/sdp
--readwrite=read --runtime=120 --iodepth=32 --numjob=96
--name=iteration23 --direct=1 --size=8192M --group_reporting
--overwrite=1
Test results from Microsoft and myself are positive. No panics were
observed.
[Regression Potential]
The fix is an upstream patch from 5.17, commit
0bd2fbee9d0b7f801a9c0264d90b1e0d8053f395 ('scsi: storvsc: Fix unsigned
comparison to zero'). Regression potential is low.
[Other Info]
SF: #00346757
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
The attachment "0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW- inside-.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
5.15.0-53 fails for me too, also with a Radeon graphics card with monitor connected via DisplayPort. Is that a common theme? 2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller]) Same as above, 5.15.0-52 still works. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996915] [NEW] megaraid_sas crash in ubuntu 22.04
*** This bug is a security vulnerability *** Private security bug reported: crash message for dmesg UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 index 2 is out of range for type 'MR_LD_SPAN_MAP [1]' CPU: 16 PID: 330 Comm: kworker/16:1H Not tainted 5.15.0-53-generic #59-Ubuntu Hardware name: GIGABYTE R282-Z91-00/MZ92-FS0-00, BIOS M10 11/23/2021 Workqueue: kblockd blk_mq_run_work_fn Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_out_of_bounds.cold+0x44/0x49 MR_GetPhyParams+0x487/0x700 [megaraid_sas] MR_BuildRaidContext+0x71e/0xb50 [megaraid_sas] ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x580 megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] megasas_queue_command+0x1c1/0x200 [megaraid_sas] ? ktime_get+0x46/0xc0 scsi_dispatch_cmd+0x96/0x200 scsi_queue_rq+0x2d5/0x690 blk_mq_dispatch_rq_list+0x13f/0x680 ? sbitmap_get+0x71/0xe0 __blk_mq_do_dispatch_sched+0xba/0x2e0 blk_mq_do_dispatch_sched+0x40/0x70 __blk_mq_sched_dispatch_requests+0x105/0x150 blk_mq_sched_dispatch_requests+0x35/0x70 __blk_mq_run_hw_queue+0x34/0xc0 blk_mq_run_work_fn+0x1f/0x30 process_one_work+0x22b/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x12a/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Information type changed from Public to Private Security ** Description changed: crash message for dmesg UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 index 2 is out of range for type 'MR_LD_SPAN_MAP [1]' CPU: 16 PID: 330 Comm: kworker/16:1H Not tainted 5.15.0-53-generic #59-Ubuntu Hardware name: GIGABYTE R282-Z91-00/MZ92-FS0-00, BIOS M10 11/23/2021 Workqueue: kblockd blk_mq_run_work_fn Call Trace: - - show_stack+0x52/0x5c - dump_stack_lvl+0x4a/0x63 - dump_stack+0x10/0x16 - ubsan_epilogue+0x9/0x49 - __ubsan_handle_out_of_bounds.cold+0x44/0x49 - MR_GetPhyParams+0x487/0x700 [megaraid_sas] - MR_BuildRaidContext+0x71e/0xb50 [megaraid_sas] - ? cpumask_next_and+0x24/0x30 - ? update_sg_lb_stats+0x78/0x580 - megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] - megasas_build_io_fusion+0x412/0x450 [megaraid_sas] - megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] - megasas_queue_command+0x1c1/0x200 [megaraid_sas] - ? ktime_get+0x46/0xc0 - scsi_dispatch_cmd+0x96/0x200 - scsi_queue_rq+0x2d5/0x690 - blk_mq_dispatch_rq_list+0x13f/0x680 - ? sbitmap_get+0x71/0xe0 - __blk_mq_do_dispatch_sched+0xba/0x2e0 - blk_mq_do_dispatch_sched+0x40/0x70 - __blk_mq_sched_dispatch_requests+0x105/0x150 - blk_mq_sched_dispatch_requests+0x35/0x70 - __blk_mq_run_hw_queue+0x34/0xc0 - blk_mq_run_work_fn+0x1f/0x30 - process_one_work+0x22b/0x3d0 - worker_thread+0x53/0x420 - ? process_one_work+0x3d0/0x3d0 - kthread+0x12a/0x150 - ? set_kthread_struct+0x50/0x50 - ret_from_fork+0x22/0x30 - + + show_stack+0x52/0x5c + dump_stack_lvl+0x4a/0x63 + dump_stack+0x10/0x16 + ubsan_epilogue+0x9/0x49 + __ubsan_handle_out_of_bounds.cold+0x44/0x49 + MR_GetPhyParams+0x487/0x700 [megaraid_sas] + MR_BuildRaidContext+0x71e/0xb50 [megaraid_sas] + ? cpumask_next_and+0x24/0x30 + ? update_sg_lb_stats+0x78/0x580 + megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] + megasas_build_io_fusion+0x412/0x450 [megaraid_sas] + megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] + megasas_queue_command+0x1c1/0x200 [megaraid_sas] + ? ktime_get+0x46/0xc0 + scsi_dispatch_cmd+0x96/0x200 + scsi_queue_rq+0x2d5/0x690 + blk_mq_dispatch_rq_list+0x13f/0x680 + ? sbitmap_get+0x71/0xe0 + __blk_mq_do_dispatch_sched+0xba/0x2e0 + blk_mq_do_dispatch_sched+0x40/0x70 + __blk_mq_sched_dispatch_requests+0x105/0x150 + blk_mq_sched_dispatch_requests+0x35/0x70 + __blk_mq_run_hw_queue+0x34/0xc0 + blk_mq_run_work_fn+0x1f/0x30 + process_one_work+0x22b/0x3d0 + worker_thread+0x53/0x420 + ? process_one_work+0x3d0/0x3d0 + kthread+0x12a/0x150 + ? set_kthread_struct+0x50/0x50 + ret_from_fork+0x22/0x30 + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Nov 17 15:48 seq - crw-rw 1
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
I experienced this problem on 20.04.5 with kernel 5.15.0-53. I have two displays running over DisplayPort via a 5700xt. Reverting to kernel 5.15.0-52 fixes the problem for me as well. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
here's a kernel build with commits for bug 1990920 reverted: https://aaltoset.kapsi.fi/lp1996740/amdgpu.tar.gz should be enough to just install the image, modules & modules-extra -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
2b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4) (prog-if 00 [VGA controller]) Manufacturer link: https://www.powercolor.com/product?id=1565954303 Sorry for the duplicated message before. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
The computer starts with the new kernel when there is no monitor connected via Display Port. Only a HDMI monitor is connected. After the system booted I can reconnect the Display Port monitor, but then the HDMI monitor is no longer recognized. After disconnecting the HDMI cable and reconnecting it, the other monitor works too. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Could you please list the GPU model, preferably from 'lspci -v|grep VGA' so we'd know if it's limited to a certain generation. I see at least Navi 10 mentioned by Johan, but what about others? -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
The computer starts with the new kernel when there is no monitor connected via Display Port. Only a HDMI monitor is connected. After the system booted I can reconnect the Display Port monitor, but then the HDMI monitor is no longer recognized. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
** Patch added: "0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW-inside-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+attachment/5631210/+files/0001-UBUNTU-SAUCE-shiftfs-fix-permanent-EOVERFLOW-inside-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Description changed: [ Impact ] - * Kernels have a set of builtin trusted and revoked certificates as a bundle - * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally - * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information + * Kernels have a set of builtin trusted and revoked certificates as a bundle + * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally + * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] - * sudo apt install linux-buildinfo-$(uname -r) - * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert - * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert + * sudo apt install linux-buildinfo-$(uname -r) + * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert + * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert + + Example output: + $ grep Subject: -r usr/lib/linux + usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing + usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing + usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing + [ Where problems could occur ] - * buildinfo is an auxiliary package not installed by default, but used + * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. -- 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/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Status in linux source package in Lunar: Incomplete Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Draft patch is ready https://lists.ubuntu.com/archives/kernel-team/2022-November/134883.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987913] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1987913 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987913 Title: suspend fails under wayland Status in linux package in Ubuntu: Incomplete Bug description: Suspend fails under wayland but works under X11. Steps to reproduce: -- Log out. Log into Wayland Session Suspend. Expected Result --- System goes into low power mode. Actual Result - Screens blank but system remains powered up. Workaround -- Log out. Log into X11 Session. Suspend System goes into low power mode. Sysinfo --- Ubuntu 22.04 LTS Kernel 5.15.0-46-generic Nvidia driver 510.85.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987913] Re: suspend fails under wayland
https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate suggests the the Linux kernel is the package against which this bug should be reported. Please provide any additional information that the kernel bot requests from you. ** Tags added: jammy ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987913 Title: suspend fails under wayland Status in linux package in Ubuntu: Incomplete Bug description: Suspend fails under wayland but works under X11. Steps to reproduce: -- Log out. Log into Wayland Session Suspend. Expected Result --- System goes into low power mode. Actual Result - Screens blank but system remains powered up. Workaround -- Log out. Log into X11 Session. Suspend System goes into low power mode. Sysinfo --- Ubuntu 22.04 LTS Kernel 5.15.0-46-generic Nvidia driver 510.85.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987913] [NEW] suspend fails under wayland
You have been subscribed to a public bug: Suspend fails under wayland but works under X11. Steps to reproduce: -- Log out. Log into Wayland Session Suspend. Expected Result --- System goes into low power mode. Actual Result - Screens blank but system remains powered up. Workaround -- Log out. Log into X11 Session. Suspend System goes into low power mode. Sysinfo --- Ubuntu 22.04 LTS Kernel 5.15.0-46-generic Nvidia driver 510.85.02 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- suspend fails under wayland https://bugs.launchpad.net/bugs/1987913 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996812] Re: Focal update: v5.4.220 upstream stable release
Skipped "r8152: Rate limit overflow messages" (already applied). ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996812 Title: Focal update: v5.4.220 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.220 upstream stable release from git://git.kernel.org/ ALSA: oss: Fix potential deadlock at unregistration ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free() ALSA: usb-audio: Fix potential memory leaks ALSA: usb-audio: Fix NULL dererence at error path ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530 ALSA: hda/realtek: Correct pin configs for ASUS G533Z ALSA: hda/realtek: Add quirk for ASUS GV601R laptop ALSA: hda/realtek: Add Intel Reference SSID to support headset keys mtd: rawnand: atmel: Unmap streaming DMA mappings cifs: destage dirty pages before re-reading them for cache=none cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message iio: dac: ad5593r: Fix i2c read protocol requirements iio: pressure: dps310: Refactor startup procedure iio: pressure: dps310: Reset chip after timeout usb: add quirks for Lenovo OneLink+ Dock can: kvaser_usb: Fix use of uninitialized completion can: kvaser_usb_leaf: Fix overread with an invalid command can: kvaser_usb_leaf: Fix TX queue out of sync after restart can: kvaser_usb_leaf: Fix CAN state after restart mmc: sdhci-sprd: Fix minimum clock limit fs: dlm: fix race between test_bit() and queue_work() fs: dlm: handle -EBUSY first in lock arg validation HID: multitouch: Add memory barriers quota: Check next/prev free block number after reading from quota file ASoC: wcd9335: fix order of Slimbus unprepare/disable regulator: qcom_rpm: Fix circular deferral regression RISC-V: Make port I/O string accessors actually work parisc: fbdev/stifb: Align graphics memory size to 4MB riscv: Allow PROT_WRITE-only mmap() riscv: Pass -mno-relax only on lld < 15.0.0 UM: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge powerpc/boot: Explicitly disable usage of SPE instructions fbdev: smscufx: Fix use-after-free in ufx_ops_open() btrfs: fix race between quota enable and quota rescan ioctl f2fs: increase the limit for reserve_root f2fs: fix to do sanity check on destination blkaddr during recovery f2fs: fix to do sanity check on summary info nilfs2: fix use-after-free bug of struct nilfs_root jbd2: wake up journal waiters in FIFO order, not LIFO ext4: avoid crash when inline data creation follows DIO write ext4: fix null-ptr-deref in ext4_write_info ext4: make ext4_lazyinit_thread freezable ext4: place buffer head allocation before handle start livepatch: fix race between fork and KLP transition ftrace: Properly unset FTRACE_HASH_FL_MOD ring-buffer: Allow splice to read previous partially read pages ring-buffer: Have the shortest_full queue be the shortest not longest ring-buffer: Check pending waiters when doing wake ups as well ring-buffer: Fix race between reset page and reading page media: cedrus: Set the platform driver data earlier KVM: x86/emulator: Fix handing of POP SS to correctly set interruptibility KVM: nVMX: Unconditionally purge queued/injected events on nested "exit" KVM: VMX: Drop bits 31:16 when shoving exception error code into VMCS gcov: support GCC 12.1 and newer compilers drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table() selinux: use "grep -E" instead of "egrep" tracing: Disable interrupt or preemption before acquiring arch_spinlock_t userfaultfd: open userfaultfds with O_RDONLY sh: machvec: Use char[] for section boundaries ARM: 9247/1: mm: set readonly for MT_MEMORY_RO with ARM_LPAE nfsd: Fix a memory leak in an error handling path wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() wifi: mac80211: allow bw change during channel switch in mesh bpftool: Fix a wrong type cast in btf_dumper_int x86/resctrl: Fix to restore to original value when re-enabling hardware prefetch register wifi: rtl8xxxu: tighten bounds checking in rtl8xxxu_read_efuse() spi: qup: add missing clk_disable_unprepare on error in spi_qup_resume() spi: qup: add missing
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
I Can confirm the same behavior on my machine
5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
I get
i915 :00:02.0: [drm] *ERROR* Sending link address failed with -5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996804] Re: Focal update: v5.4.219 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996804 Title: Focal update: v5.4.219 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.219 upstream stable release from git://git.kernel.org/ Note: Yup, just this one revert remains to apply for v5.4.219: Revert "fs: check FMODE_LSEEK to control internal pipe splicing" Linux 5.4.219 UBUNTU: Upstream stable to v5.4.219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996825] Re: Jammy update: v5.15.75 upstream stable release
Skipped "r8152: Rate limit overflow messages" (already applied). ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996825 Title: Jammy update: v5.15.75 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.75 upstream stable release from git://git.kernel.org/ Revert "fs: check FMODE_LSEEK to control internal pipe splicing" ALSA: oss: Fix potential deadlock at unregistration ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free() ALSA: usb-audio: Fix potential memory leaks ALSA: usb-audio: Fix NULL dererence at error path ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530 ALSA: hda/realtek: Correct pin configs for ASUS G533Z ALSA: hda/realtek: Add quirk for ASUS GV601R laptop ALSA: hda/realtek: Add Intel Reference SSID to support headset keys mtd: rawnand: atmel: Unmap streaming DMA mappings io_uring/net: don't update msg_name if not provided hv_netvsc: Fix race between VF offering and VF association message from host cifs: destage dirty pages before re-reading them for cache=none cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message iio: dac: ad5593r: Fix i2c read protocol requirements iio: ltc2497: Fix reading conversion results iio: adc: ad7923: fix channel readings for some variants iio: pressure: dps310: Refactor startup procedure iio: pressure: dps310: Reset chip after timeout xhci: dbc: Fix memory leak in xhci_alloc_dbc() usb: add quirks for Lenovo OneLink+ Dock can: kvaser_usb: Fix use of uninitialized completion can: kvaser_usb_leaf: Fix overread with an invalid command can: kvaser_usb_leaf: Fix TX queue out of sync after restart can: kvaser_usb_leaf: Fix CAN state after restart mmc: sdhci-sprd: Fix minimum clock limit i2c: designware: Fix handling of real but unexpected device interrupts fs: dlm: fix race between test_bit() and queue_work() fs: dlm: handle -EBUSY first in lock arg validation HID: multitouch: Add memory barriers quota: Check next/prev free block number after reading from quota file platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure ASoC: wcd9335: fix order of Slimbus unprepare/disable ASoC: wcd934x: fix order of Slimbus unprepare/disable hwmon: (gsc-hwmon) Call of_node_get() before of_find_xxx API net: thunderbolt: Enable DMA paths only after rings are enabled regulator: qcom_rpm: Fix circular deferral regression arm64: topology: move store_cpu_topology() to shared code riscv: topology: fix default topology reporting RISC-V: Make port I/O string accessors actually work parisc: fbdev/stifb: Align graphics memory size to 4MB riscv: Make VM_WRITE imply VM_READ riscv: always honor the CONFIG_CMDLINE_FORCE when parsing dtb riscv: Pass -mno-relax only on lld < 15.0.0 UM: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK nvmem: core: Fix memleak in nvmem_register() nvme-multipath: fix possible hang in live ns resize with ANA access nvme-pci: set min_align_mask before calculating max_hw_sectors dmaengine: mxs: use platform_driver_register drm/virtio: Check whether transferred 2D BO is shmem drm/virtio: Unlock reservations on virtio_gpu_object_shmem_init() error drm/virtio: Use appropriate atomic state in virtio_gpu_plane_cleanup_fb() drm/udl: Restore display mode on resume UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2441007 arm64: errata: Add Cortex-A55 to the repeat tlbi list mm/damon: validate if the pmd entry is present before accessing mm/mmap: undo ->mmap() when arch_validate_flags() fails xen/gntdev: Prevent leaking grants xen/gntdev: Accommodate VMA splitting PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge serial: 8250: Let drivers request full 16550A feature probing serial: 8250: Request full 16550A feature probing for OxSemi PCIe devices powercap: intel_rapl: Use standard Energy Unit for SPR Dram RAPL domain powerpc/boot: Explicitly disable usage of SPE instructions slimbus: qcom-ngd: use correct error in message of pdr_add_lookup() failure slimbus: qcom-ngd: cleanup in probe error path scsi: qedf: Populate sysfs attributes for vport gpio: rockchip: request GPIO mux to pinctrl when setting direction pinctrl: rockchip: add
[Kernel-packages] [Bug 1996893] [NEW] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9
*** This bug is a duplicate of bug 1996894 *** https://bugs.launchpad.net/bugs/1996894 Public bug reported: Hello, dell xps 9320 [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 [gio nov 17 12:59:42 2022] load of value 112 is not a valid value for type '_Bool' [gio nov 17 12:59:42 2022] CPU: 8 PID: Comm: camerasrc0:src Tainted: G O 5.15.0-53-generic #59-Ubuntu [gio nov 17 12:59:42 2022] Hardware name: Dell Inc. XPS 9320/0KNXGD, BIOS 1.9.0 09/23/2022 [gio nov 17 12:59:42 2022] Call Trace: [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] show_stack+0x52/0x5c [gio nov 17 12:59:42 2022] dump_stack_lvl+0x4a/0x63 [gio nov 17 12:59:42 2022] dump_stack+0x10/0x16 [gio nov 17 12:59:42 2022] ubsan_epilogue+0x9/0x49 [gio nov 17 12:59:42 2022] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [gio nov 17 12:59:42 2022] dma_buf_vmap.cold+0x38/0x3d [gio nov 17 12:59:42 2022] ipu_psys_mapbuf_locked+0x17c/0x450 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? __check_object_size.part.0+0x3a/0x150 [gio nov 17 12:59:42 2022] ipu_psys_ioctl+0x159/0x3e0 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? exit_to_user_mode_prepare+0x37/0xb0 [gio nov 17 12:59:42 2022] ? syscall_exit_to_user_mode+0x27/0x50 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] __x64_sys_ioctl+0x92/0xd0 [gio nov 17 12:59:42 2022] do_syscall_64+0x59/0xc0 [gio nov 17 12:59:42 2022] ? irqentry_exit+0x1d/0x30 [gio nov 17 12:59:42 2022] ? exc_page_fault+0x89/0x170 [gio nov 17 12:59:42 2022] entry_SYSCALL_64_after_hwframe+0x61/0xcb [gio nov 17 12:59:42 2022] RIP: 0033:0x7f19e532aaff [gio nov 17 12:59:42 2022] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [gio nov 17 12:59:42 2022] RSP: 002b:7f19e27f61e0 EFLAGS: 0246 ORIG_RAX: 0010 [gio nov 17 12:59:42 2022] RAX: ffda RBX: 7f19d80dddb0 RCX: 7f19e532aaff [gio nov 17 12:59:42 2022] RDX: 001d RSI: c0044102 RDI: 001c [gio nov 17 12:59:42 2022] RBP: 7f19d8a74070 R08: R09: 7f19d8a74070 [gio nov 17 12:59:42 2022] R10: 7f19d80006a0 R11: 0246 R12: [gio nov 17 12:59:42 2022] R13: 7f19d8a6d1b0 R14: 7f19d80dddb0 R15: 7f19e27f630c [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] intel-ipu6-isys intel-ipu6-isys0: stream on ov01a10 3-0036 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1996894 UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 -- 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/1996893 Title: UBSAN: invalid-load in /build/linux- JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 Status in linux package in Ubuntu: New Bug description: Hello, dell xps 9320 [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 [gio nov 17 12:59:42 2022] load of value 112 is not a valid value for type '_Bool' [gio nov 17 12:59:42 2022] CPU: 8 PID: Comm: camerasrc0:src Tainted: G O 5.15.0-53-generic #59-Ubuntu [gio nov 17 12:59:42 2022] Hardware name: Dell Inc. XPS 9320/0KNXGD, BIOS 1.9.0 09/23/2022 [gio nov 17 12:59:42 2022] Call Trace: [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] show_stack+0x52/0x5c [gio nov 17 12:59:42 2022] dump_stack_lvl+0x4a/0x63 [gio nov 17 12:59:42 2022] dump_stack+0x10/0x16 [gio nov 17 12:59:42 2022] ubsan_epilogue+0x9/0x49 [gio nov 17 12:59:42 2022] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [gio nov 17 12:59:42 2022] dma_buf_vmap.cold+0x38/0x3d [gio nov 17 12:59:42 2022] ipu_psys_mapbuf_locked+0x17c/0x450 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? __check_object_size.part.0+0x3a/0x150 [gio nov 17 12:59:42 2022] ipu_psys_ioctl+0x159/0x3e0 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? exit_to_user_mode_prepare+0x37/0xb0 [gio nov 17 12:59:42 2022] ? syscall_exit_to_user_mode+0x27/0x50 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] __x64_sys_ioctl+0x92/0xd0 [gio nov 17 12:59:42 2022]
[Kernel-packages] [Bug 1996894] 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/1996894 Title: UBSAN: invalid-load in /build/linux- JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 Status in linux package in Ubuntu: Confirmed Bug description: Hello, dell xps 9320 [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 [gio nov 17 12:59:42 2022] load of value 112 is not a valid value for type '_Bool' [gio nov 17 12:59:42 2022] CPU: 8 PID: Comm: camerasrc0:src Tainted: G O 5.15.0-53-generic #59-Ubuntu [gio nov 17 12:59:42 2022] Hardware name: Dell Inc. XPS 9320/0KNXGD, BIOS 1.9.0 09/23/2022 [gio nov 17 12:59:42 2022] Call Trace: [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] show_stack+0x52/0x5c [gio nov 17 12:59:42 2022] dump_stack_lvl+0x4a/0x63 [gio nov 17 12:59:42 2022] dump_stack+0x10/0x16 [gio nov 17 12:59:42 2022] ubsan_epilogue+0x9/0x49 [gio nov 17 12:59:42 2022] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [gio nov 17 12:59:42 2022] dma_buf_vmap.cold+0x38/0x3d [gio nov 17 12:59:42 2022] ipu_psys_mapbuf_locked+0x17c/0x450 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? __check_object_size.part.0+0x3a/0x150 [gio nov 17 12:59:42 2022] ipu_psys_ioctl+0x159/0x3e0 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? exit_to_user_mode_prepare+0x37/0xb0 [gio nov 17 12:59:42 2022] ? syscall_exit_to_user_mode+0x27/0x50 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] __x64_sys_ioctl+0x92/0xd0 [gio nov 17 12:59:42 2022] do_syscall_64+0x59/0xc0 [gio nov 17 12:59:42 2022] ? irqentry_exit+0x1d/0x30 [gio nov 17 12:59:42 2022] ? exc_page_fault+0x89/0x170 [gio nov 17 12:59:42 2022] entry_SYSCALL_64_after_hwframe+0x61/0xcb [gio nov 17 12:59:42 2022] RIP: 0033:0x7f19e532aaff [gio nov 17 12:59:42 2022] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [gio nov 17 12:59:42 2022] RSP: 002b:7f19e27f61e0 EFLAGS: 0246 ORIG_RAX: 0010 [gio nov 17 12:59:42 2022] RAX: ffda RBX: 7f19d80dddb0 RCX: 7f19e532aaff [gio nov 17 12:59:42 2022] RDX: 001d RSI: c0044102 RDI: 001c [gio nov 17 12:59:42 2022] RBP: 7f19d8a74070 R08: R09: 7f19d8a74070 [gio nov 17 12:59:42 2022] R10: 7f19d80006a0 R11: 0246 R12: [gio nov 17 12:59:42 2022] R13: 7f19d8a6d1b0 R14: 7f19d80dddb0 R15: 7f19e27f630c [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] intel-ipu6-isys intel-ipu6-isys0: stream on ov01a10 3-0036 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 14:25:03 2022 InstallationDate: Installed on 2022-10-27 (21 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9320 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=6d7dd1e4-07a0-4d03-8d72-6bfc7ae33a0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0KNXGD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd09/23/2022:br1.9:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0KNXGD: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:
[Kernel-packages] [Bug 1996894] [NEW] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9
Public bug reported: Hello, dell xps 9320 [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] UBSAN: invalid-load in /build/linux-JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 [gio nov 17 12:59:42 2022] load of value 112 is not a valid value for type '_Bool' [gio nov 17 12:59:42 2022] CPU: 8 PID: Comm: camerasrc0:src Tainted: G O 5.15.0-53-generic #59-Ubuntu [gio nov 17 12:59:42 2022] Hardware name: Dell Inc. XPS 9320/0KNXGD, BIOS 1.9.0 09/23/2022 [gio nov 17 12:59:42 2022] Call Trace: [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] show_stack+0x52/0x5c [gio nov 17 12:59:42 2022] dump_stack_lvl+0x4a/0x63 [gio nov 17 12:59:42 2022] dump_stack+0x10/0x16 [gio nov 17 12:59:42 2022] ubsan_epilogue+0x9/0x49 [gio nov 17 12:59:42 2022] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [gio nov 17 12:59:42 2022] dma_buf_vmap.cold+0x38/0x3d [gio nov 17 12:59:42 2022] ipu_psys_mapbuf_locked+0x17c/0x450 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? __check_object_size.part.0+0x3a/0x150 [gio nov 17 12:59:42 2022] ipu_psys_ioctl+0x159/0x3e0 [intel_ipu6_psys] [gio nov 17 12:59:42 2022] ? exit_to_user_mode_prepare+0x37/0xb0 [gio nov 17 12:59:42 2022] ? syscall_exit_to_user_mode+0x27/0x50 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] ? __fget_files+0x86/0xc0 [gio nov 17 12:59:42 2022] __x64_sys_ioctl+0x92/0xd0 [gio nov 17 12:59:42 2022] do_syscall_64+0x59/0xc0 [gio nov 17 12:59:42 2022] ? irqentry_exit+0x1d/0x30 [gio nov 17 12:59:42 2022] ? exc_page_fault+0x89/0x170 [gio nov 17 12:59:42 2022] entry_SYSCALL_64_after_hwframe+0x61/0xcb [gio nov 17 12:59:42 2022] RIP: 0033:0x7f19e532aaff [gio nov 17 12:59:42 2022] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [gio nov 17 12:59:42 2022] RSP: 002b:7f19e27f61e0 EFLAGS: 0246 ORIG_RAX: 0010 [gio nov 17 12:59:42 2022] RAX: ffda RBX: 7f19d80dddb0 RCX: 7f19e532aaff [gio nov 17 12:59:42 2022] RDX: 001d RSI: c0044102 RDI: 001c [gio nov 17 12:59:42 2022] RBP: 7f19d8a74070 R08: R09: 7f19d8a74070 [gio nov 17 12:59:42 2022] R10: 7f19d80006a0 R11: 0246 R12: [gio nov 17 12:59:42 2022] R13: 7f19d8a6d1b0 R14: 7f19d80dddb0 R15: 7f19e27f630c [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] intel-ipu6-isys intel-ipu6-isys0: stream on ov01a10 3-0036 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 14:25:03 2022 InstallationDate: Installed on 2022-10-27 (21 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9320 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=6d7dd1e4-07a0-4d03-8d72-6bfc7ae33a0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0KNXGD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd09/23/2022:br1.9:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0KNXGD: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: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- 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/1996894 Title: UBSAN: invalid-load in /build/linux- JjvoxS/linux-5.15.0/include/linux/dma-buf-map.h:224:9 Status in linux package in Ubuntu: Confirmed Bug description: Hello, dell xps 9320 [gio nov 17 12:59:42 2022] [gio nov 17 12:59:42 2022] UBSAN: invalid-load in
[Kernel-packages] [Bug 1996892] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1996892 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Status in linux source package in Lunar: Incomplete Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996541] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1996541 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996541 Title: Laptop blocked into Airplane mode after wakeup from suspend Status in linux package in Ubuntu: Incomplete Bug description: Once I put my laptop to sleep and then wake it up, I no longer have internet, as my laptop locks itself automatically into Airplane mode. The Airplane and wifi buttons become unusable and can't click them, so I have to reboot the laptop everytime it goes to sleep/suspend mode. The workaround I found to enable fn+F10 is to add this line to the grub config in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009' quiet splash" and then to run: sudo update-grub -- As mentioned this is a manual workaround that involves reactivating the wifi after each sleep; Kindly, if you can fix this to avoid this additional manual step. Warm Regards, Yassine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.19.0.1012.11)
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1012.11) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: systemd/251.4-1ubuntu7 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996541] Re: Laptop blocked into Airplane mode after wakeup from suspend
> Kindly, if you can fix this to avoid this additional manual step. You didn't tell us which release you are using. Something very necessary when you ask for a bug to be fixed. https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate suggests that this bug report should have been created against the 'linux' package. If this is still an issue then please provide any information that is requested from you by the kernel bot. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996541 Title: Laptop blocked into Airplane mode after wakeup from suspend Status in linux package in Ubuntu: New Bug description: Once I put my laptop to sleep and then wake it up, I no longer have internet, as my laptop locks itself automatically into Airplane mode. The Airplane and wifi buttons become unusable and can't click them, so I have to reboot the laptop everytime it goes to sleep/suspend mode. The workaround I found to enable fn+F10 is to add this line to the grub config in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009' quiet splash" and then to run: sudo update-grub -- As mentioned this is a manual workaround that involves reactivating the wifi after each sleep; Kindly, if you can fix this to avoid this additional manual step. Warm Regards, Yassine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] [NEW] Expose built-in trusted and revoked certificates
Public bug reported: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996541] [NEW] Laptop blocked into Airplane mode after wakeup from suspend
You have been subscribed to a public bug: Once I put my laptop to sleep and then wake it up, I no longer have internet, as my laptop locks itself automatically into Airplane mode. The Airplane and wifi buttons become unusable and can't click them, so I have to reboot the laptop everytime it goes to sleep/suspend mode. The workaround I found to enable fn+F10 is to add this line to the grub config in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009' quiet splash" and then to run: sudo update-grub -- As mentioned this is a manual workaround that involves reactivating the wifi after each sleep; Kindly, if you can fix this to avoid this additional manual step. Warm Regards, Yassine ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: airplane internet suspend wifi -- Laptop blocked into Airplane mode after wakeup from suspend https://bugs.launchpad.net/bugs/1996541 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996890] Re: linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed
5.17.0-1015 and -1019 both are obsolete, the latest version is -1021 ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1996890 Title: linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed Status in OEM Priority Project: New Status in nvidia-graphics-drivers-515 package in Ubuntu: Invalid Bug description: The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency. After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load the nvidia driver when boot up. rc linux-modules-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 ii linux-modules-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 ii linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22 amd64Extra drivers for nvidia-515 for the oem-22.04a flavour ii linux-objects-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 (objects) ii linux-objects-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 (objects) ii linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1015-oem ii linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1021-oem ii nvidia-compute-utils-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities ii nvidia-driver-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage ii nvidia-kernel-common-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64Shared files used with the kernel module ii nvidia-kernel-source-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA kernel source package u@P360-tiny-1:~$ sudo apt install linux-modules-nvidia-515-5.17.0-1015-oem Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-515-5.17.0-1015-oem : Depends: nvidia-kernel-common-515 (<= 515.65.01-1) but 515.76+really.515.65.01-0ubuntu0.22.04.2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1996890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996890] [NEW] linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed
Public bug reported: The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency. After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load the nvidia driver when boot up. rc linux-modules-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 ii linux-modules-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 ii linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22 amd64Extra drivers for nvidia-515 for the oem-22.04a flavour ii linux-objects-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 (objects) ii linux-objects-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 (objects) ii linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1015-oem ii linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1021-oem ii nvidia-compute-utils-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities ii nvidia-driver-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage ii nvidia-kernel-common-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64Shared files used with the kernel module ii nvidia-kernel-source-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA kernel source package u@P360-tiny-1:~$ sudo apt install linux-modules-nvidia-515-5.17.0-1015-oem Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-515-5.17.0-1015-oem : Depends: nvidia-kernel-common-515 (<= 515.65.01-1) but 515.76+really.515.65.01-0ubuntu0.22.04.2 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: oem-priority Importance: Critical Status: New ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1995563 sutton ** Package changed: nvidia-graphics-drivers-470 (Ubuntu) => nvidia- graphics-drivers-515 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1996890 Title: linux-modules-nvidia-515-5.17.0-1015-oem couldn't be installed Status in OEM Priority Project: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: The linux-modules-nvidia-515-5.17.0-1015-oem is in a wrong dependency. After upgraded to latest kernel 1021-oem, the 1015-oem kernel failed to load the nvidia driver when boot up. rc linux-modules-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 ii linux-modules-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 ii linux-modules-nvidia-515-oem-22.04a5.17.0-1021.22 amd64Extra drivers for nvidia-515 for the oem-22.04a flavour ii linux-objects-nvidia-515-5.17.0-1015-oem 5.17.0-1015.16 amd64Linux kernel nvidia modules for version 5.17.0-1015 (objects) ii linux-objects-nvidia-515-5.17.0-1021-oem 5.17.0-1021.22 amd64Linux kernel nvidia modules for version 5.17.0-1021 (objects) ii linux-signatures-nvidia-5.17.0-1015-oem5.17.0-1015.16 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1015-oem ii linux-signatures-nvidia-5.17.0-1021-oem5.17.0-1021.22 amd64Linux kernel signatures for nvidia modules for version 5.17.0-1021-oem ii nvidia-compute-utils-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA compute utilities ii nvidia-driver-515 515.76+really.515.65.01-0ubuntu0.22.04.2 amd64NVIDIA driver metapackage ii nvidia-kernel-common-515
[Kernel-packages] [Bug 1995004] Re: Increase stability with connection tracking offload
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995004 Title: Increase stability with connection tracking offload Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. Also, include set of patches to increase stability with connection tracking offload, including reduced cpu load and possible deadlock on cleanup. * What it could break. Packet on egress tc rule forwarding to a ingress tc rule will drop. High cpu load. Possible deadlock on cleanup. * How to test Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995109] Re: bluefield-edac: Potentially overflowing expression
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995109 Title: bluefield-edac: Potentially overflowing expression Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
The issue happened for me after installing newer nvidia proprietary drivers
(515 and also 520).
The only way to recover was to boot using a previous installed kernel (I used
rescue mode. The rescue mode in current kernel still gives the same error)
Not sure how this helps this bug investigation but was real pain knowing
that I couldn't install the nvidia drivers.
The only thing that worked was installing the nvidia drivers 470
version.
https://forums.developer.nvidia.com/t/ubuntu-22-04-1-nvidia-driver-open-
kernel-nvidia-driver-515-open-issue/231356/12?u=yohn.krichton
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to
[Kernel-packages] [Bug 1963767] Re: [jammy] Microphone not working after suspend
Did you test he same webcam as I did (Logitech BRIO)? If it happens for me with two laptops from different manufacturers that have different processors (Intel vs AMD), there is certainly something going on. It happened on 21.10 and now happns on 22.04 LTS version of Ubuntu, so the bug report should be valid IMHO. Thankfully I'm not using laptop actively, it is a really bad experience. -- 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/1963767 Title: [jammy] Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-6.0/6.0.0.1008.8)
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1008.8) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.6 (amd64) nvidia-graphics-drivers-515/515.76+really.515.65.01-0ubuntu0.22.04.2 (amd64) backport-iwlwifi-dkms/9858-0ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-6.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983128] Re: linux-lowlatency fails to build on arm64 due to kernel option settings
set to invails, since this was for a previous proposed migrations issue
that was meanwhile solved
** Changed in: linux-lowlatency (Ubuntu)
Status: New => Invalid
** Changed in: zlib (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/1983128
Title:
linux-lowlatency fails to build on arm64 due to kernel option settings
Status in linux-lowlatency package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Invalid
Bug description:
The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64:
Regression ♻"
The regression is highly likely not due to zlib itself, but due to NEW kernel
options, that don't have a default yet and a check-config FAIL, see:
...
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config:
loading config
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations
loading annotations
check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
-, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
check-config: 11323/11324 checks passed -- exit 1
...
Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
Error in reading or end of file.
...
Initialize kernel stack variables at function entry
> 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
choice[1-3?]:
Error in reading or end of file.
...
Full log is here:
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz
(this might be caused by the recent compiler update)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Running "Ubuntu 22.04.1". After updating today, was unable to fully boot. Screen goes black, unable to get to a terminal. Booted into 5.15.0-52 to report/confirm issue. Please instruct. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
