You have been subscribed to a public bug:
Problem Description:
Brought up Ubuntu 26.04 guest with a single bridge interface, ran iperf3 in server mode on the host and started iperf3 client on the guest, connecting to the server on the host via the bridge IP, with 8000 sec test time on client. At some point in the first hour or two, OOM is observed on the guest, with sudden memory usage spike.
Guest bridge xml snippet:
<interface type='bridge'>
<mac address='52:54:00:08:0d:f8'/>
<source bridge='virbr0'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</interface>
System Information:
Linux ltcden6-lp4 6.18.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Wed Dec 17 15:52:06 UTC 2025 ppc64le GNU/Linux
PRETTY_NAME="Ubuntu Resolute Raccoon (development branch)"
NAME="Ubuntu"
VERSION_ID="26.04"
VERSION="26.04 (Resolute Raccoon)"
VERSION_CODENAME=resolute
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=resolute
LOGO=ubuntu-logo
Steps to reproduce:
1. Start guest domain console with virsh start <domain name> --console
2. On a separate tab, start the iperf3 server on the host machine with the following command to use port 6969 (any port that is available is okay to use)
iperf3 -s -p 6969
3. Check the ip of virbr0 (or the bridge network in use by the guest)
ip addr
keep a note of the ip of virbr0 (or the bridge network in use), lets assume 192.168.122.1 at the moment
4. In the guest console tab, run the iperf3 client in background, attach the server IP as the IP address of the bridge noted above, with the port you started the iperf3 server at, specify the time as 8000 seconds, and monitor dmesg logs
- nohup iperf3 -c 192.198.122.1 -p 6969 -t 8000 > iperf3client.log &
- dmesg -w
5. Monitor the dmesg logs for OOM errors.
==
Here's a log from a previous run where we see OOM logs dumped on the console:
[ 5] 1339.00-1340.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1340.00-1341.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1341.00-1342.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[63842.605982] Out of memory: Killed process 1291 (systemd) total-vm:30016kB, anon-rss:4096kB, file-rss:6144kB, shmem-rss:0kB, UID:0 pgtables:32kB oom_score_adj:100
[63842.616019] Out of memory: Killed process 1293 ((sd-pam)) total-vm:33728kB, anon-rss:6208kB, file-rss:2048kB, shmem-rss:0kB, UID:0 pgtables:28kB oom_score_adj:100
[ 5] 1342.00-1343.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1343.00-1344.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1344.00-1345.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1345.00-1346.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1346.00-1347.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1347.00-1348.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1348.00-1349.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1349.00-1350.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1350.00-1351.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1351.00-1352.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1352.00-1353.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1353.00-1354.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1354.00-1355.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1355.00-1356.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1356.00-1357.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[63858.021746] Out of memory: Killed process 968 (named) total-vm:217088kB, anon-rss:77760kB, file-rss:6144kB, shmem-rss:0kB, UID:106 pgtables:42kB oom_score_adj:0
[ 5] 1357.00-1358.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1358.00-1359.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1359.00-1360.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
[ 5] 1360.00-1361.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes
Some insight from recent tests:
1. This issue is not reproducible when the iperf3 guest and host are both run on the LPAR itself.
2. Issue is also not reproducible with virtio driver (All the previous tests have been with RTL8139 driver).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
** Tags: architecture-ppc64le bugnameltc-217559 severity-high targetmilestone-inin---
--
[Ubuntu 26.04] Running iperf3 client for longer duration causes OOM on guest
https://bugs.launchpad.net/bugs/2143080
You received this bug notification because you are subscribed to linux in Ubuntu.
понедельник
[Bug 2143077] [NEW] SIGNEDv6: add support for stubble format binaries
Public bug reported:
Add support for stubble headed arm64 binaries.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143077
Title:
SIGNEDv6: add support for stubble format binaries
Status in linux package in Ubuntu:
New
Bug description:
Add support for stubble headed arm64 binaries.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143077/+subscriptions
Add support for stubble headed arm64 binaries.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143077
Title:
SIGNEDv6: add support for stubble format binaries
Status in linux package in Ubuntu:
New
Bug description:
Add support for stubble headed arm64 binaries.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143077/+subscriptions
[Bug 2142337] Re: Coresight fails to build on 6.8.0-102 due to missing function and arg definitions
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
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-nvidia package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-nvidia source package in Noble:
Fix Committed
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
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
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-nvidia package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-nvidia source package in Noble:
Fix Committed
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 2135716] Re: Enabling crypto selftests causes boot stall on 6.8
** Tags removed: verification-needed-noble-linux-nvidia-tegra
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2135716
Title:
Enabling crypto selftests causes boot stall on 6.8
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
Fix Committed
Bug description:
SRU Justification:
[Impact]
Upstream stable updates applied the v6.12.13 commit "crypto: api - Fix
boot-up self-test race" to noble 6.8. When crypto selftests are
enabled (i.e. CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n) the system
freezes during boot for 60 seconds and fails the selftest with a
kernel error. This issue has also been observed upstream for 6.6,
which caused the patch to be removed from stable updates for 6.6 [1].
Kernels 6.12+ work fine.
This was reproduced on a noble desktop VM and an NVIDIA Jetson AGX
Orin, and the AGX error is shown below.
[ 70.635664] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 70.643757] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.643762] ------------[ cut here ]------------
[ 70.656053] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.656129] WARNING: CPU: 1 PID: 139 at crypto/testmgr.c:5900 alg_test+0x580/0x620
[ 70.656197] Modules linked in:
[ 70.656214] CPU: 1 PID: 139 Comm: cryptomgr_test Not tainted 6.8.12+ #22
[ 70.656223] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 00.0.0-dev-main_e11e99_3bea0 09/22/2025
[ 70.656228] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 70.656238] pc : alg_test+0x580/0x620
[ 70.656240] lr : alg_test+0x580/0x620
[ 70.656244] sp : ffff8000818f3d50
[ 70.656247] x29: ffff8000818f3d50 x28: 0000000000000000 x27: 0000000000000000
[ 70.656253] x26: 00000000ffffff92 x25: 00000000ffffffff x24: 0000000000000154
[ 70.656258] x23: ffffbbfb9e52e350 x22: 000000000000000e x21: ffff000086c83680
[ 70.656263] x20: ffff000086c83600 x19: ffffbbfb9c79dae8 x18: 00000000fffffffe
[ 70.656268] x17: 312d3d6372282064 x16: 656c696166206e6f x15: ffff8000818f3960
[ 70.656274] x14: 0000000000000000 x13: ffffbbfb9e4f2b5f x12: 00000000000001da
[ 70.656280] x11: 00000000ffffffea x10: ffffbbfb9dfa3e80 x9 : 0000000000000001
[ 70.656284] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : c0000000ffffefff
[ 70.656290] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : 0000000000000000
[ 70.656295] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00008101ddc0
[ 70.656302] Call trace:
[ 70.656308] alg_test+0x580/0x620
[ 70.656311] cryptomgr_test+0x24/0x44
[ 70.656322] kthread+0x110/0x114
[ 70.656338] ret_from_fork+0x10/0x20
[ 70.656358] ---[ end trace 0000000000000000 ]---
[ 132.075677] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 132.083791] alg: self-tests for sha224 using sha224-arm64 failed (rc=-110)
[Fix]
Revert commit "crypto: api - Fix boot-up self-test race".
[Test Plan]
To reproduce the issue:
1. Compile the stock noble generic kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
2. Boot the kernel on any platform, like a VM.
3. Observe boot stall.
To test the fix:
1. Revert commit in noble generic kernel.
2. Compile the modified kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
3. Boot the kernel on any platform, like a VM.
4. Boot should succeed with no delays or errors.
[Where problems could occur]
The regression potential is low, since this commit was dropped from
stable 6.6 and the issue it aims to fix was never observed (it is only
a theoretical problem). Therefore, 6.8 behavior should remain
unchanged.
That said, the theoretical issue will be present after reverting this
commit, which is a problem that could occur.
[1] https://lists-ec2.96boards.org/archives/list/lkft-
triage@lists.linaro.org/message/2T73AZRFODFX57XXVWF6UD22CK6RFA44/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2135716/+subscriptions
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2135716
Title:
Enabling crypto selftests causes boot stall on 6.8
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
Fix Committed
Bug description:
SRU Justification:
[Impact]
Upstream stable updates applied the v6.12.13 commit "crypto: api - Fix
boot-up self-test race" to noble 6.8. When crypto selftests are
enabled (i.e. CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n) the system
freezes during boot for 60 seconds and fails the selftest with a
kernel error. This issue has also been observed upstream for 6.6,
which caused the patch to be removed from stable updates for 6.6 [1].
Kernels 6.12+ work fine.
This was reproduced on a noble desktop VM and an NVIDIA Jetson AGX
Orin, and the AGX error is shown below.
[ 70.635664] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 70.643757] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.643762] ------------[ cut here ]------------
[ 70.656053] alg: self-tests for sha224 using sha224-arm64-neon failed (rc=-110)
[ 70.656129] WARNING: CPU: 1 PID: 139 at crypto/testmgr.c:5900 alg_test+0x580/0x620
[ 70.656197] Modules linked in:
[ 70.656214] CPU: 1 PID: 139 Comm: cryptomgr_test Not tainted 6.8.12+ #22
[ 70.656223] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 00.0.0-dev-main_e11e99_3bea0 09/22/2025
[ 70.656228] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 70.656238] pc : alg_test+0x580/0x620
[ 70.656240] lr : alg_test+0x580/0x620
[ 70.656244] sp : ffff8000818f3d50
[ 70.656247] x29: ffff8000818f3d50 x28: 0000000000000000 x27: 0000000000000000
[ 70.656253] x26: 00000000ffffff92 x25: 00000000ffffffff x24: 0000000000000154
[ 70.656258] x23: ffffbbfb9e52e350 x22: 000000000000000e x21: ffff000086c83680
[ 70.656263] x20: ffff000086c83600 x19: ffffbbfb9c79dae8 x18: 00000000fffffffe
[ 70.656268] x17: 312d3d6372282064 x16: 656c696166206e6f x15: ffff8000818f3960
[ 70.656274] x14: 0000000000000000 x13: ffffbbfb9e4f2b5f x12: 00000000000001da
[ 70.656280] x11: 00000000ffffffea x10: ffffbbfb9dfa3e80 x9 : 0000000000000001
[ 70.656284] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : c0000000ffffefff
[ 70.656290] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : 0000000000000000
[ 70.656295] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00008101ddc0
[ 70.656302] Call trace:
[ 70.656308] alg_test+0x580/0x620
[ 70.656311] cryptomgr_test+0x24/0x44
[ 70.656322] kthread+0x110/0x114
[ 70.656338] ret_from_fork+0x10/0x20
[ 70.656358] ---[ end trace 0000000000000000 ]---
[ 132.075677] alg: hash: error allocating sha224-generic (generic impl of sha224): -110
[ 132.083791] alg: self-tests for sha224 using sha224-arm64 failed (rc=-110)
[Fix]
Revert commit "crypto: api - Fix boot-up self-test race".
[Test Plan]
To reproduce the issue:
1. Compile the stock noble generic kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
2. Boot the kernel on any platform, like a VM.
3. Observe boot stall.
To test the fix:
1. Revert commit in noble generic kernel.
2. Compile the modified kernel with CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n.
3. Boot the kernel on any platform, like a VM.
4. Boot should succeed with no delays or errors.
[Where problems could occur]
The regression potential is low, since this commit was dropped from
stable 6.6 and the issue it aims to fix was never observed (it is only
a theoretical problem). Therefore, 6.8 behavior should remain
unchanged.
That said, the theoretical issue will be present after reverting this
commit, which is a problem that could occur.
[1] https://lists-ec2.96boards.org/archives/list/lkft-
triage@lists.linaro.org/message/2T73AZRFODFX57XXVWF6UD22CK6RFA44/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2135716/+subscriptions
[Bug 2142336] Re: Coresight fails to build on 6.8.0-101 due to 'atomic_t' member accessed as 'int'
** Tags removed: verification-needed-noble-linux-nvidia-tegra
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142336
Title:
Coresight fails to build on 6.8.0-101 due to 'atomic_t' member
accessed as 'int'
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-101 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_enable':
drivers/hwtracing/coresight/coresight-catu.c:465:27: error: invalid operands to binary == (have 'atomic_t' and 'int')
465 | if (csdev->refcnt == 0) {
| ~~~~~~~~~~~~~ ^~
| |
| atomic_t
drivers/hwtracing/coresight/coresight-catu.c:471:30: error: wrong type argument to increment
471 | csdev->refcnt++;
| ^~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_disable':
drivers/hwtracing/coresight/coresight-catu.c:498:13: error: wrong type argument to decrement
498 | if (--csdev->refcnt == 0) {
| ^~
```
These errors are a result of including the following patch in upstream stable
updates, but missing some dependencies from the original patch set:
Error description: refcnt accessed as int but defined as atomic_t
Break commit: n/linux 0e2198d37507 ("coresight: catu: Introduce refcount and spinlock for enabling/disabling")
Missing commit: 4545b38ef004 ("coresight: Remove atomic type from refcnt")
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 commit:
4545b38ef004 ("coresight: Remove atomic type from refcnt")
which requires a few context fixups due to missing commits from the original
patchset. Those missing patches are not required for this commit, so we can
just fix and apply it alone to reduce the number of changes.
NOTE: These are the missing dependent patches for a clean application:
a0fef3f05cf3 ("coresight: Make language around "activated" sinks consistent")
a11ebe138b8d ("coresight: Remove ops callback checks")
9cae77cf23e3 ("coresight: Move mode to struct coresight_device")
d5e83f97eb56 ("coresight: Remove the 'enable' field.")
1f5149c7751c ("coresight: Move all sysfs code to sysfs file")
These contain pretty significant refactoring and cleanup (although they don't
alter behaviour) so they were omitted to reduce changes to a stable kernel.
[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 since this patch is purely cleanup and
does not modify observable behaviour, as stated by the author in the original
patch set. Additionally, coresight failed to build before this, so this is
a guaranteed improvement in that respect. There is a risk of breakage if I
missed some dependent commits, or if my fixups were incorrect.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142336/+subscriptions
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142336
Title:
Coresight fails to build on 6.8.0-101 due to 'atomic_t' member
accessed as 'int'
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-101 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_enable':
drivers/hwtracing/coresight/coresight-catu.c:465:27: error: invalid operands to binary == (have 'atomic_t' and 'int')
465 | if (csdev->refcnt == 0) {
| ~~~~~~~~~~~~~ ^~
| |
| atomic_t
drivers/hwtracing/coresight/coresight-catu.c:471:30: error: wrong type argument to increment
471 | csdev->refcnt++;
| ^~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_disable':
drivers/hwtracing/coresight/coresight-catu.c:498:13: error: wrong type argument to decrement
498 | if (--csdev->refcnt == 0) {
| ^~
```
These errors are a result of including the following patch in upstream stable
updates, but missing some dependencies from the original patch set:
Error description: refcnt accessed as int but defined as atomic_t
Break commit: n/linux 0e2198d37507 ("coresight: catu: Introduce refcount and spinlock for enabling/disabling")
Missing commit: 4545b38ef004 ("coresight: Remove atomic type from refcnt")
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 commit:
4545b38ef004 ("coresight: Remove atomic type from refcnt")
which requires a few context fixups due to missing commits from the original
patchset. Those missing patches are not required for this commit, so we can
just fix and apply it alone to reduce the number of changes.
NOTE: These are the missing dependent patches for a clean application:
a0fef3f05cf3 ("coresight: Make language around "activated" sinks consistent")
a11ebe138b8d ("coresight: Remove ops callback checks")
9cae77cf23e3 ("coresight: Move mode to struct coresight_device")
d5e83f97eb56 ("coresight: Remove the 'enable' field.")
1f5149c7751c ("coresight: Move all sysfs code to sysfs file")
These contain pretty significant refactoring and cleanup (although they don't
alter behaviour) so they were omitted to reduce changes to a stable kernel.
[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 since this patch is purely cleanup and
does not modify observable behaviour, as stated by the author in the original
patch set. Additionally, coresight failed to build before this, so this is
a guaranteed improvement in that respect. There is a risk of breakage if I
missed some dependent commits, or if my fixups were incorrect.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142336/+subscriptions
[Bug 2142337] Re: Coresight fails to build on 6.8.0-102 due to missing function and arg definitions
** Tags removed: verification-needed-noble-linux-nvidia-tegra
** Tags added: verification-done-noble-linux-nvidia-tegra
--
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
** Tags added: verification-done-noble-linux-nvidia-tegra
--
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 2142905] Re: Wayland bug. Global hotkeys not working in OBS Studio (Flatpak and APT version) on Ubuntu, Kubuntu 25.10
Evidence that the hotkey issue is a Wayland-specific bug
I am now certain that the issue with hotkeys not working in OBS Studio
is a bug within Wayland. I have reached this conclusion after many hours
of rigorous testing:
Ubuntu Desktop 25.10 (Live version): This version uses Wayland by
default. Global hotkeys fail to work on both the Flatpak and APT
versions of OBS.
KDE neon: The current distribution also uses Wayland, and the issue
persists there as well.
Lubuntu: Since Lubuntu still uses X11 by default, global hotkeys
work perfectly on both the APT and Flatpak versions.
The definitive proof: When I force OBS to run using the X11 backend on a Wayland session by using the following command:
QT_QPA_PLATFORM=xcb obs
The global hotkeys immediately start working correctly again.
** Summary changed:
- Wayland bug. Global hotkeys not working in OBS Studio (Flatpak) on Kubuntu 25.10
+ Wayland bug. Global hotkeys not working in OBS Studio (Flatpak and APT version) on Ubuntu, Kubuntu 25.10
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142905
Title:
Wayland bug. Global hotkeys not working in OBS Studio (Flatpak and APT
version) on Ubuntu, Kubuntu 25.10
Status in kubuntu-meta package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
Dear Canonical Developers,
Wayland is effectively in an alpha state and contains several critical
bugs. Why are you forcing this broken and unusable software onto
Ubuntu users? Why have you blocked the use of X11? What is the purpose
of this?
Dear Canonical Developers,
I am asking you to either completely get rid of this trash called Wayland or, as a second option, start developing and fixing the critical bugs in this software. Canonical has enough financial resources to fund its proper development.
Dear Developers,
Wayland is a nightmare for those developing screen recording software. You are putting too much strain on these developers. Please fix these critical issues. Described below is just one of many unsolvable problems that screen recorder developers are currently facing.
**************
Global hotkeys not working in OBS Studio (Flatpak) on Kubuntu 25.10
*********
I am experiencing an issue with global hotkeys in OBS Studio.
Environment:
OS: Kubuntu 25.10
Version: OBS Studio (Flatpak)
Display Server: Wayland
The Problem: Hotkeys for "Pause" and "Resume" recording only work when
the OBS Studio window is focused in the foreground. If I am recording
another application and that application has focus, the hotkeys do not
work at all.
Questions: Is this a Wayland-related issue? I know that Kubuntu/Ubuntu
now enforces Wayland by default. While X11 is installed, there is no
option to select it at the login screen (SDDM).
I haven't found any working guide on how to resolve this or how to
force an X11 session.
How can I get global hotkeys to work in the background on Wayland, or
how can I switch back to X11?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2142905/+subscriptions
I am now certain that the issue with hotkeys not working in OBS Studio
is a bug within Wayland. I have reached this conclusion after many hours
of rigorous testing:
Ubuntu Desktop 25.10 (Live version): This version uses Wayland by
default. Global hotkeys fail to work on both the Flatpak and APT
versions of OBS.
KDE neon: The current distribution also uses Wayland, and the issue
persists there as well.
Lubuntu: Since Lubuntu still uses X11 by default, global hotkeys
work perfectly on both the APT and Flatpak versions.
The definitive proof: When I force OBS to run using the X11 backend on a Wayland session by using the following command:
QT_QPA_PLATFORM=xcb obs
The global hotkeys immediately start working correctly again.
** Summary changed:
- Wayland bug. Global hotkeys not working in OBS Studio (Flatpak) on Kubuntu 25.10
+ Wayland bug. Global hotkeys not working in OBS Studio (Flatpak and APT version) on Ubuntu, Kubuntu 25.10
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142905
Title:
Wayland bug. Global hotkeys not working in OBS Studio (Flatpak and APT
version) on Ubuntu, Kubuntu 25.10
Status in kubuntu-meta package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
Dear Canonical Developers,
Wayland is effectively in an alpha state and contains several critical
bugs. Why are you forcing this broken and unusable software onto
Ubuntu users? Why have you blocked the use of X11? What is the purpose
of this?
Dear Canonical Developers,
I am asking you to either completely get rid of this trash called Wayland or, as a second option, start developing and fixing the critical bugs in this software. Canonical has enough financial resources to fund its proper development.
Dear Developers,
Wayland is a nightmare for those developing screen recording software. You are putting too much strain on these developers. Please fix these critical issues. Described below is just one of many unsolvable problems that screen recorder developers are currently facing.
**************
Global hotkeys not working in OBS Studio (Flatpak) on Kubuntu 25.10
*********
I am experiencing an issue with global hotkeys in OBS Studio.
Environment:
OS: Kubuntu 25.10
Version: OBS Studio (Flatpak)
Display Server: Wayland
The Problem: Hotkeys for "Pause" and "Resume" recording only work when
the OBS Studio window is focused in the foreground. If I am recording
another application and that application has focus, the hotkeys do not
work at all.
Questions: Is this a Wayland-related issue? I know that Kubuntu/Ubuntu
now enforces Wayland by default. While X11 is installed, there is no
option to select it at the login screen (SDDM).
I haven't found any working guide on how to resolve this or how to
force an X11 session.
How can I get global hotkeys to work in the background on Wayland, or
how can I switch back to X11?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2142905/+subscriptions
[Bug 2126750] Re: No vDSO for armhf processes on arm64 kernel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2126750
Title:
No vDSO for armhf processes on arm64 kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi folks,
In my investigation of bug 2125424 it turns out that the issue is that
we don't have a vDSO support for armhf userspace on arm64 kernel.
I don't know how intentional that is, since the config/annotations
file only talks about amd64 for the COMPAT_VDSO knob? FWIW, Debian
kernels seem to enable it.
Cheers!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2126750/+subscriptions
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2126750
Title:
No vDSO for armhf processes on arm64 kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi folks,
In my investigation of bug 2125424 it turns out that the issue is that
we don't have a vDSO support for armhf userspace on arm64 kernel.
I don't know how intentional that is, since the config/annotations
file only talks about amd64 for the COMPAT_VDSO knob? FWIW, Debian
kernels seem to enable it.
Cheers!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2126750/+subscriptions
[Bug 2142878] Re: While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing several readlink msg
In order to reproduce the kdump tool readlink failure it is possible to
execute:
$ sudo kdump-config unload
$ sudo rm /var/lib/kdump/initrd.img-$(uname -r)
$ sudo kdump-config load
* Creating symlink /var/lib/kdump/vmlinuz
kdump-tools: Generating /var/lib/kdump/initrd.img-6.19.0-6-generic
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:1:1074085889/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:1:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:1:1074085889/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:1:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:0:1074085889/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:0:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
...
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or directory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
* Creating symlink /var/lib/kdump/initrd.img
* loaded kdump kernel
```
Again, since I was able to reproduce the issue without updating the
kernel, this seems to be a problem which has not been cause by the
kernel update itself.
The reason why kdump-tools is generating this amount of failures must be
investigated further.
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in kdump-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in multipath-tools package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
execute:
$ sudo kdump-config unload
$ sudo rm /var/lib/kdump/initrd.img-$(uname -r)
$ sudo kdump-config load
* Creating symlink /var/lib/kdump/vmlinuz
kdump-tools: Generating /var/lib/kdump/initrd.img-6.19.0-6-generic
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:1:1074085889/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:1:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/target1:0:1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:1:1074085889/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:1:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/target0:0:1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/rport-0:0-1/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a7/0.0.0001/host0/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:0:1074085889/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:0:1074085889/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/target1:0:0/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/rport-1:0-0/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.00a6/0.0.0002/host1/driver/module: No such file or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
...
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or directory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
* Creating symlink /var/lib/kdump/initrd.img
* loaded kdump kernel
```
Again, since I was able to reproduce the issue without updating the
kernel, this seems to be a problem which has not been cause by the
kernel update itself.
The reason why kdump-tools is generating this amount of failures must be
investigated further.
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in kdump-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in multipath-tools package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
[Bug 2142878] Re: While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing several readlink msg
I was able to reproduce the problem in an s390x lpar as follows:
$ uname -a
Linux special07 6.19.0-6-generic #6-Ubuntu SMP Wed Feb 18 14:47:53 UTC 2026 s390x GNU/Linux
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.19.0-6-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
This reproduces the first problem `mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found`.
Since I was able to reproduce it without updating the kernel, the new kernel is not the root cause.
In particular, this warning is caused by a command in the multipath-tools initramfs hook:
`copy_exec /usr/lib/udev/dmsetup_env`
This command looks for `dmsetup_env` that according to the changelog has
been removed in version 0.8.8:
```
[ Chris Hofstaedtler ]
* [7fcb8ba] New upstream version 0.8.8
* [e63a379] Refresh patches
* [4ab9ce2] Drop old dmsetup_env hack
dmsetup long supports DM_NAME and DM_UUID, and the other variables
are not used anymore.
...
```
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in kdump-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in multipath-tools package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
$ uname -a
Linux special07 6.19.0-6-generic #6-Ubuntu SMP Wed Feb 18 14:47:53 UTC 2026 s390x GNU/Linux
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.19.0-6-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
This reproduces the first problem `mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found`.
Since I was able to reproduce it without updating the kernel, the new kernel is not the root cause.
In particular, this warning is caused by a command in the multipath-tools initramfs hook:
`copy_exec /usr/lib/udev/dmsetup_env`
This command looks for `dmsetup_env` that according to the changelog has
been removed in version 0.8.8:
```
[ Chris Hofstaedtler ]
* [7fcb8ba] New upstream version 0.8.8
* [e63a379] Refresh patches
* [4ab9ce2] Drop old dmsetup_env hack
dmsetup long supports DM_NAME and DM_UUID, and the other variables
are not used anymore.
...
```
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142878
Title:
While upgrading to kernel 7.0.0-2.2 on resolute snapshot4, I am seeing
several readlink msg
Status in Ubuntu on IBM z Systems:
New
Status in kdump-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in multipath-tools package in Ubuntu:
New
Bug description:
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-6.19.0-6-generic:
Installed: 6.19.0-6.6
Candidate: 6.19.0-6.6
Version table:
*** 6.19.0-6.6 500
500 http://ports.ubuntu.com/ubuntu-ports resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$ sudo add-apt-repository --yes ppa:canonical-kernel-team/unstable
Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu/
Suites: resolute
Components: main
'
Description:
CONFIGURED FOR DEVELOPMENT
Cowboy builders all the way.
More info: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute InRelease [20.2 kB]
Hit:2 http://ports.ubuntu.com/ubuntu-ports resolute InRelease
Get:3 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages [8,560 B]
Hit:4 http://ports.ubuntu.com/ubuntu-ports resolute-updates InRelease
Get:5 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main Translation-en [8,188 B]
Hit:6 http://ports.ubuntu.com/ubuntu-ports resolute-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports resolute-security InRelease
Fetched 37.0 kB in 1s (44.4 kB/s)
Reading package lists... Done
ubuntu@zlin:~$ sudo apt install linux-image-7.0.0-2-generic=7.0.0-2.2 linux-modules-7.0.0-2-generic=7.0.0-2.2
Installing:
linux-image-7.0.0-2-generic linux-modules-7.0.0-2-generic
Suggested packages:
linux-unstable-tools linux-headers-7.0.0-2-generic
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 43.9 MB
Space needed: 95.0 MB / 181 GB available
Get:1 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-modules-7.0.0-2-generic s390x 7.0.0-2.2 [33.3 MB]
Get:2 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x linux-image-7.0.0-2-generic s390x 7.0.0-2.2 [10.6 MB]
Fetched 43.9 MB in 47s (937 kB/s)
Selecting previously unselected package linux-modules-7.0.0-2-generic.
(Reading database ... 71022 files and directories currently installed.)
Preparing to unpack .../linux-modules-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Selecting previously unselected package linux-image-7.0.0-2-generic.
Preparing to unpack .../linux-image-7.0.0-2-generic_7.0.0-2.2_s390x.deb ...
Unpacking linux-image-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-modules-7.0.0-2-generic (7.0.0-2.2) ...
Setting up linux-image-7.0.0-2-generic (7.0.0-2.2) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-2-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-2-generic
Processing triggers for linux-image-7.0.0-2-generic (7.0.0-2.2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-2-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-7.0.0-2-generic
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/sdd/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/1:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/target1:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/sdb/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/0:0:
1:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/target0:0:1/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-1/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/sdc/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/1:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/target1:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/rport-1:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007d/0.0.0002/host1/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/sda/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/0:0:
0:1074348032/block/driver/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/target0:0:0/driv
er/module: No such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/rport-0:0-0/driver/module: N
o such file or directory
readlink: /sys/devices/css0/0.0.007c/0.0.0001/host0/driver/module: No such file
or directory
readlink: /sys/devices/css0/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-0/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/devices/virtual/block/dm-1/driver/module: No such file or directo
ry
readlink: /sys/devices/virtual/block/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*': No such file or directory
readlink: /sys/class/gpio/export/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: /sys/class/gpio/unexport/driver/module: Not a directory
readlink: /sys/class/gpio/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
readlink: '/sys/class/phy/*': No such file or directory
readlink: '/sys/class/pwm/*': No such file or directory
readlink: '/sys/class/regulator/*': No such file or directory
readlink: '/sys/class/rtc/*': No such file or directory
readlink: '/sys/class/backlight/*': No such file or directory
readlink: /sys/devices/virtual/graphics/fbcon/driver/module: No such file or dir
ectory
readlink: /sys/devices/virtual/graphics/driver/module: No such file or directory
readlink: /sys/devices/virtual/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: /sys/class/drm/version/driver/module: Not a directory
readlink: /sys/class/drm/driver/module: No such file or directory
readlink: /sys/class/driver/module: No such file or directory
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Run /usr/lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device: dm-1.
Done.
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Pending kernel upgrade!
Running kernel version:
6.19.0-6-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
7.0.0-2-generic.
Restarting the system to load the new kernel will not be handled automatically,
so you should consider rebooting.
Failed to check for processor microcode upgrades.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
ubuntu@zlin:~$ reboot
Call to Reboot failed: Access denied as the requested operation requires interactive authentication. However, interactive authentication has not been enabled by the calling program.
ubuntu@zlin:~$ sudo reboot
ubuntu@zlin:~$ Connection to zlin closed by remote host.
Connection to zlin closed.
user@workstation:~$ ssh ubuntu@zlin
Welcome to Ubuntu Resolute Raccoon (development branch) (GNU/Linux 7.0.0-2-generic s390x)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Fri 27 Feb 2026 05:14:49 PM UTC
System load: 0.33 Memory usage: 1% Processes: 177
Usage of /: 5.3% of 187.93GB Swap usage: 0% Users logged in: 0
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Fri Feb 27 17:10:32 2026 from 10.172.66.67
ubuntu@zlin:~$ apt-cache policy linux-image-$(uname -r)
linux-image-7.0.0-2-generic:
Installed: 7.0.0-2.2
Candidate: 7.0.0-2.2
Version table:
*** 7.0.0-2.2 500
500 https://ppa.launchpadcontent.net/canonical-kernel-team/unstable/ubuntu resolute/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@zlin:~$
The installation of the snaptshot4 ISO itself was fine.
Could actually be kernel, updateinitramfs or apparmor ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142878/+subscriptions
[Bug 2141985] Re: Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
fwts测试结果
root@larry-li-Latitude-5590:/home/larry-li# sudo fwts acpidump
Running 1 tests, results appended to results.log
Test: Dump ACPI tables.
Dump ACPI tables. 1 info only
root@larry-li-Latitude-5590:/home/larry-li# sudo fwts method
Running 1 tests, results appended to results.log
Test: ACPI DSDT Method Semantic tests.
Test Method Names. 1 passed
Test _AEI. 1 skipped
Test _EVT (Event Method). 1 skipped
Test _DLM (Device Lock Mutex). 1 skipped
Test _PIC (Inform AML of Interrupt Model). 3 passed
Test _CID (Compatible ID). 14 passed
Test _CLS (Class Code). 1 skipped
Test _DDN (DOS Device Name). 6 passed
Test _HID (Hardware ID). 78 passed, 1 failed
Test _HRV (Hardware Revision Number). 11 passed
Test _MLS (Multiple Language String). 1 passed
Test _PLD (Physical Device Location). 21 passed
Test _SUB (Subsystem ID). 1 skipped
Test _SUN (Slot User Number). 1 skipped
Test _STR (String). 8 passed
Test _UID (Unique ID). 41 passed
Test _CDM (Clock Domain). 1 skipped
Test _CRS (Current Resource Settings). 53 passed
Test _DSD (Device Specific Data). 1 skipped
Test _DIS (Disable). 8 passed
Test _DMA (Direct Memory Access). 1 skipped
Test _FIX (Fixed Register Resource Provider). 1 skipped
Test _GSB (Global System Interrupt Base). 1 skipped
Test _HPP (Hot Plug Parameters). 1 skipped
Test _MAT (Multiple APIC Table Entry). 1 skipped
Test _PRS (Possible Resource Settings). 10 passed
Test _PRT (PCI Routing Table). 28 passed
Test _PXM (Proximity). 1 skipped
Test _SLI (System Locality Information). 1 skipped
Test _CCA (Cache Coherency Attribute). 1 skipped
Test _EDL (Eject Device List). 1 skipped
Test _EJD (Ejection Dependent Device). 1 skipped
Test _EJ0 (Eject). 1 skipped
Test _EJ1 (Eject). 1 skipped
Test _EJ2 (Eject). 1 skipped
Test _EJ3 (Eject). 1 skipped
Test _EJ4 (Eject). 1 skipped
Test _LCK (Lock). 1 skipped
Test _RMV (Remove). 24 passed
Test _STA (Status). 69 passed
Test _DEP (Operational Region Dependencies). 38 passed
Test _FIT (Firmware Interface Table). 1 skipped
Test _BDN (BIOS Dock Name). 1 skipped
Test _BBN (Base Bus Number). 1 passed
Test _DCK (Dock). 1 skipped
Test _INI (Initialize). 38 passed
Test _GLK (Global Lock). 1 skipped
Test _SEG (Segment). 1 skipped
Test _LSI (Label Storage Information). 1 skipped
Test _CBR (CXL Host Bridge Register). 1 skipped
Test _OFF (Set resource off). 1 skipped
Test _ON_ (Set resource on). 1 skipped
Test _DSW (Device Sleep Wake). 3 passed
Test _IRC (In Rush Current). 1 skipped
Test _PRE (Power Resources for Enumeration). 1 skipped
Test _PR0 (Power Resources for D0). 1 skipped
Test _PR1 (Power Resources for D1). 1 skipped
Test _PR2 (Power Resources for D2). 1 skipped
Test _PR3 (Power Resources for D3). 1 skipped
Test _PRW (Power Resources for Wake). 54 passed
Test _PS0 (Power State 0). 15 passed
Test _PS1 (Power State 1). 1 skipped
Test _PS2 (Power State 2). 1 passed
Test _PS3 (Power State 3). 15 passed
Test _PSC (Power State Current). 11 passed
Test _PSE (Power State for Enumeration). 1 skipped
Test _PSW (Power State Wake). 3 passed
Test _S1D (S1 Device State). 1 skipped
Test _S2D (S2 Device State). 1 skipped
Test _S3D (S3 Device State). 1 passed
Test _S4D (S4 Device State). 1 passed
Test _S0W (S0 Device Wake State). 7 passed
Test _S1W (S1 Device Wake State). 1 skipped
Test _S2W (S2 Device Wake State). 1 skipped
Test _S3W (S3 Device Wake State). 1 passed
Test _S4W (S4 Device Wake State). 1 passed
Test _RST (Device Reset). 1 skipped
Test _PRR (Power Resource for Reset). 1 skipped
Test _DSC (Deepest State for Configuration). 1 skipped
Test _S0_ (S0 System State). 1 passed
Test _S1_ (S1 System State). 1 skipped
Test _S2_ (S2 System State). 1 skipped
Test _S3_ (S3 System State). 1 skipped
Test _S4_ (S4 System State). 1 passed
Test _S5_ (S5 System State). 1 passed
Test _SWS (System Wake Source). 1 skipped
Test _PSS (Performance Supported States). 17 passed
Test _CPC (Continuous Performance Control). 15 failed
Test _CSD (C State Dependencies). 1 skipped
Test _CST (C States). 16 passed
Test _PCT (Performance Control). 16 passed
Test _PDL (P-State Depth Limit). 1 passed
Test _PPC (Performance Present Capabilities). 17 passed
Test _PPE (Polling for Platform Error). 1 skipped
Test _PSD (Power State Dependencies). 16 passed
Test _PTC (Processor Throttling Control). 1 passed
Test _TDL (T-State Depth Limit). 1 passed
Test _TPC (Throttling Present Capabilities). 1 passed
Test _TSD (Throttling State Dependencies). 2 failed
Test _TSS (Throttling Supported States). 2 failed
Test _LPI (Low Power Idle States). 1 skipped
Test _RDI (Resource Dependencies for Idle). 1 skipped
Test _PUR (Processor Utilization Request). 1 passed
Test _MSG (Message). 1 skipped
Test _SST (System Status). 1 skipped
Test _ALC (Ambient Light Colour Chromaticity). 1 skipped
Test _ALI (Ambient Light Illuminance). 1 passed
Test _ALT (Ambient Light Temperature). 1 skipped
Test _ALP (Ambient Light Polling). 1 skipped
Test _ALR (Ambient Light Response). 1 passed
Test _LID (Lid Status). 1 passed
Test _GTF (Get Task File). 5 passed
Test _GTM (Get Timing Mode). 1 passed
Test _MBM (Memory Bandwidth Monitoring Data). 1 skipped
Test _UPC (USB Port Capabilities). 19 passed
Test _PDO (USB Power Data Object). 1 skipped
Test _UPD (User Presence Detect). 1 skipped
Test _UPP (User Presence Polling). 1 skipped
Test _GCP (Get Capabilities). 1 skipped
Test _GRT (Get Real Time). 1 skipped
Test _GWS (Get Wake Status). 1 skipped
Test _CWS (Clear Wake Status). 1 skipped
Test _SRT (Set Real Time). 1 skipped
Test _STP (Set Expired Timer Wake Policy). 1 skipped
Test _STV (Set Timer Value). 1 skipped
Test _TIP (Expired Timer Wake Policy). 1 skipped
Test _TIV (Timer Values). 1 skipped
Test _NBS (NVDIMM Boot Status). 1 skipped
Test _NCH (NVDIMM Current Health Information). 1 skipped
Test _NIC (NVDIMM Health Error Injection Capabilities) 1 skipped
Test _NIH (NVDIMM Inject/Clear Health Errors). 1 skipped
Test _NIG (NVDIMM Inject Health Error Status). 1 skipped
Test _SBS (Smart Battery Subsystem). 1 skipped
Test _BCT (Battery Charge Time). 1 skipped
Test _BIF (Battery Information). 2 passed
Test _BIX (Battery Information Extended). 1 skipped
Test _BMA (Battery Measurement Averaging). 1 skipped
Test _BMC (Battery Maintenance Control). 1 skipped
Test _BMD (Battery Maintenance Data). 1 skipped
Test _BMS (Battery Measurement Sampling Time). 1 skipped
Test _BPC (Battery Power Characteristics). 1 skipped
Test _BPS (Battery Power State). 1 skipped
Test _BPT (Battery Power Threshold). 1 skipped
Test _BST (Battery Status). 2 passed
Test _BTP (Battery Trip Point). 1 skipped
Test _BTH (Battery Throttle Limit). 1 skipped
Test _BTM (Battery Time). 1 skipped
Test _PCL (Power Consumer List). 3 passed
Test _PIF (Power Source Information). 1 skipped
Test _PRL (Power Source Redundancy List). 1 skipped
Test _PSR (Power Source). 1 passed
Test _GAI (Get Averaging Level). 1 skipped
Test _GHL (Get Hardware Limit). 1 skipped
Test _PMC (Power Meter Capabilities). 1 skipped
Test _PMD (Power Meter Devices). 1 skipped
Test _PMM (Power Meter Measurement). 1 skipped
Test _WPC (Wireless Power Calibration). 1 skipped
Test _WPP (Wireless Power Polling). 1 skipped
Test _FIF (Fan Information). 1 skipped
Test _FPS (Fan Performance States). 1 skipped
Test _FSL (Fan Set Level). 1 skipped
Test _FST (Fan Status). 1 skipped
Test _ACx (Active Cooling). 4 passed, 8 skipped
Test _ART (Active Cooling Relationship Table). 1 skipped
Test _ALx (Active List). 10 skipped
Test _CRT (Critical Trip Point). 6 passed
Test _CR3 (Warm/Standby Temperature). 5 passed
Test _DTI (Device Temperature Indication). 5 passed
Test _HOT (Hot Temperature). 5 passed
Test _MTL (Minimum Throttle Limit). 1 skipped
Test _NTT (Notification Temp Threshold). 5 passed
Test _PSL (Passive List). 1 skipped
Test _PSV (Passive Temp). 5 passed
Test _RTV (Relative Temp Values). 1 skipped
Test _SCP (Set Cooling Policy). 20 passed
Test _TC1 (Thermal Constant 1). 1 skipped
Test _TC2 (Thermal Constant 2). 1 skipped
Test _TFP (Thermal fast Sampling Period). 1 skipped
Test _TMP (Thermal Zone Current Temp). 6 passed
Test _TPT (Trip Point Temperature). 1 skipped
Test _TRT (Thermal Relationship Table). 1 passed
Test _TSN (Thermal Sensor Device). 1 skipped
Test _TSP (Thermal Sampling Period). 4 passed
Test _TST (Temperature Sensor Threshold). 1 skipped
Test _TZD (Thermal Zone Devices). 1 skipped
Test _TZM (Thermal Zone member). 1 skipped
Test _TZP (Thermal Zone Polling). 1 skipped
Test _GPE (General Purpose Events). 1 passed
Test _EC_ (EC Offset Query). 1 skipped
Test _PTS (Prepare to Sleep). 2 passed
Test _TTS (Transition to State). 1 skipped
Test _WAK (System Wake). 2 passed
Test _ADR (Return Unique ID for Device). 114 passed
Test _BCL (Query List of Brightness Control Levels S.. 1 passed
Test _BCM (Set Brightness Level). 1 passed
Test _BQC (Brightness Query Current Level). 1 passed
Test _DCS (Return the Status of Output Device). 8 passed
Test _DDC (Return the EDID for this Device). 1 skipped
Test _DSS (Device Set State). 8 passed
Test _DGS (Query Graphics State). 8 passed
Test _DOD (Enumerate All Devices Attached to Display.. 1 passed
Test _DOS (Enable/Disable Output Switching). 1 passed
Test _GPD (Get POST Device). 1 skipped
Test _ROM (Get ROM Data). 1 skipped
Test _SPD (Set POST Device). 1 skipped
Test _VPO (Video POST Options). 1 skipped
Test _CBA (Configuration Base Address). 1 skipped
Test _IFT (IPMI Interface Type). 1 skipped
Test _SRV (IPMI Interface Revision). 1 skipped
root@larry-li-Latitude-5590:/home/larry-li#
另外澄清一下，我的电脑应该不支持S3
root@larry-li-Latitude-5590:/home/larry-li# cat /sys/power/mem_sleep
[s2idle]
root@larry-li-Latitude-5590:/home/larry-li#
** Attachment added: "补充信息"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+attachment/5949684/+files/results.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141985
Title:
Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
Status in linux package in Ubuntu:
New
Bug description:
硬件型号：Dell Latitude 5590
系统版本：Ubuntu 25.10
内核版本：6.17.0-14-generic
问题描述：
执行 systemctl suspend、合盖后或按下 Super+L时，系统进入睡眠（效果类似于 shutdown -H now），黑屏且无法唤醒，只能长按电源键强制重启。
已尝试的修复措施：
更新 BIOS 到最新版本（通过 Dell 官网下载的 .rcv 文件更新）。
在GRUB内核参数中添加：
acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux acpi_osi="!Windows 2020"
确认系统支持S3,cat /sys/power/state 输出包含 mem
larry-li@larry-li-Latitude-5590:~$ cat /sys/power/state
freeze mem
larry-li@larry-li-Latitude-5590:~$
附加信息：
该问题在同一电脑 Ubuntu 24.04、Ubuntu 25.10，内核 6.14或6.17上均存在，可能与 ACPI 实现有关，另外这台电脑是通过Ubuntu的启动盘装的系统，预装Windows 10，但已被Ubuntu替代。
相关日志已通过 ubuntu-bug linux 自动收集并附加。
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: larry-li 2570 F.... wireplumber
/dev/snd/controlC1: larry-li 2570 F.... wireplumber
/dev/snd/seq: larry-li 2551 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:20:00 2026
InstallationDate: Installed on 2026-02-13 (4 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:082b Logitech, Inc. Webcam C170
Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
Bus 001 Device 004: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=e880bf76-78c5-450e-b1aa-c147ded3f816 ro quiet splash acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux "acpi_osi=!Windows 2020" crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-16 (1 days ago)
dmi.bios.date: 04/09/2025
dmi.bios.release: 1.41
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.41.0
dmi.board.name: 0MM81M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd04/09/2025:br1.41:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0MM81M:rvrA00:cvnDellInc.:ct10:cvr:sku0817:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+subscriptions
root@larry-li-Latitude-5590:/home/larry-li# sudo fwts acpidump
Running 1 tests, results appended to results.log
Test: Dump ACPI tables.
Dump ACPI tables. 1 info only
root@larry-li-Latitude-5590:/home/larry-li# sudo fwts method
Running 1 tests, results appended to results.log
Test: ACPI DSDT Method Semantic tests.
Test Method Names. 1 passed
Test _AEI. 1 skipped
Test _EVT (Event Method). 1 skipped
Test _DLM (Device Lock Mutex). 1 skipped
Test _PIC (Inform AML of Interrupt Model). 3 passed
Test _CID (Compatible ID). 14 passed
Test _CLS (Class Code). 1 skipped
Test _DDN (DOS Device Name). 6 passed
Test _HID (Hardware ID). 78 passed, 1 failed
Test _HRV (Hardware Revision Number). 11 passed
Test _MLS (Multiple Language String). 1 passed
Test _PLD (Physical Device Location). 21 passed
Test _SUB (Subsystem ID). 1 skipped
Test _SUN (Slot User Number). 1 skipped
Test _STR (String). 8 passed
Test _UID (Unique ID). 41 passed
Test _CDM (Clock Domain). 1 skipped
Test _CRS (Current Resource Settings). 53 passed
Test _DSD (Device Specific Data). 1 skipped
Test _DIS (Disable). 8 passed
Test _DMA (Direct Memory Access). 1 skipped
Test _FIX (Fixed Register Resource Provider). 1 skipped
Test _GSB (Global System Interrupt Base). 1 skipped
Test _HPP (Hot Plug Parameters). 1 skipped
Test _MAT (Multiple APIC Table Entry). 1 skipped
Test _PRS (Possible Resource Settings). 10 passed
Test _PRT (PCI Routing Table). 28 passed
Test _PXM (Proximity). 1 skipped
Test _SLI (System Locality Information). 1 skipped
Test _CCA (Cache Coherency Attribute). 1 skipped
Test _EDL (Eject Device List). 1 skipped
Test _EJD (Ejection Dependent Device). 1 skipped
Test _EJ0 (Eject). 1 skipped
Test _EJ1 (Eject). 1 skipped
Test _EJ2 (Eject). 1 skipped
Test _EJ3 (Eject). 1 skipped
Test _EJ4 (Eject). 1 skipped
Test _LCK (Lock). 1 skipped
Test _RMV (Remove). 24 passed
Test _STA (Status). 69 passed
Test _DEP (Operational Region Dependencies). 38 passed
Test _FIT (Firmware Interface Table). 1 skipped
Test _BDN (BIOS Dock Name). 1 skipped
Test _BBN (Base Bus Number). 1 passed
Test _DCK (Dock). 1 skipped
Test _INI (Initialize). 38 passed
Test _GLK (Global Lock). 1 skipped
Test _SEG (Segment). 1 skipped
Test _LSI (Label Storage Information). 1 skipped
Test _CBR (CXL Host Bridge Register). 1 skipped
Test _OFF (Set resource off). 1 skipped
Test _ON_ (Set resource on). 1 skipped
Test _DSW (Device Sleep Wake). 3 passed
Test _IRC (In Rush Current). 1 skipped
Test _PRE (Power Resources for Enumeration). 1 skipped
Test _PR0 (Power Resources for D0). 1 skipped
Test _PR1 (Power Resources for D1). 1 skipped
Test _PR2 (Power Resources for D2). 1 skipped
Test _PR3 (Power Resources for D3). 1 skipped
Test _PRW (Power Resources for Wake). 54 passed
Test _PS0 (Power State 0). 15 passed
Test _PS1 (Power State 1). 1 skipped
Test _PS2 (Power State 2). 1 passed
Test _PS3 (Power State 3). 15 passed
Test _PSC (Power State Current). 11 passed
Test _PSE (Power State for Enumeration). 1 skipped
Test _PSW (Power State Wake). 3 passed
Test _S1D (S1 Device State). 1 skipped
Test _S2D (S2 Device State). 1 skipped
Test _S3D (S3 Device State). 1 passed
Test _S4D (S4 Device State). 1 passed
Test _S0W (S0 Device Wake State). 7 passed
Test _S1W (S1 Device Wake State). 1 skipped
Test _S2W (S2 Device Wake State). 1 skipped
Test _S3W (S3 Device Wake State). 1 passed
Test _S4W (S4 Device Wake State). 1 passed
Test _RST (Device Reset). 1 skipped
Test _PRR (Power Resource for Reset). 1 skipped
Test _DSC (Deepest State for Configuration). 1 skipped
Test _S0_ (S0 System State). 1 passed
Test _S1_ (S1 System State). 1 skipped
Test _S2_ (S2 System State). 1 skipped
Test _S3_ (S3 System State). 1 skipped
Test _S4_ (S4 System State). 1 passed
Test _S5_ (S5 System State). 1 passed
Test _SWS (System Wake Source). 1 skipped
Test _PSS (Performance Supported States). 17 passed
Test _CPC (Continuous Performance Control). 15 failed
Test _CSD (C State Dependencies). 1 skipped
Test _CST (C States). 16 passed
Test _PCT (Performance Control). 16 passed
Test _PDL (P-State Depth Limit). 1 passed
Test _PPC (Performance Present Capabilities). 17 passed
Test _PPE (Polling for Platform Error). 1 skipped
Test _PSD (Power State Dependencies). 16 passed
Test _PTC (Processor Throttling Control). 1 passed
Test _TDL (T-State Depth Limit). 1 passed
Test _TPC (Throttling Present Capabilities). 1 passed
Test _TSD (Throttling State Dependencies). 2 failed
Test _TSS (Throttling Supported States). 2 failed
Test _LPI (Low Power Idle States). 1 skipped
Test _RDI (Resource Dependencies for Idle). 1 skipped
Test _PUR (Processor Utilization Request). 1 passed
Test _MSG (Message). 1 skipped
Test _SST (System Status). 1 skipped
Test _ALC (Ambient Light Colour Chromaticity). 1 skipped
Test _ALI (Ambient Light Illuminance). 1 passed
Test _ALT (Ambient Light Temperature). 1 skipped
Test _ALP (Ambient Light Polling). 1 skipped
Test _ALR (Ambient Light Response). 1 passed
Test _LID (Lid Status). 1 passed
Test _GTF (Get Task File). 5 passed
Test _GTM (Get Timing Mode). 1 passed
Test _MBM (Memory Bandwidth Monitoring Data). 1 skipped
Test _UPC (USB Port Capabilities). 19 passed
Test _PDO (USB Power Data Object). 1 skipped
Test _UPD (User Presence Detect). 1 skipped
Test _UPP (User Presence Polling). 1 skipped
Test _GCP (Get Capabilities). 1 skipped
Test _GRT (Get Real Time). 1 skipped
Test _GWS (Get Wake Status). 1 skipped
Test _CWS (Clear Wake Status). 1 skipped
Test _SRT (Set Real Time). 1 skipped
Test _STP (Set Expired Timer Wake Policy). 1 skipped
Test _STV (Set Timer Value). 1 skipped
Test _TIP (Expired Timer Wake Policy). 1 skipped
Test _TIV (Timer Values). 1 skipped
Test _NBS (NVDIMM Boot Status). 1 skipped
Test _NCH (NVDIMM Current Health Information). 1 skipped
Test _NIC (NVDIMM Health Error Injection Capabilities) 1 skipped
Test _NIH (NVDIMM Inject/Clear Health Errors). 1 skipped
Test _NIG (NVDIMM Inject Health Error Status). 1 skipped
Test _SBS (Smart Battery Subsystem). 1 skipped
Test _BCT (Battery Charge Time). 1 skipped
Test _BIF (Battery Information). 2 passed
Test _BIX (Battery Information Extended). 1 skipped
Test _BMA (Battery Measurement Averaging). 1 skipped
Test _BMC (Battery Maintenance Control). 1 skipped
Test _BMD (Battery Maintenance Data). 1 skipped
Test _BMS (Battery Measurement Sampling Time). 1 skipped
Test _BPC (Battery Power Characteristics). 1 skipped
Test _BPS (Battery Power State). 1 skipped
Test _BPT (Battery Power Threshold). 1 skipped
Test _BST (Battery Status). 2 passed
Test _BTP (Battery Trip Point). 1 skipped
Test _BTH (Battery Throttle Limit). 1 skipped
Test _BTM (Battery Time). 1 skipped
Test _PCL (Power Consumer List). 3 passed
Test _PIF (Power Source Information). 1 skipped
Test _PRL (Power Source Redundancy List). 1 skipped
Test _PSR (Power Source). 1 passed
Test _GAI (Get Averaging Level). 1 skipped
Test _GHL (Get Hardware Limit). 1 skipped
Test _PMC (Power Meter Capabilities). 1 skipped
Test _PMD (Power Meter Devices). 1 skipped
Test _PMM (Power Meter Measurement). 1 skipped
Test _WPC (Wireless Power Calibration). 1 skipped
Test _WPP (Wireless Power Polling). 1 skipped
Test _FIF (Fan Information). 1 skipped
Test _FPS (Fan Performance States). 1 skipped
Test _FSL (Fan Set Level). 1 skipped
Test _FST (Fan Status). 1 skipped
Test _ACx (Active Cooling). 4 passed, 8 skipped
Test _ART (Active Cooling Relationship Table). 1 skipped
Test _ALx (Active List). 10 skipped
Test _CRT (Critical Trip Point). 6 passed
Test _CR3 (Warm/Standby Temperature). 5 passed
Test _DTI (Device Temperature Indication). 5 passed
Test _HOT (Hot Temperature). 5 passed
Test _MTL (Minimum Throttle Limit). 1 skipped
Test _NTT (Notification Temp Threshold). 5 passed
Test _PSL (Passive List). 1 skipped
Test _PSV (Passive Temp). 5 passed
Test _RTV (Relative Temp Values). 1 skipped
Test _SCP (Set Cooling Policy). 20 passed
Test _TC1 (Thermal Constant 1). 1 skipped
Test _TC2 (Thermal Constant 2). 1 skipped
Test _TFP (Thermal fast Sampling Period). 1 skipped
Test _TMP (Thermal Zone Current Temp). 6 passed
Test _TPT (Trip Point Temperature). 1 skipped
Test _TRT (Thermal Relationship Table). 1 passed
Test _TSN (Thermal Sensor Device). 1 skipped
Test _TSP (Thermal Sampling Period). 4 passed
Test _TST (Temperature Sensor Threshold). 1 skipped
Test _TZD (Thermal Zone Devices). 1 skipped
Test _TZM (Thermal Zone member). 1 skipped
Test _TZP (Thermal Zone Polling). 1 skipped
Test _GPE (General Purpose Events). 1 passed
Test _EC_ (EC Offset Query). 1 skipped
Test _PTS (Prepare to Sleep). 2 passed
Test _TTS (Transition to State). 1 skipped
Test _WAK (System Wake). 2 passed
Test _ADR (Return Unique ID for Device). 114 passed
Test _BCL (Query List of Brightness Control Levels S.. 1 passed
Test _BCM (Set Brightness Level). 1 passed
Test _BQC (Brightness Query Current Level). 1 passed
Test _DCS (Return the Status of Output Device). 8 passed
Test _DDC (Return the EDID for this Device). 1 skipped
Test _DSS (Device Set State). 8 passed
Test _DGS (Query Graphics State). 8 passed
Test _DOD (Enumerate All Devices Attached to Display.. 1 passed
Test _DOS (Enable/Disable Output Switching). 1 passed
Test _GPD (Get POST Device). 1 skipped
Test _ROM (Get ROM Data). 1 skipped
Test _SPD (Set POST Device). 1 skipped
Test _VPO (Video POST Options). 1 skipped
Test _CBA (Configuration Base Address). 1 skipped
Test _IFT (IPMI Interface Type). 1 skipped
Test _SRV (IPMI Interface Revision). 1 skipped
root@larry-li-Latitude-5590:/home/larry-li#
另外澄清一下，我的电脑应该不支持S3
root@larry-li-Latitude-5590:/home/larry-li# cat /sys/power/mem_sleep
[s2idle]
root@larry-li-Latitude-5590:/home/larry-li#
** Attachment added: "补充信息"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+attachment/5949684/+files/results.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141985
Title:
Dell Latitude5590 Ubuntu25.10中按下Super+L会睡眠且无法唤醒
Status in linux package in Ubuntu:
New
Bug description:
硬件型号：Dell Latitude 5590
系统版本：Ubuntu 25.10
内核版本：6.17.0-14-generic
问题描述：
执行 systemctl suspend、合盖后或按下 Super+L时，系统进入睡眠（效果类似于 shutdown -H now），黑屏且无法唤醒，只能长按电源键强制重启。
已尝试的修复措施：
更新 BIOS 到最新版本（通过 Dell 官网下载的 .rcv 文件更新）。
在GRUB内核参数中添加：
acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux acpi_osi="!Windows 2020"
确认系统支持S3,cat /sys/power/state 输出包含 mem
larry-li@larry-li-Latitude-5590:~$ cat /sys/power/state
freeze mem
larry-li@larry-li-Latitude-5590:~$
附加信息：
该问题在同一电脑 Ubuntu 24.04、Ubuntu 25.10，内核 6.14或6.17上均存在，可能与 ACPI 实现有关，另外这台电脑是通过Ubuntu的启动盘装的系统，预装Windows 10，但已被Ubuntu替代。
相关日志已通过 ubuntu-bug linux 自动收集并附加。
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: larry-li 2570 F.... wireplumber
/dev/snd/controlC1: larry-li 2570 F.... wireplumber
/dev/snd/seq: larry-li 2551 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:20:00 2026
InstallationDate: Installed on 2026-02-13 (4 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:082b Logitech, Inc. Webcam C170
Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
Bus 001 Device 004: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=e880bf76-78c5-450e-b1aa-c147ded3f816 ro quiet splash acpi_sleep=s3_mode acpi_sleep=s3_bios acpi_osi=Linux "acpi_osi=!Windows 2020" crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-16 (1 days ago)
dmi.bios.date: 04/09/2025
dmi.bios.release: 1.41
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.41.0
dmi.board.name: 0MM81M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd04/09/2025:br1.41:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0MM81M:rvrA00:cvnDellInc.:ct10:cvr:sku0817:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141985/+subscriptions
[Bug 2142693] Re: [26.04] Please test secureboot and lock-down with 7.0.0 kernel (s390x) on Resolute Raccoon
Hello Thorsten, many thanks for re-testing.
The outcome is like expected then - great !
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => 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/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:
Fix Released
Status in linux package in Ubuntu:
Fix Released
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 outcome is like expected then - great !
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => 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/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:
Fix Released
Status in linux package in Ubuntu:
Fix Released
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 2142693] Comment bridged from LTC Bugzilla
------- Comment From thorsten.diehl@de.ibm.com 2026-03-02 05:45 EDT-------
I upgraded to kernel 7.0.0-2-generic as described and rebooted. System could be IPLed as expected from DASD.
Secure Boot:
1. With production key only, I got "Signature verification failure for component 3" - expected, OK, DASD part
2. With development unstable PPA key only, I got "Signature verification failure for component 1" - expected, OK, zipl part
3. With both of the above keys I was able to securely boot the LPAR with kernel 7.0.0-2 from DASD, as expected.
root@a83lp32:~# uname -a
Linux a83lp32.lnxne.boe 7.0.0-2-generic #2-Ubuntu SMP PREEMPT Fri Feb 27 10:24:48 UTC 2026 s390x GNU/Linux
root@a83lp32:~# lsreipl
Re-IPL type: eckd
Device: 0.0.7e65
bootprog: 0
br_chr: auto
Bootparm: ""
Loadparm: ""
clear: 0
Secure boot: 1
root@a83lp32:~#
--
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
I upgraded to kernel 7.0.0-2-generic as described and rebooted. System could be IPLed as expected from DASD.
Secure Boot:
1. With production key only, I got "Signature verification failure for component 3" - expected, OK, DASD part
2. With development unstable PPA key only, I got "Signature verification failure for component 1" - expected, OK, zipl part
3. With both of the above keys I was able to securely boot the LPAR with kernel 7.0.0-2 from DASD, as expected.
root@a83lp32:~# uname -a
Linux a83lp32.lnxne.boe 7.0.0-2-generic #2-Ubuntu SMP PREEMPT Fri Feb 27 10:24:48 UTC 2026 s390x GNU/Linux
root@a83lp32:~# lsreipl
Re-IPL type: eckd
Device: 0.0.7e65
bootprog: 0
br_chr: auto
Bootparm: ""
Loadparm: ""
clear: 0
Secure boot: 1
root@a83lp32:~#
--
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
Подписаться на:
Комментарии (Atom)