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/2127764
Title:
Boot up hang with ucsi call trace while plug power cord or device 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 Plucky:
Won't Fix
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
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]
Boot up process may stuck with the ucsi cod trace
<4>[ 15.117180] workqueue: cannot queue ucsi_poll_worker [typec_ucsi] on wq USBC000:00-con1
<4>[ 15.117196] WARNING: CPU: 14 PID: 0 at kernel/workqueue.c:2257 __queue_work+0x2f3/0x410
<4>[ 15.117205] Modules linked in: qrtr_mhi snd_seq_dummy snd_hrtimer rfcomm snd_soc_cs42l43 spi_cs42l43 snd_soc_cs42l43_sdw pinctrl_cs42l43 snd_soc_sof_sdw snd_soc_intel_hda_dsp_common snd_soc_sdw_utils snd_sof_probes xe snd_soc_cs35l56_sdw snd_soc_cs35l56 snd_soc_wm_adsp gpu_sched snd_soc_cs35l56_shared cs42l43_sdw snd_soc_cs_amp_lib regmap_sdw drm_gpuvm cs_dsp cs42l43 drm_ttm_helper drm_exec drm_suballoc_helper snd_soc_dmic snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel soundwire_cadence snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi qrtr snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_frequency intel_uncore_frequency_common snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp soundwire_bus cmac snd_soc_sdca coretemp algif_hash snd_soc_core algif_skcipher snd_compress ac97_bus af_alg snd_pcm_dmaengine bnep snd_hda_intel
<4>[ 15.117256] snd_intel_dspcfg dell_pc kvm_intel platform_profile snd_ctl_led snd_intel_sdw_acpi iwlmvm snd_hda_codec i915 kvm snd_hda_core mac80211 snd_hwdep snd_pcm irqbypass polyval_clmulni libarc4 snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel uvcvideo sha256_ssse3 snd_rawmidi dell_laptop sha1_ssse3 videobuf2_vmalloc aesni_intel uvc videobuf2_memops snd_seq btusb binfmt_misc videobuf2_v4l2 cmdlinepart crypto_simd drm_buddy dell_wmi videobuf2_common btrtl cryptd dell_smbios snd_seq_device spi_nor ttm btintel mtd mei_gsc_proxy intel_rapl_msr iwlwifi btbcm processor_thermal_device_pci videodev drm_display_helper snd_timer i2c_i801 btmtk processor_thermal_device dcdbas rapl nls_iso8859_1 dell_wmi_sysman intel_cstate processor_thermal_wt_hint snd cec i2c_smbus spi_intel_pci bluetooth cfg80211 mc dell_wmi_ddv dell_smm_hwmon qaic firmware_attributes_class processor_thermal_rfim dell_wmi_descriptor wmi_bmof soundcore spi_intel i2c_mux processor_thermal_rapl mei_me mhi intel_rapl_common intel_vpu
<4>[ 15.117319] rc_core mei processor_thermal_wt_req processor_thermal_power_floor i2c_algo_bit processor_thermal_mbox int3403_thermal intel_pmc_core dptf_pch_fivr int340x_thermal_zone pmt_telemetry pmt_class int3400_thermal intel_hid acpi_pad acpi_thermal_rel sparse_keymap acpi_tad intel_vsec input_leds joydev mac_hid serio_raw sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_multitouch hid_generic nvme rtsx_pci_sdmmc i2c_hid_acpi ucsi_acpi video intel_lpss_pci psmouse i2c_hid typec_ucsi nvme_core intel_ish_ipc intel_lpss igc thunderbolt rtsx_pci intel_ishtp idma64 hid typec nvme_auth wmi pinctrl_meteorlake pinctrl_meteorpoint
<4>[ 15.117366] CPU: 14 UID: 0 PID: 0 Comm: swapper/14 Not tainted 6.14.0-8011-oem #11+staging.12-Ubuntu
<4>[ 15.117370] Hardware name: Dell Inc. Dell Pro Max 16 Plus MB16250/, BIOS 89.71.16 07/29/2025
<4>[ 15.117372] RIP: 0010:__queue_work+0x2f3/0x410
<4>[ 15.117376] Code: 00 00 41 83 e4 01 0f 85 49 fe ff ff 49 8b 77 18 48 8d 93 c0 00 00 00 48 c7 c7 60 22 9f 95 c6 05 06 21 66 02 01 e8 7d 19 fd ff <0f> 0b e9 24 fe ff ff 0f 0b e9 10 fe ff ff 65 8b 05 04 14 e8 6b 48
<4>[ 15.117378] RSP: 0018:ffffcc2c805d8c98 EFLAGS: 00010046
<4>[ 15.117381] RAX: 0000000000000000 RBX: ffff8aa282eac200 RCX: 0000000000000000
<4>[ 15.117383] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
<4>[ 15.117384] RBP: ffffcc2c805d8cd0 R08: 0000000000000000 R09: 0000000000000000
<4>[ 15.117386] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
<4>[ 15.117387] R13: ffffffff941b5420 R14: ffff8aa283b33220 R15: ffff8aa283b33200
<4>[ 15.117388] FS: 0000000000000000(0000) GS:ffff8ac19ff00000(0000) knlGS:0000000000000000
<4>[ 15.117390] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[ 15.117392] CR2: 000078c0c11c5000 CR3: 000000010203f002 CR4: 0000000000f72ef0
<4>[ 15.117394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4>[ 15.117395] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
<4>[ 15.117396] PKRU: 55555554
<4>[ 15.117397] Call Trace:
<4>[ 15.117400] <IRQ>
<4>[ 15.117403] ? __pfx_delayed_work_timer_fn+0x10/0x10
<4>[ 15.117408] delayed_work_timer_fn+0x19/0x30
<4>[ 15.117411] call_timer_fn+0x2c/0x150
<4>[ 15.117414] ? __pfx_delayed_work_timer_fn+0x10/0x10
<4>[ 15.117417] __run_timers+0x1c8/0x2d0
<4>[ 15.117420] timer_expire_remote+0x52/0x80
<4>[ 15.117422] tmigr_handle_remote_cpu+0x11e/0x280
<4>[ 15.117427] tmigr_handle_remote_up+0xf1/0x140
<4>[ 15.117430] tmigr_handle_remote+0xd9/0x140
<4>[ 15.117433] run_timer_softirq+0xeb/0x100
<4>[ 15.117435] handle_softirqs+0xe4/0x340
<4>[ 15.117440] __irq_exit_rcu+0x10e/0x130
<4>[ 15.117444] irq_exit_rcu+0xe/0x20
<4>[ 15.117446] sysvec_apic_timer_interrupt+0xa0/0xc0
<4>[ 15.117450] </IRQ>
<4>[ 15.117451] <TASK>
<4>[ 15.117452] asm_sysvec_apic_timer_interrupt+0x1b/0x20
[Fix]
We submit a patch to fix this issue
https://lkml.org/lkml/2025/10/2/100
v2 - https://lkml.org/lkml/2025/10/13/312
v3 - https://lkml.org/lkml/2025/10/17/338
v4 - https://lore.kernel.org/lkml/20251218071925.3459787-1-acelan.kao@canonical.com/
[Test]
Reboot the machine with AC plug on the TBT5 port, it should always boots up correctly without call trace.
[Where problems could occur]
It should handle the destruction process correctly, and is not likely to introduce regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2127764/+subscriptions
Комментариев нет:
Отправить комментарий