[Kernel-packages] [Bug 2024199] Re: Resync CI Runner Configuration
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024199 Title: Resync CI Runner Configuration Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Ongoing CI runner configuration sync. This provides an in-tree definition for patch checking and kernel testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027535] Re: unexpected error message: invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K
Ah, I figured out what's going on: the upper limit of special_small_blocks is checked against the currently value of recordsize. But, the pool doesn't actually have a recordsize set at this point, because the pool doesn't even exist. So, the setting that was given immediately before on the command line has no influence. In short: Create the pool with only -O recordsize=1MB (or whatever) and *then* set the special_small_blocks property after the pool exists: sudo zfs set special_small_blocks=256KB newsrv This isn't ideal but it doesn't really look like an Ubuntu packaging bug. Thanks for rubberducking, launchpad! ** Changed in: zfs-linux (Ubuntu) Status: New => Invalid -- 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/2027535 Title: unexpected error message: invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K Status in zfs-linux package in Ubuntu: Invalid Bug description: Hello, I'm trying to create a new zfs pool using the special allocation vdevs and I get an error message that doesn't make sense to me: cannot create 'newsrv': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K $ echo "2 ^ 18" | bc -lq 262144 But the manpage says this number may be up to one megabyte: sarnold@wopr:~ $ PAGER=cat MANWIDTH=70 man -7 --nh --nj zfsprops 2> /dev/null | grep -A8 special_small_blocks special_small_blocks=size This value represents the threshold block size for including small file blocks into the special allocation class. Blocks smaller than or equal to this value will be assigned to the special allocation class while greater blocks will be assigned to the regular class. Valid values are zero or a power of two from 512B up to 1M. The default size is 0 which means no small file blocks will be allocated in the special class. Here is a small demonstration: sarnold@wopr:/tmp $ truncate -s 200MB disk1 sarnold@wopr:/tmp $ truncate -s 200MB disk2 sarnold@wopr:/tmp $ sudo zpool create -O recordsize=1MB -O special_small_blocks=256KB test /tmp/disk1 special /tmp/disk2 cannot create 'test': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K sarnold@wopr:/tmp 1 $ sudo zpool create -O recordsize=1MB -O special_small_blocks=128KB test /tmp/disk1 special /tmp/disk2 sarnold@wopr:/tmp $ zpool status test pool: test state: ONLINE config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 /tmp/disk1 ONLINE 0 0 0 special /tmp/disk2 ONLINE 0 0 0 errors: No known data errors sarnold@wopr:/tmp $ sudo zpool destroy test sarnold@wopr:/tmp $ And now the actual command I tried: sarnold@wopr:~ $ sudo zpool create -f -O atime=off -O checksum=skein -O compression=zstd-3 -O dedup=skein -O recordsize=1MB -O special_small_blocks=256KB -O xattr=sa newsrv mirror /dev/disk/by-id/ata-WDC_WUH721414ALE604_9RKGP7NC /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2K012NT mirror /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2KH01NT /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2KHG12T special /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312010E /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312031Z /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312033K /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312101T cannot create 'newsrv': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.5-1ubuntu6~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-70.77-generic 5.15.92 Uname: Linux 5.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jul 11 21:27:05 2023 InstallationDate: Installed on 2016-04-04 (2655 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-14 (331 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2027535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027535] [NEW] unexpected error message: invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K
Public bug reported: Hello, I'm trying to create a new zfs pool using the special allocation vdevs and I get an error message that doesn't make sense to me: cannot create 'newsrv': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K $ echo "2 ^ 18" | bc -lq 262144 But the manpage says this number may be up to one megabyte: sarnold@wopr:~ $ PAGER=cat MANWIDTH=70 man -7 --nh --nj zfsprops 2> /dev/null | grep -A8 special_small_blocks special_small_blocks=size This value represents the threshold block size for including small file blocks into the special allocation class. Blocks smaller than or equal to this value will be assigned to the special allocation class while greater blocks will be assigned to the regular class. Valid values are zero or a power of two from 512B up to 1M. The default size is 0 which means no small file blocks will be allocated in the special class. Here is a small demonstration: sarnold@wopr:/tmp $ truncate -s 200MB disk1 sarnold@wopr:/tmp $ truncate -s 200MB disk2 sarnold@wopr:/tmp $ sudo zpool create -O recordsize=1MB -O special_small_blocks=256KB test /tmp/disk1 special /tmp/disk2 cannot create 'test': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K sarnold@wopr:/tmp 1 $ sudo zpool create -O recordsize=1MB -O special_small_blocks=128KB test /tmp/disk1 special /tmp/disk2 sarnold@wopr:/tmp $ zpool status test pool: test state: ONLINE config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 /tmp/disk1 ONLINE 0 0 0 special /tmp/disk2 ONLINE 0 0 0 errors: No known data errors sarnold@wopr:/tmp $ sudo zpool destroy test sarnold@wopr:/tmp $ And now the actual command I tried: sarnold@wopr:~ $ sudo zpool create -f -O atime=off -O checksum=skein -O compression=zstd-3 -O dedup=skein -O recordsize=1MB -O special_small_blocks=256KB -O xattr=sa newsrv mirror /dev/disk/by-id/ata-WDC_WUH721414ALE604_9RKGP7NC /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2K012NT mirror /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2KH01NT /dev/disk/by-id/ata-WDC_WUH721414ALE604_Z2KHG12T special /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312010E /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312031Z /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312033K /dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6PJNS0W312101T cannot create 'newsrv': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.5-1ubuntu6~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-70.77-generic 5.15.92 Uname: Linux 5.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jul 11 21:27:05 2023 InstallationDate: Installed on 2016-04-04 (2655 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-14 (331 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: Hello, I'm trying to create a new zfs pool using the special allocation vdevs and I get an error message that doesn't make sense to me: cannot create 'newsrv': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K $ echo "2 ^ 18" | bc -lq 262144 + But the manpage says this number may be up to one megabyte: + + sarnold@wopr:~ $ PAGER=cat MANWIDTH=70 man -7 --nh --nj zfsprops 2> /dev/null | grep -A8 special_small_blocks + special_small_blocks=size +This value represents the threshold block size for including +small file blocks into the special allocation class. Blocks +smaller than or equal to this value will be assigned to the +special allocation class while greater blocks will be +assigned to the regular class. Valid values are zero or a +power of two from 512B up to 1M. The default size is 0 which +means no small file blocks will be allocated in the special +class. + Here is a small demonstration: sarnold@wopr:/tmp $ sudo zpool create -O recordsize=1MB -O special_small_blocks=256KB test /tmp/disk1 special /tmp/disk2 cannot create 'test': invalid 'special_small_blocks=262144' property: must be zero or a power of 2 from 512B to 128K sarnold@wopr:/tmp 1 $ sudo zpool create -O recordsize=1MB -O special_small_blocks=128KB test /tmp/disk1 special /tmp/disk2 sarnold@wopr:/tmp $ zpool status test -
[Kernel-packages] [Bug 2025670] Re: amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
** Changed in: linux-oem-6.1 (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/2025670 Title: amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571 This is specifically when a system advertises support for PMF, but doesn't support static power slider for any reason. Upstream fix in https://github.com/torvalds/linux/commit/146b6f6855e7656e8329910606595220c761daac, which has been backported to v6.1.36 (oem-6.1 in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13), v6.3.10 (linux/mantic in v6.3.8), v6.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
** Changed in: linux-oem-6.1 (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-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2027531 ** Tags added: iso-testing -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
on this currently working system ubuntu@ubuntu:~$ sudo lshw -C network *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 6b serial: 5c:51:4f:0d:d7:9d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=6.3.0-7-generic firmware=17.3216344376.0 7260-17.ucode ip=192.168.15.102 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:46 memory:f7e0-f7e01fff ** Attachment added: "lshw run on an installed ubuntu mantic system (what I'm getting most of the time)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+attachment/5685536/+files/lshw_network.txt -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
current (live) session dmesg ** Attachment added: "dmesg.this" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+attachment/5685538/+files/dmesg.this -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
The attached dmesg is for a session (installed) where the wifi wasn't working.. (same boot as lshw_network in prior comment) I won't include current dmesg here (too long) but intend attaching next comment ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+attachment/5685537/+files/dmesg.txt -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027531] [NEW] ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
Public bug reported: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
Can you try the below commit from linus's "linux" tree and see if the warning goes away? commit f5451547b8310868f5b5acff7cd4aa7c0267edb3 Author: Thomas Gleixner Date: Tue Feb 7 15:16:53 2023 +0100 mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024126] Re: eDP power on flow enhancement to speed up kernel boot time
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024126 Title: eDP power on flow enhancement to speed up kernel boot time Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] eDP power on flow enhancement to speed up kernel boot time. This commit is recommended by Intel. [Fix] The commit below is from 6.2-rc1 36d357169891 drm/i915/edp: wait power off delay at driver remove to optimize probe [Test] No [Where problems could occur] The assumption of the patch should be always correct, we don't have to wait the panel to be powered off when boots up, the panel power should has been switched off right before boots up. And the panel_power_off_time value will be set to the desired value in wait_panel_power_cycle(). So, should be pretty safe to include this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024449] Re: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2024449 Title: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When playing audio from HDMI/DP port on AMD W6300 gfx, there's always white noise. It will disappear after suspend/resume. Disabling ASPM on W6300 also fix this. [Fix] Backport a fix from AMD on https://www.spinics.net/lists/amd-gfx/msg93796.html https://www.spinics.net/lists/amd-gfx/msg93797.html [Test] 1. Power on the Desktop installed with AMD W6300 gfx 2. Connect a monitor with either HDMI or DP cable. 3. Change the audio output port to HDMI/DP and play audio. 4. Verify if there's noise from the audio output [Where problems could occur] Only observed on AMD W6300. The fix revise the ASPM L1 inactivily time out on NAVI10 GPU series. The impact should be only for this particular GPU series. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
yeah I suspect that.. there are couple of irq patches in the 6.2.0-1004-nvidia could be the cause.. I will update here shortly! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023691] Re: Unable to boot into linux image 5.15 in Ubuntu 22.04
I believe the package with the problem is linux-image-5.15.0-73-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023691 Title: Unable to boot into linux image 5.15 in Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: I cannot boot linux-image-5.15.0-73-generic on Ubuntu 22.04. The attached image shows what happens. * The initial grub boot screen appears, "Advanced options for Ubuntu" is selected * On the next screen, "Ubuntu. with Linux 5.15.0-73-generic" is selected * The next screen shows that initial ramdisk is being loaded for Linux 5.15.0-73-generic * The last screen shows the boot has failed, and the user is dropped into the ramdisk with an (initramfs) command prompt. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ninehs 3175 F pulseaudio /dev/snd/pcmC0D0p: ninehs 3175 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-21 (25 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. XPS 15 9530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=f8da35e6-4c99-4abe-8178-b74ee050ae3f ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 5.19.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2023 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 09J5GK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd03/23/2023:br1.2:efr1.2:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn09J5GK:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB: dmi.product.family: XPS dmi.product.name: XPS 15 9530 dmi.product.sku: 0BEB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
I ran through several kernels on our DGX-2 server, only the latest 6.2.0-1004-nvidia kernel emitted the warning. Here are all the kernels I tried: Lunar 6.2.0-24.24 generic - PASS Jammy 5.15.0-1028-nvidia - PASS Jammy 5.19.0-46-generic - PASS Jammy 5.19.0-1014-nvidia - PASS Jammy 6.2.0-25-generic - PASS Jammy 6.2.0-1003-nvidia - PASS Jammy 6.2.0-1004-nvidia - FAIL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
The issue persists with 5.4.0-152 -- 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/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
This bug is about installing on a system with a different version of binutils. I assumed that is what you are doing because that is what this bug is about. But based on your comment @khteh, I now assume that you are not hitting the problem I reported. Do you have a reason to believe your issue is caused by binutils, or are you just seeing this same error message? modprobe: ERROR: could not insert 'nvidia': Key was rejected by service binutils version differences is not the only reason you might see that error. You may be having an issue unrelated to this bug. One possibility is that the installation method you selected is trying to build its own version of the module, which is not signed by a trusted Canonical key. The fact that you have a make.log at all (as shown in comment #19) is a hint there. nvidia-driver-535 will try to install the prebuilt and signed modules where possible, but if it can't, it will revert to installing the "source" and building an unsigned one instead. If you have the nvidia-dkms-535 driver installed instead of linux-modules-nvidia-535-generic, then that may be what happened. If that is the case, you can try switching to the prebuilt/signed one by running: sudo apt install nvidia-driver-535 linux-modules-nvidia-535-generic sudo apt remove nvidia-dkms-535 # ^ That should only remove nvidia-dkms-535 I hope that fixes your system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
This bug was fixed in the package linux-kvm - 6.2.0-1008.8 --- linux-kvm (6.2.0-1008.8) lunar; urgency=medium * lunar/linux-kvm: 6.2.0-1008.8 -proposed tracker (LP: #2025454) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY=m [ Ubuntu: 6.2.0-25.25 ] * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix
[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2019320] Re: i2c devices missing in lunar
This bug was fixed in the package linux-raspi - 6.2.0-1008.10 --- linux-raspi (6.2.0-1008.10) lunar; urgency=medium * lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update annotations scripts * raspi-nolpae flavor is pointless nowadays (LP: #2023359) - [Packaging] raspi: Remove raspi-nolpae armhf flavor * Pi Camera 3 not working with Lunar (LP: #2024434) - [Config] raspi: Set VIDEO_DW9807_VCM=m * i2c devices missing in lunar (LP: #2019320) - [Config] raspi: Set I2C_CHARDEV=y [ Ubuntu: 6.2.0-25.25 ] * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all
[Kernel-packages] [Bug 2019915] Re: Enable audio LEDs on HP laptops
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2020356] Re: generate linux-lib-rust only on amd64
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2023359] Re: raspi-nolpae flavor is pointless nowadays
This bug was fixed in the package linux-raspi - 6.2.0-1008.10 --- linux-raspi (6.2.0-1008.10) lunar; urgency=medium * lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update annotations scripts * raspi-nolpae flavor is pointless nowadays (LP: #2023359) - [Packaging] raspi: Remove raspi-nolpae armhf flavor * Pi Camera 3 not working with Lunar (LP: #2024434) - [Config] raspi: Set VIDEO_DW9807_VCM=m * i2c devices missing in lunar (LP: #2019320) - [Config] raspi: Set I2C_CHARDEV=y [ Ubuntu: 6.2.0-25.25 ] * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all
[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2023929] Re: Lunar update: v6.2.13 upstream stable release
This bug was fixed in the package linux - 6.2.0-25.25 --- linux (6.2.0-25.25) lunar; urgency=medium * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set - bonding: Fix memory leak when changing bond type to Ethernet - net: rpl: fix rpl header size calculation - mlxsw: pci: Fix possible crash during initialization - spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() - bpf: Fix incorrect verifier pruning due to missing register precision taints
[Kernel-packages] [Bug 2024434] Re: Pi Camera 3 not working with Lunar
This bug was fixed in the package linux-raspi - 6.2.0-1008.10 --- linux-raspi (6.2.0-1008.10) lunar; urgency=medium * lunar/linux-raspi: 6.2.0-1008.10 -proposed tracker (LP: #2025455) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update annotations scripts * raspi-nolpae flavor is pointless nowadays (LP: #2023359) - [Packaging] raspi: Remove raspi-nolpae armhf flavor * Pi Camera 3 not working with Lunar (LP: #2024434) - [Config] raspi: Set VIDEO_DW9807_VCM=m * i2c devices missing in lunar (LP: #2019320) - [Config] raspi: Set I2C_CHARDEV=y [ Ubuntu: 6.2.0-25.25 ] * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
This bug was fixed in the package linux-lowlatency-hwe-6.2 - 6.2.0-1008.8~22.04.1 --- linux-lowlatency-hwe-6.2 (6.2.0-1008.8~22.04.1) jammy; urgency=medium * jammy/linux-lowlatency-hwe-6.2: 6.2.0-1008.8~22.04.1 -proposed tracker (LP: #2024536) [ Ubuntu: 6.2.0-1008.8 ] * lunar/linux-lowlatency: 6.2.0-1008.8 -proposed tracker (LP: #2024537) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on older P3/P4 chips - mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() - LoongArch: Fix build error if CONFIG_SUSPEND is not set -
[Kernel-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 I was unable to select the "Ubuntu on Xorg" as a configuration option, so I did it manually. I modified /etc/gdm3/custom.conf current configuration: # GDM configuration storage # # See /usr/share/gdm/gdm.schemas for a list of available options. [daemon] # Uncomment the line below to force the login screen to use Xorg WaylandEnable=false # Enabling automatic login # AutomaticLoginEnable = true # AutomaticLogin = user1 # Enabling timed login # TimedLoginEnable = true # TimedLogin = user1 # TimedLoginDelay = 10 [security] DisallowTCP=false [xdmcp] ServerArguments=-listen tcp [chooser] [debug] # Uncomment the line below to turn on debugging # More verbose logs # Additionally lets the X server dump core if it crashes Enable=true This does not appear to work-around the problem. I am getting drm errors : [Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma Keyboard as /devices/pci:00/:00:07.2/:50:00.0/:51:04.0/:53:00.0/:54:02.0/:57:00.0/usb9/9-2/9-2:1.1/0003:1532:0F1A.000C/input/input39 [Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0006 [Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0007 [Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0008 [Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Tue Jul 11 13:24:20 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0009 [Tue Jul 11 13:24:20 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma as /devices/pci:00/:00:07.2/:50:00.0/:51:04.0/:53:00.0/:54:02.0/:57:00.0/usb9/9-2/9-2:1.1/0003:1532:0F1A.000C/input/input40 [Tue Jul 11 13:24:20 2023] hid-generic 0003:1532:0F1A.000C: input,hidraw8: USB HID v1.11 Keyboard [Razer Razer Core X Chroma] on usb-:57:00.0-2/input1 [Tue Jul 11 13:24:20 2023] input: Razer Razer Core X Chroma as /devices/pci:00/:00:07.2/:50:00.0/:51:04.0/:53:00.0/:54:02.0/:57:00.0/usb9/9-2/9-2:1.2/0003:1532:0F1A.000D/input/input41 [Tue Jul 11 13:24:20 2023] hid-generic 0003:1532:0F1A.000D: input,hidraw9: USB HID v1.11 Mouse [Razer Razer Core X Chroma] on usb-:57:00.0-2/input2 [Tue Jul 11 13:24:21 2023] ax88179_178a 10-1:1.0 eth0: register 'ax88179_178a' at usb-:57:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 98:bb:1e:1e:f9:7c [Tue Jul 11 13:24:21 2023] usbcore: registered new interface driver ax88179_178a [Tue Jul 11 13:24:21 2023] ax88179_178a 10-1:1.0 enx98bb1e1ef97c: renamed from eth0 [Tue Jul 11 13:24:24 2023] ax88179_178a 10-1:1.0 enx98bb1e1ef97c: ax88179 - Link status is: 1 [Tue Jul 11 13:24:24 2023] IPv6: ADDRCONF(NETDEV_CHANGE): enx98bb1e1ef97c: link becomes ready [Tue Jul 11 13:24:26 2023] thunderbolt 1-1: new device found, vendor=0x127 device=0x2 [Tue Jul 11 13:24:26 2023] thunderbolt 1-1: Razer Core X Chroma [Tue Jul 11 13:24:33 2023] thunderbolt 1-101: new device found, vendor=0x127 device=0x3 [Tue Jul 11 13:24:33 2023] thunderbolt 1-101: Razer Core X Chroma [Tue Jul 11 13:24:53 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0006 [Tue Jul 11 13:24:53 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Tue Jul 11 13:24:53 2023] [drm:nv_drm_dumb_map_offset [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to lookup gem object for mapping: 0x0007 [Tue Jul 11 13:24:53 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available
[Kernel-packages] [Bug 2026783] Re: soft lockup - likely NVIDIA GPU
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags added: 3d ** Summary changed: - soft lockup - likely NVIDIA GPU + soft lockup when enabling VirtualBox 3d Accel driver for a windows guest - likely a host NVIDIA GPU driver issue ** Description changed: Using VirtualBox on the main host, with the "3d Acceleration" enabled for the windows 10 guest, I somehow triggered a bug. I suspect this is a bug in handling for the NVIDIA driver, it has an impact on the kernel because of the loaded module. Soft Lockups repeatedly occur, please see the dmesg logfile attached. - Here is the spinlock -- [Mon Jul 10 18:37:39 2023] CPU: 4 PID: 90 Comm: irq/126-pciehp Tainted: P OEL 6.2.0-24-generic #24-Ubuntu [Mon Jul 10 18:37:39 2023] Hardware name: LENOVO 20XY0027US/20XY0027US, BIOS N32ET84W (1.60 ) 04/05/2023 [Mon Jul 10 18:37:39 2023] RIP: 0010:_raw_spin_unlock_irqrestore+0x21/0x60 [Mon Jul 10 18:37:39 2023] Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 49 89 f0 48 89 e5 c6 07 00 0f 1f 00 41 f7 c0 00 02 00 00 74 06 fb 0f 1f 44 00 00 <65> ff 0d 90 a5 95 73 74 13 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 [Mon Jul 10 18:37:39 2023] RSP: 0018:ab64005ef780 EFLAGS: 0206 [Mon Jul 10 18:37:39 2023] RAX: RBX: 0001 RCX: [Mon Jul 10 18:37:39 2023] RDX: 0003d268 RSI: 0202 RDI: 9d86d183f668 [Mon Jul 10 18:37:39 2023] RBP: ab64005ef780 R08: 0202 R09: [Mon Jul 10 18:37:39 2023] R10: R11: R12: 0010 [Mon Jul 10 18:37:39 2023] R13: 0003d258 R14: ab64020b0008 R15: 0002 [Mon Jul 10 18:37:39 2023] FS: () GS:9d8a0f70() knlGS: [Mon Jul 10 18:37:39 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 10 18:37:39 2023] CR2: 0153dfa8 CR3: 0002e5210006 CR4: 00772ee0 [Mon Jul 10 18:37:39 2023] PKRU: 5554 [Mon Jul 10 18:37:39 2023] Call Trace: [Mon Jul 10 18:37:39 2023] [Mon Jul 10 18:37:39 2023] os_release_spinlock+0x1a/0x30 [nvidia] [Mon Jul 10 18:37:39 2023] _nv038078rm+0xd9/0x100 [nvidia] [Mon Jul 10 18:37:39 2023] WARNING: kernel stack frame pointer at c662e071 in irq/126-pciehp:90 has bad value a30f4baf [ See the rest of the logs in the attached file. + + The VirtualBox Guest no longer responded. The host machine also became + unstable. -- 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/2026783 Title: soft lockup when enabling VirtualBox 3d Accel driver for a windows guest - likely a host NVIDIA GPU driver issue Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: Using VirtualBox on the main host, with the "3d Acceleration" enabled for the windows 10 guest, I somehow triggered a bug. I suspect this is a bug in handling for the NVIDIA driver, it has an impact on the kernel because of the loaded module. Soft Lockups repeatedly occur, please see the dmesg logfile attached. Here is the spinlock -- [Mon Jul 10 18:37:39 2023] CPU: 4 PID: 90 Comm: irq/126-pciehp Tainted: P OEL 6.2.0-24-generic #24-Ubuntu [Mon Jul 10 18:37:39 2023] Hardware name: LENOVO 20XY0027US/20XY0027US, BIOS N32ET84W (1.60 ) 04/05/2023 [Mon Jul 10 18:37:39 2023] RIP: 0010:_raw_spin_unlock_irqrestore+0x21/0x60 [Mon Jul 10 18:37:39 2023] Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 49 89 f0 48 89 e5 c6 07 00 0f 1f 00 41 f7 c0 00 02 00 00 74 06 fb 0f 1f 44 00 00 <65> ff 0d 90 a5 95 73 74 13 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 [Mon Jul 10 18:37:39 2023] RSP: 0018:ab64005ef780 EFLAGS: 0206 [Mon Jul 10 18:37:39 2023] RAX: RBX: 0001 RCX: [Mon Jul 10 18:37:39 2023] RDX: 0003d268 RSI: 0202 RDI: 9d86d183f668 [Mon Jul 10 18:37:39 2023] RBP: ab64005ef780 R08: 0202 R09: [Mon Jul 10 18:37:39 2023] R10: R11: R12: 0010 [Mon Jul 10 18:37:39 2023] R13: 0003d258 R14: ab64020b0008 R15: 0002 [Mon Jul 10 18:37:39 2023] FS: () GS:9d8a0f70() knlGS: [Mon Jul 10 18:37:39 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 10 18:37:39 2023] CR2: 0153dfa8 CR3: 0002e5210006 CR4: 00772ee0 [Mon Jul 10 18:37:39 2023] PKRU: 5554 [Mon Jul 10 18:37:39 2023] Call Trace: [Mon Jul 10 18:37:39 2023] [Mon Jul 10 18:37:39 2023]
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-6.2/6.2.0.1007.7~22.04.1)
All autopkgtests for the newly accepted linux-meta-aws-6.2 (6.2.0.1007.7~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-aws-6.2/6.2.0-1007.7~22.04.1 (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-aws-6.2 [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 packaging 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 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
** Changed in: linux-nvidia-6.2 (Ubuntu) Assignee: (unassigned) => Tushar Dave (tdavenvidia) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023007] Re: kernel .config lowlatency improvements
This bug was fixed in the package linux-lowlatency - 6.3.0-7.7.1 --- linux-lowlatency (6.3.0-7.7.1) mantic; urgency=medium * mantic/linux-lowlatency: 6.3.0-7.7.1 -proposed tracker (LP: #2024476) * Miscellaneous Ubuntu changes - [Config] update toolchain version [ Ubuntu: 6.3.0-7.7 ] * mantic/linux: 6.3.0-7.7 -proposed tracker (LP: #2023297) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) -- Paolo Pisati Tue, 20 Jun 2023 17:52:45 +0200 ** Changed in: linux-lowlatency (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2023007 Title: kernel .config lowlatency improvements Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-lowlatency source package in Mantic: Fix Released Bug description: [Impact] The lowlatency kernel in Ubuntu is specifically designed to prioritize high responsiveness, making it ideal for multimedia environments like DAWs and audio processing platforms, as well as soft real-time environments. With the introduction of a real-time kernel, it might be worth reconsidering the role of the lowlatency kernel and potentially including it as the default kernel in desktop images, focusing on its suitability for desktop-oriented usage. To achieve this, we can enable additional configuration settings and make it more focused for a low-latency and highly responsive desktop environment. Optionally (for the future) provide also an additional user-space package that would enable specific run-time kernel settings focused at certain preset workload profiles (e.g, web navigation, gaming, audio processing, etc.). [Test case] Use linux-lowlatency in a desktop environment and measure responsiveness of interactive applications. [Fix] Enable the following additional .config settings to make this kernel more suitable for a low-latency desktop kernel: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`) - CONFIG_RCU_NOCB_CPU=y, CONFIG_RCU_NOCB_CPU_DEFAULT_ALL=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (can provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/) [Regression potential] Enabling all these settings can introduce a potential performance regression, but the kernel should result more responsive and make it more suitable for a desktop/multimedia/gaming/audio processing context. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2023007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
@mfo revised the debdiffs for F, J and L and uploaded v2s. 1) Done 2.1) Done 2.2) patches cherry-pick -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel()
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
** Patch added: "lp2024479_lunar-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685459/+files/lp2024479_lunar-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm:
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
** Patch added: "lp2024479_jammy-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685458/+files/lp2024479_jammy-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm:
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
** Patch added: "lp2024479_focal-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024479/+attachment/5685457/+files/lp2024479_focal-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm:
[Kernel-packages] [Bug 2026891] [NEW] linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
Public bug reported: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI:
[Kernel-packages] [Bug 2017571] Re: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package
This bug was fixed in the package linux-signed-azure - 6.2.0-1004.4+1 --- linux-signed-azure (6.2.0-1004.4+1) mantic; urgency=medium * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log * SIGNEDv4: add Azure CVM support to the linux-generate ancillary package (LP: #2017571) - [Packaging] Add Azure CVM support to linux-generate - [Packaging] Activate azure-fde build -- Dimitri John Ledkov Wed, 28 Jun 2023 13:27:00 +0100 ** Changed in: linux-signed-azure (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017571 Title: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package Status in linux package in Ubuntu: Triaged Status in linux-signed-azure package in Ubuntu: Fix Released Bug description: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. * Extend package.config inside linux-signed-azure* to add cvm builds * Add linux-meta changes for the above * Drop linux-azure-fde* source kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
This bug is awaiting verification that the linux-
aws-6.2/6.2.0-1007.7~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-aws-6.2 verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-aws-6.2 package in Ubuntu:
Confirmed
Status in linux-azure-6.2 package in Ubuntu:
Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
This bug is awaiting verification that the linux-
azure-6.2/6.2.0-1007.7~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-azure-6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-aws-6.2 package in Ubuntu:
Confirmed
Status in linux-azure-6.2 package in Ubuntu:
Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026883] Re: vector floating point registers get clobbered when running stress-ng --vecfp with more instances than CPUs
It may be worth trying this on real H/W to factor our the QEMU component. ** Description changed: When running the stress-ng vector floating point stressor in QEMU PPC64 virtual machines I get floating point verification errors when running more stressor instances than the number of virtual CPUs. How to reproduce: Create a PPC64 VM in QEMU on a x86 host with 8 virtual CPUs. Login, and then do: get latest stress-ng: sudo apt-get build-dep stress-ng git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ./stress-ng --vecfp 32 --verify -t 10 One should get failures such as: stress-ng: info: [1487] setting to a 10 second run per stressor stress-ng: info: [1487] dispatching hogs: 32 vecfp stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 1078998925312.00, expected 180812.062500 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 46779686912.00, expected 13278722.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 24992688128.00, expected 26213772.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 17185787904.00, expected 39415832.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 157250576.00, expected 33576.261719 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 170314032.00, expected 13129044.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 183516080.00, expected 26348392.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 196647552.00, expected 39365508.00 etc.. However, running less instances than the number of CPUs this runs fine without any errors: /stress-ng --vecfp 1 --verify -t 10 stress-ng: info: [1521] setting to a 10 second run per stressor stress-ng: info: [1521] dispatching hogs: 1 vecfp stress-ng: info: [1521] passed: 1: vecfp (1) stress-ng: info: [1521] failed: 0 stress-ng: info: [1521] skipped: 0 stress-ng: info: [1521] metrics untrustworthy: 0 stress-ng: info: [1521] successful run completed in 19.00s It appears this only fails when the number of instances of the vecfp stressor is more than the number of virtual CPUs. This seems to indicate that vector floating point registers are being clobbered between processes, which could be a security exploitable issue. Reproduced with Ubuntu Lunar PPC64 VM (6.2.0-20-generic) and x86 host - (6.2.0-21-generic + qemu-kvm 1:5.0-5ubuntu6) + (6.2.0-21-generic + qemu-kvm 1:5.0-5ubuntu6). + + List of PPC64el kernels reproducers: + + Lunar: 6.2.0-20-generic + Mantic: 6.3.0-7-generic + Not sure if this is a kernel or KVM issue, or both. ** Information type changed from Public to Private Security ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Mantic) Importance: High Status: New ** Description changed: When running the stress-ng vector floating point stressor in QEMU PPC64 virtual machines I get floating point verification errors when running more stressor instances than the number of virtual CPUs. How to reproduce: Create a PPC64 VM in QEMU on a x86 host with 8 virtual CPUs. Login, and then do: get latest stress-ng: sudo apt-get build-dep stress-ng git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ./stress-ng --vecfp 32 --verify -t 10 One should get failures such as: stress-ng: info: [1487] setting to a 10 second run per stressor stress-ng: info: [1487] dispatching hogs: 32 vecfp stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 1078998925312.00, expected 180812.062500 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 46779686912.00, expected 13278722.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 24992688128.00, expected 26213772.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 17185787904.00, expected 39415832.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 157250576.00, expected 33576.261719 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 170314032.00, expected 13129044.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 183516080.00, expected 26348392.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got
[Kernel-packages] [Bug 2026883] [NEW] vector floating point registers get clobbered when running stress-ng --vecfp with more instances than CPUs
*** This bug is a security vulnerability *** Private security bug reported: When running the stress-ng vector floating point stressor in QEMU PPC64 virtual machines I get floating point verification errors when running more stressor instances than the number of virtual CPUs. How to reproduce: Create a PPC64 VM in QEMU on a x86 host with 8 virtual CPUs. Login, and then do: get latest stress-ng: sudo apt-get build-dep stress-ng git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ./stress-ng --vecfp 32 --verify -t 10 One should get failures such as: stress-ng: info: [1487] setting to a 10 second run per stressor stress-ng: info: [1487] dispatching hogs: 32 vecfp stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 1078998925312.00, expected 180812.062500 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 46779686912.00, expected 13278722.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 24992688128.00, expected 26213772.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 17185787904.00, expected 39415832.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 157250576.00, expected 33576.261719 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 170314032.00, expected 13129044.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 183516080.00, expected 26348392.00 stress-ng: fail: [1488] vecfp: floatv16div float vector operation result mismatch, got 196647552.00, expected 39365508.00 etc.. However, running less instances than the number of CPUs this runs fine without any errors: /stress-ng --vecfp 1 --verify -t 10 stress-ng: info: [1521] setting to a 10 second run per stressor stress-ng: info: [1521] dispatching hogs: 1 vecfp stress-ng: info: [1521] passed: 1: vecfp (1) stress-ng: info: [1521] failed: 0 stress-ng: info: [1521] skipped: 0 stress-ng: info: [1521] metrics untrustworthy: 0 stress-ng: info: [1521] successful run completed in 19.00s It appears this only fails when the number of instances of the vecfp stressor is more than the number of virtual CPUs. This seems to indicate that vector floating point registers are being clobbered between processes, which could be a security exploitable issue. Reproduced with Ubuntu Lunar PPC64 VM (6.2.0-20-generic) and x86 host (6.2.0-21-generic + qemu-kvm 1:5.0-5ubuntu6). List of PPC64el kernels reproducers: Focal: 5.4.0-148-generic Jammy: 5.15.0-58-generic Lunar: 6.2.0-20-generic Mantic: 6.3.0-7-generic Not sure if this is a kernel or KVM issue, or both. ** Affects: linux (Ubuntu) Importance: High Status: New ** Affects: linux (Ubuntu Focal) Importance: High Status: New ** Affects: linux (Ubuntu Lunar) Importance: High Status: New ** Affects: linux (Ubuntu Mantic) Importance: High Status: New ** Also affects: linux (Ubuntu Lunar) 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/2026883 Title: vector floating point registers get clobbered when running stress-ng --vecfp with more instances than CPUs Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Bug description: When running the stress-ng vector floating point stressor in QEMU PPC64 virtual machines I get floating point verification errors when running more stressor instances than the number of virtual CPUs. How to reproduce: Create a PPC64 VM in QEMU on a x86 host with 8 virtual CPUs. Login, and then do: get latest stress-ng: sudo apt-get build-dep stress-ng git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ./stress-ng --vecfp 32 --verify -t 10 One should get failures such as: stress-ng: info: [1487] setting to a 10 second run per stressor stress-ng: info: [1487] dispatching hogs: 32 vecfp stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 1078998925312.00, expected 180812.062500 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 46779686912.00, expected 13278722.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 24992688128.00, expected 26213772.00 stress-ng: fail: [1489] vecfp: floatv64div float vector operation result mismatch, got 17185787904.00, expected 39415832.00 stress-ng: fail: [1488] vecfp: floatv16div float vector
[Kernel-packages] [Bug 1960893] Re: i915 gives trace in dmesg
Another thing i found out that blacklisting snd_hda_core prevents the system from freezing -- 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/1960893 Title: i915 gives trace in dmesg Status in linux package in Ubuntu: Confirmed Bug description: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport dr m ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel: driver_attach+0x1e/0x20 [1.904705] kernel: bus_add_driver+0x135/0x200 [1.904707] kernel: driver_register+0x95/0xf0 [1.904708] kernel: __pci_register_driver+0x68/0x70 [1.904709] kernel: i915_register_pci_driver+0x23/0x30 [i915] [1.904746] kernel: i915_init+0x3b/0xfc [i915] [1.904793] kernel: ? 0xc0cad000 [1.904794] kernel: do_one_initcall+0x46/0x1d0 [1.904797] kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.904800] kernel: do_init_module+0x62/0x280 [1.904801] kernel: load_module+0xac9/0xbb0 [1.904803] kernel: __do_sys_finit_module+0xbf/0x120 [1.904804] kernel: __x64_sys_finit_module+0x18/0x20 [1.904805] kernel: do_syscall_64+0x59/0xc0 [1.904807]
[Kernel-packages] [Bug 1960893] Re: i915 gives trace in dmesg
I experience the same problem on an HP laptop(HP Laptop 15s-fq4xxx/89BC, BIOS F.31 03/25/2023) with a tigerlake CPU. But this one also freezes when a do a reboot. A cold boot always works. The only kernels to work reliably are the liquorix kernels. And they only work after falling back to the intel hda legacy driver in combination with the model dell-headset-multi. This might sound weird but apparently there is some interaction between the audio drivers and the i915 module. Probably has something to do with hdmi and or usb-c audio? I think the problem is a that the bios if just very buggy and needs some workaround to function correctly. One thing i noticed is that the liqourix kernel has hpet en intel_pstate disabled. These had no effects on the default kernel, at least it did not prevent the freezes after a reboot. -- 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/1960893 Title: i915 gives trace in dmesg Status in linux package in Ubuntu: Confirmed Bug description: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport dr m ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel:
[Kernel-packages] [Bug 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
Note that this could be triggered with stress-ng --apparmor 0; see https://bugs.launchpad.net/ubuntu/mantic/+source/linux/+bug/2024599 -- 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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
Thanks JJ, much appreciated :-) -- 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/2024599 Title: linux-image-5.15.0-1032-realtime locks up under scheduler test load Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in apparmor source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in apparmor source package in Kinetic: New Status in linux source package in Kinetic: New Status in apparmor source package in Lunar: New Status in linux source package in Lunar: New Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Incomplete Bug description: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -a Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 24 11:45:03 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux free totalusedfree shared buff/cache available Mem: 4013888 200984 34390121204 373892 3744628 Swap:4014076 0 4014076 Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake, IBRS): how to reproduce issue: git clone https://github.com/ColinIanKing/stress-ng sudo apt-get update sudo apt-get build-dep stress-ng sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev libglvnd-dev libgbm-dev cd stress-ng make clean make -j 8 sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m ..wait for all the stressors to get invoked, system becomes unresponsive, can't ^C stress-ng, can't swap consoles on the VM, appears to be hard locked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026862] [NEW] I/O scheduler kernel modules are not included
Public bug reported: The current inclusion list (https://git.launchpad.net/~canonical- kernel/ubuntu/+source/linux- aws/+git/focal/tree/debian.aws-5.15/control.d/aws.inclusion- list?h=aws-5.15) used to determine what to put inside the package seems to skip the modules built under the block/ directory which includes two I/O schedulers that are built as modules in the current build configuration (CONFIG_MQ_IOSCHED_KYBER=m and CONFIG_IOSCHED_BFQ=m) Could those two modules be included in the distribution or is there a size concern about them? ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2026862 Title: I/O scheduler kernel modules are not included Status in linux-aws package in Ubuntu: New Bug description: The current inclusion list (https://git.launchpad.net/~canonical- kernel/ubuntu/+source/linux- aws/+git/focal/tree/debian.aws-5.15/control.d/aws.inclusion- list?h=aws-5.15) used to determine what to put inside the package seems to skip the modules built under the block/ directory which includes two I/O schedulers that are built as modules in the current build configuration (CONFIG_MQ_IOSCHED_KYBER=m and CONFIG_IOSCHED_BFQ=m) Could those two modules be included in the distribution or is there a size concern about them? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2026862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026863] [NEW] zfs-linux SRU build support against hwe kernels
Public bug reported: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has potential to break userspace * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy * verify existing zsys installs continue to work * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will not land in jammy until after mantic release. Mantic already has much newer 2.2.x series zfs-linux. [ Other Info ] * This is similar to previous zfs-linux SRUs we have performed in the past. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Description changed: [ Impact ] - * hwe kernels keep on changing + * hwe kernels keep on changing - * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 -or 2.2 has potential to break userspace + * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 + or 2.2 has potential to break userspace - * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if + * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. - * the cherry-picks area gainst config/* code (autoconf/m4) and kernel + * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] - * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy - * verify existing zsys installs continue to work - * verify kernel team zfs tests-suites continue to work with v5.15 kernel + * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy + * verify existing zsys installs continue to work + * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] - * majority of diff is in config macros to detect different compatible + * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. - * Note this is still at feature parity with Lunar's upload + * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will - not land in jammy until after mantic release. + not land in jammy until after mantic release. Mantic already has much + newer 2.2.x series zfs-linux. [ Other Info ] - - * This is similar to previous zfs-linux SRUs we have performed in the past. + + * This is similar to previous zfs-linux SRUs we have performed in the + past. -- 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/2026863 Title: zfs-linux SRU build support against hwe kernels Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: New Bug description: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1023.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1023.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1023.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-xilinx- zynqmp/5.15.0-1023.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp -- 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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
Łukasz Zemczak (sil2100) gave me the greenlight to implement the "-latest" solution. You can find the merge proposal here: https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497 -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
** Merge proposal linked: https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497 -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026821] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2026821 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: installation problem ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakti 1914 F wireplumber /dev/snd/seq:shakti 1912 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Tue Jul 11 15:10:15 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-10 (30 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=4fb6c419-cba7-43ff-856c-3adb6810ed18 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 02DYKC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd03/13/2023:br1.23:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn02DYKC:rvrA00:cvnDellInc.:ct10:cvr:sku096A: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.product.sku: 096A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026821] [NEW] package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess
Public bug reported: installation problem ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakti 1914 F wireplumber /dev/snd/seq:shakti 1912 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Tue Jul 11 15:10:15 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-10 (30 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=4fb6c419-cba7-43ff-856c-3adb6810ed18 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 02DYKC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd03/13/2023:br1.23:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn02DYKC:rvrA00:cvnDellInc.:ct10:cvr:sku096A: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.product.sku: 096A dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2026821 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: installation problem ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakti 1914 F wireplumber /dev/snd/seq:shakti 1912 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Tue Jul 11 15:10:15 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-10 (30 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=4fb6c419-cba7-43ff-856c-3adb6810ed18 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1
