суббота

[Bug 2127960] Re: Ease the sysfs call trace which comes from ucsi firmware issue

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: Fix Committed => Fix Released

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2127960

Title:
Ease the sysfs call trace which comes from ucsi firmware issue

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:
Won't Fix
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:
In Progress
Status in linux-oem-6.14 source package in Questing:
New
Status in linux-oem-6.17 source package in Questing:
New
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]
We'll see this call trace while plugged tbt device

Sep 24 13:24:22 ubuntu-202504-36599 kernel: sysfs: cannot create duplicate filename '/devices/platform/USBC000:00/typec/port0/port0.0/partner'
Sep 24 13:24:22 ubuntu-202504-36599 kernel: CPU: 1 UID: 0 PID: 132 Comm: kworker/u64:1 Tainted: G O 6.14.0-1012-oem #12-Ubuntu
Sep 24 13:24:22 ubuntu-202504-36599 kernel: Tainted: [O]=OOT_MODULE
Sep 24 13:24:22 ubuntu-202504-36599 kernel: Hardware name: Dell Inc. /, BIOS x.x.x xx/xx/2025
Sep 24 13:24:22 ubuntu-202504-36599 kernel: Workqueue: USBC000:00-con1 ucsi_poll_worker [typec_ucsi]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: Call Trace:
Sep 24 13:24:22 ubuntu-202504-36599 kernel: <TASK>
Sep 24 13:24:22 ubuntu-202504-36599 kernel: dump_stack_lvl+0x76/0xa0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: dump_stack+0x10/0x20
Sep 24 13:24:22 ubuntu-202504-36599 kernel: sysfs_warn_dup+0x8a/0xb0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: sysfs_do_create_link_sd+0xf1/0x100
Sep 24 13:24:22 ubuntu-202504-36599 kernel: sysfs_create_link+0x21/0x50
Sep 24 13:24:22 ubuntu-202504-36599 kernel: typec_probe+0x7e/0x100 [typec]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ? driver_sysfs_add+0x66/0xd0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: really_probe+0xee/0x3c0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: __driver_probe_device+0x8c/0x180
Sep 24 13:24:22 ubuntu-202504-36599 kernel: driver_probe_device+0x24/0xd0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: __device_attach_driver+0xcd/0x170
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ? _pfx__device_attach_driver+0x10/0x10
Sep 24 13:24:22 ubuntu-202504-36599 kernel: bus_for_each_drv+0x94/0xf0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: __device_attach+0xb6/0x1d0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: device_initial_probe+0x13/0x20
Sep 24 13:24:22 ubuntu-202504-36599 kernel: bus_probe_device+0x9f/0xb0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: device_add+0x513/0x710
Sep 24 13:24:22 ubuntu-202504-36599 kernel: device_register+0x1a/0x30
Sep 24 13:24:22 ubuntu-202504-36599 kernel: typec_register_altmode+0x253/0x3a0 [typec]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: typec_partner_register_altmode+0xe/0x20 [typec]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ucsi_register_altmode.constprop.0+0x30e/0x390 [typec_ucsi]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ucsi_register_altmodes+0x162/0x250 [typec_ucsi]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ucsi_check_altmodes+0x19/0xb0 [typec_ucsi]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ucsi_poll_worker+0x3d/0xf0 [typec_ucsi]
Sep 24 13:24:22 ubuntu-202504-36599 kernel: process_one_work+0x178/0x3d0
Sep 24 13:24:22 ubuntu-202504-36599 kernel: worker_thread+0x2de/0x410
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ? __pfx_worker_thread+0x10/0x10
Sep 24 13:24:22 ubuntu-202504-36599 kernel: kthread+0xfb/0x230
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ? __pfx_kthread+0x10/0x10
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ret_from_fork+0x44/0x70
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ? __pfx_kthread+0x10/0x10
Sep 24 13:24:22 ubuntu-202504-36599 kernel: ret_from_fork_asm+0x1a/0x30
Sep 24 13:24:22 ubuntu-202504-36599 kernel: </TASK>
Sep 24 13:24:22 ubuntu-202504-36599 kernel: typec-thunderbolt port0-partner.1: failed to create symlinks
Sep 24 13:24:22 ubuntu-202504-36599 kernel: typec-thunderbolt port0-partner.1: probe with driver typec-thunderbolt failed with error -17

[Fix]
The patch ease the call trace and only shows the firmware bug warning in the log
https://lkml.org/lkml/2025/10/16/154
v3 - https://lore.kernel.org/lkml/20251224070022.4082182-1-acelan.kao@canonical.com/

[Test]
Boot up the machine which shows the same call trace after booted up, the call trace should be replaced by something like this
   ucsi_acpi USBC000:00: con0: Firmware bug: duplicate partner altmode SVID 0x8087 at offset 1, ignoring. Please update your system firmware.

[Where problems could occur]
It doesn't affect functionalities, just detect the duplicated modes and skip it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2127960/+subscriptions

Комментариев нет:

Отправить комментарий