seems to be fixed
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056489
Title:
autopkgtest failure due to linux-doc unavailable
Status in linux package in Ubuntu:
Won't Fix
Status in zfs-linux package in Ubuntu:
Fix Released
Bug description:
zfs-linux autopkgtest depends on linux-doc.
However, linux-doc binary package is removed. Is this removal intentional? And if there a replacement package for it?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056489/+subscriptions
среда
[Bug 2142682] Re: [26.04 FEAT] [VS2215] KVM: Rewrite gmap using MMU notifiers
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Massimiliano Pellizzer (mpellizzer)
** Information type changed from Private to Public
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142682
Title:
[26.04 FEAT] [VS2215] KVM: Rewrite gmap using MMU notifiers
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Feature Description:
This is an item with the goal to improve the guest memory management
for 1M and 2G page sizes using hugetlbfs and transparent huge pages,
also in nested KVM setups while retaining backward compatibility.
This rework became a requirement for the new hardware work areas and
to ease the memory management support for 1M and 2G page sizes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142682/+subscriptions
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Massimiliano Pellizzer (mpellizzer)
** Information type changed from Private to Public
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142682
Title:
[26.04 FEAT] [VS2215] KVM: Rewrite gmap using MMU notifiers
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Feature Description:
This is an item with the goal to improve the guest memory management
for 1M and 2G page sizes using hugetlbfs and transparent huge pages,
also in nested KVM setups while retaining backward compatibility.
This rework became a requirement for the new hardware work areas and
to ease the memory management support for 1M and 2G page sizes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142682/+subscriptions
[Bug 2141203] Re: kernel panic after upgrade to linux kernel 6.17.0-14-generic
Same issue
Linux Mint 22.3 x86_64
Went thru kernel panic once and then just black screen on subsequent boots. Usually takes three to four times for it to boot, unless I boot to an older kernel.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
Linux Mint 22.3 x86_64
Went thru kernel panic once and then just black screen on subsequent boots. Usually takes three to four times for it to boot, unless I boot to an older kernel.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
[Bug 2142654] Re: [26.04 FEAT] [VS2539] KVM: KVM enhancement to enable zVDT Parallel Sysplex support
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Massimiliano Pellizzer (mpellizzer)
** Information type changed from Private to Public
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142654
Title:
[26.04 FEAT] [VS2539] KVM: KVM enhancement to enable zVDT Parallel
Sysplex support
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Feature Description:
Development and upstreaming of KVM changes to enable zVDT for Parallel
Sysplex support. In detail, this means to provide KVM changes to run
z/VM on top of zVDT and within the z/VM instance, z/OS instances and
Coupling Facility programs that form the Parallel Sysplex.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142654/+subscriptions
Assignee: Skipper Bug Screeners (skipper-screen-team) => Massimiliano Pellizzer (mpellizzer)
** Information type changed from Private to Public
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142654
Title:
[26.04 FEAT] [VS2539] KVM: KVM enhancement to enable zVDT Parallel
Sysplex support
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Feature Description:
Development and upstreaming of KVM changes to enable zVDT for Parallel
Sysplex support. In detail, this means to provide KVM changes to run
z/VM on top of zVDT and within the z/VM instance, z/OS instances and
Coupling Facility programs that form the Parallel Sysplex.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142654/+subscriptions
[Bug 1976248] Re: Revert PPC get_user workaround
** Changed in: zfs-linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1976248
Title:
Revert PPC get_user workaround
Status in linux package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in zfs-linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Jammy:
New
Status in linux source package in Kinetic:
Won't Fix
Status in zfs-linux source package in Kinetic:
Won't Fix
Bug description:
[Impact]
* A change of kernel symbol license allows to drop a PPC specific
workaround in zfs-dkms to use the regular (better) code paths.
* See details in:
https://git.launchpad.net/ubuntu/+source/zfs-
linux/tree/debian/patches/4900-ppc-get-user-workaround.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242
[Test Plan]
* linux: apply
https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23
* zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs-
linux/tree/debian/patches/4900-ppc-get-user-workaround.patch
* Build on kernel with zfs module on ppc
* Ensure that zfs.ko successfully loads and works
* Test that root on zfs installations work on ppc (however, Ubuntu
currently doesn't provide an installation method to achieve this, so
this bit of verification might be hard to complete)
[Where problems could occur]
* linux: the patch only changes the symbol licensing and the
potential tainteness status of the kernel, without any observable user
or kernel space impacts
* zfs-dkms: The PPC workaround patch is known to be buggy, and the
new arch-independent codepath may now use optimized codepaths inside
kernel resulting in a different behavior as observed by user-space
(operation successful, EFAULT not returned) matching the behavior of
all other architectures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1976248
Title:
Revert PPC get_user workaround
Status in linux package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in zfs-linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Jammy:
New
Status in linux source package in Kinetic:
Won't Fix
Status in zfs-linux source package in Kinetic:
Won't Fix
Bug description:
[Impact]
* A change of kernel symbol license allows to drop a PPC specific
workaround in zfs-dkms to use the regular (better) code paths.
* See details in:
https://git.launchpad.net/ubuntu/+source/zfs-
linux/tree/debian/patches/4900-ppc-get-user-workaround.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242
[Test Plan]
* linux: apply
https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23
* zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs-
linux/tree/debian/patches/4900-ppc-get-user-workaround.patch
* Build on kernel with zfs module on ppc
* Ensure that zfs.ko successfully loads and works
* Test that root on zfs installations work on ppc (however, Ubuntu
currently doesn't provide an installation method to achieve this, so
this bit of verification might be hard to complete)
[Where problems could occur]
* linux: the patch only changes the symbol licensing and the
potential tainteness status of the kernel, without any observable user
or kernel space impacts
* zfs-dkms: The PPC workaround patch is known to be buggy, and the
new arch-independent codepath may now use optimized codepaths inside
kernel resulting in a different behavior as observed by user-space
(operation successful, EFAULT not returned) matching the behavior of
all other architectures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions
[Bug 2142693] [NEW] [26.04] Please test secureboot and lock-down with 7.0.0 kernel (s390x) on Resolute Raccoon
Public bug reported:
The Canonical kernel team is working on an early 7.0.0 kernel for Ubuntu
Resolute Raccoon (26.04) and has an early build ready for secure-boot
and lockdown testing (version 7.0.0-1.1).
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+packages?field.name_filter=&field.status_filter=published&field.series_filter=resolute
To avoid potentially negative implications that a broken secure-boot
lockdown functionality would cause (esp. using the production key), we
kindly ask to get secure-boot tested, using Canonical kernel team's PPA
key for signature.
The linux-generic (7.0.0-1.1 or actually latest) is available in ppa:canonical-kernel-team/unstable.
(https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable)
$ sudo add-apt-repository ppa:canonical-kernel-team/unstable # add the unstable kernel PPA
$ sudo apt update # if not done automatically after the previous command
$ apt-cache policy linux-generic # will show potential install candidates
$ sudo apt install linux-generic=7.0.0-1.1 # install explicit version; or just latest available
Please note that this kernel is coming from the 'canonical-kernel-team'
PPA, hence it is NOT signed with the regular archive/release/production
key, BUT instead with the above PPA test signing key.
** Affects: ubuntu-z-systems
Importance: High
Assignee: bugproxy (bugproxy)
Status: Triaged
** Affects: linux (Ubuntu)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Triaged
** Tags: reverse-proxy-bugzilla s390x
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Tags added: reverse-proxy-bugzilla
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142693
Title:
[26.04] Please test secureboot and lock-down with 7.0.0 kernel (s390x)
on Resolute Raccoon
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
The Canonical kernel team is working on an early 7.0.0 kernel for
Ubuntu Resolute Raccoon (26.04) and has an early build ready for
secure-boot and lockdown testing (version 7.0.0-1.1).
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+packages?field.name_filter=&field.status_filter=published&field.series_filter=resolute
To avoid potentially negative implications that a broken secure-boot
lockdown functionality would cause (esp. using the production key), we
kindly ask to get secure-boot tested, using Canonical kernel team's
PPA key for signature.
The linux-generic (7.0.0-1.1 or actually latest) is available in ppa:canonical-kernel-team/unstable.
(https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable)
$ sudo add-apt-repository ppa:canonical-kernel-team/unstable # add the unstable kernel PPA
$ sudo apt update # if not done automatically after the previous command
$ apt-cache policy linux-generic # will show potential install candidates
$ sudo apt install linux-generic=7.0.0-1.1 # install explicit version; or just latest available
Please note that this kernel is coming from the 'canonical-kernel-team'
PPA, hence it is NOT signed with the regular archive/release/production
key, BUT instead with the above PPA test signing key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142693/+subscriptions
The Canonical kernel team is working on an early 7.0.0 kernel for Ubuntu
Resolute Raccoon (26.04) and has an early build ready for secure-boot
and lockdown testing (version 7.0.0-1.1).
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+packages?field.name_filter=&field.status_filter=published&field.series_filter=resolute
To avoid potentially negative implications that a broken secure-boot
lockdown functionality would cause (esp. using the production key), we
kindly ask to get secure-boot tested, using Canonical kernel team's PPA
key for signature.
The linux-generic (7.0.0-1.1 or actually latest) is available in ppa:canonical-kernel-team/unstable.
(https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable)
$ sudo add-apt-repository ppa:canonical-kernel-team/unstable # add the unstable kernel PPA
$ sudo apt update # if not done automatically after the previous command
$ apt-cache policy linux-generic # will show potential install candidates
$ sudo apt install linux-generic=7.0.0-1.1 # install explicit version; or just latest available
Please note that this kernel is coming from the 'canonical-kernel-team'
PPA, hence it is NOT signed with the regular archive/release/production
key, BUT instead with the above PPA test signing key.
** Affects: ubuntu-z-systems
Importance: High
Assignee: bugproxy (bugproxy)
Status: Triaged
** Affects: linux (Ubuntu)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Triaged
** Tags: reverse-proxy-bugzilla s390x
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Tags added: reverse-proxy-bugzilla
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142693
Title:
[26.04] Please test secureboot and lock-down with 7.0.0 kernel (s390x)
on Resolute Raccoon
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
The Canonical kernel team is working on an early 7.0.0 kernel for
Ubuntu Resolute Raccoon (26.04) and has an early build ready for
secure-boot and lockdown testing (version 7.0.0-1.1).
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+packages?field.name_filter=&field.status_filter=published&field.series_filter=resolute
To avoid potentially negative implications that a broken secure-boot
lockdown functionality would cause (esp. using the production key), we
kindly ask to get secure-boot tested, using Canonical kernel team's
PPA key for signature.
The linux-generic (7.0.0-1.1 or actually latest) is available in ppa:canonical-kernel-team/unstable.
(https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable)
$ sudo add-apt-repository ppa:canonical-kernel-team/unstable # add the unstable kernel PPA
$ sudo apt update # if not done automatically after the previous command
$ apt-cache policy linux-generic # will show potential install candidates
$ sudo apt install linux-generic=7.0.0-1.1 # install explicit version; or just latest available
Please note that this kernel is coming from the 'canonical-kernel-team'
PPA, hence it is NOT signed with the regular archive/release/production
key, BUT instead with the above PPA test signing key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142693/+subscriptions
[Bug 2142337] Re: Coresight fails to build on 6.8.0-102 due to missing function and arg definitions
** Description changed:
SRU Justification:
[Impact]
When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
- 728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~
+ 728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
- 736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~~~
- | coresight_remove_links
+ 736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~~~
+ | coresight_remove_links
+ ...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
- 500 | coresight_get_uci_data(id));
- | ^~
- | fd
+ 500 | coresight_get_uci_data(id));
+ | ^~
+ | fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
+ ...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
- 728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~
+ 728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
- 733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~~~
- | coresight_remove_links
+ 733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~~~
+ | coresight_remove_links
+ ...
+ drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
+ drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
+ 299 | if (!coresight_take_mode(csdev, mode)) {
+ | ^~~~~~~~~~~~~~~~~~~
+ | coresight_make_links
+ drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
+ drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
+ 345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
+ | ^~~~~~~~~~~~~~~~~~
+ | coresight_get_pid
+ drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
+ drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
+ 26 | if (!coresight_take_mode(csdev, mode))
+ | ^~~~~~~~~~~~~~~~~~~
+ | coresight_make_links
+ drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
+ drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
+ 37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
+ | ^~~~~~~~~~~~~~~~~~
+ | coresight_get_pid
```
These errors are a result of including the following patches in upstream
stable updates, but missing some dependencies from the original patch
sets:
- Error description: __tmc_probe:id not defined
- Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
- Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
- 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
- Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
- (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+ Error description: __tmc_probe:id not defined
+ Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
+ Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
+ 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
+ Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
+ (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
- Error description: coresight_{init,remove}_driver not defined
- Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
- Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
- Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
- (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+ Error description: catu,tmc: coresight_{init,remove}_driver not defined
+ Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
+ n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
+ Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
+ Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
+ (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+
+ Error description: tpdm,dummy: coresight_{set,take}_mode not defined
+ Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
+ n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
+ Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
+ Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
+ (https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)
[Fix]
- Cherry-pick upstream commits:
- 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
- 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
- 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
- from the series:
- "coresight: Move remaining AMBA ACPI devices into platform driver".
-
- NOTE: The series also has "Move remaining AMBA ACPI devices into platform driver"
- commits for the remaining devices, but I elected not to port them. We have
- the respective commits for tmc and catu applied because they were
- dependencies of "{tmc,catu}: Support atclk", but since the commits for the
- other devices are not necessary for the patches to apply, and as of now there
- are no upstream stable candidates with "Fixes" for the other devices, I don't
- think it's worth the increased change size. Fortunately, if they are needed
- in the future, they are clean cherry-picks (besides simple context changes)
- and we have all the dependencies.
+ Revert the break commits.
[Test Plan]
Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.
[Where problems could occur]
- There is a low chance of regression because these commits are only small
- refactors that don't change behaviour. Only static function definitions are
- modified, and functionality is only added via new helpers, not removed.
- The new patches have a potential to create conflicts for derivative kernels
- and other downstream projects that rebase on this kernel.
+ These reverts are technically removing fixes from the tree, which have the
+ potential to cause behaviour changes or regressions. However, the generic
+ kernel has never been able to build these coresight features, and thus we have
+ not observed any examples of the issue the patches intended to fix.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142337
Title:
Coresight fails to build on 6.8.0-102 due to missing function and arg
definitions
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
SRU Justification:
[Impact]
When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
500 | coresight_get_uci_data(id));
| ^~
| fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
299 | if (!coresight_take_mode(csdev, mode)) {
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
26 | if (!coresight_take_mode(csdev, mode))
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
```
These errors are a result of including the following patches in
upstream stable updates, but missing some dependencies from the
original patch sets:
Error description: __tmc_probe:id not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: catu,tmc: coresight_{init,remove}_driver not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: tpdm,dummy: coresight_{set,take}_mode not defined
Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
(https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)
[Fix]
Revert the break commits.
[Test Plan]
Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.
[Where problems could occur]
These reverts are technically removing fixes from the tree, which have the
potential to cause behaviour changes or regressions. However, the generic
kernel has never been able to build these coresight features, and thus we have
not observed any examples of the issue the patches intended to fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142337/+subscriptions
SRU Justification:
[Impact]
When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
- 728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~
+ 728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
- 736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~~~
- | coresight_remove_links
+ 736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~~~
+ | coresight_remove_links
+ ...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
- 500 | coresight_get_uci_data(id));
- | ^~
- | fd
+ 500 | coresight_get_uci_data(id));
+ | ^~
+ | fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
+ ...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
- 728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~
+ 728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
- 733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
- | ^~~~~~~~~~~~~~~~~~~~~~~
- | coresight_remove_links
+ 733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
+ | ^~~~~~~~~~~~~~~~~~~~~~~
+ | coresight_remove_links
+ ...
+ drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
+ drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
+ 299 | if (!coresight_take_mode(csdev, mode)) {
+ | ^~~~~~~~~~~~~~~~~~~
+ | coresight_make_links
+ drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
+ drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
+ 345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
+ | ^~~~~~~~~~~~~~~~~~
+ | coresight_get_pid
+ drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
+ drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
+ 26 | if (!coresight_take_mode(csdev, mode))
+ | ^~~~~~~~~~~~~~~~~~~
+ | coresight_make_links
+ drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
+ drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
+ 37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
+ | ^~~~~~~~~~~~~~~~~~
+ | coresight_get_pid
```
These errors are a result of including the following patches in upstream
stable updates, but missing some dependencies from the original patch
sets:
- Error description: __tmc_probe:id not defined
- Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
- Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
- 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
- Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
- (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+ Error description: __tmc_probe:id not defined
+ Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
+ Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
+ 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
+ Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
+ (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
- Error description: coresight_{init,remove}_driver not defined
- Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
- Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
- Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
- (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+ Error description: catu,tmc: coresight_{init,remove}_driver not defined
+ Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
+ n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
+ Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
+ Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
+ (https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
+
+ Error description: tpdm,dummy: coresight_{set,take}_mode not defined
+ Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
+ n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
+ Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
+ Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
+ (https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)
[Fix]
- Cherry-pick upstream commits:
- 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
- 3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
- 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
- from the series:
- "coresight: Move remaining AMBA ACPI devices into platform driver".
-
- NOTE: The series also has "Move remaining AMBA ACPI devices into platform driver"
- commits for the remaining devices, but I elected not to port them. We have
- the respective commits for tmc and catu applied because they were
- dependencies of "{tmc,catu}: Support atclk", but since the commits for the
- other devices are not necessary for the patches to apply, and as of now there
- are no upstream stable candidates with "Fixes" for the other devices, I don't
- think it's worth the increased change size. Fortunately, if they are needed
- in the future, they are clean cherry-picks (besides simple context changes)
- and we have all the dependencies.
+ Revert the break commits.
[Test Plan]
Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.
[Where problems could occur]
- There is a low chance of regression because these commits are only small
- refactors that don't change behaviour. Only static function definitions are
- modified, and functionality is only added via new helpers, not removed.
- The new patches have a potential to create conflicts for derivative kernels
- and other downstream projects that rebase on this kernel.
+ These reverts are technically removing fixes from the tree, which have the
+ potential to cause behaviour changes or regressions. However, the generic
+ kernel has never been able to build these coresight features, and thus we have
+ not observed any examples of the issue the patches intended to fix.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142337
Title:
Coresight fails to build on 6.8.0-102 due to missing function and arg
definitions
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
SRU Justification:
[Impact]
When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
500 | coresight_get_uci_data(id));
| ^~
| fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
299 | if (!coresight_take_mode(csdev, mode)) {
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
26 | if (!coresight_take_mode(csdev, mode))
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
```
These errors are a result of including the following patches in
upstream stable updates, but missing some dependencies from the
original patch sets:
Error description: __tmc_probe:id not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: catu,tmc: coresight_{init,remove}_driver not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: tpdm,dummy: coresight_{set,take}_mode not defined
Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
(https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)
[Fix]
Revert the break commits.
[Test Plan]
Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.
[Where problems could occur]
These reverts are technically removing fixes from the tree, which have the
potential to cause behaviour changes or regressions. However, the generic
kernel has never been able to build these coresight features, and thus we have
not observed any examples of the issue the patches intended to fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142337/+subscriptions
[Bug 2142675] [NEW] Mouse wheel of Logitech M510 mouse is not working in Ubuntu 25.10
Public bug reported:
Hello,
I just wanted to report that the mouse wheel isn't working after
installing Ubuntu 25.10.
Mouse: Logitech M510
```none
$ cat /etc/issue
Ubuntu 25.10 \n \l
```
# `libinput debug-events`
```
$ sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event16 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event15 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event1 DEVICE_ADDED Lid Switch seat0 default group3 cap:S
-event0 DEVICE_ADDED Sleep Button seat0 default group4 cap:k
-event5 DEVICE_ADDED Logitech M510 seat0 default group5 cap:p left scroll-nat scroll-button
-event9 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard seat0 default group6 cap:k
-event11 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard System Control seat0 default group6 cap:k
-event12 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard Consumer Control seat0 default group6 cap:k
-event6 DEVICE_ADDED Wacom Pen and multitouch sensor Pen seat0 default group7 cap:T size 344x194mm calib
-event7 DEVICE_ADDED Wacom Pen and multitouch sensor Finger seat0 default group7 cap:t size 344x194mm ntouches 10 calib
-event20 DEVICE_ADDED sof-hda-dsp Headphone seat0 default group8 cap:k
-event17 DEVICE_ADDED Synaptics TM3625-010 seat0 default group9 cap:pg size 97x65mm tap (dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwtp-on
-event18 DEVICE_ADDED TPPS/2 Elan TrackPoint seat0 default group10 cap:p left scroll-nat scroll-button
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group11 cap:k
-event8 DEVICE_ADDED ThinkPad Extra Buttons seat0 default group12 cap:k
-event5 POINTER_MOTION +0.000s -0.62/ 0.31 ( -2.00/ +1.00)
event5 POINTER_MOTION 2 +0.008s -0.89/ 0.89 ( -1.00/ +1.00)
event5 POINTER_MOTION 3 +0.016s -2.00/ 2.00 ( -2.00/ +2.00)
event5 POINTER_MOTION 4 +0.022s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 5 +0.030s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 6 +0.038s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 7 +0.046s -1.00/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 8 +0.054s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 9 +0.062s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 10 +0.084s 0.00/ 0.96 ( +0.00/ +1.00)
event5 POINTER_MOTION 11 +0.240s -0.56/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 12 +0.262s 0.00/ 0.56 ( +0.00/ +1.00)
-event9 KEYBOARD_KEY +0.938s *** (-1) pressed
event9 KEYBOARD_KEY +1.161s *** (-1) pressed
```
# `dmidecode -t system`
```
$ sudo dmidecode -t system
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20TK001HUS
Version: ThinkPad X1 Extreme Gen 3
Serial Number: R90ZBA06
UUID: 1069ddcc-24b8-11b2-a85c-d98c9a52a342
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
Family: ThinkPad X1 Extreme Gen 3
Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options
Handle 0x0039, DMI type 15, 31 bytes
System Event Log
Area Length: 1026 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0000003F
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None
```
$ cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/2142675/+attachment/5948529/+files/lspci-vnvn.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142675
Title:
Mouse wheel of Logitech M510 mouse is not working in Ubuntu 25.10
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I just wanted to report that the mouse wheel isn't working after
installing Ubuntu 25.10.
Mouse: Logitech M510
```none
$ cat /etc/issue
Ubuntu 25.10 \n \l
```
# `libinput debug-events`
```
$ sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event16 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event15 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event1 DEVICE_ADDED Lid Switch seat0 default group3 cap:S
-event0 DEVICE_ADDED Sleep Button seat0 default group4 cap:k
-event5 DEVICE_ADDED Logitech M510 seat0 default group5 cap:p left scroll-nat scroll-button
-event9 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard seat0 default group6 cap:k
-event11 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard System Control seat0 default group6 cap:k
-event12 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard Consumer Control seat0 default group6 cap:k
-event6 DEVICE_ADDED Wacom Pen and multitouch sensor Pen seat0 default group7 cap:T size 344x194mm calib
-event7 DEVICE_ADDED Wacom Pen and multitouch sensor Finger seat0 default group7 cap:t size 344x194mm ntouches 10 calib
-event20 DEVICE_ADDED sof-hda-dsp Headphone seat0 default group8 cap:k
-event17 DEVICE_ADDED Synaptics TM3625-010 seat0 default group9 cap:pg size 97x65mm tap (dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwtp-on
-event18 DEVICE_ADDED TPPS/2 Elan TrackPoint seat0 default group10 cap:p left scroll-nat scroll-button
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group11 cap:k
-event8 DEVICE_ADDED ThinkPad Extra Buttons seat0 default group12 cap:k
-event5 POINTER_MOTION +0.000s -0.62/ 0.31 ( -2.00/ +1.00)
event5 POINTER_MOTION 2 +0.008s -0.89/ 0.89 ( -1.00/ +1.00)
event5 POINTER_MOTION 3 +0.016s -2.00/ 2.00 ( -2.00/ +2.00)
event5 POINTER_MOTION 4 +0.022s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 5 +0.030s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 6 +0.038s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 7 +0.046s -1.00/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 8 +0.054s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 9 +0.062s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 10 +0.084s 0.00/ 0.96 ( +0.00/ +1.00)
event5 POINTER_MOTION 11 +0.240s -0.56/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 12 +0.262s 0.00/ 0.56 ( +0.00/ +1.00)
-event9 KEYBOARD_KEY +0.938s *** (-1) pressed
event9 KEYBOARD_KEY +1.161s *** (-1) pressed
```
# `dmidecode -t system`
```
$ sudo dmidecode -t system
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20TK001HUS
Version: ThinkPad X1 Extreme Gen 3
Serial Number: R90ZBA06
UUID: 1069ddcc-24b8-11b2-a85c-d98c9a52a342
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
Family: ThinkPad X1 Extreme Gen 3
Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options
Handle 0x0039, DMI type 15, 31 bytes
System Event Log
Area Length: 1026 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0000003F
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None
```
$ cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142675/+subscriptions
Hello,
I just wanted to report that the mouse wheel isn't working after
installing Ubuntu 25.10.
Mouse: Logitech M510
```none
$ cat /etc/issue
Ubuntu 25.10 \n \l
```
# `libinput debug-events`
```
$ sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event16 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event15 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event1 DEVICE_ADDED Lid Switch seat0 default group3 cap:S
-event0 DEVICE_ADDED Sleep Button seat0 default group4 cap:k
-event5 DEVICE_ADDED Logitech M510 seat0 default group5 cap:p left scroll-nat scroll-button
-event9 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard seat0 default group6 cap:k
-event11 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard System Control seat0 default group6 cap:k
-event12 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard Consumer Control seat0 default group6 cap:k
-event6 DEVICE_ADDED Wacom Pen and multitouch sensor Pen seat0 default group7 cap:T size 344x194mm calib
-event7 DEVICE_ADDED Wacom Pen and multitouch sensor Finger seat0 default group7 cap:t size 344x194mm ntouches 10 calib
-event20 DEVICE_ADDED sof-hda-dsp Headphone seat0 default group8 cap:k
-event17 DEVICE_ADDED Synaptics TM3625-010 seat0 default group9 cap:pg size 97x65mm tap (dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwtp-on
-event18 DEVICE_ADDED TPPS/2 Elan TrackPoint seat0 default group10 cap:p left scroll-nat scroll-button
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group11 cap:k
-event8 DEVICE_ADDED ThinkPad Extra Buttons seat0 default group12 cap:k
-event5 POINTER_MOTION +0.000s -0.62/ 0.31 ( -2.00/ +1.00)
event5 POINTER_MOTION 2 +0.008s -0.89/ 0.89 ( -1.00/ +1.00)
event5 POINTER_MOTION 3 +0.016s -2.00/ 2.00 ( -2.00/ +2.00)
event5 POINTER_MOTION 4 +0.022s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 5 +0.030s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 6 +0.038s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 7 +0.046s -1.00/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 8 +0.054s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 9 +0.062s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 10 +0.084s 0.00/ 0.96 ( +0.00/ +1.00)
event5 POINTER_MOTION 11 +0.240s -0.56/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 12 +0.262s 0.00/ 0.56 ( +0.00/ +1.00)
-event9 KEYBOARD_KEY +0.938s *** (-1) pressed
event9 KEYBOARD_KEY +1.161s *** (-1) pressed
```
# `dmidecode -t system`
```
$ sudo dmidecode -t system
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20TK001HUS
Version: ThinkPad X1 Extreme Gen 3
Serial Number: R90ZBA06
UUID: 1069ddcc-24b8-11b2-a85c-d98c9a52a342
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
Family: ThinkPad X1 Extreme Gen 3
Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options
Handle 0x0039, DMI type 15, 31 bytes
System Event Log
Area Length: 1026 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0000003F
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None
```
$ cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/2142675/+attachment/5948529/+files/lspci-vnvn.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142675
Title:
Mouse wheel of Logitech M510 mouse is not working in Ubuntu 25.10
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I just wanted to report that the mouse wheel isn't working after
installing Ubuntu 25.10.
Mouse: Logitech M510
```none
$ cat /etc/issue
Ubuntu 25.10 \n \l
```
# `libinput debug-events`
```
$ sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event16 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event15 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event1 DEVICE_ADDED Lid Switch seat0 default group3 cap:S
-event0 DEVICE_ADDED Sleep Button seat0 default group4 cap:k
-event5 DEVICE_ADDED Logitech M510 seat0 default group5 cap:p left scroll-nat scroll-button
-event9 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard seat0 default group6 cap:k
-event11 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard System Control seat0 default group6 cap:k
-event12 DEVICE_ADDED Metadot - Das Keyboard Das Keyboard Consumer Control seat0 default group6 cap:k
-event6 DEVICE_ADDED Wacom Pen and multitouch sensor Pen seat0 default group7 cap:T size 344x194mm calib
-event7 DEVICE_ADDED Wacom Pen and multitouch sensor Finger seat0 default group7 cap:t size 344x194mm ntouches 10 calib
-event20 DEVICE_ADDED sof-hda-dsp Headphone seat0 default group8 cap:k
-event17 DEVICE_ADDED Synaptics TM3625-010 seat0 default group9 cap:pg size 97x65mm tap (dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwtp-on
-event18 DEVICE_ADDED TPPS/2 Elan TrackPoint seat0 default group10 cap:p left scroll-nat scroll-button
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group11 cap:k
-event8 DEVICE_ADDED ThinkPad Extra Buttons seat0 default group12 cap:k
-event5 POINTER_MOTION +0.000s -0.62/ 0.31 ( -2.00/ +1.00)
event5 POINTER_MOTION 2 +0.008s -0.89/ 0.89 ( -1.00/ +1.00)
event5 POINTER_MOTION 3 +0.016s -2.00/ 2.00 ( -2.00/ +2.00)
event5 POINTER_MOTION 4 +0.022s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 5 +0.030s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 6 +0.038s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 7 +0.046s -1.00/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 8 +0.054s 0.00/ 1.00 ( +0.00/ +1.00)
event5 POINTER_MOTION 9 +0.062s -1.00/ 1.00 ( -1.00/ +1.00)
event5 POINTER_MOTION 10 +0.084s 0.00/ 0.96 ( +0.00/ +1.00)
event5 POINTER_MOTION 11 +0.240s -0.56/ 0.00 ( -1.00/ +0.00)
event5 POINTER_MOTION 12 +0.262s 0.00/ 0.56 ( +0.00/ +1.00)
-event9 KEYBOARD_KEY +0.938s *** (-1) pressed
event9 KEYBOARD_KEY +1.161s *** (-1) pressed
```
# `dmidecode -t system`
```
$ sudo dmidecode -t system
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0012, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20TK001HUS
Version: ThinkPad X1 Extreme Gen 3
Serial Number: R90ZBA06
UUID: 1069ddcc-24b8-11b2-a85c-d98c9a52a342
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
Family: ThinkPad X1 Extreme Gen 3
Handle 0x0027, DMI type 12, 5 bytes
System Configuration Options
Handle 0x0039, DMI type 15, 31 bytes
System Event Log
Area Length: 1026 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0000003F
Header Format: Type 1
Supported Log Type Descriptors: 4
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: PCI system error
Data Format 2: None
Descriptor 3: System reconfigured
Data Format 3: None
Descriptor 4: Log area reset/cleared
Data Format 4: None
```
$ cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142675/+subscriptions
[Bug 2139667] Re: [NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-ofed-25.10-dkms DKMS suite
Hello Robie, thanks for the feedback. For "customers" I intended all the
Ubuntu users, not only hardware enabled users; I definitely used the
wrong term.
I will perform a regression analysis again as requested, and will be
more careful with wording in my next edit.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
Ubuntu users, not only hardware enabled users; I definitely used the
wrong term.
I will perform a regression analysis again as requested, and will be
more careful with wording in my next edit.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-azure-fde/6.8.0-1048.55)
All autopkgtests for the newly accepted linux-meta-azure-fde (6.8.0-1048.55) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-azure-fde
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-azure-fde
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
[Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.8.0-1049.55)
All autopkgtests for the newly accepted linux-meta-azure (6.8.0-1049.55) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-azure
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-azure
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
вторник
[Bug 2142623] Re: [Kernel] Bluetooth LE connection timeout too short for industrial Te connectivity sensors
** Tags added: patch
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142623
Title:
[Kernel] Bluetooth LE connection timeout too short for industrial Te
connectivity sensors
Status in linux package in Ubuntu:
New
Bug description:
In an industrial IoT context (Volvo Group), we are using TE
Connectivity M5600 BLE pressure sensors. These sensors have a high
response latency during the initial connection handshake.
Problem:
The current hardcoded timeout in net/bluetooth/hci_conn.c is set to 2 seconds (msecs_to_jiffies(2000)). This is too short for these specific sensors, causing systematic connection failures on Ubuntu Core 22 (Raspberry Pi 4).
Proposed Solution:
I have successfully tested a custom kernel build where the timeout is increased to 20 seconds.
Attached Patch:
Please find attached the patch modifying hci_connect_le and hci_connect_le_scan in net/bluetooth/hci_conn.c.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142623/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142623
Title:
[Kernel] Bluetooth LE connection timeout too short for industrial Te
connectivity sensors
Status in linux package in Ubuntu:
New
Bug description:
In an industrial IoT context (Volvo Group), we are using TE
Connectivity M5600 BLE pressure sensors. These sensors have a high
response latency during the initial connection handshake.
Problem:
The current hardcoded timeout in net/bluetooth/hci_conn.c is set to 2 seconds (msecs_to_jiffies(2000)). This is too short for these specific sensors, causing systematic connection failures on Ubuntu Core 22 (Raspberry Pi 4).
Proposed Solution:
I have successfully tested a custom kernel build where the timeout is increased to 20 seconds.
Attached Patch:
Please find attached the patch modifying hci_connect_le and hci_connect_le_scan in net/bluetooth/hci_conn.c.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142623/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-xilinx/6.8.0.1025.26)
All autopkgtests for the newly accepted linux-meta-xilinx (6.8.0.1025.26) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (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/noble/update_excuses.html#linux-meta-xilinx
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (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/noble/update_excuses.html#linux-meta-xilinx
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
Подписаться на:
Комментарии (Atom)