This bug is awaiting verification that the linux-intel/6.17.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2129812
Title:
bareudp.sh in ubuntu_kselftests_net fails because of dash default
shell
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Questing:
Fix Committed
Bug description:
[ Impact ]
In bareudp.sh, this script uses /bin/sh and it will load another lib.sh
BASH script at the very beginning.
But on some operating systems like Ubuntu, /bin/sh is actually pointed to
DASH, thus it will try to run BASH commands with DASH and consequently
leads to syntax issues:
# ./bareudp.sh: 4: ./lib.sh: Bad substitution
# ./bareudp.sh: 5: ./lib.sh: source: not found
# ./bareudp.sh: 24: ./lib.sh: Syntax error: "(" unexpected
Fix this by explicitly using BASH for bareudp.sh. This fixes test
execution failures on systems where /bin/sh is not BASH.
[ Test Plan ]
Run the bareudp.sh with this patch applied, the syntax issues above will
be fixed and the test can proceed.
[ Where problems could occur ]
The change has been applied upstream and 6.17.10, it can be cherry-picked
the scope is limited to the test script itself, with no functional changes
to the kernel.
We may discover new failures through this test. Even if this change is
incorrect, it should not make anything worse, as the test has already
been blocked by this syntax issue.
== Original bug report ==
bareudp.sh execution fails on questing because the shebang /bin/sh under ubuntu points to dash.
Explicitly changing to /bin/bash fixes the issue
20052 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 4: ./lib.sh: Bad substitution
20053 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 5: ./lib.sh: source: not found
20054 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 24: ./lib.sh: Syntax error: "(" unexpected
Full Log:
20041 13:57:36 INFO | START ubuntu_kselftests_net.net:bareudp.sh ubuntu_kselftests_net.net:bareudp.sh timeout=2700 timestamp=1760968656 localtime=Oct 20 13:57:36
20042 13:57:36 DEBUG| Persistent state client._record_indent now set to 2
20043 13:57:36 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_kselftests_net.net:bareudp.sh', 'ubuntu_kselftests_net.net:bareudp.sh')
20044 13:57:36 DEBUG| Waiting for pid 1348605 for 2700 seconds
20045 13:57:36 WARNI| System python is too old, crash handling disabled
20046 13:57:36 DEBUG| Running 'make run_tests -C net TEST_PROGS=bareudp.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
20047 13:57:36 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
20048 13:57:36 DEBUG| [stdout] TAP version 13
20049 13:57:36 DEBUG| [stdout] 1..1
20050 13:57:36 DEBUG| [stdout] # timeout set to 0
20051 13:57:36 DEBUG| [stdout] # selftests: net: bareudp.sh
20052 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 4: ./lib.sh: Bad substitution
20053 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 5: ./lib.sh: source: not found
20054 13:57:37 DEBUG| [stdout] # ./bareudp.sh: 24: ./lib.sh: Syntax error: "(" unexpected
20055 13:57:37 DEBUG| [stdout] not ok 1 selftests: net: bareudp.sh # exit=2
20056 13:57:37 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
20057 13:57:37 ERROR| Exception escaping from test:
20058 Traceback (most recent call last):
20059 File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
20060 _call_test_function(self.execute, *p_args, **p_dargs)
20061 ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20062 File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
20063 return func(*args, **dargs)
20064 File "/home/ubuntu/autotest/client/shared/test.py", line 290, in execute
20065 self._call_run_once(constraints, profile_only,
20066 ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
20067 postprocess_profiled_run, args, dargs)
20068 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20069 File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
20070 self.run_once(*args, **dargs)
20071 ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
20072 File "/home/ubuntu/autotest/client/tests/ubuntu_kselftests_net/ubuntu_kselftests_net.py", line 174, in run_once
20073 raise error.TestError(test_name + ' failed.')
20074 autotest.client.shared.error.TestError: net:bareudp.sh failed.
20075 13:57:37 ERROR| child process failed
20076 13:57:37 DEBUG| Traceback (most recent call last):
20077 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
20078 13:57:37 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
20079 13:57:37 DEBUG| ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20080 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
20081 13:57:37 DEBUG| return func(*args, **dargs)
20082 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 290, in execute
20083 13:57:37 DEBUG| self._call_run_once(constraints, profile_only,
20084 13:57:37 DEBUG| ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
20085 13:57:37 DEBUG| postprocess_profiled_run, args, dargs)
20086 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20087 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
20088 13:57:37 DEBUG| self.run_once(*args, **dargs)
20089 13:57:37 DEBUG| ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
20090 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/tests/ubuntu_kselftests_net/ubuntu_kselftests_net.py", line 174, in run_once
20091 13:57:37 DEBUG| raise error.TestError(test_name + ' failed.')
20092 13:57:37 DEBUG| autotest.client.shared.error.TestError: net:bareudp.sh failed.
20093 13:57:37 DEBUG|
20094 13:57:37 DEBUG| During handling of the above exception, another exception occurred:
20095 13:57:37 DEBUG|
20096 13:57:37 DEBUG| Traceback (most recent call last):
20097 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25, in fork_start
20098 13:57:37 DEBUG| l()
20099 13:57:37 DEBUG| ~^^
20100 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 506, in
20101 13:57:37 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
20102 13:57:37 DEBUG| ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20103 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 121, in runtest
20104 13:57:37 DEBUG| common_test.runtest(job, url, tag, args, dargs, locals(), globals(),
20105 13:57:37 DEBUG| ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20106 13:57:37 DEBUG| job.sysinfo.log_before_each_test,
20107 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20108 13:57:37 DEBUG| job.sysinfo.log_after_each_test,
20109 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20110 13:57:37 DEBUG| job.sysinfo.log_before_each_iteration,
20111 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20112 13:57:37 DEBUG| job.sysinfo.log_after_each_iteration)
20113 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20114 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 913, in runtest
20115 13:57:37 DEBUG| mytest._exec(args, dargs)
20116 13:57:37 DEBUG| ~~~~~~~~~~~~^^^^^^^^^^^^^
20117 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 434, in _exec
20118 13:57:37 DEBUG| raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
20119 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
20120 13:57:37 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
20121 13:57:37 DEBUG| ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20122 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
20123 13:57:37 DEBUG| return func(*args, **dargs)
20124 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 290, in execute
20125 13:57:37 DEBUG| self._call_run_once(constraints, profile_only,
20126 13:57:37 DEBUG| ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
20127 13:57:37 DEBUG| postprocess_profiled_run, args, dargs)
20128 13:57:37 DEBUG| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
20129 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
20130 13:57:37 DEBUG| self.run_once(*args, **dargs)
20131 13:57:37 DEBUG| ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
20132 13:57:37 DEBUG| File "/home/ubuntu/autotest/client/tests/ubuntu_kselftests_net/ubuntu_kselftests_net.py", line 174, in run_once
20133 13:57:37 DEBUG| raise error.TestError(test_name + ' failed.')
20134 13:57:37 DEBUG| autotest.client.shared.error.TestError: net:bareudp.sh failed.
20135 13:57:38 INFO | ERROR ubuntu_kselftests_net.net:bareudp.sh ubuntu_kselftests_net.net:bareudp.sh timestamp=1760968658 localtime=Oct 20 13:57:38 net:bareudp.sh failed.
20136 13:57:38 INFO | END ERROR ubuntu_kselftests_net.net:bareudp.sh
ubuntu_kselftests_net.net:bareudp.sh timestamp=1760968658
localtime=Oct 20 13:57:38
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2129812/+subscriptions
воскресенье
[Bug 2136820] Re: ubuntu_kselftests:_net/net:gre_gso.sh failing
This bug is awaiting verification that the linux-intel/6.17.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136820
Title:
ubuntu_kselftests:_net/net:gre_gso.sh failing
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Committed
Status in linux source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
rarely gre_gso.sh fails with socat getting killed by signal 15. Note
that in the log below two "exiting on signal 15" are ok. The first one
should not be there.
1002773 01:08:59 DEBUG| Running 'make run_tests -C net TEST_PROGS=gre_gso.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
1002774 01:08:59 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
1002775 01:08:59 DEBUG| [stdout] TAP version 13
1002776 01:08:59 DEBUG| [stdout] 1..1
1002777 01:08:59 DEBUG| [stdout] # timeout set to 0
1002778 01:08:59 DEBUG| [stdout] # selftests: net: gre_gso.sh
1002779 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689576] W exiting on signal 15
1002780 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ TSO [FAIL]
1002781 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ GSO [ OK ]
1002782 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689568] W exiting on signal 15
1002783 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ TSO [ OK ]
1002784 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ GSO [ OK ]
1002785 01:09:03 DEBUG| [stdout] # 2025/11/28 01:09:03 socat[689583] W exiting on signal 15
1002786 01:09:03 DEBUG| [stdout] #
1002787 01:09:03 DEBUG| [stdout] # Tests passed: 3
1002788 01:09:03 DEBUG| [stdout] # Tests failed: 1
1002789 01:09:03 DEBUG| [stdout] not ok 1 selftests: net: gre_gso.sh # exit=1
This is most likely timing issue.
[Fix]
This can be mitigated by increasing timeout for socat from 1 to 3
seconds.
[Test Plan]
Run the test in a loop many times
[What could go wrong]
This is not a change to the kernel code but tests. The timeout does
not increase test duration when everything is fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2136820/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136820
Title:
ubuntu_kselftests:_net/net:gre_gso.sh failing
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Committed
Status in linux source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
rarely gre_gso.sh fails with socat getting killed by signal 15. Note
that in the log below two "exiting on signal 15" are ok. The first one
should not be there.
1002773 01:08:59 DEBUG| Running 'make run_tests -C net TEST_PROGS=gre_gso.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
1002774 01:08:59 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
1002775 01:08:59 DEBUG| [stdout] TAP version 13
1002776 01:08:59 DEBUG| [stdout] 1..1
1002777 01:08:59 DEBUG| [stdout] # timeout set to 0
1002778 01:08:59 DEBUG| [stdout] # selftests: net: gre_gso.sh
1002779 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689576] W exiting on signal 15
1002780 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ TSO [FAIL]
1002781 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ GSO [ OK ]
1002782 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689568] W exiting on signal 15
1002783 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ TSO [ OK ]
1002784 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ GSO [ OK ]
1002785 01:09:03 DEBUG| [stdout] # 2025/11/28 01:09:03 socat[689583] W exiting on signal 15
1002786 01:09:03 DEBUG| [stdout] #
1002787 01:09:03 DEBUG| [stdout] # Tests passed: 3
1002788 01:09:03 DEBUG| [stdout] # Tests failed: 1
1002789 01:09:03 DEBUG| [stdout] not ok 1 selftests: net: gre_gso.sh # exit=1
This is most likely timing issue.
[Fix]
This can be mitigated by increasing timeout for socat from 1 to 3
seconds.
[Test Plan]
Run the test in a loop many times
[What could go wrong]
This is not a change to the kernel code but tests. The timeout does
not increase test duration when everything is fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2136820/+subscriptions
[Bug 2137698] Re: ubuntu_blktrace_smoke_test fails on questing with rust coreutils
This bug is awaiting verification that the linux-intel/6.17.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137698
Title:
ubuntu_blktrace_smoke_test fails on questing with rust coreutils
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Questing:
Fix Committed
Bug description:
ubuntu_blktrace_smoke_test fails on questing with rust coreutils
enabled. Executing with GNU coreutils makes the test pass.
2043 ID: com.canonical.kernel::ubuntu_blktrace_smoke_test/blktrace-smoke-test
2044 Category: com.canonical.plainbox::uncategorised
2045 ... 8< -------------------------------------------------------------------------
2046 PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-6.17.0-11-generic)
2047
2048 Using block device /dev/loop0 for path /tmp/cwd-hmzznri9.43f7bf5d91458d09dc595f27a2105298dbd7be4196a6f7444786bd783e1e92a1/mnt
2049
2050 Test regime:
2051 dd performing 65536 1K block writes
2052 looking for at least 1024 blktrace events
2053
2054 Sat Dec 20 19:52:16 UTC 2025: blktrace starting
2055 Sat Dec 20 19:52:16 UTC 2025: dd starting
2056 Sat Dec 20 19:52:16 UTC 2025: dd stopped
2057 Sat Dec 20 19:52:16 UTC 2025: waiting for 10 seconds
2058 Sat Dec 20 19:52:26 UTC 2025: blktrace being terminated
2059 Sat Dec 20 19:52:26 UTC 2025: blktrace terminated
2060 Sat Dec 20 19:52:26 UTC 2025: blktrace data parsed
2061
2062 FAILED (expecting at least 1024 block traces events from the dd process, got 0)
2063 FAILED (expecting at least 1024 block read traces events, got 0)
2064 FAILED (expecting at least 1024 block write traces events, got 0)
Regressing the issue, this is the breaking commit.
ommit 6c840c16c7cc0d3464ebf4a6d4c4f03763a45ff0
Author: Jan Kara <jack@suse.cz>
Date: Mon Sep 1 13:27:40 2025 +0200
ext4: fail unaligned direct IO write with EINVAL
BugLink: https://bugs.launchpad.net/bugs/2131259
commit 963845748fe67125006859229487b45485564db7 upstream.
Commit bc264fea0f6f ("iomap: support incremental iomap_iter advances")
changed the error handling logic in iomap_iter(). Previously any error
from iomap_dio_bio_iter() got propagated to userspace, after this commit
if ->iomap_end returns error, it gets propagated to userspace instead of
an error from iomap_dio_bio_iter(). This results in unaligned writes to
ext4 to silently fallback to buffered IO instead of erroring out.
Now returning ENOTBLK for DIO writes from ext4_iomap_end() seems
unnecessary these days. It is enough to return ENOTBLK from
ext4_iomap_begin() when we don't support DIO write for that particular
file offset (due to hole).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2137698/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-questing-linux-intel' to 'verification-done-
questing-linux-intel'. If the problem still exists, change the tag
'verification-needed-questing-linux-intel' to 'verification-failed-
questing-linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-questing-linux-intel-v2 verification-needed-questing-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137698
Title:
ubuntu_blktrace_smoke_test fails on questing with rust coreutils
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Questing:
Fix Committed
Bug description:
ubuntu_blktrace_smoke_test fails on questing with rust coreutils
enabled. Executing with GNU coreutils makes the test pass.
2043 ID: com.canonical.kernel::ubuntu_blktrace_smoke_test/blktrace-smoke-test
2044 Category: com.canonical.plainbox::uncategorised
2045 ... 8< -------------------------------------------------------------------------
2046 PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-6.17.0-11-generic)
2047
2048 Using block device /dev/loop0 for path /tmp/cwd-hmzznri9.43f7bf5d91458d09dc595f27a2105298dbd7be4196a6f7444786bd783e1e92a1/mnt
2049
2050 Test regime:
2051 dd performing 65536 1K block writes
2052 looking for at least 1024 blktrace events
2053
2054 Sat Dec 20 19:52:16 UTC 2025: blktrace starting
2055 Sat Dec 20 19:52:16 UTC 2025: dd starting
2056 Sat Dec 20 19:52:16 UTC 2025: dd stopped
2057 Sat Dec 20 19:52:16 UTC 2025: waiting for 10 seconds
2058 Sat Dec 20 19:52:26 UTC 2025: blktrace being terminated
2059 Sat Dec 20 19:52:26 UTC 2025: blktrace terminated
2060 Sat Dec 20 19:52:26 UTC 2025: blktrace data parsed
2061
2062 FAILED (expecting at least 1024 block traces events from the dd process, got 0)
2063 FAILED (expecting at least 1024 block read traces events, got 0)
2064 FAILED (expecting at least 1024 block write traces events, got 0)
Regressing the issue, this is the breaking commit.
ommit 6c840c16c7cc0d3464ebf4a6d4c4f03763a45ff0
Author: Jan Kara <jack@suse.cz>
Date: Mon Sep 1 13:27:40 2025 +0200
ext4: fail unaligned direct IO write with EINVAL
BugLink: https://bugs.launchpad.net/bugs/2131259
commit 963845748fe67125006859229487b45485564db7 upstream.
Commit bc264fea0f6f ("iomap: support incremental iomap_iter advances")
changed the error handling logic in iomap_iter(). Previously any error
from iomap_dio_bio_iter() got propagated to userspace, after this commit
if ->iomap_end returns error, it gets propagated to userspace instead of
an error from iomap_dio_bio_iter(). This results in unaligned writes to
ext4 to silently fallback to buffered IO instead of erroring out.
Now returning ENOTBLK for DIO writes from ext4_iomap_end() seems
unnecessary these days. It is enough to return ENOTBLK from
ext4_iomap_begin() when we don't support DIO write for that particular
file offset (due to hole).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2137698/+subscriptions
[Bug 2141241] [NEW] "Activation of network connection failed"
Public bug reported:
"Connection failed: Activation of network connection failed" when trying to connect using USB 3.0 Gigabit Ethernet Network Adapter TPLink UE306.
USB 3.10 controller recognized System INFO as: Asics Electronics Corp. AX88179 Gigabit Ethernet (id: 0b95:1790)
Linux Mint 22.3 Cinnamon 64 bit
Kernel 6.17.0-14-generic
** 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/2141241
Title:
"Activation of network connection failed"
Status in linux package in Ubuntu:
New
Bug description:
"Connection failed: Activation of network connection failed" when trying to connect using USB 3.0 Gigabit Ethernet Network Adapter TPLink UE306.
USB 3.10 controller recognized System INFO as: Asics Electronics Corp. AX88179 Gigabit Ethernet (id: 0b95:1790)
Linux Mint 22.3 Cinnamon 64 bit
Kernel 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141241/+subscriptions
"Connection failed: Activation of network connection failed" when trying to connect using USB 3.0 Gigabit Ethernet Network Adapter TPLink UE306.
USB 3.10 controller recognized System INFO as: Asics Electronics Corp. AX88179 Gigabit Ethernet (id: 0b95:1790)
Linux Mint 22.3 Cinnamon 64 bit
Kernel 6.17.0-14-generic
** 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/2141241
Title:
"Activation of network connection failed"
Status in linux package in Ubuntu:
New
Bug description:
"Connection failed: Activation of network connection failed" when trying to connect using USB 3.0 Gigabit Ethernet Network Adapter TPLink UE306.
USB 3.10 controller recognized System INFO as: Asics Electronics Corp. AX88179 Gigabit Ethernet (id: 0b95:1790)
Linux Mint 22.3 Cinnamon 64 bit
Kernel 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141241/+subscriptions
[Bug 2138328] Re: linux-tools: consider linking perf against LLVM
re-applied in git
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2138328
Title:
linux-tools: consider linking perf against LLVM
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Currently the perf tool has 3 possible ways of converting addresses into source code line numbers:
- LLVM library
- BFD library
- addr2line executable
In Ubuntu, perf is not built with LLVM or libbfd, so it falls back to using "addr2line". On large binaries this runs extremely slow and gives errors, making it effectively unusable. This is a longstanding issue; for some context and previous reports see
- https://michcioperz.com/post/slow-perf-script/
- https://github.com/flamegraph-rs/flamegraph/issues/74
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815
- bug 1894407
The option of linking with BFD was rejected in bug 1894407. The
possibility of linking with LLVM is a newer option, with the upstream
support being added in Sep 2024; see the upstream commit message
describing why it is now recommended as the primary choice:
https://github.com/torvalds/linux/commit/c3f8644c21df9b7db97eb70e08e2826368aaafa0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138328/+subscriptions
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2138328
Title:
linux-tools: consider linking perf against LLVM
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Currently the perf tool has 3 possible ways of converting addresses into source code line numbers:
- LLVM library
- BFD library
- addr2line executable
In Ubuntu, perf is not built with LLVM or libbfd, so it falls back to using "addr2line". On large binaries this runs extremely slow and gives errors, making it effectively unusable. This is a longstanding issue; for some context and previous reports see
- https://michcioperz.com/post/slow-perf-script/
- https://github.com/flamegraph-rs/flamegraph/issues/74
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815
- bug 1894407
The option of linking with BFD was rejected in bug 1894407. The
possibility of linking with LLVM is a newer option, with the upstream
support being added in Sep 2024; see the upstream commit message
describing why it is now recommended as the primary choice:
https://github.com/torvalds/linux/commit/c3f8644c21df9b7db97eb70e08e2826368aaafa0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138328/+subscriptions
[Bug 2141234] [NEW] RTL8153 powersave quirk no longer works as expected
Public bug reported:
RTL8153 has some stupid default powersave settings that prevent a link
by default.
I was required to add
usbcore.quirks=0bda:8153:k
to my kernel commandline to revert back to the behavior seen since 6.8
in 24.04, through 6.17 in the latest version I had upgraded to before
switching to amd64v3 variant 26.04 on February 6th 2026.
Not sure where the quirk went, but the device won't function normally
without the kernel commandline.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-6.18.0-9-generic 6.18.0-9.9
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mike 239610 F.... pipewire
mike 239611 F.... wireplumber
/dev/snd/pcmC0D3p: mike 239610 F...m pipewire
/dev/snd/seq: mike 239610 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Feb 8 07:00:26 2026
Dependencies: wireless-regdb 2025.10.07-0ubuntu1
InstallationDate: Installed on 2024-05-10 (639 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Zenbook S 13 UX5304VA_UX5304VA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fu8mf4@/vmlinuz-6.18.0-9-generic root=ZFS=rpool/ROOT/ubuntu_fu8mf4 ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-01-19 (20 days ago)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX5304VA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX5304VA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX5304VA.305:bd11/20/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnZenbookS13UX5304VA_UX5304VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX5304VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook S 13 UX5304VA_UX5304VA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141234
Title:
RTL8153 powersave quirk no longer works as expected
Status in linux package in Ubuntu:
New
Bug description:
RTL8153 has some stupid default powersave settings that prevent a link
by default.
I was required to add
usbcore.quirks=0bda:8153:k
to my kernel commandline to revert back to the behavior seen since 6.8
in 24.04, through 6.17 in the latest version I had upgraded to before
switching to amd64v3 variant 26.04 on February 6th 2026.
Not sure where the quirk went, but the device won't function normally
without the kernel commandline.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-6.18.0-9-generic 6.18.0-9.9
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mike 239610 F.... pipewire
mike 239611 F.... wireplumber
/dev/snd/pcmC0D3p: mike 239610 F...m pipewire
/dev/snd/seq: mike 239610 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Feb 8 07:00:26 2026
Dependencies: wireless-regdb 2025.10.07-0ubuntu1
InstallationDate: Installed on 2024-05-10 (639 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Zenbook S 13 UX5304VA_UX5304VA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fu8mf4@/vmlinuz-6.18.0-9-generic root=ZFS=rpool/ROOT/ubuntu_fu8mf4 ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-01-19 (20 days ago)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX5304VA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX5304VA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX5304VA.305:bd11/20/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnZenbookS13UX5304VA_UX5304VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX5304VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook S 13 UX5304VA_UX5304VA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141234/+subscriptions
RTL8153 has some stupid default powersave settings that prevent a link
by default.
I was required to add
usbcore.quirks=0bda:8153:k
to my kernel commandline to revert back to the behavior seen since 6.8
in 24.04, through 6.17 in the latest version I had upgraded to before
switching to amd64v3 variant 26.04 on February 6th 2026.
Not sure where the quirk went, but the device won't function normally
without the kernel commandline.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-6.18.0-9-generic 6.18.0-9.9
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mike 239610 F.... pipewire
mike 239611 F.... wireplumber
/dev/snd/pcmC0D3p: mike 239610 F...m pipewire
/dev/snd/seq: mike 239610 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Feb 8 07:00:26 2026
Dependencies: wireless-regdb 2025.10.07-0ubuntu1
InstallationDate: Installed on 2024-05-10 (639 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Zenbook S 13 UX5304VA_UX5304VA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fu8mf4@/vmlinuz-6.18.0-9-generic root=ZFS=rpool/ROOT/ubuntu_fu8mf4 ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-01-19 (20 days ago)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX5304VA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX5304VA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX5304VA.305:bd11/20/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnZenbookS13UX5304VA_UX5304VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX5304VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook S 13 UX5304VA_UX5304VA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141234
Title:
RTL8153 powersave quirk no longer works as expected
Status in linux package in Ubuntu:
New
Bug description:
RTL8153 has some stupid default powersave settings that prevent a link
by default.
I was required to add
usbcore.quirks=0bda:8153:k
to my kernel commandline to revert back to the behavior seen since 6.8
in 24.04, through 6.17 in the latest version I had upgraded to before
switching to amd64v3 variant 26.04 on February 6th 2026.
Not sure where the quirk went, but the device won't function normally
without the kernel commandline.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-modules-6.18.0-9-generic 6.18.0-9.9
ProcVersionSignature: Ubuntu 6.18.0-9.9-generic 6.18.5
Uname: Linux 6.18.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mike 239610 F.... pipewire
mike 239611 F.... wireplumber
/dev/snd/pcmC0D3p: mike 239610 F...m pipewire
/dev/snd/seq: mike 239610 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Feb 8 07:00:26 2026
Dependencies: wireless-regdb 2025.10.07-0ubuntu1
InstallationDate: Installed on 2024-05-10 (639 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUSTeK COMPUTER INC. Zenbook S 13 UX5304VA_UX5304VA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fu8mf4@/vmlinuz-6.18.0-9-generic root=ZFS=rpool/ROOT/ubuntu_fu8mf4 ro quiet splash usbcore.quirks=0bda:8153:k vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20260108.gitd86b47f7-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-01-19 (20 days ago)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX5304VA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX5304VA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX5304VA.305:bd11/20/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnZenbookS13UX5304VA_UX5304VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX5304VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook S 13 UX5304VA_UX5304VA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141234/+subscriptions
[Bug 2141223] Re: Dummy output is used for sound after last update. I have to call "sudo alsa reload".
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141223
Title:
Dummy output is used for sound after last update. I have to call "sudo
alsa reload".
Status in linux package in Ubuntu:
New
Bug description:
After last update when I reboot the system dummy output is used for sound.
When I call "sudo alsa reload" everything is good again.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10.1
ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: piitr 1486 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Feb 8 11:10:12 2026
InstallationDate: Installed on 2025-10-26 (105 days ago)
InstallationMedia: Xubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: Acer Aspire A315-31
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ivysaur_AP
dmi.board.vendor: APL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd10/17/2017:br1.9:efr1.4:svnAcer:pnAspireA315-31:pvrV1.09:rvnAPL:rnIvysaur_AP:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-31
dmi.product.sku: 0000000000000000
dmi.product.version: V1.09
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141223/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141223
Title:
Dummy output is used for sound after last update. I have to call "sudo
alsa reload".
Status in linux package in Ubuntu:
New
Bug description:
After last update when I reboot the system dummy output is used for sound.
When I call "sudo alsa reload" everything is good again.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10.1
ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: piitr 1486 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Feb 8 11:10:12 2026
InstallationDate: Installed on 2025-10-26 (105 days ago)
InstallationMedia: Xubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: Acer Aspire A315-31
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ivysaur_AP
dmi.board.vendor: APL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd10/17/2017:br1.9:efr1.4:svnAcer:pnAspireA315-31:pvrV1.09:rvnAPL:rnIvysaur_AP:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-31
dmi.product.sku: 0000000000000000
dmi.product.version: V1.09
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141223/+subscriptions
[Bug 2141223] [NEW] Dummy output is used for sound after last update. I have to call "sudo alsa reload".
You have been subscribed to a public bug:
After last update when I reboot the system dummy output is used for sound.
When I call "sudo alsa reload" everything is good again.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10.1
ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: piitr 1486 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Feb 8 11:10:12 2026
InstallationDate: Installed on 2025-10-26 (105 days ago)
InstallationMedia: Xubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: Acer Aspire A315-31
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ivysaur_AP
dmi.board.vendor: APL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd10/17/2017:br1.9:efr1.4:svnAcer:pnAspireA315-31:pvrV1.09:rvnAPL:rnIvysaur_AP:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-31
dmi.product.sku: 0000000000000000
dmi.product.version: V1.09
dmi.sys.vendor: Acer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
Dummy output is used for sound after last update. I have to call "sudo alsa reload".
https://bugs.launchpad.net/bugs/2141223
You received this bug notification because you are subscribed to linux in Ubuntu.
After last update when I reboot the system dummy output is used for sound.
When I call "sudo alsa reload" everything is good again.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10.1
ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: piitr 1486 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Feb 8 11:10:12 2026
InstallationDate: Installed on 2025-10-26 (105 days ago)
InstallationMedia: Xubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: Acer Aspire A315-31
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ivysaur_AP
dmi.board.vendor: APL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd10/17/2017:br1.9:efr1.4:svnAcer:pnAspireA315-31:pvrV1.09:rvnAPL:rnIvysaur_AP:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-31
dmi.product.sku: 0000000000000000
dmi.product.version: V1.09
dmi.sys.vendor: Acer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
Dummy output is used for sound after last update. I have to call "sudo alsa reload".
https://bugs.launchpad.net/bugs/2141223
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2141212] Re: 6.17.0-12-generic Boot Hangs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2141212
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://help.ubuntu.com/community/ReportingBugs.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141212
Title:
6.17.0-12-generic Boot Hangs
Status in linux package in Ubuntu:
New
Bug description:
When booting up Ubuntu 25.10 with kernel 6.17.0-12-generic on a HP
B4HN8UA (Laptop 15-fd0127dx) the boot hangs up with the following
error messages:
skl_hda_dsp_generic skl_hda_generic: ASoC: Parent card not yet available, widget card binding deferred
skl_hda_dsp_generic skl_hda_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
Bluetooth: hci0: Malformed MSFT vendor event: 0x00
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCD.EC0._Q20.PNOT], AE_NOT_FOUND (20250404/psargs-332)
No Local Variables are initialized for Method [_Q20]
No Arguments are initialized for method [_Q20]
ACPI Error: Aborting method \_SB.PC00.LPCD.EC0._Q20 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
These ACPI BIOS errors don't occur when booting kernel
6.17.0-7-generic. I updated the BIOS from F.20 to F.24 to see that
would help, but it didn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141212/+subscriptions
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2141212
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://help.ubuntu.com/community/ReportingBugs.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141212
Title:
6.17.0-12-generic Boot Hangs
Status in linux package in Ubuntu:
New
Bug description:
When booting up Ubuntu 25.10 with kernel 6.17.0-12-generic on a HP
B4HN8UA (Laptop 15-fd0127dx) the boot hangs up with the following
error messages:
skl_hda_dsp_generic skl_hda_generic: ASoC: Parent card not yet available, widget card binding deferred
skl_hda_dsp_generic skl_hda_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
Bluetooth: hci0: Malformed MSFT vendor event: 0x00
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCD.EC0._Q20.PNOT], AE_NOT_FOUND (20250404/psargs-332)
No Local Variables are initialized for Method [_Q20]
No Arguments are initialized for method [_Q20]
ACPI Error: Aborting method \_SB.PC00.LPCD.EC0._Q20 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
These ACPI BIOS errors don't occur when booting kernel
6.17.0-7-generic. I updated the BIOS from F.20 to F.24 to see that
would help, but it didn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141212/+subscriptions
[Bug 2141212] [NEW] 6.17.0-12-generic Boot Hangs
You have been subscribed to a public bug:
When booting up Ubuntu 25.10 with kernel 6.17.0-12-generic on a HP
B4HN8UA (Laptop 15-fd0127dx) the boot hangs up with the following error
messages:
skl_hda_dsp_generic skl_hda_generic: ASoC: Parent card not yet available, widget card binding deferred
skl_hda_dsp_generic skl_hda_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
Bluetooth: hci0: Malformed MSFT vendor event: 0x00
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCD.EC0._Q20.PNOT], AE_NOT_FOUND (20250404/psargs-332)
No Local Variables are initialized for Method [_Q20]
No Arguments are initialized for method [_Q20]
ACPI Error: Aborting method \_SB.PC00.LPCD.EC0._Q20 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
These ACPI BIOS errors don't occur when booting kernel 6.17.0-7-generic.
I updated the BIOS from F.20 to F.24 to see that would help, but it
didn't.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
6.17.0-12-generic Boot Hangs
https://bugs.launchpad.net/bugs/2141212
You received this bug notification because you are subscribed to linux in Ubuntu.
When booting up Ubuntu 25.10 with kernel 6.17.0-12-generic on a HP
B4HN8UA (Laptop 15-fd0127dx) the boot hangs up with the following error
messages:
skl_hda_dsp_generic skl_hda_generic: ASoC: Parent card not yet available, widget card binding deferred
skl_hda_dsp_generic skl_hda_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
Bluetooth: hci0: Malformed MSFT vendor event: 0x00
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCD.EC0._Q20.PNOT], AE_NOT_FOUND (20250404/psargs-332)
No Local Variables are initialized for Method [_Q20]
No Arguments are initialized for method [_Q20]
ACPI Error: Aborting method \_SB.PC00.LPCD.EC0._Q20 due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
These ACPI BIOS errors don't occur when booting kernel 6.17.0-7-generic.
I updated the BIOS from F.20 to F.24 to see that would help, but it
didn't.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
6.17.0-12-generic Boot Hangs
https://bugs.launchpad.net/bugs/2141212
You received this bug notification because you are subscribed to linux in Ubuntu.
суббота
[Bug 2141203] Re: kernel panic after upgrade to linux kernel 6.17.0-14-generic
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
New
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141203
Title:
kernel panic after upgrade to linux kernel 6.17.0-14-generic
Status in linux package in Ubuntu:
New
Bug description:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel
panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor
fs on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141203/+subscriptions
[Bug 2141203] [NEW] kernel panic after upgrade to linux kernel 6.17.0-14-generic
You have been subscribed to a public bug:
After boot on linux kernel 6.17.0-14-generic, I got linux kernel panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor fs
on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug dist-upgrade noble wayland-session
--
kernel panic after upgrade to linux kernel 6.17.0-14-generic
https://bugs.launchpad.net/bugs/2141203
You received this bug notification because you are subscribed to linux in Ubuntu.
After boot on linux kernel 6.17.0-14-generic, I got linux kernel panic:
Kerlen panic! Please reboot your computer. VFS: Unable to mount roor fs
on unknown-block(0,0).
When I boot older version 6.14.0-37-generic (from which I report this
issue), all works fine.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.28
ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-37-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
640:0:125:43960:2026-02-06 09:11:11.651818513 +0100:2026-02-06 09:11:12.651818513 +0100:/var/crash/virtualbox-dkms.0.crash
640:125:125:245621:2026-02-07 20:54:08.530334422 +0100:2026-02-07 20:54:05.008334214 +0100:/var/crash/_usr_lib_snapd_snap-seccomp.125.crash
600:0:125:185474:2026-02-06 09:10:34.075934410 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-generic-hwe-24.04.0.crash
600:0:125:184744:2026-02-06 09:10:34.054041147 +0100:2026-02-06 10:14:05.212289660 +0100:/var/crash/linux-headers-generic-hwe-24.04.0.crash
600:0:125:183749:2026-02-06 09:10:31.168778657 +0100:2026-02-06 10:14:05.202289652 +0100:/var/crash/linux-headers-6.17.0-14-generic.0.crash
CurrentDesktop: GNOME
Date: Sat Feb 7 21:34:48 2026
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-01-12 (1852 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeApttermlog: Error: [Errno 13] Operace zamítnuta: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug dist-upgrade noble wayland-session
--
kernel panic after upgrade to linux kernel 6.17.0-14-generic
https://bugs.launchpad.net/bugs/2141203
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2132119] Re: [HP][ZBook Power 16 G11] Laptop freezed after upgrading the BIOS
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132119
Title:
[HP][ZBook Power 16 G11] Laptop freezed after upgrading the BIOS
Status in linux package in Ubuntu:
Expired
Bug description:
Hi team,
I experienced a serious bug on my laptop after upgrading a new BIOS with firmware-updater application. The details are:
Environment:
Laptop: HP ZBook Power 16 inch G11
OS ver: Ubuntu 24.04.3
BIOS Information
Vendor: HP
Version: W97 Ver. 01.07.01
Release Date: 09/24/2025
Kernel: 6.17.0-1005-oem
DE: GNOME
Problem description:
My laptop is working well with the previous BIOS with ver: 01.06.01.
However, a notification says there's a new BIOS release and suggests
upgrading. After the upgrade, reboot the laptop, works as usual. But,
it can't reboot or shutdown, it remains freezing after exection the
commands. By entering the text model I can see the logs as below:
2025-11-20T20:28:08.362397+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362397+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362398+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362399+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362399+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362400+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362401+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362401+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362402+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362402+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362403+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362404+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362404+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362405+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362406+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362406+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362407+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362408+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362408+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362409+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362414+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362415+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362415+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362416+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.363396+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.363405+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.363407+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.363407+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
I have to do a hard reset to shut down. By searching on Google, the issue is caused by the Realtek SD card reader driver. The temp fix is to add a 'pcie_aspm=off' parameter in the GRUB CMDLINE. Then, it's working.
Can you help check the issue? Firmware or Kernel?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2132119/+subscriptions
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132119
Title:
[HP][ZBook Power 16 G11] Laptop freezed after upgrading the BIOS
Status in linux package in Ubuntu:
Expired
Bug description:
Hi team,
I experienced a serious bug on my laptop after upgrading a new BIOS with firmware-updater application. The details are:
Environment:
Laptop: HP ZBook Power 16 inch G11
OS ver: Ubuntu 24.04.3
BIOS Information
Vendor: HP
Version: W97 Ver. 01.07.01
Release Date: 09/24/2025
Kernel: 6.17.0-1005-oem
DE: GNOME
Problem description:
My laptop is working well with the previous BIOS with ver: 01.06.01.
However, a notification says there's a new BIOS release and suggests
upgrading. After the upgrade, reboot the laptop, works as usual. But,
it can't reboot or shutdown, it remains freezing after exection the
commands. By entering the text model I can see the logs as below:
2025-11-20T20:28:08.362397+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362397+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362398+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362399+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362399+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362400+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362401+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362401+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362402+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362402+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362403+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362404+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362404+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362405+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362406+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362406+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362407+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362408+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362408+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362409+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.362414+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.362415+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.362415+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.362416+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
2025-11-20T20:28:08.363396+08:00 zbook-g11 kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:56:00.0
2025-11-20T20:28:08.363405+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-11-20T20:28:08.363407+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: device [10ec:525a] error status/mask=00001000/00006000
2025-11-20T20:28:08.363407+08:00 zbook-g11 kernel: rtsx_pci 0000:56:00.0: [12] Timeout
I have to do a hard reset to shut down. By searching on Google, the issue is caused by the Realtek SD card reader driver. The temp fix is to add a 'pcie_aspm=off' parameter in the GRUB CMDLINE. Then, it's working.
Can you help check the issue? Firmware or Kernel?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2132119/+subscriptions
Подписаться на:
Комментарии (Atom)