[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
I have the same problem on Slackware64 15.0 with 6.7.2 Also see https://gitlab.freedesktop.org/drm/intel/-/issues/4458#note_2273700 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4458 https://gitlab.freedesktop.org/drm/intel/-/issues/4458 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
Hi Roxana, Do We get the kernel source tree link where we can check our included patches for confirmation? -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 2052649] Re: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script post-installation insta
You have an unsupported DKMS module installed. Please remove it:
$ dkms remove nvidia/390.157
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052649
Title:
package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-
headers-6.5.0-17-generic script post-installation installé a renvoyé
un état de sortie d'erreur 1
Status in linux package in Ubuntu:
Invalid
Bug description:
Erreur lors des mises a jour. semble concerner les drivers Nvidia.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nielda 4350 F wireplumber
/dev/snd/controlC1: nielda 4350 F wireplumber
/dev/snd/seq:nielda 4344 F pipewire
CRDA: N/A
CasperMD5CheckMismatches:
./pool/restricted/l/linux-restricted-modules-hwe-6.2/linux-objects-nvidia-470-6.2.0-26-generic_6.2.0-26.26~22.04.1+2_amd64.deb
CasperMD5CheckResult: fail
Date: Wed Feb 7 17:10:23 2024
ErrorMessage: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2024-02-02 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=2a7e435c-f372-4a81-9f6c-eb4d7cd263d0 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: Upgraded to mantic on 2024-02-02 (5 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ET2700I
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/21/2011:br4.6:svnASUSTeKComputerINC.:pnET2700I:pvr0502:rvnASUSTeKComputerINC.:rnET2700I:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuTobefilledbyO.E.M.:
dmi.product.family: Eee Family
dmi.product.name: ET2700I
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0502
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052649/+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 2052649] Re: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script post-installation insta
Error! Bad return status for module build on kernel: 6.5.0-17-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
dkms autoinstall on 6.5.0-17-generic/x86_64 failed for nvidia(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-17-generic
...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
--
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/2052649
Title:
package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-
headers-6.5.0-17-generic script post-installation installé a renvoyé
un état de sortie d'erreur 1
Status in linux package in Ubuntu:
Invalid
Bug description:
Erreur lors des mises a jour. semble concerner les drivers Nvidia.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nielda 4350 F wireplumber
/dev/snd/controlC1: nielda 4350 F wireplumber
/dev/snd/seq:nielda 4344 F pipewire
CRDA: N/A
CasperMD5CheckMismatches:
./pool/restricted/l/linux-restricted-modules-hwe-6.2/linux-objects-nvidia-470-6.2.0-26-generic_6.2.0-26.26~22.04.1+2_amd64.deb
CasperMD5CheckResult: fail
Date: Wed Feb 7 17:10:23 2024
ErrorMessage: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2024-02-02 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=2a7e435c-f372-4a81-9f6c-eb4d7cd263d0 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: Upgraded to mantic on 2024-02-02 (5 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ET2700I
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/21/2011:br4.6:svnASUSTeKComputerINC.:pnET2700I:pvr0502:rvnASUSTeKComputerINC.:rnET2700I:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuTobefilledbyO.E.M.:
dmi.product.family: Eee Family
dmi.product.name: ET2700I
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0502
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052649/+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 2052587] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
Uninstall linux-laptop-tools-common. You should not install any of the
linux-laptop packages unless you're on a Lenovo X13s arm64 laptop.
** This bug has been marked a duplicate of bug 2048183
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
--
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/2052587
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
Status in linux package in Ubuntu:
New
Bug description:
jan@jan-ThinkPad-P1-Gen-6:~/work/mariadb/10.11/mysql-test$ sudo apt-get
install linux-tools-6.5.0-14-generic linux-cloud-tools-6.5.0-14-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-cloud-tools-6.5.0-14-generic is already the newest version
(6.5.0-14.14).
The following additional packages will be installed:
hwdata linux-tools-6.5.0-14 linux-tools-common
The following NEW packages will be installed:
hwdata linux-tools-6.5.0-14 linux-tools-6.5.0-14-generic linux-tools-common
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 452 kB/8.591 kB of archives.
After this operation, 28,6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ly.archive.ubuntu.com/ubuntu mantic-updates/main amd64
linux-tools-common all 6.5.0-15.15 [452 kB]
Fetched 452 kB in 1s (859 kB/s)
Selecting previously unselected package hwdata.
(Reading database ... 536450 files and directories currently installed.)
Preparing to unpack .../hwdata_0.374-1_all.deb ...
Unpacking hwdata (0.374-1) ...
Preparing to unpack .../linux-tools-common_6.5.0-15.15_all.deb ...
Unpacking linux-tools-common (6.5.0-15.15) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package linux-tools-6.5.0-14.
Preparing to unpack .../linux-tools-6.5.0-14_6.5.0-14.14_amd64.deb ...
Unpacking linux-tools-6.5.0-14 (6.5.0-14.14) ...
Selecting previously unselected package linux-tools-6.5.0-14-generic.
Preparing to unpack .../linux-tools-6.5.0-14-generic_6.5.0-14.14_amd64.deb ...
Unpacking linux-tools-6.5.0-14-generic (6.5.0-14.14) ...
Errors were encountered while processing:
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
jan@jan-ThinkPad-P1-Gen-6:~/work/mariadb/10.11/mysql-test$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
hwdata:amd64: Install
linux-tools-common:amd64: Install
linux-tools-6.5.0-14:amd64: Install
linux-tools-6.5.0-14-generic:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CRDA: N/A
CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img
./boot/grub/grub.cfg ./casper/initrd
CasperMD5CheckResult: fail
Date: Wed Feb 7 08:46:38 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sutton-jammy-amd64-20230811-498
DuplicateSignature:
package:linux-tools-common:(not installed)
Unpacking linux-tools-common (6.5.0-15.15) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in
package linux-laptop-tools-common 6.5.0-1006.9
InstallationDate: Installed on 2023-08-11 (180 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-sutton-jammy-amd64-20230811-498
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=1e33d8c0-26a1-4a48-930e-5fe39eff7474 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
[Kernel-packages] [Bug 2046345] Re: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation s
Might be related? On first attempt in the updater GUI in Ubuntu 23.10 (latest STS stable version), I got linux-image-nvidia-6.5.0-17-generic: constructing .ko files ./BUILD: 10: make: not found ./BUILD: 11: make: not found ./BUILD: 12: make: not found ./BUILD: 13: make: not found ./BUILD: 14: make: not found nvidia-drm.ko: OK nvidia-modeset.ko: OK nvidia-peermem.ko: OK nvidia-uvm.ko: OK nvidia.ko: OK So apparently that worked OK, but it still seemed strange, so I installed build-essentials and did apt install --reinstall linux- modules-nvidia-535-6.5.0-17-generic and got: (error messages translate to the same "no such file or directory" and "no rule to make target... stop.)" linux-image-nvidia-6.5.0-17-generic: constructing .ko files make: arch/x86/Makefile.postlink: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um „arch/x86/Makefile.postlink“ zu erstellen. Schluss. make: arch/x86/Makefile.postlink: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um „arch/x86/Makefile.postlink“ zu erstellen. Schluss. make: arch/x86/Makefile.postlink: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um „arch/x86/Makefile.postlink“ zu erstellen. Schluss. make: arch/x86/Makefile.postlink: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um „arch/x86/Makefile.postlink“ zu erstellen. Schluss. make: arch/x86/Makefile.postlink: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um „arch/x86/Makefile.postlink“ zu erstellen. Schluss. nvidia-drm.ko: OK nvidia-modeset.ko: OK nvidia-peermem.ko: OK nvidia-uvm.ko: OK nvidia.ko: OK [..] I have not rebooted yet to check if my nvidia driver still works, but since it says "OK" I guess I should be fine. -- 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/2046345 Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Occurs when upgrading to an unreleased version Setting up linux-modules-nvidia-535-6.5.0-9-generic (6.5.0-9.9) ... linux-image-nvidia-6.5.0-9-generic: constructing .ko files make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-peermem.ko: OK nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match dpkg: error processing package linux-modules-nvidia-535-6.5.0-9-generic (--configure): installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-modules-nvidia-535-generic-hwe-22.04: linux-modules-nvidia-535-generic-hwe-22.04 depends on linux-modules-nvidia-535-6.5.0-9-generic (= 6.5.0-9.9); however: Package linux-modules-nvidia-535-6.5.0-9-generic is not configured yet. dpkg: error processing package linux-modules-nvidia-535-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-modules-nvidia-530-generic-hwe-22.04: linux-modules-nvidia-530-generic-hwe-22.04 depends on linux-modules-nvidia-535-generic-hwe-22.04; however: Package linux-modules-nvidia-535-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-modules-nvidia-530-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-modules-nvidia-535-6.5.0-9-generic linux-modules-nvidia-535-generic-hwe-22.04 linux-modules-nvidia-530-generic-hwe-22.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 14:36:34 2023 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess
[Kernel-packages] [Bug 2052677] [NEW] PATCH for 24.04 | Corrected memory error propagation in the Linux stack
Private bug reported: This below patch needs to be part of the Ubuntu 24.04 and other OS versions which supports Intel Sierra Forrest and Granite Rapids Server Processors. When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does not clear the status word of the BIOS supplied error record for corrected errors. This may prevent logging of subsequent uncorrected errors. Link to the patch: https://lore.kernel.org/all/20240122235819.177989...@linuxfoundation.org/ 1. What is this patch about? This is about the corrected memory error propagation the Linux stack 2. Why is this patch required? What issue does it fix? When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does not clear the status word of the BIOS supplied error record for corrected errors. This may prevent logging of subsequent uncorrected errors. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Description changed: - PATCH for 24.04 | Corrected memory error propagation in the Linux stack + This below patch needs to be part of the Ubuntu 24.04 and other OS + versions which supports Intel Sierra Forrest and Granite Rapids Server + Processors. + + When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does + not clear the status word of the BIOS supplied error record for + corrected errors. This may prevent logging of subsequent uncorrected + errors. + + Link to the patch: + https://lore.kernel.org/all/20240122235819.177989...@linuxfoundation.org/ + + 1. What is this patch about? + This is about the corrected memory error propagation the Linux stack + + 2. Why is this patch required? What issue does it fix? + When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does not clear the status word of the BIOS supplied error record for corrected errors. This may prevent logging of subsequent uncorrected errors. -- 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/2052677 Title: PATCH for 24.04 | Corrected memory error propagation in the Linux stack Status in linux package in Ubuntu: New Bug description: This below patch needs to be part of the Ubuntu 24.04 and other OS versions which supports Intel Sierra Forrest and Granite Rapids Server Processors. When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does not clear the status word of the BIOS supplied error record for corrected errors. This may prevent logging of subsequent uncorrected errors. Link to the patch: https://lore.kernel.org/all/20240122235819.177989...@linuxfoundation.org/ 1. What is this patch about? This is about the corrected memory error propagation the Linux stack 2. Why is this patch required? What issue does it fix? When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does not clear the status word of the BIOS supplied error record for corrected errors. This may prevent logging of subsequent uncorrected errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.15/5.15.0.1056.64~20.04.45)
All autopkgtests for the newly accepted linux-meta-azure-5.15 (5.15.0.1056.64~20.04.45) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.23 (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/focal/update_excuses.html#linux-meta-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing 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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
This bug is awaiting verification that the linux- hwe-6.5/6.5.0-18.18~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-linux- hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'. 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-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5 -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 2052676] Re: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC
** Attachment added: "Information from 6.2.0.33 kernel" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+attachment/5745180/+files/output-6.2.0-33-generic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052676 Title: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+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 2052676] Re: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC
** Attachment added: "Information from 6.5.0.17 kernel" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+attachment/5745179/+files/output-6.5.0-17-generic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052676 Title: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+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 2052676] [NEW] Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC
Public bug reported: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052676 Title: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+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 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5
Hi Andrea,
I'm having some trouble with this bug, particularly on jammy-hwe.
You see, is_rust_module.sh seems to have returned again.
I see you removed it in 4f2dbd4037a697c6d96eb3d8867253e2c8d6f8d0 (ubuntu-mantic)
but if you look at 0eec6d2a63d86ac94dc8fa7c56820a0972ccbe1f (ubuntu-mantic),
right at the bottom, it has been re-added again.
It was then moved around in 6ab0eb19936ebc2a85f911b098bde6c885a28f54
(ubuntu-mantic).
I'm trying to build a 6.5.0-15-generic on Jammy HWE, and its there too, both
in debian.master/reconstruct and debian.hwe-6.5/reconstruct.
Could you please take another look at this?
Thanks!
Matthew
--
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/2038611
Title:
drop all references to is_rust_module.sh in kernels >= 6.5
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a reference of it in debian.master/reconstruct and
that generates the following warning during the build:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or
directory
[Fix]
Drop the reference to is_rust_module.sh from reconstruct to prevent
unnecessary warnings during the build.
[Test case]
The following command ran from the kernel source directory is enough
to trigger the warning:
$ fakeroot debian/rules clean
[Regression potential]
This change is affecting only our packaging. The change is trivial but
it might affect our kernel build process in case of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Do we have any updates when we will see this released for Ubuntu 22.04?
We are seeing an increase in inquires.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake
Integrated laptop screen is now detected and functions since upgrading to kernel and hwe 6.5.0-17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2050103 Title: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake Status in linux-hwe-6.5 package in Ubuntu: New Bug description: lsb_release Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy Laptop: Rebadged Clevo Graphics: on-board Intel UHD 630 Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic Problem:- LCD laptop screen not detected on kernel 6.5.0-14 The laptop LCD screen is black but the external RGB monitor works fine. Using kernel 6.2.0-39, both the LCD and external monitor work. inxi -Gxx on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is the LCD Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e9b Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 5986:2110 Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1 compositor: gnome-shell v: 42.9 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: i915 display-ID: 0 Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19") Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3") OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes inxi -Gxx on 6.5 kernel shows 1 Monitor - DP-1 is the external Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e9b Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 5986:2110 Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1 compositor: gnome-shell v: 42.9 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: i915 display-ID: 0 Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19") OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes This line using journalctl is in the boot log of kernel 6.2 but not in the boot log of 6.5(probably not relevant) Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping intel_backlight registration Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is against nvidia graphics but will try 1024x768 resolution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+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 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
I identified a similar bug today when installing nvidia- fabricmanager-535 on a noble dev build for arm64 that may be related: https://bugs.launchpad.net/ubuntu/+source/fabric- manager-535/+bug/2052663 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Confirmed Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954] x26: 00056d1d76c8 x25: c87cf18bdd10 x24: 0003 [ 384.007527] x23: 0001 x22: 00056d1d76c8 x21:
[Kernel-packages] [Bug 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320
Changed status to 'Fix Released' as multiple reports have been made that this issue no longer occurs on kernel 6.5.0-17-generic. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048935 Title: Right speaker broken on Dell XPS 13 Plus 9320 Status in linux-meta-hwe-6.5 package in Ubuntu: Fix Released Bug description: After upgrading from the previous HWE kernel 6.2.0-39-generic to the new HWE kernel 6.5.0-14-generic, the right speaker no longer works. When booting back into the old HWE kernel, the right speaker functions again. The left speaker works in both cases. Hardware info: Dell XPS 13 Plus 9320 with Intel i7 1260P Software info: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package info: apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.14.14~22.04.7 Candidate: 6.5.0.14.14~22.04.7 Version table: *** 6.5.0.14.14~22.04.7 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages lspci output on kernel 6.5.0-14-generic: ``` 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) Subsystem: Dell Device 0af3 Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15 Memory at 603e1d (64-bit, non-prefetchable) [size=16K] Memory at 603e00 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) Subsystem: Dell Device 0af3 Flags: medium devsel, IRQ 16, IOMMU group 15 Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] ``` aplay -l output on kernel 6.5.0-14-generic: ``` List of PLAYBACK Hardware Devices card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 21:40:02 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-06-25 (563 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1056.52)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1056.52) for jammy have finished running. The following regressions have been reported in tests triggered by the package: digimend-dkms/10-4 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
** Summary changed: - smb1: wsize blocks of bytes followed with binary zeros on copy, destroying data + smb: wsize blocks of bytes followed with binary zeros on copy, destroying data -- 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/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb 1.0 mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, etc. An example of a broken file is: https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt [Where problems could occur] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+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 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320
Confirming that this is also fixed for me in 6.5.0-17-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048935 Title: Right speaker broken on Dell XPS 13 Plus 9320 Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading from the previous HWE kernel 6.2.0-39-generic to the new HWE kernel 6.5.0-14-generic, the right speaker no longer works. When booting back into the old HWE kernel, the right speaker functions again. The left speaker works in both cases. Hardware info: Dell XPS 13 Plus 9320 with Intel i7 1260P Software info: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package info: apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.14.14~22.04.7 Candidate: 6.5.0.14.14~22.04.7 Version table: *** 6.5.0.14.14~22.04.7 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages lspci output on kernel 6.5.0-14-generic: ``` 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) Subsystem: Dell Device 0af3 Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15 Memory at 603e1d (64-bit, non-prefetchable) [size=16K] Memory at 603e00 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) Subsystem: Dell Device 0af3 Flags: medium devsel, IRQ 16, IOMMU group 15 Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] ``` aplay -l output on kernel 6.5.0-14-generic: ``` List of PLAYBACK Hardware Devices card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 21:40:02 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-06-25 (563 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+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 2048701] Re: [i915] Screen freeze, kernel crash
AFAIKT this bug is resolved in 6.5.0-17-generic, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048701 Title: [i915] Screen freeze, kernel crash Status in linux-hwe-6.5 package in Ubuntu: New Bug description: After updating from 23.04 to 23.10 Screen freezes on boot. Booting with 23.04 kernel 6.2.0-36 still works. After getting 6.5.11-060511 from kernel ppa it works fine. From journal of failed X: jan 08 22:14:06 chromium kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] applying backlight present quirk jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] [ENCODER:76:DDI A/PHY A] HPD is down, disabling eDP jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] *ERROR* crtc 45: Can't calculate constants, dotclock = 0! jan 08 22:14:06 chromium kernel: [ cut here ] jan 08 22:14:06 chromium kernel: i915 :00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) jan 08 22:14:06 chromium kernel: WARNING: CPU: 1 PID: 101 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+> jan 08 22:14:06 chromium kernel: Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper cec polyval> jan 08 22:14:06 chromium kernel: CPU: 1 PID: 101 Comm: (udev-worker) Not tainted 6.5.0-14-generic #14-Ubuntu jan 08 22:14:06 chromium kernel: Hardware name: Acer Peppy, BIOS 03/02/2017 jan 08 22:14:06 chromium kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 df 49 68 e4 48 c7 c1 48 b5 71 c0 48 89 da 48 c7 c7 50 e3 71 c0 48 89 > jan 08 22:14:06 chromium kernel: RSP: 0018:a231804c3658 EFLAGS: 00010046 jan 08 22:14:06 chromium kernel: RAX: RBX: 933d80c7be30 RCX: jan 08 22:14:06 chromium kernel: RDX: RSI: RDI: jan 08 22:14:06 chromium kernel: RBP: a231804c36c8 R08: R09: jan 08 22:14:06 chromium kernel: R10: R11: R12: jan 08 22:14:06 chromium kernel: R13: 933d8b6f04a8 R14: a231804c36ec R15: 053f jan 08 22:14:06 chromium kernel: FS: 7fed1ae408c0() GS:933df8b0() knlGS: jan 08 22:14:06 chromium kernel: CS: 0010 DS: ES: CR0: 80050033 jan 08 22:14:06 chromium kernel: CR2: 56204b159120 CR3: 00010027c004 CR4: 000706e0 jan 08 22:14:06 chromium kernel: Call Trace: jan 08 22:14:06 chromium kernel: jan 08 22:14:06 chromium kernel: ? show_regs+0x6d/0x80 jan 08 22:14:06 chromium kernel: ? __warn+0x89/0x160 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? report_bug+0x17e/0x1b0 jan 08 22:14:06 chromium kernel: ? handle_bug+0x51/0xa0 jan 08 22:14:06 chromium kernel: ? exc_invalid_op+0x18/0x80 jan 08 22:14:06 chromium kernel: ? asm_exc_invalid_op+0x1b/0x20 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? _raw_spin_lock_irqsave+0xe/0x20 jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: drm_crtc_get_last_vbltimestamp+0x56/0x90 [drm] jan 08 22:14:06 chromium kernel: drm_reset_vblank_timestamp+0x73/0x100 [drm] jan 08 22:14:06 chromium kernel: drm_crtc_vblank_on+0xa9/0x1a0 [drm] jan 08 22:14:06 chromium kernel: ? assert_vblank_disabled+0x1d/0xd0 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_vblank_on+0x34/0x90 [i915] jan 08 22:14:06 chromium kernel: intel_modeset_setup_hw_state+0x1ea/0x540 [i915] jan 08 22:14:06 chromium kernel: ? drm_modeset_lock_all_ctx+0x99/0x1d0 [drm] jan 08 22:14:06 chromium kernel: ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0xa0 [drm] jan 08 22:14:06 chromium kernel: intel_display_driver_probe_nogem+0x186/0x250 [i915] jan 08 22:14:06 chromium kernel: i915_driver_probe+0x315/0x5b0 [i915] jan 08 22:14:06 chromium kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] jan 08 22:14:06 chromium kernel: ? acpi_dev_found+0x64/0x80 jan 08 22:14:06 chromium kernel: i915_pci_probe+0xd0/0x170 [i915] jan 08 22:14:06 chromium kernel: local_pci_probe+0x44/0xb0 jan 08 22:14:06 chromium kernel: pci_call_probe+0x55/0x190
[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? ** Changed in: linux (Ubuntu) Status: Confirmed => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045386] Re: Add ODM driver gpio-m058ssan
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045387] Re: Add ODM driver f81604 usb-can
Hi, we are using the generic kernel. Are linux-bluefield/5.15.0-1035.37 linux-raspi/5.15.0-1046.49 linux-azure/5.15.0-1056.64 relevant in our case? -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2052663] Re: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052663
Title:
fabric-manager-535 setup fails during install on Grace/Hopper arm64
system running noble
Status in fabric-manager-535 package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
New
Bug description:
This error occurs on both the standard and largemem variants of the latest
Noble server build of Ubuntu:
Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic-64k
aarch64) (iso link:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207.1/noble-live-server-arm64+largemem.iso)
Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic aarch64)
(iso link:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207/noble-live-server-arm64.iso)
CPU/GPU: Nvidia Grace/Hopper
lsb_release -rd:
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
Kernel versions affected:
GNU/Linux 6.6.0-14-generic-64k aarch64
GNU/Linux 6.6.0-14-generic aarch64
Package version: nvidia-fabricmanager-535 (535.154.05-0ubuntu1 arm64)
Expected behavior: Package starts as expected during post-install
setup steps
Actual behavior:
On our grace/hopper system running noble, when installing
nvidia-fabricmanager-535, the installation froze at 60% twice, along with all
ssh processes. I am also unable to ssh back into the system after this happens.
This is the last output I see from my installer shell:
+ apt install -y nvidia-fabricmanager-535
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
nvidia-fabricmanager-535
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 1795 kB of archives.
After this operation, 8679 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports noble/multiverse arm64
nvidia-fabricmanager-535 arm64 535.154.05-0ubuntu1 [1795 kB]
Fetched 1795 kB in 1s (2439 kB/s)
Selecting previously unselected package nvidia-fabricmanager-535.
(Reading database ... 103745 files and directories currently installed.)
Preparing to unpack
.../nvidia-fabricmanager-535_535.154.05-0ubuntu1_arm64.deb ...
Unpacking nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
Setting up nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/nvidia-fabricmanager.service →
/lib/systemd/system/nvidia-fabricmanager.service.
Progress: [ 60%]
[#...]
This does not appear to cause a panic/reboot, as I can still interact with
the console, and it even appears that the apt process is still running in ps
aux (although it doesn't seem to progress). However, I observe the following
output in the console that I believe may be related:
[ 1453.814597] watchdog: BUG: soft lockup - CPU#16 stuck for 670s!
[(udev-worker):33269]
[ 1477.814602] watchdog: BUG: soft lockup - CPU#16 stuck for 693s!
[(udev-worker):33269]
[ 1501.814606] watchdog: BUG: soft lockup - CPU#16 stuck for 715s!
[(udev-worker):33269]
[ 1525.814611] watchdog: BUG: soft lockup - CPU#16 stuck for 738s!
[(udev-worker):33269]
[ 1579.666718] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 17-...D } 240893 ji
ffies s: 653 root: 0x2/.
[ 1579.678114] rcu: blocking rcu_node structures (internal RCU debug):
l=1:15-29:0x4/.
[ 1597.814625] watchdog: BUG: soft lockup - CPU#16 stuck for 805s!
[(udev-worker):33269]
[ 1621.814630] watchdog: BUG: soft lockup - CPU#16 stuck for 827s!
[(udev-worker):33269]
[ 1630.562655] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 1630.568973] rcu: 17-...0: (1 GPs behind) idle=2444/1/0x4000
softirq=13696/13700 f
qs=126842
[ 1630.578665] rcu:hardirqs softirqs csw/system
[ 1630.584381] rcu:number:0 00
[ 1630.590109] rcu: cputime:0 00 ==>
1110384(ms)
[ 1630.597458] rcu: (detected by 20, t=285099 jiffies, g=74061, q=113266
ncpus=72)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2052663/+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 2052662] [NEW] move_mount mediation does not detect if source is detached
Public bug reported: Impact: In AppArmor mediation, detached mounts are appearing as / when applying mount mediation, which is incorrect and leads to bad AppArmor policy being generated. In addition, the move_mount mediation is not being advertised to userspace, which denies the applications the possibility to respond accordingly. Fix: Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44 by preventing move_mont from applying the attach_disconnected flag. Testcase: Check if move_mount file is available in securityfs: $ cat /sys/kernel/security/apparmor/features/mount/move_mount detached Run upstream AppArmor mount tests, which include move_mount mediation. https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052662 Title: move_mount mediation does not detect if source is detached Status in linux package in Ubuntu: New Bug description: Impact: In AppArmor mediation, detached mounts are appearing as / when applying mount mediation, which is incorrect and leads to bad AppArmor policy being generated. In addition, the move_mount mediation is not being advertised to userspace, which denies the applications the possibility to respond accordingly. Fix: Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44 by preventing move_mont from applying the attach_disconnected flag. Testcase: Check if move_mount file is available in securityfs: $ cat /sys/kernel/security/apparmor/features/mount/move_mount detached Run upstream AppArmor mount tests, which include move_mount mediation. https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052662/+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 2049195] Re: Wifi missing after upgrade to 6.5 kernel
Affecting my Lenovo P15(20YQ-003WUS) also. Very similar errors logged by the kernel.(available if you need them) 09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) 09:00.0 0280: 8086:2725 (rev 1a) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+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 2049195] Re: Wifi missing after upgrade to 6.5 kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+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 2049993] Re: tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum segment size
after turning OFF all HW features of the LANIC. only CRC calculation remains in the LANIC. I have not seen the effect in wireshark again. I assume the LANIC was adding TCP segments together. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049993 Title: tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum segment size Status in linux-hwe-6.5 package in Ubuntu: New Bug description: a wireshark trace will follow. filter for "ip.len>1500" in the wireshark trace ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 21 08:41:18 2024 Dependencies: InstallationDate: Installed on 2022-05-31 (599 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049993/+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
Issue confirmed on 5.4.0-170. ** Attachment added: "20240207_103433.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5745140/+files/20240207_103433.jpg -- 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 2049242] Re: CIFS Mounts Keep Load Average at n+1
Same with Linux 6.5.0-17-generic kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049242 Title: CIFS Mounts Keep Load Average at n+1 Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Today I noticed that my two primary Ubuntu boxes were running at high load. After investigation, I discovered at that unmounting their CIFS shares alleviating the high load. I rebooted to the previous kernel, linux-modules-6.2.0-39-generic, and saw that the load was low after everything had settled after startup. I rebooted to the current kernel, linux-modules-6.5.0-14-generic, and again saw the high load. The load appears to be n+1, where n is the number of CIFS mounts. (Based on a sample of two boxes.) I confirmed that the default mount options (e.g. the ones not specified in fstab) are the same between the two kernels. This *might* also be slowing down external (USB disk access. I'm still investigating that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 19:47:25 2024 InstallationDate: Installed on 2020-10-01 (1198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-01-01 (376 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049242/+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 2049242] Re: CIFS Mounts Keep Load Average at n+1
I experienced the same behaviour on Operating System: Ubuntu 23.10 Kernel: Linux 6.5.0-15-generic Architecture: x86-64 (Intel N100 4CPU) And the following mount options: ///paperless /share/smb/paperless cifs credentials=/root/.smbcredentials,multichannel,iocharset=utf8 0 0 9 cifs mounts in total with the same options and a totally idle system goes from 0 to 10 Load average Nfs mounts are not producing this bug, it's strictly cifs related. Before mounts: cat /proc/loadavg 0.00 0.26 3.15 1/244 203137 After mounts: cat /proc/loadavg 9.99 7.37 5.39 1/252 203256 That said all other metrics cpu/io/memory... are totally fine, just a calculation bug I suppose. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049242 Title: CIFS Mounts Keep Load Average at n+1 Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Today I noticed that my two primary Ubuntu boxes were running at high load. After investigation, I discovered at that unmounting their CIFS shares alleviating the high load. I rebooted to the previous kernel, linux-modules-6.2.0-39-generic, and saw that the load was low after everything had settled after startup. I rebooted to the current kernel, linux-modules-6.5.0-14-generic, and again saw the high load. The load appears to be n+1, where n is the number of CIFS mounts. (Based on a sample of two boxes.) I confirmed that the default mount options (e.g. the ones not specified in fstab) are the same between the two kernels. This *might* also be slowing down external (USB disk access. I'm still investigating that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 19:47:25 2024 InstallationDate: Installed on 2020-10-01 (1198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-01-01 (376 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049242/+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 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320
Fixed for me with new kernel Ubuntu 22.04 Linux XPS-9320 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048935 Title: Right speaker broken on Dell XPS 13 Plus 9320 Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading from the previous HWE kernel 6.2.0-39-generic to the new HWE kernel 6.5.0-14-generic, the right speaker no longer works. When booting back into the old HWE kernel, the right speaker functions again. The left speaker works in both cases. Hardware info: Dell XPS 13 Plus 9320 with Intel i7 1260P Software info: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package info: apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.14.14~22.04.7 Candidate: 6.5.0.14.14~22.04.7 Version table: *** 6.5.0.14.14~22.04.7 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages lspci output on kernel 6.5.0-14-generic: ``` 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) Subsystem: Dell Device 0af3 Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15 Memory at 603e1d (64-bit, non-prefetchable) [size=16K] Memory at 603e00 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) Subsystem: Dell Device 0af3 Flags: medium devsel, IRQ 16, IOMMU group 15 Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] ``` aplay -l output on kernel 6.5.0-14-generic: ``` List of PLAYBACK Hardware Devices card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 21:40:02 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-06-25 (563 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+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 2052452] Re: External displays go white after a display sleep
After more research (including getting different symptoms with kernel 6.8-rc3), this appears to be the amdgpu scatter/gather bug: https://community.frame.work/t/responded-screen-flashing-partially- white-on-framework-13-amd-ubuntu-22-04/40626/2 I've applied the `amdgpu.sg_display=0` kernel command line workaround and will report back. -- 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/2052452 Title: External displays go white after a display sleep Status in linux package in Ubuntu: New Bug description: After letting the displays timeout and go to sleep, external displays have a white layer between the windows and the mouse. It's still possible to interact with the windows below this layer, but it's not possible to see what's happening without moving them to a display that doesn't have this glitch. This occurs in both x11 and wayland sessions, and it's new on noble (didn't see it on mantic, including with the backports ppa). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: kwin-wayland 4:5.27.10-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Feb 5 11:41:37 2024 InstallationDate: Installed on 2023-10-23 (106 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: kwin UpgradeStatus: Upgraded to noble on 2024-01-26 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052452/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
This is s390x-specific only and does not affect gcp. Hence I'm adjusting the tag to potentially unblock the process. ** Tags added: verification-done -- 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/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It also included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which is necessary to activate this kernel feature. For lunar and mantic, the kernel code did not
[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
** Tags added: verification-done -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
This is s390x specific only and does not impact gcp. -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2052452] Re: External displays go white after a display sleep
Attached: a photograph of the displays after exiting display sleep but before unlocking. If it's relevant, the affected display is attached to the front right port of an AMD Framework laptop (USB 3.2 gen 2) using a device recognised by lsusb as `Bus 001 Device 002: ID 0bda:5442 Realtek Semiconductor Corp. Cable Matters USB-C Video Cable` This display seems to be more often affected than the one attached to my docking station. However, disconnecting it and moving it to the rear left port (USB 4) does not fix the issue. ** Attachment added: "Example of screen issue" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052452/+attachment/5745134/+files/PXL_20240207_165756203.jpg -- 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/2052452 Title: External displays go white after a display sleep Status in linux package in Ubuntu: New Bug description: After letting the displays timeout and go to sleep, external displays have a white layer between the windows and the mouse. It's still possible to interact with the windows below this layer, but it's not possible to see what's happening without moving them to a display that doesn't have this glitch. This occurs in both x11 and wayland sessions, and it's new on noble (didn't see it on mantic, including with the backports ppa). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: kwin-wayland 4:5.27.10-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Feb 5 11:41:37 2024 InstallationDate: Installed on 2023-10-23 (106 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: kwin UpgradeStatus: Upgraded to noble on 2024-01-26 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052452/+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 2052452] Re: External displays go white after a display sleep
This occurred after a fresh reboot this morning, after letting my displays go to sleep for ~5 minutes. dmesg log also attached. The IO_PAGE_FAULT entries begin shortly after moving my mouse to turn the displays back on. ** Attachment added: "dmesg log after getting this issue." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052452/+attachment/5745123/+files/dmesg.log -- 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/2052452 Title: External displays go white after a display sleep Status in linux package in Ubuntu: New Bug description: After letting the displays timeout and go to sleep, external displays have a white layer between the windows and the mouse. It's still possible to interact with the windows below this layer, but it's not possible to see what's happening without moving them to a display that doesn't have this glitch. This occurs in both x11 and wayland sessions, and it's new on noble (didn't see it on mantic, including with the backports ppa). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: kwin-wayland 4:5.27.10-0ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Feb 5 11:41:37 2024 InstallationDate: Installed on 2023-10-23 (106 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: kwin UpgradeStatus: Upgraded to noble on 2024-01-26 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052452/+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 2051184] Re: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051184 Title: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: Boot testing fails for b/gcp-5.4 on new c3a-standard instance as below: Causes WARNING at: arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148 [0.060607] WARNING: CPU: 3 PID: 29 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060612] WARNING: CPU: 2 PID: 23 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060613] Modules linked in: [0.060615] Modules linked in: [0.060621] CPU: 3 PID: 29 Comm: migration/3 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060622] CPU: 2 PID: 23 Comm: migration/2 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060628] WARNING: CPU: 1 PID: 17 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060629] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060630] Modules linked in: [0.060632] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060635] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060636] CPU: 1 PID: 17 Comm: migration/1 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060637] sp : 80001012bce0 [0.060639] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060639] x29: 80001012bce0 x28: 0002 [0.060642] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060645] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060646] x27: 80001003bd10 [0.060647] sp : 8000100fbce0 [0.060647] x26: [0.060648] x29: 8000100fbce0 [0.060650] x28: 0002 [0.060652] x25: 0060 [0.060653] x24: [0.060655] x27: 80001003bd10 x26: [0.060657] x23: 0001 [0.060661] x22: dca01ea9a3c0 [0.060663] x25: 0060 x24: [0.060665] x21: dca01dda4970 [0.060668] x20: 0001 [0.060669] x23: 0001 x22: dca01ea9a3c0 [0.060671] x19: dca01ecca000 [0.060675] x18: dca01dc56a10 [0.060680] x21: dca01dda4970 x20: 0001 [0.060684] x17: bc8dcec3 [0.060687] x16: b1e1b9b5 [0.060688] x19: dca01ecca000 x18: dca01dc56a10 [0.060694] x17: 7e50fa5f [0.060694] x15: 0001 [0.060695] x16: 9cd7320e [0.060696] x14: 74e6bd9c01c8 [0.060699] x13: 0004 [0.060701] x15: 0001 [0.060702] x12: 0228 [0.060703] x14: 74e6bd99f1c8 [0.060705] x11: [0.060711] x13: 0004 [0.060712] x10: 0b00 [0.060713] x12: 0228 [0.060716] x11: [0.060722] x9 : 80001012bd20 [0.060723] x10: 0b00 [0.060724] x8 : 74e6ba3c66e0 [0.060726] x7 : x6 : dca01d822000 [0.060727] x9 : 8000100fbd20 [0.060729] x8 : 74e6ba33a9e0 [0.060729] x5 : c00fac30 [0.060730] x4 : [0.060731] x7 : [0.060734] x6 : dca01d822000 [0.060735] x3 : 000b [0.060736] x2 : dca01ecca508 [0.060738] x5 : c00fac30 x4 : [0.060740] x1 : 000b [0.060742] x0 : 000b [0.060746] x3 : 000b x2 : dca01ecca508 [0.060749] Call trace: [0.060751] x1 : 000b [0.060753] spectre_bhb_enable_mitigation+0x148/0x228 [0.060755] x0 : 000b [0.060757] cpu_enable_non_boot_scope_capabilities+0x6c/0xa8 [0.060761] multi_cpu_stop+0xac/0x188 [0.060762] Call trace: [0.060763] cpu_stopper_thread+0xe4/0x1a0 [0.060766] spectre_bhb_enable_mitigation+0x148/0x228 [0.060769] smpboot_thread_fn+0x1a8/0x1d8 [0.060771] cpu_enable_non_boot_scope_capabilities+0x6c/0xa8 [0.060773] kthread+0x114/0x118 [0.060775] multi_cpu_stop+0xac/0x188 [0.060778] ret_from_fork+0x10/0x18 [0.060779] cpu_stopper_thread+0xe4/0x1a0 [0.060780] ---[ end trace 82b1638f0eea221b ]---
[Kernel-packages] [Bug 2051184] Re: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance
>From LP: #2052632 log_check/kernel_tainted tests will fail on AmpereOne based machines like c3a-standard-4 for focal:linux 5.4.0-168.186 and newer. The warning was introduced with upstream commit f41cab7a4653 arm64: Add AMPERE1 to the Spectre-BHB affected list that came with upstream stable release v5.4.253 as part of Ubuntu-5.4.0-168.186: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038652 Looking at the code, this warning will always be issued on AMPERE1 based machines but Spectre-BHB mitigation should be guaranteed regardless. The warning is issued because there is no case for loop iteration count 11 necessary for AMPERE1 CPUs in spectre_bhb_enable_mitigation(). -- 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/2051184 Title: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: Boot testing fails for b/gcp-5.4 on new c3a-standard instance as below: Causes WARNING at: arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148 [0.060607] WARNING: CPU: 3 PID: 29 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060612] WARNING: CPU: 2 PID: 23 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060613] Modules linked in: [0.060615] Modules linked in: [0.060621] CPU: 3 PID: 29 Comm: migration/3 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060622] CPU: 2 PID: 23 Comm: migration/2 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060628] WARNING: CPU: 1 PID: 17 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060629] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060630] Modules linked in: [0.060632] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060635] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060636] CPU: 1 PID: 17 Comm: migration/1 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060637] sp : 80001012bce0 [0.060639] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060639] x29: 80001012bce0 x28: 0002 [0.060642] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060645] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060646] x27: 80001003bd10 [0.060647] sp : 8000100fbce0 [0.060647] x26: [0.060648] x29: 8000100fbce0 [0.060650] x28: 0002 [0.060652] x25: 0060 [0.060653] x24: [0.060655] x27: 80001003bd10 x26: [0.060657] x23: 0001 [0.060661] x22: dca01ea9a3c0 [0.060663] x25: 0060 x24: [0.060665] x21: dca01dda4970 [0.060668] x20: 0001 [0.060669] x23: 0001 x22: dca01ea9a3c0 [0.060671] x19: dca01ecca000 [0.060675] x18: dca01dc56a10 [0.060680] x21: dca01dda4970 x20: 0001 [0.060684] x17: bc8dcec3 [0.060687] x16: b1e1b9b5 [0.060688] x19: dca01ecca000 x18: dca01dc56a10 [0.060694] x17: 7e50fa5f [0.060694] x15: 0001 [0.060695] x16: 9cd7320e [0.060696] x14: 74e6bd9c01c8 [0.060699] x13: 0004 [0.060701] x15: 0001 [0.060702] x12: 0228 [0.060703] x14: 74e6bd99f1c8 [0.060705] x11: [0.060711] x13: 0004 [0.060712] x10: 0b00 [0.060713] x12: 0228 [0.060716] x11: [0.060722] x9 : 80001012bd20 [0.060723] x10: 0b00 [0.060724] x8 : 74e6ba3c66e0 [0.060726] x7 : x6 : dca01d822000 [0.060727] x9 : 8000100fbd20 [0.060729] x8 : 74e6ba33a9e0 [0.060729] x5 : c00fac30 [0.060730] x4 : [0.060731] x7 : [0.060734] x6 : dca01d822000 [0.060735] x3 : 000b [0.060736] x2 : dca01ecca508 [0.060738] x5 : c00fac30 x4 : [0.060740] x1 : 000b [0.060742] x0 : 000b [0.060746] x3 : 000b x2 : dca01ecca508 [0.060749] Call trace: [0.060751] x1 : 000b [0.060753] spectre_bhb_enable_mitigation+0x148/0x228 [0.060755] x0 : 000b [0.060757]
[Kernel-packages] [Bug 2052649] [NEW] package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script post-installation ins
Public bug reported:
Erreur lors des mises a jour. semble concerner les drivers Nvidia.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nielda 4350 F wireplumber
/dev/snd/controlC1: nielda 4350 F wireplumber
/dev/snd/seq:nielda 4344 F pipewire
CRDA: N/A
CasperMD5CheckMismatches:
./pool/restricted/l/linux-restricted-modules-hwe-6.2/linux-objects-nvidia-470-6.2.0-26-generic_6.2.0-26.26~22.04.1+2_amd64.deb
CasperMD5CheckResult: fail
Date: Wed Feb 7 17:10:23 2024
ErrorMessage: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2024-02-02 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=2a7e435c-f372-4a81-9f6c-eb4d7cd263d0 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: Upgraded to mantic on 2024-02-02 (5 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ET2700I
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/21/2011:br4.6:svnASUSTeKComputerINC.:pnET2700I:pvr0502:rvnASUSTeKComputerINC.:rnET2700I:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuTobefilledbyO.E.M.:
dmi.product.family: Eee Family
dmi.product.name: ET2700I
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0502
dmi.sys.vendor: ASUSTeK Computer INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package 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/2052649
Title:
package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-
headers-6.5.0-17-generic script post-installation installé a renvoyé
un état de sortie d'erreur 1
Status in linux package in Ubuntu:
New
Bug description:
Erreur lors des mises a jour. semble concerner les drivers Nvidia.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nielda 4350 F wireplumber
/dev/snd/controlC1: nielda 4350 F wireplumber
/dev/snd/seq:nielda 4344 F pipewire
CRDA: N/A
CasperMD5CheckMismatches:
./pool/restricted/l/linux-restricted-modules-hwe-6.2/linux-objects-nvidia-470-6.2.0-26-generic_6.2.0-26.26~22.04.1+2_amd64.deb
CasperMD5CheckResult: fail
Date: Wed Feb 7 17:10:23 2024
ErrorMessage: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2024-02-02 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=2a7e435c-f372-4a81-9f6c-eb4d7cd263d0 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17 failed to
install/upgrade: le sous-processus paquet linux-headers-6.5.0-17-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: Upgraded to mantic on 2024-02-02 (5 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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 2052453] Re: Azure: Fix regression introduced in LP: #2045069
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+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 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.
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-v2
verification-needed-jammy-linux-azure
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
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 Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046105 Title: Sound: Add rtl quirk of M90-Gen5 Status in HWE Next: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: 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-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 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 Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: 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 Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2041842] Re: Kernel doesn't compile with CONFIG_IMA
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2041842 Title: Kernel doesn't compile with CONFIG_IMA Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Because of typo error in function declaration kernel doesn't compile with specific configuration Steps to reproduce: make defconfig ./scripts/config --file .config \ -d SECURITY_SELINUX \ -e IMA make olddefconfig grep -E "CONFIG_IMA=|CONFIG_IMA_LSM_RULES" .config make bzImage Grep should return "CONFIG_IMA=y" but not "CONFIG_IMA_LSM_RULES=y" Error: In file included from security/integrity/ima/ima_fs.c:25: security/integrity/ima/ima.h:440:41: error: unknown type name 'strcut'; did you mean 'struct'? 440 | static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 field, u32 op, | ^~ | struct make[3]: *** [scripts/Makefile.build:297: security/integrity/ima/ima_fs.o] Error 1 make[2]: *** [scripts/Makefile.build:560: security/integrity/ima] Error 2 make[1]: *** [scripts/Makefile.build:560: security/integrity] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041842/+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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.
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-v2
verification-needed-jammy-linux-azure
--
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/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2044192] Re: Patches needed for AmpereOne (arm64)
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.
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-v2
verification-needed-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Status in linux-gcp source package in Jammy:
Fix Released
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: 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-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 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 Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Lunar, $ git push l_cbd Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 8 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm remote: * 9/9 workers busy, 0 builds queued remote: 2023-11-20 16:00:11
[Kernel-packages] [Bug 2046217] Re: Some machines can't pass the pm-graph test
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046217 Title: Some machines can't pass the pm-graph test Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux-hwe-6.5 source package in Jammy: Fix Released Status in linux-signed-hwe-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Fix Released Status in linux-hwe-6.5 source package in Mantic: New Status in linux-signed-hwe-6.5 source package in Mantic: New Status in linux source package in Noble: Confirmed Status in linux-hwe-6.5 source package in Noble: New Status in linux-signed-hwe-6.5 source package in Noble: In Progress Bug description: == SRU Justification == [Impact] When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system resume, NULL pointer dereference occurs and the system stops working. [Fix] Rescan the bus in order to reprobe the device to avoid mac80211 layer gets messed up. [Test] With the fix in place, system keeps working after firmware issue occurs. Verified with thousand times of suspend. [Where problems could occur] If the firmware/hardware is really dead and beyond recoverable, the same process can be triggered again and again. == Original bug report == During the jammy-hwe migration test, I found some machines failed to run the pm-graph. test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604) One of machine when I rerun it locally, it passed, but others are still failed. Following are the machines failed to run pm-graph. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201702-25401/ https://certification.canonical.com/hardware/202002-27718/ https://certification.canonical.com/hardware/201711-25989/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Tue Dec 12 02:48:24 2023 InstallationDate: Installed on 2023-02-22 (293 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046217/+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 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2045562 Title: [Debian] autoreconstruct - Do not generate chmod -x for deleted files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: 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 Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A [Fix] Generate chmod commands first. And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. [Test Plan] It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. [Other Info] An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
This bug was fixed in the package nvidia-graphics-drivers-545 - 545.29.06-0ubuntu5 --- nvidia-graphics-drivers-545 (545.29.06-0ubuntu5) noble; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch, debian/dkms_nvidia/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch: - Fix build with Linux 6.8 (LP: #2052420) -- Paolo Pisati Mon, 05 Feb 2024 08:33:36 + ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2045385] Re: Add ODM driver rtc-pcf85263
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2047630] Re: Add quirk to disable i915 fastboot on B PC
This bug is awaiting verification that the linux-azure/5.15.0-1056.64 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-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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-v2 verification-needed-jammy-linux-azure -- 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/2047630 Title: Add quirk to disable i915 fastboot on B PC Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some displays connect to the B PC device got the garbled display [Fix] The issue will disappear after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, but these patches cannot be backported from 5.19 to 5.15. So add quirk to force disable the i915 fastboot on the device to fix the abnormal display [Test Case] 1. Connect the display and power on the B PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
l-f landed in noble
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
l-f landed in noble ** Changed in: linux-firmware (Ubuntu Noble) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2046534] Re: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114 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-focal-linux-raspi' to 'verification-done-focal- linux-raspi'. If the problem still exists, change the tag 'verification- needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'. 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-focal-linux-raspi-v2 verification-needed-focal-linux-raspi -- 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/2046534 Title: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration Status in linux package in Ubuntu: New Status in linux source package in Focal: Fix Released Bug description: [Impact] When a page fault is triggered in RDMA ODP, it registers an MMU notifier during the process. Unfortunately, an error arises due to a race condition where the mm is released while attempting to register a notifier. == Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at mm/mmu_notifier.c:255! Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 EFLAGS: 00010246 Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: a0f913ba5800 RCX: Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: c0b601c7 RDI: a0f913ba5850 Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX: RBX: c0b5a060 RCX: Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: a1152ed3c400 RDI: a1102dcd4300 Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: a1163f4f50e0 R09: a11638c072c0 Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: R12: a1152c923b80 Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: a1163f7350e0 R09: a11638c072c0 Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: R12: a1102dcd4300 Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: a1152c923bf8 R15: a114f8127800 Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS: () GS:a1163f4c() knlGS: Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: a1152ed3c478 R15: a1101cbfbc00 Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS: () GS:a1163f70() knlGS: Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS: 0010 DS: ES: CR0: 80050033 Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 001722472004 CR4: 00760ee0 Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS: 0010 DS: ES: CR0: 80050033 Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 001f9f1fc004 CR4: 00760ee0 Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0: DR1: DR2: Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3: DR6: fffe07f0 DR7: 0400 Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0: DR1: DR2: Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554 Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace: Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3: DR6: fffe07f0 DR7: 0400 Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554 Oct 14 23:38:32 bnode001 kernel: [1576115.923112] mmu_notifier_get_locked+0x5f/0xe0 Oct 14 23:38:32 bnode001 kernel: [1576115.923867] Call Trace: Oct 14 23:38:32 bnode001 kernel: [1576115.923870] ? mmu_notifier_get_locked+0x79/0xe0 Oct 14 23:38:32 bnode001 kernel: [1576115.924645] ib_umem_odp_alloc_child+0x15a/0x290 [ib_core] Oct 14 23:38:32 bnode001 kernel: [1576115.925409] ib_umem_odp_alloc_child+0x15a/0x290 [ib_core] Oct 14 23:38:32 bnode001 kernel: [1576115.926161] pagefault_mr+0x312/0x5d0 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.926906] pagefault_mr+0x312/0x5d0 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.927651] pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.928393] pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib] Oct 14 23:38:32
[Kernel-packages] [Bug 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.223.02-0ubuntu2 --- nvidia-graphics-drivers-470 (470.223.02-0ubuntu2) noble; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch, debian/dkms_nvidia/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch: - Fix build with Linux 6.8 (LP: #2052420) -- Paolo Pisati Mon, 05 Feb 2024 08:33:36 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114 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-focal-linux-raspi' to 'verification-done-focal- linux-raspi'. If the problem still exists, change the tag 'verification- needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'. 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-focal-linux-raspi-v2 verification-needed-focal-linux-raspi -- 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/2045562 Title: [Debian] autoreconstruct - Do not generate chmod -x for deleted files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: 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 Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A [Fix] Generate chmod commands first. And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. [Test Plan] It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. [Other Info] An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2052637] [NEW] [i386] please add 550-server to the i386 seed
Public bug reported: Please add the following packages to i386 seed: - nvidia-graphics-drivers-550-server The other one: - nvidia-graphics-drivers-550 is already included. such that beta driver can be packaged and built for i386. ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Description changed: Please add the following packages to i386 seed: - - nvidia-graphics-drivers-550 - nvidia-graphics-drivers-550-server + The other one: + + - nvidia-graphics-drivers-550 is already included. + + such that beta driver can be packaged and built for i386. ** Summary changed: - [i386] please add 550 & 550-server to the i386 seed + [i386] please add 550-server to the i386 seed ** Package changed: nvidia-graphics-drivers-545 (Ubuntu) => nvidia- graphics-drivers-535-server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2052637 Title: [i386] please add 550-server to the i386 seed Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Please add the following packages to i386 seed: - nvidia-graphics-drivers-550-server The other one: - nvidia-graphics-drivers-550 is already included. such that beta driver can be packaged and built for i386. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2052637/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
linux-oem-22.04d 6.5.0.1013.15 in jammy-updates contains the fix.
https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-
oem-6.5/linux-oem-6.5_6.5.0-1013.14/changelog
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Confirmed
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
X-HWE-Bug: Bug #2047389
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2045573] Re: AMDGPU: cp queue preemption timeout
*** This bug is a duplicate of bug 2047389 *** https://bugs.launchpad.net/bugs/2047389 linux-oem-22.04d 6.5.0.1013.15 in jammy-updates contains the fix. https://changelogs.ubuntu.com/changelogs/pool/main/l/linux- oem-6.5/linux-oem-6.5_6.5.0-1013.14/changelog -- 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/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: Fix Released Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached X-HWE-Bug: Bug #2047389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114 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-focal-linux-raspi' to 'verification-done-focal- linux-raspi'. If the problem still exists, change the tag 'verification- needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'. 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-focal-linux-raspi-v2 verification-needed-focal-linux-raspi -- 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/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
kernel 6.5.0-17-generic has just arrived in 23.10 (Mantic) and that
seems to clear the issue.
mount/unmount an external btrfs filesystem no longer produces the
messages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114 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-focal-linux-raspi' to 'verification-done-focal- linux-raspi'. If the problem still exists, change the tag 'verification- needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'. 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-focal-linux-raspi-v2 verification-needed-focal-linux-raspi -- 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/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: 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 Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.
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-raspi-v2
verification-needed-jammy-linux-raspi
--
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/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
This bug was fixed in the package linux - 5.4.0-171.189 --- linux (5.4.0-171.189) focal; urgency=medium * focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282) * Packaging resync (LP: #1786013) - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration (LP: #2046534) - RDMA/odp: Ensure the mm is still alive before creating an implicit child * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 (LP: #2032641) - selftests: Skip TM tests on synthetic TM implementations * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-45863 - kobject: Fix slab-out-of-bounds in fill_kobj_path() * Focal update: v5.4.259 upstream stable release (LP: #2043724) - RDMA/cxgb4: Check skb value for failure to allocate - lib/test_meminit: fix off-by-one error in test_pages() - pwm: hibvt: Explicitly set .polarity in .get_state() - HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect - quota: Fix slow quotaoff - net: prevent address rewrite in kernel_bind() - drm: etvnaviv: fix bad backport leading to warning - drm/msm/dsi: skip the wait for video mode done if not applicable - ravb: Fix up dma_free_coherent() call in ravb_remove() - ieee802154: ca8210: Fix a potential UAF in ca8210_probe - mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type - xen-netback: use default TX queue size for vifs - drm/vmwgfx: fix typo of sizeof argument - ixgbe: fix crash with empty VF macvlan list - net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() - nfc: nci: assert requested protocol is valid - workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() - dmaengine: stm32-mdma: abort resume if no ongoing transfer - usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer - net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read - usb: dwc3: Soft reset phy on probe for host - usb: musb: Get the musb_qh poniter after musb_giveback - usb: musb: Modify the "HWVers" register address - iio: pressure: bmp280: Fix NULL pointer exception - iio: pressure: dps310: Adjust Timeout Settings - iio: pressure: ms5611: ms5611_prom_is_valid false negative bug - mcb: remove is_added flag from mcb_device struct - libceph: use kernel_connect() - ceph: fix incorrect revoked caps assert in ceph_fill_file_size() - Input: powermate - fix use-after-free in powermate_config_complete - Input: psmouse - fix fast_reconnect function for PS/2 mode - Input: xpad - add PXN V900 support - cgroup: Remove duplicates in cgroup v1 tasks file - pinctrl: avoid unsafe code pattern in find_pinctrl() - usb: gadget: udc-xilinx: replace memcpy with memcpy_toio - usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call - x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs - dmaengine: mediatek: Fix deadlock caused by synchronize_irq() - powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE - powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() - ravb: Fix use-after-free issue in ravb_tx_timeout_work() - Documentation: sysctl: align cells in second content column - usb: hub: Guard against accesses to uninitialized BOS descriptors - Bluetooth: hci_event: Ignore NULL link key - Bluetooth: Reject connection with the device which has same BD_ADDR - Bluetooth: Fix a refcnt underflow problem for hci_conn - Bluetooth: vhci: Fix race when opening vhci device - Bluetooth: hci_event: Fix coding style - Bluetooth: avoid memcmp() out of bounds warning - ice: fix over-shifted variable - nfc: nci: fix possible NULL pointer dereference in send_acknowledge() - regmap: fix NULL deref on lookup - KVM: x86: Mask LVTPC when handling a PMI - netfilter: nft_payload: fix wrong mac header matching - qed: fix LL2 RX buffer allocation - xfrm: fix a data-race in xfrm_gen_index() - xfrm: interface: use DEV_STATS_INC() - net: ipv4: fix return value check in esp_remove_trailer - net: ipv6: fix
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.
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-bluefield-v2
verification-needed-jammy-linux-bluefield
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
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 Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 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-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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 2052631] [NEW] Jammy update: v6.1.77 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.77 upstream stable release from git://git.kernel.org/ Linux 6.1.77 drm/amdgpu: Fix missing error code in 'gmc_v6/7/8/9_0_hw_init()' ASoC: codecs: wsa883x: fix PA volume control ASoC: codecs: lpass-wsa-macro: fix compander volume hack bonding: remove print in bond_verify_device_path gve: Fix use-after-free vulnerability LoongArch/smp: Call rcutree_report_cpu_starting() at tlb_init() drm/msm/dsi: Enable runtime PM Revert "drm/amd/display: Disable PSR-SU on Parade 0803 TCON again" mm, kmsan: fix infinite recursion due to RCU critical section arm64: irq: set the correct node for shadow call stack selftests: bonding: Check initial state selftests: team: Add missing config options net: sysfs: Fix /sys/class/net/ path selftests: net: fix available tunnels detection af_unix: fix lockdep positive in sk_diag_dump_icons() net: ipv4: fix a memleak in ip_setup_cork netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations netfilter: nf_log: replace BUG_ON by WARN_ON_ONCE when putting logger netfilter: nf_tables: restrict tunnel object to NFPROTO_NETDEV netfilter: conntrack: correct window scaling with retransmitted SYN selftests: net: add missing config for GENEVE bridge: mcast: fix disabled snooping after long uptime llc: call sock_orphan() at release time ipv6: Ensure natural alignment of const ipv6 loopback and router addresses net: dsa: qca8k: fix illegal usage of GPIO ixgbe: Fix an error handling path in ixgbe_read_iosf_sb_reg_x550() ixgbe: Refactor overtemp event handling ixgbe: Refactor returning internal error codes tcp: add sanity checks to rx zerocopy net: lan966x: Fix port configuration when using SGMII interface ipmr: fix kernel panic when forwarding mcast packets ipv4: raw: add drop reasons ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() selftests: net: give more time for GRO aggregation HID: hidraw: fix a problem of memory leak in hidraw_release() scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler regulator: ti-abb: don't use devm_platform_ioremap_resource_byname for shared interrupt register scsi: isci: Fix an error code problem in isci_io_request_build() drm: using mul_u32_u32() requires linux/math64.h wifi: cfg80211: fix RCU dereference in __cfg80211_bss_update perf: Fix the nr_addr_filters fix drm/amdkfd: Fix 'node' NULL check in 'svm_range_get_range_boundaries()' drm/amdgpu: Release 'adev->pm.fw' before return in 'amdgpu_device_need_post()' drm/amdgpu: Fix with right return code '-EIO' in 'amdgpu_gmc_vram_checking()' drm/amd/powerplay: Fix kzalloc parameter 'ATOM_Tonga_PPM_Table' in 'get_platform_power_management_table()' ceph: fix invalid pointer access if get_quota_realm return ERR_PTR ceph: fix deadlock or deadcode of misusing dget() ceph: reinitialize mds feature bit even when session in open blk-mq: fix IO hang from sbitmap wakeup race virtio_net: Fix "‘%d’ directive writing between 1 and 11 bytes into a region of size 10" warnings drm/amdkfd: Fix lock dependency warning with srcu drm/amdkfd: Fix lock dependency warning libsubcmd: Fix memory leak in uniq() misc: lis3lv02d_i2c: Add missing setting of the reg_ctrl callback 9p: Fix initialisation of netfs_inode for 9p PCI/AER: Decode Requester ID when no error info found PCI: Fix 64GT/s effective data rate calculation spmi: mediatek: Fix UAF on device remove fs/kernfs/dir: obey S_ISGID tty: allow TIOCSLCKTRMIOS with CAP_CHECKPOINT_RESTORE selftests/sgx: Fix linker script asserts usb: hub: Add quirk to decrease IN-ep poll interval for Microchip USB491x hub usb: hub: Replace hardcoded quirk value with BIT() macro perf cs-etm: Bump minimum OpenCSD version to ensure a bugfix is present PCI: switchtec: Fix stdev_release() crash after surprise hot remove PCI: Only override AMD USB controller if required mailbox: arm_mhuv2: Fix a bug for mhuv2_sender_interrupt mfd: ti_am335x_tscadc: Fix TI SoC dependencies xen/gntdev: Fix the abuse of underlying struct page in DMA-buf import i3c: master: cdns: Update maximum prescaler value for i2c clock um: time-travel: fix time corruption um: net: Fix return type of uml_net_start_xmit() um: Don't use vfprintf() for os_info() um: Fix naming clash between UML and scheduler leds: trigger: panic: Don't register panic notifier if creating the trigger failed ALSA: hda/conexant: Fix headset auto detect fail in cx8070 and SN6140 drm/amdkfd: Fix iterator used outside loop in 'kfd_add_peer_prop()' drm/amdgpu: Drop 'fence' check in 'to_amdgpu_amdkfd_fence()'
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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 2047908] Re: Jammy update: v6.1.66 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2047908 Title: Jammy update: v6.1.66 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.66 upstream stable release from git://git.kernel.org/ Linux 6.1.66 iomap: update ki_pos a little later in iomap_dio_complete x86/apic/msi: Fix misconfigured non-maskable MSI quirk x86/xen: fix percpu vcpu_info allocation xen: simplify evtchn_do_upcall() call maze xen: Allow platform PCI interrupt to be shared r8169: fix deadlock on RTL8125 in jumbo mtu mode r8169: disable ASPM in case of tx timeout drm/amd/display: Fix MPCC 1DLUT programming drm/amd/display: Fix the delta clamping for shaper LUT drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut drm/amd/display: Expand kernel doc for DC mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled mmc: core: add helpers mmc_regulator_enable/disable_vqmmc drm/amd/pm: fix a memleak in aldebaran_tables_init iommu/vt-d: Make context clearing consistent with context mapping iommu/vt-d: Disable PCI ATS in legacy passthrough mode iommu/vt-d: Add device_block_translation() helper iommu/vt-d: Allocate pasid table in device probe path iommu/vt-d: Omit devTLB invalidation requests when TES=0 cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily cpufreq: imx6q: don't warn for disabling a non-existing frequency drm/amd/display: Guard against invalid RPTR/WPTR being set drm/amd/display: Restore rptr/wptr for DMCUB as workaround spi: Fix null dereference on suspend fbdev: stifb: Make the STI next font pointer a 32-bit signed offset PCI: qcom-ep: Add dedicated callback for writing to DBI2 registers octeontx2-af: Initialize 'cntr_val' to fix uninitialized symbol error PCI: Lengthen reset delay for VideoPropulsion Torrent QN16e card KVM: x86: Fix lapic timer interrupt lost after loading a snapshot. net: ravb: Keep reverse order of operations in ravb_remove() net: ravb: Stop DMA in case of failures on ravb_open() net: ravb: Start TX queues after HW initialization succeeded net: ravb: Make write access to CXR35 first before accessing other EMAC registers net: ravb: Use pm_runtime_resume_and_get() net: ravb: Check return value of reset_control_deassert() ravb: Fix races between ravb_tx_timeout_work() and net related ops r8169: prevent potential deadlock in rtl8169_close octeontx2-pf: Restore TC ingress police rules when interface is up octeontx2-af: Install TC filter rules in hardware based on priority octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64 net: stmmac: xgmac: Disable FPE MMC interrupts octeontx2-af: Fix possible buffer overflow selftests/net: mptcp: fix uninitialized variable warnings selftests/net: unix: fix unused variable compiler warning selftests/net: fix a char signedness issue selftests/net: ipsec: fix constant out of range uapi: propagate __struct_group() attributes to the container union dpaa2-eth: increase the needed headroom to account for alignment ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet usb: config: fix iteration issue in 'usb_get_bos_descriptor()' USB: core: Change configuration warnings to notices USB: xhci-plat: fix legacy PHY double init wifi: cfg80211: fix CQM for non-range use serial: sc16is7xx: add missing support for rs485 devicetree properties serial: sc16is7xx: Put IOControl register into regmap_volatile auxdisplay: hd44780: move cursor home after clear display command Input: xpad - add HyperX Clutch Gladiate Support btrfs: fix 64bit compat send ioctl arguments not initializing version member btrfs: make error messages more clear when getting a chunk map btrfs: send: ensure send_fd is
[Kernel-packages] [Bug 2046577] Re: Jammy update: v6.1.63 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2046577 Title: Jammy update: v6.1.63 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.63 upstream stable release from git://git.kernel.org/ Linux 6.1.63 virtio/vsock: fix header length on skb merging virtio/vsock: Fix uninit-value in virtio_transport_recv_pkt() virtio/vsock: fix leaks due to missing skb owner vsock/loopback: use only sk_buff_head.lock to protect the packet queue virtio/vsock: don't drop skbuff on copy failure virtio/vsock: remove redundant 'skb_pull()' call virtio/vsock: don't use skbuff state to account credit wifi: cfg80211: fix kernel-doc for wiphy_delayed_work_flush() btrfs: use u64 for buffer sizes in the tree search ioctls Revert "mmc: core: Capture correct oemid-bits for eMMC cards" x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs io_uring/net: ensure socket is marked connected on connect retry tracing/kprobes: Fix the order of argument descriptions fbdev: fsl-diu-fb: mark wr_reg_wa() static fbdev: imsttfb: fix a resource leak in probe fbdev: imsttfb: Fix error path of imsttfb_probe() spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies ASoC: dapm: fix clock get name ASoC: hdmi-codec: register hpd callback on component probe ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: trivial: fix error messages drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE RISC-V: Don't fail in riscv_of_parent_hartid() for disabled HARTs netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses netfilter: nft_redir: use `struct nf_nat_range2` throughout and deduplicate eval call-backs netfilter: xt_recent: fix (increase) ipv6 literal buffer length i2c: iproc: handle invalid slave state r8169: respect userspace disabling IFF_MULTICAST vsock/virtio: remove socket from connected/bound list on shutdown virtio/vsock: replace virtio_vsock_pkt with sk_buff blk-core: use pr_warn_ratelimited() in bio_check_ro() nbd: fix uaf in nbd_open tg3: power down device only on SYSTEM_POWER_OFF nvme: fix error-handling for io_uring nvme-passthrough net/smc: put sk reference if close work was canceled net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT octeontx2-pf: Free pending and dropped SQEs octeontx2-pf: qos send queues management octeontx2-pf: Rename tot_tx_queues to non_qos_queues selftests: pmtu.sh: fix result checking net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs Fix termination state for idr_for_each_entry_ul() net: r8169: Disable multicast filter for RTL8168H and RTL8107E dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses. dccp: Call security_inet_conn_request() after setting IPv4 addresses. net: page_pool: add missing free_percpu when page_pool_init fail octeontx2-pf: Fix holes in error code octeontx2-pf: Fix error codes inet: shrink struct flowi_common bpf: Check map->usercnt after timer->timer is assigned tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING hsr: Prevent use after free in prp_create_tagged_frame() llc: verify mac len before reading mac header watchdog: ixp4xx: Make sure restart always works Input: synaptics-rmi4 - fix use after free in rmi_unregister_function() pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume pwm: sti: Reduce number of allocations and drop usage of chip_data regmap: prevent noinc writes from clobbering cache media: cec: meson: always include meson sub-directory in Makefile media: dvb-usb-v2: af9035: fix missing unlock media: cadence: csi2rx: Unregister v4l2 async notifier media: cedrus: Fix
[Kernel-packages] [Bug 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug was fixed in the package linux - 5.4.0-171.189 --- linux (5.4.0-171.189) focal; urgency=medium * focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282) * Packaging resync (LP: #1786013) - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration (LP: #2046534) - RDMA/odp: Ensure the mm is still alive before creating an implicit child * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 (LP: #2032641) - selftests: Skip TM tests on synthetic TM implementations * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-45863 - kobject: Fix slab-out-of-bounds in fill_kobj_path() * Focal update: v5.4.259 upstream stable release (LP: #2043724) - RDMA/cxgb4: Check skb value for failure to allocate - lib/test_meminit: fix off-by-one error in test_pages() - pwm: hibvt: Explicitly set .polarity in .get_state() - HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect - quota: Fix slow quotaoff - net: prevent address rewrite in kernel_bind() - drm: etvnaviv: fix bad backport leading to warning - drm/msm/dsi: skip the wait for video mode done if not applicable - ravb: Fix up dma_free_coherent() call in ravb_remove() - ieee802154: ca8210: Fix a potential UAF in ca8210_probe - mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type - xen-netback: use default TX queue size for vifs - drm/vmwgfx: fix typo of sizeof argument - ixgbe: fix crash with empty VF macvlan list - net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() - nfc: nci: assert requested protocol is valid - workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() - dmaengine: stm32-mdma: abort resume if no ongoing transfer - usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer - net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read - usb: dwc3: Soft reset phy on probe for host - usb: musb: Get the musb_qh poniter after musb_giveback - usb: musb: Modify the "HWVers" register address - iio: pressure: bmp280: Fix NULL pointer exception - iio: pressure: dps310: Adjust Timeout Settings - iio: pressure: ms5611: ms5611_prom_is_valid false negative bug - mcb: remove is_added flag from mcb_device struct - libceph: use kernel_connect() - ceph: fix incorrect revoked caps assert in ceph_fill_file_size() - Input: powermate - fix use-after-free in powermate_config_complete - Input: psmouse - fix fast_reconnect function for PS/2 mode - Input: xpad - add PXN V900 support - cgroup: Remove duplicates in cgroup v1 tasks file - pinctrl: avoid unsafe code pattern in find_pinctrl() - usb: gadget: udc-xilinx: replace memcpy with memcpy_toio - usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call - x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs - dmaengine: mediatek: Fix deadlock caused by synchronize_irq() - powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE - powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() - ravb: Fix use-after-free issue in ravb_tx_timeout_work() - Documentation: sysctl: align cells in second content column - usb: hub: Guard against accesses to uninitialized BOS descriptors - Bluetooth: hci_event: Ignore NULL link key - Bluetooth: Reject connection with the device which has same BD_ADDR - Bluetooth: Fix a refcnt underflow problem for hci_conn - Bluetooth: vhci: Fix race when opening vhci device - Bluetooth: hci_event: Fix coding style - Bluetooth: avoid memcmp() out of bounds warning - ice: fix over-shifted variable - nfc: nci: fix possible NULL pointer dereference in send_acknowledge() - regmap: fix NULL deref on lookup - KVM: x86: Mask LVTPC when handling a PMI - netfilter: nft_payload: fix wrong mac header matching - qed: fix LL2 RX buffer allocation - xfrm: fix a data-race in xfrm_gen_index() - xfrm: interface: use DEV_STATS_INC() - net: ipv4: fix return value check in esp_remove_trailer - net: ipv6: fix
[Kernel-packages] [Bug 2048230] Re: Jammy update: v6.1.69 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2048230 Title: Jammy update: v6.1.69 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.69 upstream stable release from git://git.kernel.org/ Linux 6.1.69 r8152: fix the autosuspend doesn't work r8152: remove rtl_vendor_mode function r8152: avoid to change cfg for all devices net: tls, update curr on splice as well ring-buffer: Have rb_time_cmpxchg() set the msb counter too ring-buffer: Do not try to put back write_stamp ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs ring-buffer: Fix writing to the buffer with max_data_size ring-buffer: Have saved event hold the entire event ring-buffer: Do not update before stamp when switching sub-buffers tracing: Update snapshot buffer on resize if it is allocated ring-buffer: Fix memory leak of free page smb: client: fix OOB in smb2_query_reparse_point() smb: client: fix NULL deref in asn1_ber_decoder() smb: client: fix OOB in receive_encrypted_standard() drm/i915: Fix remapped stride with CCS on ADL+ drm/amd/display: Disable PSR-SU on Parade 0803 TCON again drm/amdgpu: fix tear down order in amdgpu_vm_pt_free btrfs: don't clear qgroup reserved bit in release_folio btrfs: free qgroup reserve when ORDERED_IOERR is set mm/shmem: fix race in shmem_undo_range w/THP mm/mglru: fix underprotected page cache dmaengine: stm32-dma: avoid bitfield overflow assertion drm/amdgpu/sdma5.2: add begin/end_use ring callbacks team: Fix use-after-free when an option instance allocation fails arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS soundwire: stream: fix NULL pointer dereference for multi_link btrfs: do not allow non subvolume root targets for snapshot perf: Fix perf_event_validate_size() lockdep splat HID: hid-asus: add const to read-only outgoing usb buffer arm64: add dependency between vmlinuz.efi and Image net: usb: qmi_wwan: claim interface 4 for ZTE MF290 asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad HID: hid-asus: reset the backlight brightness level on resume nbd: pass nbd_sock to nbd_read_reply() instead of index HID: add ALWAYS_POLL quirk for Apple kb HID: glorious: fix Glorious Model I HID report platform/x86: intel_telemetry: Fix kernel doc descriptions LoongArch: Implement constant timer shutdown interface LoongArch: Add dependency between vmlinuz.efi and vmlinux.efi selftests/bpf: fix bpf_loop_bench for new callback verification scheme nvme: catch errors from nvme_configure_metadata() nvme-auth: set explanation code for failure2 msgs nbd: fold nbd config initialization into nbd_alloc_config() bcache: avoid NULL checking to c->root in run_cache_set() bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: remove redundant assignment to variable cur_idx bcache: avoid oversize memory allocation by small stripe_size blk-cgroup: bypass blkcg_deactivate_policy after destroying blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" stmmac: dwmac-loongson: Add architecture dependency usb: aqc111: check packet for fixup for true limit x86/hyperv: Fix the detection of E820_TYPE_PRAM in a Gen2 VM drm/mediatek: Add spinlock for setting vblank event in atomic_begin ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE PCI: loongson: Limit MRRS to 256 Revert "PCI: acpiphp: Reassign resources on bridge if necessary" ALSA: hda/realtek: Apply mute LED quirk for HP15-db ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/hdmi: add
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2045385] Re: Add ODM driver rtc-pcf85263
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2046217] Re: Some machines can't pass the pm-graph test
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046217 Title: Some machines can't pass the pm-graph test Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux-hwe-6.5 source package in Jammy: Fix Released Status in linux-signed-hwe-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Fix Released Status in linux-hwe-6.5 source package in Mantic: New Status in linux-signed-hwe-6.5 source package in Mantic: New Status in linux source package in Noble: Confirmed Status in linux-hwe-6.5 source package in Noble: New Status in linux-signed-hwe-6.5 source package in Noble: In Progress Bug description: == SRU Justification == [Impact] When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system resume, NULL pointer dereference occurs and the system stops working. [Fix] Rescan the bus in order to reprobe the device to avoid mac80211 layer gets messed up. [Test] With the fix in place, system keeps working after firmware issue occurs. Verified with thousand times of suspend. [Where problems could occur] If the firmware/hardware is really dead and beyond recoverable, the same process can be triggered again and again. == Original bug report == During the jammy-hwe migration test, I found some machines failed to run the pm-graph. test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604) One of machine when I rerun it locally, it passed, but others are still failed. Following are the machines failed to run pm-graph. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201702-25401/ https://certification.canonical.com/hardware/202002-27718/ https://certification.canonical.com/hardware/201711-25989/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Tue Dec 12 02:48:24 2023 InstallationDate: Installed on 2023-02-22 (293 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046217/+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 2045387] Re: Add ODM driver f81604 usb-can
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2043724] Re: Focal update: v5.4.259 upstream stable release
This bug was fixed in the package linux - 5.4.0-171.189 --- linux (5.4.0-171.189) focal; urgency=medium * focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282) * Packaging resync (LP: #1786013) - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration (LP: #2046534) - RDMA/odp: Ensure the mm is still alive before creating an implicit child * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 (LP: #2032641) - selftests: Skip TM tests on synthetic TM implementations * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-45863 - kobject: Fix slab-out-of-bounds in fill_kobj_path() * Focal update: v5.4.259 upstream stable release (LP: #2043724) - RDMA/cxgb4: Check skb value for failure to allocate - lib/test_meminit: fix off-by-one error in test_pages() - pwm: hibvt: Explicitly set .polarity in .get_state() - HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect - quota: Fix slow quotaoff - net: prevent address rewrite in kernel_bind() - drm: etvnaviv: fix bad backport leading to warning - drm/msm/dsi: skip the wait for video mode done if not applicable - ravb: Fix up dma_free_coherent() call in ravb_remove() - ieee802154: ca8210: Fix a potential UAF in ca8210_probe - mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type - xen-netback: use default TX queue size for vifs - drm/vmwgfx: fix typo of sizeof argument - ixgbe: fix crash with empty VF macvlan list - net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() - nfc: nci: assert requested protocol is valid - workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() - dmaengine: stm32-mdma: abort resume if no ongoing transfer - usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer - net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read - usb: dwc3: Soft reset phy on probe for host - usb: musb: Get the musb_qh poniter after musb_giveback - usb: musb: Modify the "HWVers" register address - iio: pressure: bmp280: Fix NULL pointer exception - iio: pressure: dps310: Adjust Timeout Settings - iio: pressure: ms5611: ms5611_prom_is_valid false negative bug - mcb: remove is_added flag from mcb_device struct - libceph: use kernel_connect() - ceph: fix incorrect revoked caps assert in ceph_fill_file_size() - Input: powermate - fix use-after-free in powermate_config_complete - Input: psmouse - fix fast_reconnect function for PS/2 mode - Input: xpad - add PXN V900 support - cgroup: Remove duplicates in cgroup v1 tasks file - pinctrl: avoid unsafe code pattern in find_pinctrl() - usb: gadget: udc-xilinx: replace memcpy with memcpy_toio - usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call - x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs - dmaengine: mediatek: Fix deadlock caused by synchronize_irq() - powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE - powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() - ravb: Fix use-after-free issue in ravb_tx_timeout_work() - Documentation: sysctl: align cells in second content column - usb: hub: Guard against accesses to uninitialized BOS descriptors - Bluetooth: hci_event: Ignore NULL link key - Bluetooth: Reject connection with the device which has same BD_ADDR - Bluetooth: Fix a refcnt underflow problem for hci_conn - Bluetooth: vhci: Fix race when opening vhci device - Bluetooth: hci_event: Fix coding style - Bluetooth: avoid memcmp() out of bounds warning - ice: fix over-shifted variable - nfc: nci: fix possible NULL pointer dereference in send_acknowledge() - regmap: fix NULL deref on lookup - KVM: x86: Mask LVTPC when handling a PMI - netfilter: nft_payload: fix wrong mac header matching - qed: fix LL2 RX buffer allocation - xfrm: fix a data-race in xfrm_gen_index() - xfrm: interface: use DEV_STATS_INC() - net: ipv4: fix return value check in esp_remove_trailer - net: ipv6: fix
[Kernel-packages] [Bug 2042107] Re: Focal update: v5.4.258 upstream stable release
This bug was fixed in the package linux - 5.4.0-171.189 --- linux (5.4.0-171.189) focal; urgency=medium * focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282) * Packaging resync (LP: #1786013) - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration (LP: #2046534) - RDMA/odp: Ensure the mm is still alive before creating an implicit child * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 (LP: #2032641) - selftests: Skip TM tests on synthetic TM implementations * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-45863 - kobject: Fix slab-out-of-bounds in fill_kobj_path() * Focal update: v5.4.259 upstream stable release (LP: #2043724) - RDMA/cxgb4: Check skb value for failure to allocate - lib/test_meminit: fix off-by-one error in test_pages() - pwm: hibvt: Explicitly set .polarity in .get_state() - HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect - quota: Fix slow quotaoff - net: prevent address rewrite in kernel_bind() - drm: etvnaviv: fix bad backport leading to warning - drm/msm/dsi: skip the wait for video mode done if not applicable - ravb: Fix up dma_free_coherent() call in ravb_remove() - ieee802154: ca8210: Fix a potential UAF in ca8210_probe - mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type - xen-netback: use default TX queue size for vifs - drm/vmwgfx: fix typo of sizeof argument - ixgbe: fix crash with empty VF macvlan list - net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() - nfc: nci: assert requested protocol is valid - workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() - dmaengine: stm32-mdma: abort resume if no ongoing transfer - usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer - net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read - usb: dwc3: Soft reset phy on probe for host - usb: musb: Get the musb_qh poniter after musb_giveback - usb: musb: Modify the "HWVers" register address - iio: pressure: bmp280: Fix NULL pointer exception - iio: pressure: dps310: Adjust Timeout Settings - iio: pressure: ms5611: ms5611_prom_is_valid false negative bug - mcb: remove is_added flag from mcb_device struct - libceph: use kernel_connect() - ceph: fix incorrect revoked caps assert in ceph_fill_file_size() - Input: powermate - fix use-after-free in powermate_config_complete - Input: psmouse - fix fast_reconnect function for PS/2 mode - Input: xpad - add PXN V900 support - cgroup: Remove duplicates in cgroup v1 tasks file - pinctrl: avoid unsafe code pattern in find_pinctrl() - usb: gadget: udc-xilinx: replace memcpy with memcpy_toio - usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call - x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs - dmaengine: mediatek: Fix deadlock caused by synchronize_irq() - powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE - powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() - ravb: Fix use-after-free issue in ravb_tx_timeout_work() - Documentation: sysctl: align cells in second content column - usb: hub: Guard against accesses to uninitialized BOS descriptors - Bluetooth: hci_event: Ignore NULL link key - Bluetooth: Reject connection with the device which has same BD_ADDR - Bluetooth: Fix a refcnt underflow problem for hci_conn - Bluetooth: vhci: Fix race when opening vhci device - Bluetooth: hci_event: Fix coding style - Bluetooth: avoid memcmp() out of bounds warning - ice: fix over-shifted variable - nfc: nci: fix possible NULL pointer dereference in send_acknowledge() - regmap: fix NULL deref on lookup - KVM: x86: Mask LVTPC when handling a PMI - netfilter: nft_payload: fix wrong mac header matching - qed: fix LL2 RX buffer allocation - xfrm: fix a data-race in xfrm_gen_index() - xfrm: interface: use DEV_STATS_INC() - net: ipv4: fix return value check in esp_remove_trailer - net: ipv6: fix
[Kernel-packages] [Bug 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug is awaiting verification that the linux-oracle/5.4.0-1117.126 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-focal-linux-oracle' to 'verification-done- focal-linux-oracle'. If the problem still exists, change the tag 'verification-needed-focal-linux-oracle' to 'verification-failed-focal- linux-oracle'. 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-focal-linux-oracle-v2 verification-needed-focal-linux-oracle -- 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/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: 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 Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2045385] Re: Add ODM driver rtc-pcf85263
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 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-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2044192] Re: Patches needed for AmpereOne (arm64)
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.
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-raspi-v2
verification-needed-jammy-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Status in linux-gcp source package in Jammy:
Fix Released
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.
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-bluefield-v2
verification-needed-jammy-linux-bluefield
--
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/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 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-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2046656] Re: Jammy update: v6.1.64 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2046656 Title: Jammy update: v6.1.64 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.64 upstream stable release from git://git.kernel.org/ Linux 6.1.64 RISC-V: drop error print from riscv_hartid_to_cpuid() cxl/port: Fix NULL pointer access in devm_cxl_add_port() mmc: sdhci-pci-gli: GL9755: Mask the replay timer timeout of AER Input: xpad - add VID for Turtle Beach controllers tracing: Have trace_event_file have ref counters powerpc/powernv: Fix fortify source warnings in opal-prd.c drm/amd/display: Change the DMCUB mailbox memory location from FB to inbox drm/amd/display: Enable fast plane updates on DCN3.2 and above drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer() drm/amdgpu: lower CS errors to debug severity drm/amdgpu: fix error handling in amdgpu_bo_list_get() drm/amdgpu: don't use ATRM for external devices drm/amdgpu: don't use pci_is_thunderbolt_attached() drm/amdgpu/smu13: drop compute workload workaround drm/amd/pm: Fix error of MACO flag setting code drm/i915: Fix potential spectre vulnerability drm/i915: Bump GLK CDCLK frequency when driving multiple pipes drm/amd/pm: Handle non-terminated overdrive commands. ext4: properly sync file size update after O_SYNC direct IO ext4: add missed brelse in update_backups ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks ext4: correct the start block of counting reserved clusters ext4: correct return value of ext4_convert_meta_bg ext4: mark buffer new if it is unwritten to avoid stale data exposure ext4: correct offset of gdb backup in non meta_bg group to update_backups ext4: apply umask if ACL support is disabled Revert "net: r8169: Disable multicast filter for RTL8168H and RTL8107E" media: qcom: camss: Fix csid-gen2 for test pattern generator media: qcom: camss: Fix invalid clock enable bit disjunction media: qcom: camss: Fix missing vfe_lite clocks check media: qcom: camss: Fix VFE-480 vfe_disable_output() media: qcom: camss: Fix VFE-17x vfe_disable_output() media: qcom: camss: Fix vfe_get() error jump media: qcom: camss: Fix pm_domain_on sequence in probe mmc: sdhci-pci-gli: GL9750: Mask the replay timer timeout of AER r8169: add handling DASH when DASH is disabled r8169: fix network lost after resume on DASH systems mptcp: fix setsockopt(IP_TOS) subflow locking mptcp: add validity check for sending RM_ADDR mptcp: deal with large GSO size mm: kmem: drop __GFP_NOFAIL when allocating objcg vectors mm: fix for negative counter: nr_file_hugepages mmc: sdhci-pci-gli: A workaround to allow GL9750 to enter ASPM L1.2 riscv: kprobes: allow writing to x0 riscv: correct pt_level name via pgtable_l5/4_enabled riscv: mm: Update the comment of CONFIG_PAGE_OFFSET LoongArch: Mark __percpu functions as always inline nfsd: fix file memleak on client_opens_release dm-verity: don't use blocking calls from tasklets drm/mediatek/dp: fix memory leak on ->get_edid callback error path drm/mediatek/dp: fix memory leak on ->get_edid callback audio detection media: ccs: Correctly initialise try compose rectangle media: venus: hfi: add checks to handle capabilities from firmware media: venus: hfi: fix the check to handle session buffer requirement media: venus: hfi_parser: Add check to keep the number of codecs within range media: sharp: fix sharp encoding media: lirc: drop trailing space from scancode transmit f2fs: avoid format-overflow warning f2fs: do not return EFSCORRUPTED, but try to run online repair i2c: i801: fix potential race in i801_block_transaction_byte_by_byte net: phylink: initialize carrier state at creation net: dsa:
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
This bug is awaiting verification that the linux-oracle/5.4.0-1117.126 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-focal-linux-oracle' to 'verification-done- focal-linux-oracle'. If the problem still exists, change the tag 'verification-needed-focal-linux-oracle' to 'verification-failed-focal- linux-oracle'. 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! -- 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/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+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 2047915] Re: Jammy update: v6.1.67 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2047915 Title: Jammy update: v6.1.67 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.67 upstream stable release from git://git.kernel.org/ Linux 6.1.67 Revert "wifi: cfg80211: fix CQM for non-range use" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2047915/+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 2048234] Re: Jammy update: v6.1.70 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2048234 Title: Jammy update: v6.1.70 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.70 upstream stable release from git://git.kernel.org/ Linux 6.1.70 loop: deprecate autoloading callback loop_probe() wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x) wifi: cfg80211: fix CQM for non-range use fuse: share lookup state between submount and its parent mm/damon/core: make damon_start() waits until kdamond_fn() starts x86/alternatives: Sync core before enabling interrupts KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() KVM: arm64: vgic: Simplify kvm_vgic_destroy() thunderbolt: Fix memory leak in margining_port_remove() lib/vsprintf: Fix %pfwf when current node refcount == 0 gpio: dwapb: mask/unmask IRQ when disable/enale it bus: ti-sysc: Flush posted write only after srst_udelay pinctrl: starfive: jh7100: ignore disabled device tree nodes dm-integrity: don't modify bio's immutable bio_vec in integrity_metadata() tracing / synthetic: Disable events after testing in synth_event_gen_test_init() scsi: core: Always send batch on reset or error handling command Revert "scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity" selftests: mptcp: join: fix subflow_send_ack lookup ublk: move ublk_cancel_dev() out of ub->mutex ubifs: fix possible dereference after free btrfs: zoned: no longer count fresh BG region as zone unusable Revert "drm/amd/display: Do not set DRR on pipe commit" dm thin metadata: Fix ABBA deadlock by resetting dm_bufio_client loop: do not enforce max_loop hard limit by (new) default RISC-V: Fix do_notify_resume / do_work_pending prototype 9p: prevent read overrun in protocol dump tracepoint drm/i915: Reject async flips with bigjoiner smb: client: fix OOB in smbCalcSize() smb: client: fix OOB in SMB2_query_info_init() smb: client: fix potential OOB in cifs_dump_detail() smb: client: fix OOB in cifsd when receiving compounded resps dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp net: ks8851: Fix TX stall caused by TX buffer overrun net: rfkill: gpio: set GPIO direction net: 9p: avoid freeing uninit memory in p9pdu_vreadf Input: soc_button_array - add mapping for airplane mode button net: usb: ax88179_178a: avoid failed operations when device is disconnected Bluetooth: Add more enc key size check Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Bluetooth: L2CAP: Send reject on command corrupted request Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent ALSA: hda/realtek: Add quirk for ASUS ROG GV302XA USB: serial: option: add Quectel RM500Q R13 firmware support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel EG912Y module support USB: serial: ftdi_sio: update Actisense PIDs constant names wifi: cfg80211: fix certs build to not depend on file order wifi: cfg80211: Add my certificate usb-storage: Add quirk for incorrect WP on Kingston DT Ultimate 3.0 G3 ALSA: usb-audio: Increase delay in MOTU M quirk iio: triggered-buffer: prevent possible freeing of wrong buffer iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() Input: ipaq-micro-keys - add error handling for devm_kmemdup interconnect: qcom: sm8250: Enable sync_state iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw interconnect: Treat xlate()
[Kernel-packages] [Bug 2046660] Re: Jammy update: v6.1.65 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33 --- linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966) * Jammy update: v6.1.63 upstream stable release (LP: #2046577) - Restore "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" -- Timo Aaltonen Thu, 01 Feb 2024 20:16:28 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2046660 Title: Jammy update: v6.1.65 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.65 upstream stable release from git://git.kernel.org/ Linux 6.1.65 io_uring: fix off-by one bvec index USB: dwc3: qcom: fix wakeup after probe deferral USB: dwc3: qcom: fix software node leak on probe errors usb: dwc3: set the dma max_seg_size usb: dwc3: Fix default mode initialization USB: dwc2: write HCINT with INTMASK applied usb: typec: tcpm: Skip hard reset when in error recovery USB: serial: option: don't claim interface 4 for ZTE MF290 USB: serial: option: fix FM101R-GL defines USB: serial: option: add Fibocom L7xx modules usb: cdnsp: Fix deadlock issue during using NCM gadget bcache: fixup lock c->root error bcache: fixup init dirty data errors bcache: prevent potential division by zero error bcache: check return value from btree_node_alloc_replacement() dm-delay: fix a race between delay_presuspend and delay_bio hv_netvsc: Mark VF as slave before exposing it to user-mode hv_netvsc: Fix race of register_netdevice_notifier and VF register hv_netvsc: fix race of netvsc and VF register_netdevice USB: serial: option: add Luat Air72*U series products s390/dasd: protect device queue against concurrent access io_uring/fs: consider link->flags when getting path for LINKAT bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race md: fix bi_status reporting in md_end_clone_io bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() swiotlb-xen: provide the "max_mapping_size" method ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA arm64: dts: imx8mn-var-som: add 20ms delay to ethernet regulator enable NFSD: Fix checksum mismatches in the duplicate reply cache NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() ext4: make sure allocate pending entry not fail ext4: fix slab-use-after-free in ext4_es_insert_extent() ext4: using nofail preallocation in ext4_es_insert_extent() ext4: using nofail preallocation in ext4_es_insert_delayed_block() ext4: using nofail preallocation in ext4_es_remove_extent() ext4: use pre-allocated es in __es_remove_extent() ext4: use pre-allocated es in __es_insert_extent() ext4: factor out __es_alloc_extent() and __es_free_extent() ext4: add a new helper to check if es must be kept media: qcom: camss: Fix genpd cleanup media: qcom: camss: Fix V4L2 async notifier error path media: qcom: Initialise V4L2 async notifier later media: camss: Convert to platform remove callback returning void media: camss: Split power domain management MIPS: KVM: Fix a build warning about variable set but not used cifs: fix leak of iface for primary channel cifs: account for primary channel in the interface list cifs: distribute channels across interfaces based on speed cifs: print last update time for interface list smb3: allow dumping session and tcon id to improve stats analysis and debugging cifs: minor cleanup of some headers lockdep: Fix block chain corruption USB: dwc3: qcom: fix ACPI platform device leak USB: dwc3: qcom: fix resource leaks on probe deferral nvmet: nul-terminate the NQNs passed in the connect command i40e: Fix adding unsupported cloud filters i40e: use ERR_PTR error print in i40e messages arm64: mm: Fix "rodata=on" when CONFIG_RODATA_FULL_DEFAULT_ENABLED=y mm,kfence: decouple kfence from page granularity mapping judgement afs: Fix file locking on R/O volumes to operate in local mode afs: Return ENOENT if no cell DNS record can be found net: axienet: Fix check for partial TX checksum amd-xgbe: propagate the correct speed and duplex status
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 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-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug is awaiting verification that the linux- bluefield/5.15.0-1035.37 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-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- 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/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: 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 Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2044192] Re: Patches needed for AmpereOne (arm64)
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.
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-bluefield-v2
verification-needed-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Status in linux-gcp source package in Jammy:
Fix Released
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2045387] Re: Add ODM driver f81604 usb-can
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 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-linux-raspi' to 'verification-done-jammy- linux-raspi'. If the problem still exists, change the tag 'verification- needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'. 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-raspi-v2 verification-needed-jammy-linux-raspi -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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
