This bug was fixed in the package linux - 6.19.0-3.3
---------------
linux (6.19.0-3.3) resolute; urgency=medium
* resolute/linux: 6.19.0-3.3 -proposed tracker (LP: #2138935)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(main/d2026.01.12)
- [Packaging] update variants
* [26.04] Please test secureboot and lock-down with 6.18 kernel (s390x) on
Resolute Raccoon (LP: #2131805)
- SAUCE: s390/boot/vmlinux.lds.S: Ensure bzImage ends with SecureBoot
trailer
* unconfined profile denies userns_create for chromium based processes
- [Config] disable CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS
* update apparmor and LSM stacking patch set
- SAUCE: apparmor5.0.0 [1/53]: Stacking: LSM: Single calls in secid hooks
- SAUCE: apparmor5.0.0 [2/53]: Stacking: LSM: Exclusive secmark usage
- SAUCE: apparmor5.0.0 [3/53]: Stacking: Audit: Call only the first of the
audit rule hooks
- SAUCE: apparmor5.0.0 [4/53]: Stacking: AppArmor: Remove the exclusive
flag
- SAUCE: apparmor5.0.0 [5/53]: apparmor-next 7.0: apparmor: replace
sprintf with snprintf in aa_new_learning_profile
- SAUCE: apparmor5.0.0 [6/53]: apparmor-next 7.0: apparmor: Replace
sprintf/strcpy with scnprintf/strscpy in aa_policy_init
- SAUCE: apparmor5.0.0 [7/53]: apparmor-next 7.0: apparmor: Replace
deprecated strcpy in d_namespace_path
- SAUCE: apparmor5.0.0 [8/53]: apparmor-next 7.0: apparmor: fix NULL
pointer dereference in __unix_needs_revalidation
- SAUCE: apparmor5.0.0 [9/53]: apparmor-next 7.0: apparmor: fix NULL sock
in aa_sock_file_perm
- SAUCE: apparmor5.0.0 [10/53]: apparmor-next 7.0: apparmor: Replace
deprecated strcpy with memcpy in gen_symlink_name
- SAUCE: apparmor5.0.0 [11/53]: apparmor-next 7.0: AppArmor: Allow
apparmor to handle unaligned dfa tables
- SAUCE: apparmor5.0.0 [12/53]: apparmor-next 7.0: apparmor: Fix &
Optimize table creation from possibly unaligned memory
- SAUCE: apparmor5.0.0 [13/53]: apparmor-next 7.0: apparmor: make str
table more generic and be able to have multiple entries
- SAUCE: apparmor5.0.0 [14/53]: apparmor-next 7.0: apparmor: add support
loading per permission tagging
- SAUCE: apparmor5.0.0 [15/53]: apparmor-next 7.0: aoparmor: userns: Add
support for execpath in userns
- SAUCE: apparmor5.0.0 [16/53]: apparmor-next 7.0: apparmor: fix boolean
argument in apparmor_mmap_file
- SAUCE: apparmor5.0.0 [17/53]: apparmor-next 7.0: apparmor: drop
in_atomic flag in common_mmap, and common_file_perm
- SAUCE: apparmor5.0.0 [18/53]: apparmor-next 7.0: apparmor: account for
in_atomic removal in common_file_perm
- SAUCE: apparmor5.0.0 [19/53]: apparmor-next 7.0: apparmor: return
-ENOMEM in unpack_perms_table upon alloc failure
- SAUCE: apparmor5.0.0 [20/53]: apparmor-next 7.0: apparmor: guard against
free routines being called with a NULL
- SAUCE: apparmor5.0.0 [21/53]: apparmor-next 7.0: apparmor: move check
for aa_null file to cover all cases
- SAUCE: apparmor5.0.0 [22/53]: apparmor-next 7.0: apparmor: fix label and
profile debug macros
- SAUCE: apparmor5.0.0 [23/53]: apparmor-next 7.0: apparmor:
refactor/cleanup cred helper fns.
- SAUCE: apparmor5.0.0 [24/53]: apparmor-next 7.0: apparmor: fix rlimit
for posix cpu timers
- SAUCE: apparmor5.0.0 [25/53]: apparmor-next 7.0: apparmor: fix fast path
cache check for unix sockets
- SAUCE: apparmor5.0.0 [26/53]: apparmor-next 7.0: apparmor: remove
apply_modes_to_perms from label_match
- SAUCE: apparmor5.0.0 [27/53]: apparmor-next 7.0: apparmor: make
label_match return a consistent value
- SAUCE: apparmor5.0.0 [28/53]: apparmor-next 7.0: apparmor: split
xxx_in_ns into its two separate semantic use cases
- SAUCE: apparmor5.0.0 [29/53]: apparmor-next 7.0: apparmor: avoid per-cpu
hold underflow in aa_get_buffer
- SAUCE: apparmor5.0.0 [30/53]: Revert "apparmor: fix dbus permission
queries to v9 ABI"
- SAUCE: apparmor5.0.0 [31/53]: Revert "apparmor: gate make fine grained
unix mediation behind v9 abi"
- SAUCE: apparmor5.0.0 [32/53]: apparmor: net: patch to provide
compatibility with v2.x net rules
- SAUCE: apparmor5.0.0 [33/53]: apparmor: net: add fine grained ipv4/ipv6
mediation
- SAUCE: apparmor5.0.0 [34/53]: apparmor: lift compatibility check out of
profile_af_perm
- SAUCE: apparmor5.0.0 [35/53]: apparmor: userns: add unprivileged user ns
mediation
- SAUCE: apparmor5.0.0 [36/53]: apparmor: userns: Add sysctls for
additional controls of unpriv userns restrictions
- SAUCE: apparmor5.0.0 [37/53]: apparmor: userns - make it so special
unconfined profiles can mediate user namespaces
- SAUCE: apparmor5.0.0 [38/53]: apparmor: userns: open userns related
sysctl so lxc can check if restriction are in place
- SAUCE: apparmor5.0.0 [39/53]: apparmor: userns: allow profile to be
transitioned when a userns is created
- SAUCE: apparmor5.0.0 [40/53]: apparmor: mqueue: call
security_inode_init_security on inode creation
- SAUCE: apparmor5.0.0 [41/53]: apparmor: mqueue: add fine grained
mediation of posix mqueues
- SAUCE: apparmor5.0.0 [42/53]: apparmor: uring: add io_uring mediation
- SAUCE: apparmor5.0.0 [43/53]: apparmor: create an
AA_SFS_TYPE_BOOLEAN_INTPRINT sysctl variant
- SAUCE: apparmor5.0.0 [44/53]: apparmor: Use AA_SFS_FILE_BOOLEAN_INTPRINT
for userns and io_uring sysctls
- SAUCE: apparmor5.0.0 [45/53]: apparmor: prompt: setup slab cache for
audit data
- SAUCE: apparmor5.0.0 [46/53]: apparmor: prompt: add the ability for
profiles to have a learning cache
- SAUCE: apparmor5.0.0 [47/53]: apparmor: prompt: enable userspace upcall
for mediation
- SAUCE: apparmor5.0.0 [48/53]: apparmor: prompt: pass prompt boolean
through into path_name as well
- SAUCE: apparmor5.0.0 [49/53]: apparmor: check for supported version in
notification messages.
- SAUCE: apparmor5.0.0 [50/53]: apparmor: refactor building notice so it
is easier to extend
- SAUCE: apparmor5.0.0 [51/53]: apparmor: switch from ENOTSUPP to
EPROTONOSUPPORT
- SAUCE: apparmor5.0.0 [52/53]: apparmor: add support for meta data tags
- SAUCE: apparmor5.0.0 [53/53]: apparmor: prevent profile->disconnected
double free in aa_free_profile
* Blacklisted sbsa_gwdt module makes machines reboot (LP: #2138924)
- [Packaging] remove sbsa_gwdt from watchdog blacklist
* Integrate IgH EtherCAT master (LP: #2138621)
- SAUCE: ubuntu/igh-ecat: Import IgH EtherCAT master
- SAUCE: igh-ecat: Plug IgH EtherCAT master into Kbuild
- SAUCE: igh-ecat: Fix build failure with kernel 6.19
- [Config] Enable IgH EtherCAT master
* TBT call trace while connecting TBT4 monitor on TBT5 port (LP: #2137613)
- SAUCE: thunderbolt: log path activation failures without WARN backtraces
* Boot up hang with ucsi call trace while plug power cord or device on tbt5
port (LP: #2127764)
- SAUCE: usb: typec: ucsi: Fix workqueue destruction race during connector
cleanup
* Ease the sysfs call trace which comes from ucsi firmware issue
(LP: #2127960)
- usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware
- usb: typec: ucsi: Add duplicate detection to nvidia registration path
- usb: typec: ucsi: yoga_c630: Remove redundant duplicate altmode handling
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Enable RTL ASPM for new Dell platforms (LP: #2121200)
- SAUCE: r8169: enable ASPM on all new Dell platforms
* Miscellaneous Ubuntu changes
- [Packaging] Bump clang build-dep to match the current default.
- [Config] updateconfig after rebase to v6.19-rc6
- [Packaging] update Ubuntu.md
-- Timo Aaltonen <timo.aaltonen@canonical.com> Fri, 23 Jan 2026
17:50:01 +0200
** Changed in: linux (Ubuntu Resolute)
Status: In Progress => 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/2137613
Title:
TBT call trace while connecting TBT4 monitor on TBT5 port
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Committed
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
When connecting Thunderbolt devices (especially monitors like Dell
U2725QE), users see alarming kernel backtraces in dmesg during device
enumeration. While the devices eventually work after automatic
reconnection, the call traces cause user concern and can trigger
automated bug reporting tools.
Error log example:
```
[ 36.031530] thunderbolt 0000:c7:00.6: PCIe Down path activation failed
[ 36.031531] WARNING: drivers/thunderbolt/path.c:589 at 0x0, CPU#12: pool-/usr/libex/3145
[ 36.031605] CPU: 12 UID: 0 PID: 3145 Comm: pool-/usr/libex Tainted: G D W 6.18.0+ #8
[ 36.031610] RIP: 0010:tb_path_activate+0x126/0x530 [thunderbolt]
[ 36.031637] Call Trace:
[ 36.031638] <TASK>
...
```
The issue occurs when:
- Type-C connections have transient electrical issues
- During lane bonding transitions (single lane to dual lane)
- The Thunderbolt port's control channel is temporarily unavailable
The devices typically recover automatically within a few seconds and
work normally, but the kernel backtrace (tb_WARN) is generated
unnecessarily for these expected transient conditions.
Affected hardware:
- Dell U2725QE Thunderbolt monitor (USB4 device 8087:b26)
- Other Thunderbolt/USB4 devices experiencing similar transient connection issues
- AMD and Intel Thunderbolt controllers
[Fix]
Modify tb_path_activate() in drivers/thunderbolt/path.c to
differentiate between expected transient failures and actual errors:
- For -ENOTCONN errors: Use tb_warn() to log the error without generating a kernel backtrace
- For all other errors: Keep tb_WARN() to generate the full call trace for debugging
This approach aligns with the existing comment in
drivers/thunderbolt/ctl.c which states that
TB_CFG_ERROR_PORT_NOT_CONNECTED "can happen during surprise removal"
and we should "not warn" about it.
The fix does not suppress the warning message itself - users and
developers can still see the path activation failure in dmesg. It only
removes the unnecessary kernel backtrace (stack dump, register dump,
etc.) for this specific expected transient condition.
Patch:
https://lore.kernel.org/lkml/20260102031905.27416-1-acelan.kao@canonical.com/T/#u
("thunderbolt: Suppress call trace for transient -ENOTCONN errors
during path activation")
[Test Plan]
Hardware needed:
- Dell U2725QE Thunderbolt monitor or similar Thunderbolt device that exhibits transient connection issues
- System with Thunderbolt 3/4 or USB4 controller
Test steps:
```bash
# Clear dmesg
sudo dmesg -C
# Connect Dell U2725QE or similar Thunderbolt device
# Wait 10 seconds
# Check for call traces
dmesg | grep -A 30 "path activation failed"
```
Without the patch: A full kernel backtrace appears with WARNING, RIP,
Call Trace, register dump, etc.
With the patch: Only a simple warning message appears without the backtrace:
```
thunderbolt 0000:c7:00.6: PCIe Down path activation failed (port not connected)
```
[Where problems could occur]
The patch modifies error reporting in the Thunderbolt path activation
code, which could affect debugging and error handling:
1. **Thunderbolt subsystem**: If there are genuine bugs that manifest
as -ENOTCONN errors (not just transient issues), developers might miss
important debugging information because the full backtrace won't be
generated. This would make it harder to diagnose actual Thunderbolt
controller bugs or firmware issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2137613/+subscriptions
Комментариев нет:
Отправить комментарий